James

Use ? for 'null' values: T=? turns temperature protection off. Also, T=MONITOR is temperature monitoring mode: it keeps measuring it, but does not control to it. E=GET MFR and E=GET PRODUCT are the board. As for the feature keys... E=GET FEATURE can go above 8, by the way -- query it until you receive a question mark. PC means power commands/queries. TC means temperature commands/queries. St means long-term statistics queries. (Total energy, etc.) FG means fuel-gauging (DNA 200/250), so C=GET works. (Capacity.) S:3 means multi-cell, max 3. You can use B=GET CELLS to get the actual cell count. M means profiles. The feature keys enable creating devices with more restricted or more extended feature sets. For example, if a device responds with PC as its only feature, ECigStats is happy to talk to and sync it (that implies single-cell, power-controlled only, so it won't send T=GET, etc.). Or if it's only St, it'll only ask about puff count and time.

Try hard rebooting (Tools->Diagnostics->Reboot Device).. Did you recently upload settings, or..? (Did you install a new version?)

Is your DNA colder than -40C? That is what the thermistor is showing. (If it is not that cold, the thermistor may be broken. It's never so cold here in Ohio.) The DNA must be above 0C (4C?) to charge full speed, for battery safety reasons.

-39.9F board temperature. It looks like your thermistor is not working. (Unless you live somewhere VERY cold.)

SP5a just fixed a cosmetic refresh issue between related fields. For example, in SP5 if you chose "Do not change brightness." as the Brightness setting for firing, the (related) brightness slider did not disappear until you clicked it. This was weird. Unless you reset your device settings, I'd definitely look at Cold Ohms.

See in the system tray if Windows is still searching Windows Update for drivers. This can take a while but is often the cause. If you just let it sit, or click to skip searching Windows Update for drivers, it'll work.

This particular behavior is mostly an artifact -- on-screen Ohms is Cold Ohms for temperature-sensing coils and Live Ohms for non-temperature-sensing coils. In Device Monitor / EScribe fields on-screen Ohms are labeled Cold Ohms. The underlying query is R=GET. So, for non-temperature-sensing coils, you are always seeing Live Ohms. As for 0.29 vs. 0.26, does this occur when you have preheat off as well, and if you fire at only a watt or two?

No? Where did you download EScribe from? The version on our website should do it fine. ( Although, as you observe, ECigStats communicates in the same way with all devices. )

It should work with the default install

Hmm. What version of EScribe are you running, and what firmware version on the device? (DNA 250 should run fine with 1.2 SP3 and later Service Packs.)

Fixed. Thanks for reporting that.

Could you try a traceroute (tracert evolvapor-downloads.r.worldssl.net on a command line)? Also to downloads.evolvapor.com? Thanks! (Does your country censor Internet? The CDN would share an IP address with many other sites. Also, what IP address does your PC think that site is? Lastly, do you have any plugins in your browser/firewall that might block sites?)

I've posted up 1.2 SP5. Please let me know if you run into any issues with it. Have a good night. James

Hello MacVap, We moved to a CDN for our downloads, since the traffic is into the terabytes... I've contacted them and will let you know what I find out. James

If Connect and Download Settings worked, what did you try next that said no USB devices were connected?

skrilla, in Device Monitor, what do your cell voltages say, and what is the USB Voltage?

When you used SP4, did it not automatically make the minimum 0.9? If not that's a bug

lewiss, if you go to Device Monitor and click Diagnostics, Set USB Current Limit, and set it to 1A, what does the USB current read? 1A, or does it stay at 1.8A? (You have the device set to "Wait Until USB Charge Current Goes Above": 0.9 (or higher) A, right? If it is set to 0.1, the default for DNA 200, this is the cause of the error.) I'd recommend using the SP4 Production Utility not the SP3, by the way. Its USB charging test is better.

At a 3.2V soft cutoff under load, it's not surprising you don't get significant vapor if the lowest cell is at 3.29V when not under load. Most of the capacity is at higher voltages, so it would appear to even out voltage-wise after a bit of charging despite having a large difference in charge level between the cells. (When they are very low cells tend to crater on voltage, so if the other batteries are at 5% and that one is at 0%, it'd appear a lot lower, whereas at 20% and 15% they'd appear similar.) I'd let it charge up to 4.2V and give it time to rebalance. It's not necessarily anything wrong with the pack. Balanced, next time, you should get closer to that 19% it thinks you have left.

The DNA 200 doesn't have the charging issue SP4 addresses. There may be a SP5 for DNA 200 at some point with other fixes.

That sounds like an issue with the balancer taps, or alternatively, are you sure your batteries are seated correctly?

I've fixed the link. Sorry about that

This is part of the reverse battery protection. It won't pull any power from the port unless it sees a reasonable positive battery voltage.

Once the charge is complete (4.20V/cell unloaded) the DNA will correct the meter. If the meter is off, it may say 100% but until the cells actually get to 4.20V and the current declines to nearly zero, it's not actually finished charging. If you have a cell at 3.33V your battery is basically empty. The meter, when the DNA detects it should do a correction, always does it based on the weakest cell (since Weak Battery will limit on the weakest cell anyway, for safety). If the other two are that much higher, you need to let it charge and give it some time to rebalance the cells.

salsadoom, the problem is that Wine doesn't have support for Windows's USB HID APIs. I don't think it'd be terribly hard for them to add. Presumably it's just that nobody's up and done it. Humorously, the C# HID library I use, HidSharp, actually does support Linux's native USB HID APIs (though Linux does require you to set udev rules to access HID devices on non-root accounts.)