druckle

I've occasionally had these same issues and it has always been a windows problem with respect to how USB drivers/devices are detected. My solution so far is to shut down the machine with the DNA device connected and reboot. Proper detection of all USB drivers and devices sometimes seems to take a long time so I pour a cup of coffee and chill or do some useful work elsewhere. So far this simple solution has not failed me. It's an inconvenience but apparently one just has to let Windows be Windows.

The titanium temperature coefficient of resistance is basically a straight line in the temperature region of interest for vaping. The steam engine .csv is working fine for me.

The high resistance with firm attachment of the atomizer appears to be consistent for 4 different atomizers I've tried. Two subtank mini's, an origen dripper and a manta dripper. I'll explore more but I'm having the resistance jump around even in locked mode. I assume it may be a mechanical contact problem within the devices 510 connector.

John: I will go back to earlier firmware than 7/16 but when I've run with 7/9 or 7/16 I still get much higher ohms readings and always have the problem that temp is not showing up in Escribe most of the time. I'm not sure that I'm getting any temp limiting at all. I'll try a dry coil to be sure on that. In the meantime I'm wondering if I have a hardware problem. It's beginning to look like a hardware problem to me. Any other suggestions?

John: As you suggested: I went back to 7/14 firmware and again no temp readout in Device Monitor no positive response from a hard boot but with a single try that is not unusual for this mod. Sometimes multiple hard boots are required to get the temp trace to show up and even then it's not permanent if the device sits idle for an hour or so. I then loaded 7/9 firmware and again no temp trace in Device Monitor before or after a single hard boot.

John: OK will do.

John: The resistance reading is stable in the tightness range where I normally tighten an atty but if I crank it down really hard the resistance rises from ~0.37 ohms to the 0.47-.05 ohm range. The atty is a Kanger Subtank Mini that is stable on other devices and the ohm meter where it reads o.3 ohms. This is a Evolv Beta box sent by Brandon and the center pin moves when depressed by a bamboo skewer. l also cleaned both the atty 510 and the beta box 510 with alcohol and dried it prior to doing the Atomizer Analyzer eval. I checked in Device monitor at several points as I tightened and loosened the atomizer and there was never a temperature trace being shown. I did not try hard rebooting which is almost always required to get the Device Monitor to show the temperature trace.

John. Forgot to mention this was the 0.3 ohm build and I can feel the connector center pin move when I depress it with a toothpick although of course it's tight as it should be.

John: It's stable unless within the normal range that I tighten the attys but if you crank it down really hard the apparent resistance rises from the .37 range to .47-.5. I checked the Device Monitor at several points and there was never an indication of a temperature curve during a puff.

John: As requested....Atomizer Analyzer shot of cold atomizer.

The primary attomizers used on the DNA 200 are Kanger subtank mini's although I've also checked the same parameters with original (non clone) Origen and Manta drippers).

John: I just put on a NI 200 coil with unlocked resistance. Resistance is shown as 0.17 oms...That also does not show a temp trace in Device Monitor

John: I locked the ohms then put on a different atty that mesures 0.3 ohms on a dna 40 and on my ohm meter. The DNA 200 asked if it was a new coil and I said yes (of course). The DNA 200 shows the resistance at 0.445 ohms. Unlocked the resistance and put on a tank that measures 0.2 ohms on the ohm meter. The DNA 200 shows resistance of 0.390 ohms. None of these attys are showing a temp curve in Device Monitor.

John: Yes, the reference resistance does change with ohm lock on. I first tired to lock ohms to see if that was related to the problem. I'll go check that again just to confirm. I'm pretty sure it's not a problem with the coil or 510 since the same tank gives stable resistance on other devices and I've checked it multiple times on an ohm meter two dna 40's and two SX M's and found no resistance floating. I'll get back to you asap after checking ohm lock again.

John: I posted a screen shot earlier showing the temp not showing up in escribe during a puff. After multiple hard boots I managed to get the temp to show up normally and then left the device to sit on the desk for over an hour with no activity. Now I get the following behavior....temp shows up but definitely NOT normal. I'd appreciate your help/recommendations.

John: I'm using titanium grade 1 wire with Steam Engine l.csv on profile 2. This is an example of the missing temp data during a fire. If I set up on Profile 1 (Ni 200) with the max temp set at 300 as an example) I also get the same lack of temp data being displayed. I also seem to be getting erratic resistance readings quite often.

Sometimes temperature data is not showing up in device monitor during a puff. A hard boot sometimes restores the ability for temperature to be displayed, but sometimes not. Is this normal behavior? Is there a way to assure that device monitor does actively display temperature?

I don't understand the difference between Sample Ohms and Sample Ohms (TC). Is there anything written that explains the debug values...Including bandgap? I'm just learning obviously.

DUH.....pretty obvious when you think about it. Obviously I didn't.

Does the Escribe program allow a user to save the full data for an individual profile to a file on the computer? I ask because I had entered the Steam Engine csv data for Grade 1 titanium as profile 2 and then in playing with the software did a "restore defaults" command at a later time. Apparently "restore defaults" put the sample RST data back in the profile 2. It took a while for me to realize that the data was incorrect after my "restore defaults" command because I hadn't expected custom data to be changed since I didn't think custom data would be considered default data. The vape had become wonky and I didn't think about the changed RST data. If I am correct that the software does change all profiles to default values it would be good to have our own saved custom profiles in a file on the computer....or maybe custom profile data shouldn't be changed by a restore defaults command?

False alarm. The issue does not appear to be associated with the new firmware. For whatever reason the resistance appears to detect correctly with a new cold coil but adjusts to higher and higher values. A hard boot and locking the initial resistance appears to make things function OK. Should I address the question in another thread?

i'M seeing a significant resistance measurement "error" since updating to the 7/9 firmware. For example a coil and device combination that measures 0.25 ohms on a precision ohm meter (and on other DNA devices) measures 0.41 ohms on the DNA 200 with the upgraded firmware. I was not seeing this error prior to the firmware upgrade. I am also seeing apparent temperatures that are lower than previously observed. I'd appreciate it if you guys could check this. I assume it's not just my DNA 200 device but if it is I'd like to chase down the cause of the error.

Would it be possible to add the option of charging high performance batteries like the Hyperion G6 (4.35V)? Possibly a warning note could be added to assure that inappropriate V would not be selected for standard Lipo's.