James

combatwombat: Ideally, using the battery analyzer with a sufficiently sized resistor block for an atomizer. If your battery is a standard 3S LiPo, the curve won't change substantially. That'll just tell you what the actual battery life is. If it jumps around substantially, chances are your battery has very different voltage from the stock settings (less likely) or the wrong capacity set (more likely. Also, once you change the watt-hours setting, it's good to let the battery fully charge so that it has the correct starting point. What battery are you using and what watt-hours do you have, out of curiosity?

If you use EScribe's Soft Reboot, it will save settings. Hard Reboot or cutting power will not.

Posted up 08/07/2015. Custom splash screen times, and some improvements to the 2-cell support. Have a good weekend, James

XP should work, as long as you have Service Pack 3 installed. Do you have any software that hooks into the operating system (say, antivirus) that is rarer?

ndb: Yes, the atomizer resistance should not be included in the mod resistance. If it's the only atomizer you use, it doesn't really hurt, but that's a big if... As far as mod resistance goes, honestly it's much better to leave it at zero than to be guessing. A value higher than what is right can destabilize the temperature protection, especially at low power when it's most useful (the dry case).

Hello sammao, What are you clicking that gives that error? Thanks James

VapingBad: What do you mean by while the device was connected? Normally it's connected when it suggests updating firmware. Or have you found that affects its success?

Battery Analyzer considers the pack 'empty' when it can no longer sustain 5 watts. Due to the Weak Battery feature, the DNA will "walk horizontally" to lower C levels on a traditional battery discharge curve when the battery is getting low (hits the soft cutoff voltage). The battery would have been finished had it kept demanding the same power level. By doing this we extract basically all the useful life the battery has to give. So the difference due to chosen power level will be mostly losses due to internal resistance in the battery (and some heat dissipation in the fuse). I wouldn't sweat a 10 or 20 watt difference in the power level you choose for Battery Analyzer.

Good find. Fixed. I updated the 2015-08-05 download.

Thanks speed4mee. That is a good find. I've rebuilt it and no longer get that error. So there's a newer version up. Also made Device Monitor remember the time scale while I was at it.

For those it is not working for, are you on 32 or 64 bit Windows 10?

Laguz, yes, if you don't want to use Battery Analyzer you can put in a curve manually. The only difference is that EScribe wants the curve in percent remaining, not mAh. (It splits out Watt-hours as a separate setting.) I think you will find Battery Analyzer produces a similar result, though.

Out of curiosity what happens if you disconnect, so that you don't have any connection at all? When my laptop lacks WiFi it works.

Okay. I've posted it in Early Firmware. Let me know how it works for you! Good night, James

Added a link to the 8/4/2015 EScribe, which includes the 7/29/2015 R1 firmware. Mostly usability tweaks.

I was able to reproduce this on Windows 7's "Windows XP Mode". Maybe an issue with graphics hardware acceleration? I reimplemented a draw call and fill call in software, and... It's working great now. The fix will be in the next EScribe update.

If you set the time scale to 1 second does it make the displayed part wider? What fonts size are you using/video card? I wonder if I can find a similar computer to test with.

If the screen connector is getting kinked/mashed under the fire button it could be losing connection entirely. Then when it regains connection, the device has already started up, so the screen doesn't get its startup commands. I've attached a firmware which is more resilient to this possible case. Unzip it and apply the .sw-update file using Tools->Update Firmware. (Use a recent EScribe.) If you aren't having problems, I wouldn't bother with this experimental firmware. If you do, though... If this firmware doesn't correct the issue for you, revert to an older one using Tools->Update Firmware. If it does, great. Let me know! If this is the issue, we'll roll this into the next official update. Have a good night! James DNA_200_2015-07-31_Screen_Disconnect.zip

Submit a warranty request at: http://helpdesk.evolvapor.com/index.php?a=add Give them the link to the thread as well.

AllenH: Yes you can. EScribe uses USB HID to communicate, leaving the USB serial port free for your use. You can issue commands as well as queries.

? The fuse should be quite cheap. How is it $30? If you want, send us the board and we'll put a replacement one on for you.

Given that it's at 3.76V while charging, 25% sounds about right, honestly. That said, the charging code does not read the battery meter. It looks at the cell voltages (and a few other things, such as the board temperature, USB current and voltage...). The LiPo pack we tested gets 4.20V at 100% and 3.65V at 7.6% when not under load. LiPo packs are better in this way than 18650s from what I've seen. A LiPo pack will hold its voltage quite well until it is nearly drained.

Feklar, did the new version with the timeout make any difference? If not, what all USB devices do you have connected? Anything unusual? I am wondering if one is getting it stuck while looking for DNA 200s.

Use 80% or 90% of what you measure, btw. You really do want some stability margin. And the 7/29/2015 (or newer) firmware from /topic/66731-topic/

Two points about Mod Resistance: (1) If you are experimenting with Mod Resistance, I'd strongly recommend giving the 7/29/2015 (or newer) Early Firmware I posted a try. Mod Resistance directly affects the DNA's resistance reading, so in certain corner cases there's a bit of 'here be dragons'. I've added some extra protections so you can't get the DNA in too bad of a spot. (2) Always make sure the Mod Resistance you have is conservative -- keep the value you enter at or lower than the real Mod Resistance. If the value you enter is higher than the real Mod Resistance of the device, it can negatively affect the stability of the temperature protection system. It's best to measure it if you can, honestly. And then use, say, 80% of that value to give yourself some margin. Having a fairly accurate Mod Resistance will deliver a more accurate power and temperature. The compensation is really only notable in extremely low Ohm coils where the 510's resistance is significant though.