James

D022A, what version of firmware were you running at the time? What mod is this? Could you PM me the serial number? Thanks! Help Desk should be able to look at your board and replace it.

Has cell 1 ever read properly? If not, how did the mod pass through Production Utility? (Did the mod maker not use it?)

Once you hit the Fire button, does it stay on? That'd narrow it down between a USB Voltage reading issue and a sleep pin related issue.

The newer versions of EScribe (in the Early Firmware thread) save where the program was when you last closed it. If this is not working, hmm. Do you have a multimonitor setup? Running in Extra Large Fonts by any chance? The fire button should not cause reboots. If you're able to fire at a reasonable wattage though the power connector has to be fine...

How do you know pressing the fire button reboots the device specifically? What behavior are you seeing? Does something display on the device screen? If you see anything on screen, that rules out it being a firmware issue. If Device Monitor works then your firmware is working. What are you seeing for battery voltage? I wonder if something is wrong with your battery connector. When you use Device Monitor, are you able to fire? Or does it say CHECK ATOMIZER? (What are the battery voltages reading? Keep in mind, battery voltage is read over the balancer taps, whereas power actually comes from the main connector (JST in the Hana's case).)

Google for LiPo discharge curves, or the discharge curve for your particular battery to see what will happen. You will see that capacity does not advance much at all once you are in the 3V range - at that point a LiPo battery is essentially drained. Weak Battery will move horizontally along that curve to lower C levels until it finds what the battery can sustain at its current state of charge, allowing you to use all the capacity available at lower C levels. You can see on these curves that the 10C line will end at a lower capacity than 5C, which ends at a lower level than 1C, etc. When the battery is really low, it simply can't do 50W, and a few puffs later, can't do 40, 30, etc. But we have it give you what the battery can stably give. Letting the battery fall even further before reducing the current demanded of it won't help. Without the Weak Battery feature (it's not just a warning message), you see the capacity falls off a cliff on those discharge curves? You'd be done already. Unless your battery connections have a ton of resistance, lowering it is unlikely to buy you more than a percent or two.

Hello promod2000avenger, What do you mean by XP 'flashes between black and normal screen'? This sounds like a bug we ought to fix. Could you describe the behavior (or post a video)? Thanks, 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