James

If the meter is jumping that means it is automatically correcting for a significant mismatch between the battery capacity and/or discharge profile curve vs. what it is reading from the cells. If it thought it had 45% at 3V/cell, the meter is definitely in the wrong spot. This can happen after the battery capacity and/or discharge profile curve have been changed, but if they are set right, it helps to let it charge up to full once so that it has a good starting point for its metering, as the corrector is just an estimate. The board temperature is fine so it doesn't look like anything is off there.

That battery is nearly dead and needs to be charged. If your battery capacity was set wrong, the percentage you are seeing in the meter may be off. Get the capacity set right, let it charge up to around 4.2V on all cells, and let the USB Current taper off. You should be in good shape. It will charge at 0.1A if the battery cells are below 3V for safety reasons, as well as if the room temperature is too cold or too hot. (Once the cells get above 3V it will go back to a normal charge rate.)

For Device Monitor, the 1.0.35 (2015-10-20) version of EScribe will now do this conversion if your temperature setting is in Celsius.

You can actually hit Undo after it downloads settings. That said, I've added this to the 1.0.35 2015-10-20 EScribe. Most people benefit from the automatic download of settings (otherwise, you end up with blank, default Evolv settings at startup), but for folks who want to do it manually, it can now be turned off.

Hello Bobby, I've added this to the latest EScribe (1.0.35 2015-10-20). Thanks! James

I have added Save/Load and Copy Profile functions to the latest EScribe, 1.0.35 (2015-10-20).

Hi Copyman, 1.0.35.2 (in the Early Firmware thread) now includes your translation. I expect everyone speaking Bulgarian will find this very helpful. Thanks! James

Hello Dina, What do you have to do to get that second error message? Thanks, James

Did you have Debug options checked the previous time? Good catch. I've updated the download link with a fixed version.

punksofada, I've made a version (2015-10-20 1.0.35) that can show the underlying error message. It's in the Early Firmware thread in the Software and Firmware forum. To unlock the full error details, go to Help->About and left click on the Evolv logo seven times. After that, it will show the error details along with the error.

It will always assume a new coil if you've just attached it and the newly measured resistance has changed so drastically that, if it *were* the same coil, its temperature would have to be below -100F or over 800F (lowest or highest electrical resistivity on the Material Profile).

Based on the numbers you've said, assuming 0.061 is *definitely* the coil resistance (a milliohm meter is helpful to confirm), the resistance of the 510 is significant compared to the resistance of your (fairly low resistance) coil - around 25% - enough to cause a temperature error of (I estimate) 70 degrees C. This is a problem with lower resistance atomizers combined with higher resistance 510s, and a reason a manufacturer really should measure and fill in the mod resistance. Here is John's post detailing mod resistance, if you want technical details: /topic/65594-topic/?do=findComment&comment=886200 Make sure you are running a recent firmware, 2015-08-07 or newer. Beyond that, if you don't have a setup to measure mod resistance, and are absolutely sure your coil is 0.061 and it is reading 0.076, that's a difference of 0.015. It is good to leave a little margin (as overestimating can be bad from a control standpoint, and not all the extra resistance is necessarily in the mod). I'd try estimating a mod resistance of 0.012 Ohm and see how it does.

Conan, the version information is in Help->About, near the OK button. If your resistance is jumping that much, your 510 may have a bad or dirty connection. If it is coming out of unlock, that suggests a pretty large change in resistance (over 25%), which should not happen with a solid connection.

Your problem is not the room temperature reading. In the Mod tab, is a mod resistance set? If not, does anyone know what it tends to be on a VT200?

Hello, Thought I should clarify one thing: I noticed Material Profile is translated as TCR-curve. This is not technically correct: a graph of temperature coefficient of resistance would be the derivative of this graph. With a constant TCR, a TCR-curve would be flat, but our curve (the scientific term of the Y axis is electrical resistivity) is linear in that case. Steam Engine has been calling this table TFR ('temperature factors of resistance'). We called it Material Profile. TCR-curve would be a different curve. James

Bobby, good catch on the Nothing Connected window. Watts Press Increment should be localizable. It needs the : at the end, though: msgid "Watts Press Increment:" Similarly with those other three.

The reason the room temperature stops reading at that point is that the board heats from firing, so the board temperature doesn't reflect the room temperature. It waits until the board is idle again for a reasonable amount of time before sampling again. It may be climbing a few degrees due to body heat. The Case Analyzer can help if the temperature is off when charging or right after taking it off charging. How far off is your ohm reading? It may not be due to the room temperature measurement.

Hello copyman, Thanks for this! A question: The Plural-Forms: line in the header of your .po file says Bulgarian has three forms of plurals for numbers ("nplurals=3;"), like jQuery's Russian translation. However, msgid "{0} second" only has msgstr[0] and msgstr[1]. It is missing msgstr[2]. Does Bulgarian do numbers differently from Russian? James

Hello jQuery! Thanks for this! I have included it in EScribe 1.0.35.1. A question: I was looking at your translation with Google Translate, and "Break Research Seal", the 'seal' in the English is an analogy to the seal on an unopened medicine bottle. It just tells researchers that the seal has been broken or is intact. (Settings cannot be changed without breaking the seal.) It does not change any data other than that, does not destroy any data. James

Hmm. What version of EScribe are you running that works? 9/3 and 9/30 both time out and do not work for you? (What firmware version right now?)

What firmware are you running? What does the temperature show in Device Monitor? Can you post what the Cold Ohms, Live Ohms, Temperature and Power look like?

VapenHippie, to set a custom (non-Nickel 200) material for a profile, it's Material->Custom, then click Load CSV to load in the CSV file SteamEngine makes for the DNA 200. Nickel 200 you don't need to do anything. You could do one profile per material configuration, or one profile per atomizer. The latter is nice if you have particular wattages, temperature limits, etc. that you prefer for different atomizers. To access it on the device, hold up and down for a few seconds to get the device into Power Lock mode. Then you can switch between profiles by pressing up or down twice, and Fire to select the new profile. This is nice because if you have specific settings you like for each atomizer, you never have to come out of Power Lock mode, and can change atomizers by just, up-up-fire, or whatnot.

Hmm. I was going to make a small EScribe update on Monday. "EEPROM read failed" is a very generic error -- nearly all underlying errors while uploading/downloading will give it. I'll add a debug feature to Monday's release to make it possible to get at the underlying error message. All other functions - Tools->Reboot Device, Tools->Show Serial Number, etc. all work perfectly? Does Device Monitor say 'error' in the fields at any consistent rate?

Interesting. How far along in the status bar does it go before you get the error? And what other errors are you getting?

punksofada, what firmware is your device running? (What version in Device Monitor?) If it is 2015-06-02, you will definitely need to update your firmware before uploading/downloading. That was a beta firmware that manufacturers were supposed to update to release firmware before shipping. A few didn't, unfortunately. Manufacturers are supposed to run all their mods through Production Utility as well for final functional test, which would specifically prevent this, but, again, a few don't. Most do, thankfully... So, update your firmware, and it will work perfectly. If your firmware is fairly recent, try the 9/3 or 9/30 EScribe in the Early Firmware thread. Those have longer timeouts for slower PCs and for computers running Windows under virtualization (Macs for instance).