James

There is & in front of the D in Device: "Automatically Connect to &Device" (This is to give it a shortcut key.) We actually received two German translations. I was going to put in soulvape's, from GERMAN DNA CREW, but miwu sent me one which is exactly the same except that the credits, GERMAN DNA CREW, is instead his vendor website. He is claiming his is the original. We've not had a conflict of claimed authorship for any other language. Still haven't decided what to do. Thoughts are welcome.

By the material: From a consistency standpoint, the problem with Stainless is that it is an alloy - a mixture, not a pure element - and graded by mechanical properties, not electrical properties. By the coil design: Because SS's electrical resistivity changes less with temperature than other metals, there is a greater need for mod resistance to be correct (something, ideally, the manufacturer would have measured and set, and many do), and mostly importantly, a higher resistance would help. Here's an example: Say our coil is 0.06, and the mod resistance is 0.02. A worst case scenario. Honestly, most mods have half or less this mod resistance. At temperature, say, 400F, the coil resistance will rise 20%. If the mod resistance is set correctly, it will read the coil at 0.060 cold, and be 0.072 hot. This does mean the full temperature range is 0.012 Ohms. That's 0.012 Ohm/330F, you're literally talking 25 degrees per milliohm. This will be very hard to control accurately. It will average 400F though. If the mod resistance is not set (that is, set to 0), it will read the coil at 0.080 cold, and a 20% rise is 0.096. The actual coil will be 0.060 cold, and 0.076 hot. This is a 26% rise instead of 20%. It will average 510F -- an error of 110F. This error in mod resistance corresponds to 70F on Nickel. Now, say we double the coil resistance to 0.12. Because this doubles the number of Ohms in the full temperature range, it doubles the precision with which temperatures can be measured. Additionally, if the mod resistance is set wrong, let's do the calculation again: 0.120 cold reads 0.140. 20% rise is 0.168, so 0.148 on the real coil instead of 0.144 if mod resistance were right. 23% rise. About a 60F error. Better. If we double it again, twice as good again... So: (1) correct mod resistance helps to avoid offset errors, which are magnified by SS's less changing electrical resistivity (2) for Stainless, a higher cold resistance would mean a greater range when it's hot, so better ability to accurately measure the material (3) even if you do both of these, SS is still an alloy so, unless you control a steel mill, you are going to have trouble getting consistent electrical properties between orders... and because of SS's electrical resistivity, even small errors in what goes into the CSV will translate into large errors in temperature. Good luck.

Keep in mind that all battery manufacturers tend to rate their batteries at very low powers (representative for consumer electronics), not the high powers used in e-cigarettes. Battery Analyzer defaults to testing at 40W, and as a result its real-world measured battery capacity will tend to be below the rated value. For instance, our FullyMax battery tested around 9 Wh real world, though its rating is 10 Wh (this is where the default 9 comes from, if your manufacturer did not enter in a battery capacity). This is true for all batteries - 18650, LiPo, LiFePO4, whatever. For instance, I found this on Google Image Search: http://img.photobucket.com/albums/v137/Tweek_CPF/18650_2400mAh.jpg On that image, if you really wanted to vape at C/3 (3W), you might get that 18650 manufacturer's rated capacity. Also, Battery Analyzer considers the battery totally empty for meter purposes at the point when the battery can no longer sustain a 5W vape. There may be a few more puffs left in there, honestly, and the DNA will let you vape it (showing Weak Battery most likely), but them'll be weak puffs.

The actual ramp up is in the milliseconds. What you are seeing is that the screen is updated four times per second with the average values from the past quarter second. So if you start firing half-way through that quarter second, the average will be between 0 (not firing) and your wattage, and that screen update will be at a midpoint. Take a look at Power in the Device Monitor to see what I mean.

Wattage is what affects vapor production, that's true. Provided you aren't encountering the temperature protection, it's approximately proportional. Is your atomizer reaching maximum temperature even at 10W? The reason it is an error message is that the original intent of temperature protection was to prevent dry hits and/or to keep the coil temperature below the breakdown temperature of the juice components, and otherwise the vape would be identical to normal coils. Preheat was added so people don't have to wait for their juice to reach its active vaping temperature. So, if set up in this manner, you would never get that message except when it prevented a dry hit or other unsafe vaping condition. The problem is that many atomizers are not designed properly to be able to emit large quantities of vapor without getting dangerously hot. So people run into the temperature protection a lot, and have come to use the temperature protection to achieve 'absolutely the maximum possible amount of vapor for this atomizer, while keeping at a safe level'. That's fair, but it would be better if the atomizer design was such that you never needed to hit such high temperatures to get good amounts of vapor.

Does it do this with the 9/30 as well?

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.