VapingBad

IIWU I would just swap battery % as it is the same info as the battery bar for pack voltage, BTW the hard cell cutoff is 2.85 V not 2.5 V.

EScribe will show you that info in far far more detail plus you can record it, on the mod you can put the battery pack voltage on the screen which again will be far more accurate than a bar and IIRC updates 4 time a second.

The only times I have had res rise were over night when there was a connection issue, it may also be the clapton they can vary in res a bit. I would just make sure the screws are tight, including the large screw in the atty 510 and if it still does it lock the resistance. It wont be the wire profile, also check your mod resistance is not set too high it is normally < 0.010 ohm.

"it should be fine with most 18650s but probably too low for LiPos"

It is the under load cut off so you batteries will not stay that low, it should be fine with most 18650s but probably too low for LiPos. It will shorten the life of your batteries a little, but IIRC less that the difference between charging to 4.1 V vs 4.2 V which can double their life. Have a read of this for fuller info http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries

Yes you can use the material/wire profiles for DNA 200s.

Yes, you can't hard reboot without it connected to UBS, I was confirming the puff counter behaviour was the same with or without temp limiting enabled. So if I follow you it is just doing hard reboot after disconnecting and reconnecting the batteries while temp limiting is disabled?

I can't recreate what you describe, it works as it always has done and how I have described on this thread, that doesn't mean you're observations are wrong, but it does mean they are not universal. On my rolo with temp limiting enabled I started at pc 20474, took 6 puff now pc 20480, soft reboot pc still 20480, took 5 more puffs, pc now 20485, did hard reboot and pc reverted to last saved value 20480 and battery cells read perfectly. So then I disable temp limiting pc still 20480 take 5 puffs, pc 20485, soft reboot settings preserved pc 20485, take another 5 puffs pc 20490 cells all 3.97 V, hard reboot pc as expected 20485 and all cells reading 3.97 V.

You could say user tries hard reboot and a fault reading the cell voltages appears, I don't see that it is connected to the puff counter. We have seen this fault a few times and it is just once (you in this thread) that the puff counter has been mentioned, I'm not sure that hard reboot is a common pre-condition either. You keep saying cause the puff counter to mess up like it is overwriting with some random number, it seems to me it just has the last value saved to the flash memory and the value in RAM was not saved, they have worked like this for the past 10 months. Sure that is not desirable and therefore a bug, but I don't believe it is any kind of software or hardware malfunction.

It is well document around this forum that the DNA 200 does not save settings and working data to non-volatile flash memory every time it changes, this is not a case of the board changing the puff counter value just that it hasn't written the latest value to storage before the batteries were disconnected. I fail to see how the misreading of cell voltages could be connected to the puff counter which is what this thread is about. As to the hard reboot killing boards IDK it is the first I've heard of it and don't know that it has anything to do with the misreading of cell voltages which I have seen people report. There is a 12-bit ADC in the main processor, but I think it far more likely the voltage measurement for the cell monitoring is done by the battery management chip not the main processor. Making the battery management chip and it's associated components a more likely area to look at for misread cell voltages. The main processor handles the USB so I suppose it could be affected by a power spike, but it looks like all the inputs are protected with discrete components. But it is all speculation as to what the fault is you believe is caused by hard reboot Bill and even if it is is a single fault, in the CPU, discrete components or battery management chip, not saying that there isn't a fault but 10 months or 3 months since the last fw is a vary long time for it to have gone unnoticed if it is that cut and dried.

It is just something I suggested in the past for the DNA 75, but had not implemented I believe they are working in another way of doing it.

Actually reading your last post Bill maybe having temp limiting active could well causes it to save more often, saving refinement data. Nobody else seeing it probably means nobody else noticing it, the puff counter gets very little interest from users from what I can see. I am concerned about you saying that a dozen of your mods are failing during hard reboot, I almost never do hard reboots as IMO the only thing that help with is clearing temporary memory of refinement and battery data, the same for forcing fw updates as I don't believe it does anything 99.9% of the time despite both getting recommended often.

I suggested they save when locking so you could force it without having to learn a new button combination.

It is by design Bill see post #28, it was designed for a permanently connected battery and has not been an issue for the vast majority as this issue taking 10 months to be raised demonstrates, sorry I don't mean to sound unsympathetic. There is no modes for temp or normal just one operating mode where you can turn off temp limiting so that should not make a difference.

It is a side effect of these boards not saving their settings and data to memory every time it changes to save power, they save when the go to sleep or you do a soft reboot.

If you want to show a particular graphic on demand you can assign it to a spare profile, then change to that profile to show it for a few seconds.

Try running the installer as an administrator it may have a folder permission issue seeing that it is stalling creating a profile, you should be able to do this by right-clicking the setup.exe file.

Don't know, but notice it could be related to the cold res, the one working well has the lowest cold res, the other two are 60% and 30% higher so I would swap the tanks around and see what happens. The 1st plot looks a bit like when it is hitting the voltage limit so I suggest putting pack voltage in the plots.

Hi, you should be able to just open a ticket with Evolv http://helpdesk.evolvapor.com/index.php?a=add

No, but it is easy to do a dry solder joint in the positive than you would think, I would expect it is not showing any resistance in device monitor either. If it is a common ground design that could also be the cause. I would start by checking the continuity or resistance with a metre

And the max output voltage is reduced to 6 V which will lower the max resistance you can get full power in.

Not saying there is anything wrong with the tube at all, just that it is unnecessary unless you want to design around a tube. If you took the tube and ground the body so it only had a 2 or 3 mm strip of metal each side lengthwise between the two terminals the performance would likely be the same. Or you could cut both ends off the tube and fit those in your box.

Those are still not great for high power mods, those mods do not have the current requirement we have. I have been using springs from other mods for a year or two, last one was ProVari latest version cut down so probably half the resistance and it is still not as good as the set up I posted above. Also re tubes: the tube is not important, necessary or even useful unless you wanted to build a mod with a tube, IMO it would just take up room with no real benefit, but oversized mods are a pet hate of mine. It's the contact area, pressure and resistance of the contacts that matter. IMO it is easier to make good contacts rather than cram a tube into a mod that is not a tube mod.

You only need to make more substantial contacts and add some pressure, spring or threaded and you can reuse the plastic chassis.

It should be in previous saved config files if not on the mod, load one without the mod attached and save the battery profile than load it in again with the mod attached. I think the default profile is the fullymax 900 mAh anyway.