James

Does your directory structure (C:\Users\name\) have Unicode (non-Roman alphabet) characters? If so, maybe try installing a newer installer from the Early Firmware thread on top of it. The older installers were not Unicode-enabled, I believe. This should not affect the ability to check for updates, only install/uninstall. Unable to launch web browser... Hmm... If you do Windows Key+R and type https://my.evolvapor.com into the Run dialog, does it go to it properly? That's effectively what EScribe tries to do.

Hello Obi, I don't speak German, but at 21:30 of your first video, I notice that the mod on the upper right table is consistently low on power. The manufacturer should have set a Mod Resistance, but if they did not, it is most noticeable at low resistances such as your 0.27 Ohm. If you set the Mod Resistance correctly, the DNA 200 will deliver extra power to compensate for resistive losses in the mod's 510 connector and wiring. You should get the correct delivered power. This will also improve the accuracy of temperature protection. If it is set to 0 on that mod right now, by your table I think it is probably about 0.008 Ohms. Thanks for these reviews! James

What version of Windows are you running? Is Internet Explorer installed? If so, are you able to visit https://my.evolvapor.com without getting certificate errors?

Could you give a link to this calibration file? If it is a .CSV file, go to Material and choose Custom, then click Load CSV on the Material Profile. If it is a .ecigprofile file, click Load Profile on one of your profiles.

Hmm. It must not have made that new Root Certificate take priority over the built-in, expired one. EScribe uses Microsoft's .NET Framework, so underlying web requests use Internet Explorer. If it can't make a secure connection it will fail to connect -- we don't override the default verification. Here's a Windows update that should give you newer root certificates. Hopefully the GlobalSign is among them... https://www.microsoft.com/en-us/download/details.aspx?id=26609 There was an even newer one, but it appears Microsoft has removed it in their desperately needy attempt to force people to use their new OS...

Hmm. Well, try going to https://support.globalsign.com/customer/portal/articles/1426602-globalsign-root-certificates selecting Download Root-R1 for "R1 GlobalSign Root Certificate", open the file, and click Install Certificate. I'm pretty sure that one comes preinstalled all the way back to Windows 98 though... (What OS is this running? XP without Service Packs or..?) If this does not solve it, do you get these warnings when visiting bank websites etc. as well in MSIE? Try going to the padlock icon at https://www.dimensionengineering.com , View Certificates , Certification Path. It should say GlobalSign, AlphaSSL CA - G2, www.dimensionengineering.com with paper-with-award icons.

Production Utility is the only tool that Login affects, presently. However, if you are having SSL certificate issues, this also affects USB Recovery Charging (I believe), Send Feedback, Report a Bug, Get Information and Restore Defaults. Could you take a screenshot of the security warning? (You get the error on both?) That is the reason it is failing, and if I know the exact issue I can probably give advice on how to resolve it. Thanks! James

Could you please try these two websites with Internet Explorer, and see if you can access them? https://my.evolvapor.com https://www.dimensionengineering.com The https:// is important. I am wondering if your system certificate store may not have the appropriate SSL certificate authorities. Firefox uses its own store.

Interesting! What keyboards are yall using?

You can set it in Device Monitor. It's in Diagnostics.

New Coil actually should show up in Stealth. Is it not for you? What firmware are you running? If you want to change wattage and have that make the screen bright, instead of using Stealth, you can achieve this by editing the Brightness settings in the Screen tab.

Hmm. soulvape, that video shows for the 29th? The first e-mail I received from you about translation is indeed earlier, on the 19th (but the link didn't work when I tried it, admittedly a week later - is the 23rd the same link?), and the first from miwu is the 30th. Bobby, the "Example Language File.po" is fairly complete I believe. I should probably just rename that one to en\EScribe.po

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.