BillW50

No retird, saving a ecig file, disconnecting and unplugging the USB, change batteries, reconnect USB and upload ecig file to device, the puff counter still jumps back. Although just having USB power and changing batteries, puff counter behaves correctly.

Nope, I haven't cracked it open yet and I probably don't have a lot of time tomorrow to do much either. But I wouldn't be surprised I'll find what others have found. That all the voltages are good going into the ADC. And it would be a good guess that some gate or amp opened or shorted inside of the chip during the Hard Reboot.

@VapingBad: No, I was talking about all of the people who post here of having the problem of their DNA isn't reading the cell voltages correctly. Sure, I first thought they must have had a bad cell in their lipo. That happens from time to time. But a few of them have digital meters and the lipos are fine, just the DNA isn't reading them correctly. So far, those of us here don't know why that happens. But this time, it happened to me. And it happened during a Hard Reboot with a messed up puff counter. Now if the rest of the other failures also did a Hard Reboot before everything went to hell... well guess what? Maybe nobody should use Hard Reboot until Evolv figures it out. Otherwise they they be receiving more dead DNAs and having more upset customers. I am sure they don't want that. Yes so true about the puff counter is often ignored. I too wouldn't have bothered logging the puff count except I was curious about battery life. And the good news is that the DNA200 wins as far as battery capacity vs. per ml of juice used. I didn't know whether I would need the puff count in this research or not, but the DNA had it so I recorded it. And I know the puff counter works perfectly in TC. I had no idea about wattage mode, since I rarely used it. And as far as blaming the lack of saves... that is minor compared to blown DNA200s. The DNA200 probably uses an A/D converter (ADC) to read the cell voltages and converts it to a digital value. Things were working right (except the puff counter) until a Hard Reboot command was issued. Now it can't even read cell voltages correctly and makes the DNA200 totally useless for most users.

JaI Haze, you didn't cause any problems for me. You opened the door for me to see a huge warning about using Hard Reboot. As under certain conditions it can ruin your DNA200.

@VapingBad: Five of mine were working fine off of 18650 cells in TC. Not one hint of any trouble and I was replacing cells all of the time. JaI Haze has been having this puff counter jumping back for sometime now. Nobody else was seeing it at all. Having sometime today, I spent more time working on this and found out that if you swap batteries in wattage mode, it screws up the puff counter. Fine. Now we know. So I go back to TC and that puff counter is now messed up there too. Fine. Do a Hard Reboot and your DNA200 is now toast. You know how many have DNA200s not reading cells correctly since I have been here? Even those with lipo DNA200? Must be a dozen at least in the last few months. And if all of them failed after doing a Hard Reboot, this is a serious problem! It is a failure related to using wattage mode. Not having neither the source code or the schematics, I could only guess from here. Evolv has to have seen many of these sent back to them by now. And I am sure they know what component is failing. What they may not know is why? Well I believe it is reproducible now. And it will be easy for them to fix. Maybe not existing ones, but at least future ones.

Ok, I think we have a bug that is toasting DNA200s. Getting the puff counter to screw up in wattage mode, it also messed up the puff counter in TC too. Not only does it count back for the reset puffs (what the screen displays), but also the total puff counter in the Device Monitor. Trying to fix the puff counter, I did. 1) Reinstall firmware (no help) 2) Download from device then upload back (no help) 3) Soft Reboot (no help) 4) Hard Reboot - Here caused cell 1 to read zero volts. Error message says check battery when fired (both batteries are 3.65v with multimeter - swapped with two cells which tested as 4.16v each - no help) 5) Restore Defaults (no help) 6) Tried Soft and then Hard Reboot again (no help) 7) Tried reinstall firmware (no help) 8) Fires if power supply selected on 3.65v batteries Is that Hard Reboot sometimes causing the DNA200 to fail reading the cell voltages correctly?

All of mine, Profile 1 is my wattage profile. And Profile 2 is my Ni200 TC profile. And when I remove the cells and put them back in it pops back to Profile 2. I guess you can change which one it defaults to (maybe). Oh crap! I put my nickel coil back in and now it is doing it in TC mode too.

I got it to happen in wattage mode all of the time (on my VT133 1 of 4). I start with 2793 puffs and vape and it counts up. Remove the batteries and put them back in and it resets it back to 2793 every time in wattage mode.

Do you use wattage mode only? As I almost always run in temperature control. I don't think I have ever swapped batteries in wattage (power) mode before.

I just checked my logs and my puff never lost puffs. All of mine are running 2/23/2016 firmware.

Does it do it too if you remove the cells and put the same ones back in? I just did that with one of my VT133 a dozen times and it was 2793 puffs when I started and the same 2793 puffs now.

Interesting! My puff counter is the middle value where your coil voltage is (is that your video?). And where your puff counter shows up, I have cell 1 voltage displayed. That is the only difference I see. Oh wait... I have a Welcome screen (2 seconds) and a secondary welcome screen (2 seconds) on mine.

I have two Reuleaux DNA200 and four HCigar VT133 and they all use 18650 cells (the fourth one is still in the mail). I am also keeping a log of battery levels and puff counter whenever I refill them and/or swap cells. Since I don't want to connect up to EScribe to read the puffs, I have the puff counter displayed on the main screen. And if the puff counter drops puffs by changing the batteries, I would see it. None of mine are doing it. I can't recall a time of swapping cells with the USB connector connected, nor being connected to EScribe obviously. And 99% of the time I am using Ni200 and like 95% of that time, I will lock the ohms before removing the atty or swapping cells. As I noticed the DNA200 will likely forget what the cold ohms was if I don't. So are you doing anything differently than I am?

Yes these are really awesome. I can vape 25ml+ per charge. None of my other mods even come close to this amount of juice.

I think the first one is the one it comes with.

If all of the cells are 4.20v after charging (or 4.10v, depending on your settings), the DNA200 is operating like it should. And the battery capacity is measured by actual watt hours used.

The charging current will drop when it gets close to a full charge. Also the DNA200 will not draw more current from the USB than it can safely supply. The battery percentage is based on the configuration of the battery capacity. As cells age, they lose a bit of capacity. So you might have to drop the watt hours in EScribe's Mod (tab) with time.

@ChunkyButt200: I really appreciate your reply. Yes I have heard others speak about the RBA not reaching down far enough to make a good connection. So solder sticks to SS? Yes this could be the whole problem for sure. Although I would also expect to see this in the resistance. I do have an odd resistance thing going on that I had seen with the old build too. That is overnight it was sitting for 9 hours and the VT133_3 should see it as 0.11 ohm. But it saw it as 0.17 ohm. And it didn't pulse this time. But the wattage stayed pegged, the volts was higher than it should, and the temperature was struggling to get to 470ºF, which it never got to. Here is the screen shot. It acts like some of the power was going somewhere else, besides the coil. But the resistance is showing it is just higher than normal. But not that bad to explain the voltage, power, and low temperature readings. Oh John said cell 3 should read something with two cells? That is odd since all of the wiring diagrams I have seen shows the balance connection pins 2 and 3 are shorted (only TV133_1 shows some voltage while my others show nil). And that is where cell 3 voltage is read from. @VapingBad: I really appreciate your reply. Yes that is a 0.11 ohm Ni200 coil in the first two. But I was moving it from mod to mod and yes it was warm. Only VT133_1 and VT133_3 did it act up on. Everything else I tried the Black Crown ran flawlessly. As I mentioned to CB above, after sitting all night, my VT133_3 read it as 0.17 ohm which it should be 0.11. It didn't pulse this time, but the voltage went to 2.4v and the wattage pegged and even at those settings and even at 0.17 ohms cold, it should have easily reached 470ºF. I am currently running that same coil (Black Crown) on my VT133_2 which I had never seen it act up at all (or my other mods). Oh I am not seeing it hit the voltage limit at anytime. From all of these shots, 2.4v is the highest it has gone. But when I see it again, I'll record the data and see what it says. @black lace: I really appreciate your reply. Although it is acting very much like sudden resistance increases. Although the Device Monitor shows it very stable. Maybe the sampling rate is just too slow to show it. I have four scopes here. Although to use them I would have to disassemble a mod or atty to get to the connections. Either that or build a 510 breaker box which I have been thinking of for sometime now. And yes, I am using a 0.4mm plastic washer. Tried it without too. @All: I have been running this Crown on my VT133_2 which it never acted up on. I just watching it carefully just to make sure it isn't going to mess up on this one.

Courtesy of VapingBad

I am trying to figure this one out and I don't get it. I have two Crowns w/RBA and I use 28g Ni200 with them. I haven't checked the other one, but my black Crown I am having problems with HCigar VT133 #1 and #3. My second VT133 is fine as well as my Reuleaux DNA200s with this Crown (as well as other non-DNA mods). I just rebuilt it since I was having the same problem. The first image shows it is working normally on #3 and then starts to pulse (voltage and current). The second image is on #1 and it starts out good again (it isn't shown) and then pulses too, but not as bad as #3. Last image is a totally different tank on #1 and everything is normal. The temperature is purposely set low for first two images because I was moving that hot coil from device to device. Right now it is at room temperature and it is reading 0.1133 ohms. #1 will show cell 3 (VT133 are two cell mods) from 0.5v to 1.2v and kind of floats around. I never found it affect anything so I never investigated why it reads something there. My Profile 2 is my Ni200 Profile on all of my DNAs.

Oh thanks awsum. I never even thought about using mech parts for battery tubes. Love it!

Battery tubes? Where? I have been looking for those.

Yes Temperature Protect means it has reached your temperature setting. You can turn that off in EScribe. Whether you have Temperature Dominant checked or not depends on how you vape in TC. Some people tweak the vape by wattage. And others tweak by temperature. If you adjust your vape by temperature, and leave your wattage at 65 watts for example. Then you usually want the Temperature Dominant checked.