James

The 2015-10-21 EScribe includes the 2015-09-30 firmware. I mean in Device Monitor, the Version: in the lower right corner.

Givesuhe11, if you use three 10K resistors to split the wheelchair's 12V into three 4V outputs, you can hook that into the balancer connection and read the voltage. This will drain 0.4 mA continually, so 9.6 mAh per day, but it will work.

footbag, it should change the press increments as well. Did you update the firmware to 2015-09-30? That version adds support for changing the increment.

Hmm. The issue might be, the lines in Nothing Connected are all separate translations instead of being a single message.

Mm. As far as VMs go... Parallels was a bit quirky when I tried it on a Mac Mini -- I'd tell it to allow the failsafe device, but it still wouldn't detect in the VM until I physically reattached it a second time. In that case, I think Parallels first tells the host OS 'send this to me', but the host OS decides where it goes on attachment. It makes sense from a programming perspective, but from a usability perspective, confusing as hell. I could probably do to increase the timeouts more, or perhaps 'X is taking a long time. Keep waiting?' instead of a flat-out failure.

SteveAdams, your device is in bootloader failsafe mode. Let the virtual machine see that device with the serial number. Then go to Tools->Update Firmware and select the firmware manually. Normally updating firmware will automatically detect this other device mode, but in a virtual machine only the selected devices get to the VM, so it is unable to find it unless you manually enable that one.

All Evolv DNAs by default have a 20 second puff cutoff. You don't need to set anything to get this.

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