[Therion DNA75 SS316L Issues]

Spirometry said:

You are fighting refinement. The cold resistance between your first post and 2nd post are pretty far apart. Always mate a cold atomizer with a cold Mod. It is even better if you set the mod down for about 20 minutes afterwards(after the new coil prompt).

Wait for refinement before settling on a temperature to vape at. Don't set your temperature at 455° then try to force your mod to vape at that temperature. With the tank you have and the power you have it set at, I probably would have it set between 480 and 520.

The DNA won't remember the cold resistance when removing the battery unless you have the resistance locked in. Replace the batteries one at a time so you don't loose power to the board.

Could you elaborate on waiting to set the temp? I usually vape around 390-410ish, should i start lower and work up to it?

[SS 316L coil with DNA200 board Problems]

BillW50 said:

Have you tried EScribe v1.2 SP3 yet? They say it really helps with SS problems.

I have not, but I will. Thanks!

[SS 316L coil with DNA200 board Problems]

Scy123 said:

I turned off preheat cause it was recommended somewhere for SS. I have not tried locking the res but, will do it later. I doubt it is a connection issue cause when it happens it keeps happening all the time with any tank until I remove the batteries and restart the device. Also the cold ohms read the same so if it shifted it is not displaying it.

I will play around with it a bit and report back later with pics and such.

I know this is old, but dod you figure anything out? I'm having the same problems.

[Therion DNA75 SS316L Issues]

goldfish18 said:

 
The picture above also happens (it's currently doing this). It's showing that it is reaching my set temperature, but producing little to no vapor at all. What the hell is going on? I've also found that if I take both batteries out then put them back in, it kind of resets itself and works again for a while then goes back to performing crappy.

It looks like Escribe bumped me back down to the 2016-05-02 firmware. Any idea why it would do that? If you look at the pictures I posted in the original post it shows the 2016-06-05. Really weird!

Have you figured anything out? I'm fighting the exact same thing, and it is super frustrating.