James

Thanks! I've fixed this.

Good catch. I have fixed this. It will be working in the next EScribe service pack.

Good catch. I've fixed this for the next EScribe service pack.

Make sure the board is well-grounded. If the grounding screws are making poor contact, Ohms can shift as power rises. 1.2 SP5 introduced an overtemperature failsafe (that is, if it measures a temperature well over what it should be controlling at, it assumes the wire is out of control and cuts power). In practice this does not occur often, but it can due to Ohms misreading if you have a grounding issue. Barring everything else, you can certainly revert back to SP3. EScribe should be compatible with it long-term. If it ever stops being compatible let us know.

What browser and operating system are you running? It's working for me in Chrome, Firefox, and IE.

I will be posting early versions of EScribe Suite 2.0 to this thread from now on.

Device Monitor will correct the time when it connects to the device. Also, if you use ECigStats, it will correct the time after it synchronizes with the device (if you have made one or more puffs since the last time you plugged in). The board has enough energy storage to preserve the clock through a (quick) battery swap.

4.2V does not mean charge is complete. Just as there is a voltage drop when you pull power from a battery, there is a voltage rise when you push power into a battery. When a battery is first charging, 1A is not enough to push the voltage to its target value. (This stage is called Constant Current charging. It takes about 2/3 of the time of charging.) When the voltage (while charging) reaches 4.2V, the charger essentially balances the voltage rise from charging with how far under the voltage would be if it weren't charging. If you click Diagnostics->Disable Charging, you can see this: the battery voltage will drop to its real level. (Be sure to enable it again. ) If the charger did not do this, as the current tapered off, it might end up above 4.2V. (This stage is called Constant Voltage charging. It takes about 1/3 of the time of charging.) This second stage is what you are seeing, most likely. It should eventually finish.

What operating system, and what version of EScribe are you running (1.2 SP5.1?)? Does it work if you manually use Tools->Update Firmware?

What issue are you trying to fix?

Try the EScribe in the [EARLY] section of /topic/66731-topic/ It fixes the EEPROM read error.

Out of curiosity, what firmware version was your device running before? Also, what operating system are you running? Thanks! James

You shouldn't need any special delay to get a response from the DNA. (Device Monitor does not have any delays.) That may be a parser or HID issue.

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?)