James

salsadoom, the problem is that Wine doesn't have support for Windows's USB HID APIs. I don't think it'd be terribly hard for them to add. Presumably it's just that nobody's up and done it. Humorously, the C# HID library I use, HidSharp, actually does support Linux's native USB HID APIs (though Linux does require you to set udev rules to access HID devices on non-root accounts.)

The 1.2 version is much more portable than earlier versions -- a good 90% of the user interface is in platform-independent code, as opposed to perhaps 50%. As time has allowed, I've been moving more and more of the code this direction. Keep in mind though that time and resources are limited, and there's a lot more we're doing than EScribe. It'll get there.

I don't think the internal resistance has changed. 1.2 SP3 may have trouble reading resistances that low, probably due to some of the extra protection code we added. I'll have to look at it this coming week. Other than this issue, I am glad it is working well for yall.

The results of Battery Analyzer only affect the battery meter. If you can live with a battery meter that is maybe 10% or 15% off, you really don't need to configure anything in EScribe for your batteries. Weak Battery messages are based on a minimum voltage, and charging goes to a maximum voltage. We did this intentionally so that accidental misconfigurations have cosmetic effects only. The safety-critical systems are not user-configurable. The battery *type* matters, but Lithium Polymer/18650 is already selected by default. Only if you are using LiFePO4 batteries (I thought people would want to, but it seems not) are you going to need to configure that...

There are no modes on the DNA. X watts is X watts... What material is your coil? If it is Kanthal, no temperature protection is going to occur, so you will get a purely power-controlled vape. The power level is related to the amount of vapor production. I'd try turning down the power. It may be much too high. You don't need to select Kanthal on a DNA device. We autodetect the non-temperature-sensing case. If it is a temperature-sensing wire and it is temperature protecting, disabling temperature protection is going to increase the amount of vapor. I'd try turning down power.

The purpose of preheat is to raise the temperature of the liquid above the boiling point so vapor production can begin as soon as possible from the time the fire button is pressed. Kanthal has no meaningful rise in resistance with temperature. We cannot sense its temperature. Therefore, we do not preheat it.

It sounds like one of your batteries is fully charged and the other is not. If one cell is at 4.2V and the other is at 3.8V, the DNA will need to rebalance the cells. This is very slow. It can only charge quickly if the cells are nearly at the same state of charge. Let it try and charge for about 24 hours, and see if the cells become closer. Once the cells are balanced you should be fine.

Do you have a mod resistance set? Maybe it is set inaccurately high. That can cause a cooler vape.

soulvape, if the automatic firmware update fails (what it sounds like), have him go to Tools->Apply Service Pack and choose 1.2 SP3 manually.

I've posted up an EScribe that should fix the VaporShark charging issue that 1.2 SP2 had. It also fixes the bug with Copy Profile and the Watts profile.

If the setpoint is 450F and the DNA is spending 75% of its time at 449.5F instead of 450.5F, it still ought to display the message. The purpose of messages is helping people not math. As far as overshoot goes, the new firmwares have a "Temp Peak" option in Device Monitor. That shows the maximum temperature observed by the temperature protection code at any point during the puff.

Ah, I see. Disregard that update, it's only for one of the two variants of the VS board (the one I was able to reproduce the problem on). I suppose most people do have the other one. I'll post a different one later today.

Someone try this. It's a single value change, nothing big. The current sense amp and charger are right next to each other on the VaporShark board, so the code was getting confused by a bit of electrical noise. Easy fix. Let me know if this works for you and if so, I'll put it in a quick update tonight. EDIT: Need to make one for both variants of the VS board.

It worked fine on my VS DNA 200, as well as Nick's. No problems charging at all. What are your cell voltages at, and your USB voltage? Of course if your batteries are nearly full, the charge will not be at 2A. Hmm. What kind of chargers are you using? I am using an Aukey Quick Charge 3.0 single port and the charge port on a 7-port Anker USB hub.

aonoukraine, I am curious, why do you say according to the core wire? I may be extremely tired from coding, but I believe you'd do a custom curve in Steam Engine with the two wires considered to be electrically in parallel.

It does that right after a firmware update. I believe it's due to the cell balancing being active when the firmware update completes. Reboot it and it'll be good from then on.

What version of Windows are you running?

If 3V is not giving you trouble it certainly can't hurt to be at a higher voltage, especially since you are interested in battery cycle life. E-cigarette batteries tend to lead hard lives, though Samsung INR etc. 75W capable 18650s are generally quite happy at that voltage. Keep in mind also it's under-load voltage, so the battery is not at 2.75V unloaded unless you vape at... very... low powers. At 15W I lose about 0.2V just in wiring, meaning at 2.75V the battery itself is at 2.95V. If the only issue you are finding is Weak Battery messages, FWIW, we'll be making a patch to make that message less eager during preheat. Some 18650s have trouble holding 75W when they get low, but if they're still preheating at 70W, the message is more annoying than the problem, especially if the condition causing the blinks only lasted for a quarter second.

We set the default soft cutoff down at 2.75V on DNA 75 for just this reason. Wiring and battery box voltage drop at high currents can be quite significant (and internal resistance, of course), even when the battery has plenty of charge left.

We can fire just fine from LiFePO batteries (our soft limit right now is 2.75V, our hard limit is 2.50V). Our charger chip, however, charges batteries up to around 4.20V. 3.60V is the ideal termination. We do have the ability to disable charging, by which technically we could limit it, but even if we did, if the board got into a failsafe mode (failed firmware update etc.),the battery would be charged to 4.20V... Now, a quick Googling finds http://www.powerstream.com/LLLF.htm which claims LiFePO batteries can be safely charged to that level, but I haven't seen that anywhere else. There was less demand for LiFePO on the 200 than I'd expected so I hadn't really looked into it for the 75. Beyond the charger issue, I'd also wonder if any LiFePO batteries can handle the current demands of the 75.

black lace, what are you talking about? His graph is showing the setpoint. That's the Up button most likely.

Howdy all, The 2016-04-25 firmware for DNA 200 that some people have been trying is an experimental version. Please do not install it -- it is known to have problems. When we have new DNA 200 firmware ready for public test, we'll put it in the Early Firmware thread like we always do. Thanks! James

This happens on a DNA 75 as well? What happens if you wait a few minutes before removing the battery?

You can get back to earlier settings. After it downloads the settings, click Upload Settings with the earlier firmware installed. It will upload appropriate settings for that version.

Hmm. Could you please PM me your mod's serial number? I'd like to see what the file Restore Defaults is getting looks like. Thanks!