James

Win10/IE SmartScreen is not an antivirus.

retird: We reissued our code signing certificate to SHA-2 so Windows 10 would recognize it post-2016. (The earlier 'corrupt or invalid signature' people were experiencing is Microsoft... stretching the truth... to force developers off SHA-1 certificates.) It's a new certificate, so SmartScreen should recognize it as "safe" in a day or two. If we had paid extra for an "extended validation" code signing certificate, of course, we would have gotten "immediate reputation". Protecting YOU... from people who don't pay them enough. Good times.

I've posted up a new version for yall to try. The changes are smaller this time around, but I think the improvement to power adjust speed will be welcome. Let me know what you think! Have a good night, James

MikeA&P, did the detected cold resistance change at all?

Yes, you will need one of the 2016 versions to connect to the VaporShark. ahpaa, if you are using a combined coil of two materials intertwined, specify it as two parallel coils of different materials in Steam Engine. Done right you can have an accurately generated curve for your specific coil. (Assuming, as with everything, that your manufacturer set Mod Resistance right.)

moto, you should be able to control the VaporShark DNA with the newest EScribe version in Early Firmware. Please let me know if it does not work.

Could you send me the file that is giving this error? Thanks! James Also, for a VaporShark version, please try the EScribe in the Early Firmware thread and let me know.

Conan, could you message me an example file that fails to open? I'll see if I can make it read them. Thanks! James

I've put up a new version 2016-02-12 / 1.0.39 with some small fixes. The changes are: (1) it adds a separate graphic for Hold To Change Power, (2) the curve resizes correctly so Actions is always visible, and (3) there's a "New Material" button on the Materials tab, so it doesn't always have to come from a file.

I'm not sure I understand -- why are you setting a Tcr for Nickel or Titanium? Tcr is less accurate than a temperature profile, and we included them for both of those. You transfer them from "Available Materials" to "Materials on Device", and then you can switch on the fly, or set a material for a profile on the General tab.

Ack! You're right, while doing all the repository features, I forgot to put a way to 'Create New'. I'll get it back in today. When you look at something for too long...

Did you update your firmware? Mine says 'hold to change power'.

I've put up a new version for yall to try. Let me know if you run into any issues. Comments and suggestions are welcome. I expect we'll make an follow-on update based on feedback for the Materials tab UI etc. Enjoy James

It only doesn't matter if you set your wattage to 40W or 150W if you, or (often) your atomizer, are unable to draw at 40W. Incidentally, this is almost always the case at 200W, but there, people are targeting specific flavor components.

Temperature protection prevents burnt hits and unsafe temperatures. When you are not vaping, or looking at the screen, yes, this does bring the power level low. (Or if the atomizer design in question is incapable of decent vapor production (wattage) without getting you into unsafe temperatures.) A legitimate use I _have_ seen for hanging out at the temperature limit is targeting particular flavor components that are brought out at specific temperatures. The purpose of preheat is to quickly bring the coil up above the boiling point. Once boiling, the thermodynamics change. In this region, wattage is _the_ determining factor for maximum vapor production.

This is possible in my test version. I am however a bit curious: if you are doing this when you switch atomizers, why not use a profile for each atomizer?

That error is related to either a curve in a profile, or the battery discharge curve. Either way, with normal settings you should not encounter it. What language is your version of Windows running, and what EScribe version? Could you post the settings file that causes this? Thanks

fwa, for LiFePO4, Max Recharges is 3.5V. LiFePO4 has excellent recharge cycles even with the normal 3.6V though.

Could you please post your EScribe settings? I wonder if there is anything special about them to cause this. When it is in this state, does Cold Ohms change? As far as hardware possibilities... One time, I did have a dodgy connection (I had just mashed the wires in for testing) whose Ohms would occasionally bounce to random values (it was losing connection) and the DNA would assume it to be a different coil. 9/30 should lock in the notion of TC after firing though. Does it still show a temperature, or does it switch to the Kanthal display of volts?

Hmm. 0.007 sounds very reasonable - many 510s are around this. Do try setting it to 0 to see if it helps stability though. It probably will not, but if it does that indicates the mod resistance was too high. I am surprised 0.90 Ohm did not help.

eziotroito, does your mod have a mod resistance set? If it *is* set but incorrectly and too high, it can cause control instability like this. Of course, if it is too low that can affect the accuracy of TC. It is much more important that your mod manufacturer set this accurately for SS. (If not, you can do it yourself, if you know/can measure it.) Nickel is less sensitive. You may get a better result with a higher-resistance coil, as that reduces the effect of mod resistance being set wrong. It isn't a given that this is the problem, but certainly something to make sure of. Also, do you have alternative wire you can try? The problem with SS is that (1) its resistance does not change as much as Nickel, and (2) it is an alloy and is not graded by electrical properties. That means not all SS is identical, so the curves may be off.

The battery discharge curve is based on unloaded voltage. The cell soft cutoff is based on loaded voltage. When a battery gets very low, it can still sustain voltage, especially if all it has to power is the screen, but as soon as you want it to push 50W, it's really much too drained. Think of it as bench pressing 2 lb vs 200 lb when you're incredibly fatigued. One of the two, the bar is going to stay up. Soft cutoff reduces the power the battery is being asked to push so the voltage doesn't drop fast. Try monitoring the battery cells while firing in EScribe. You'll see the effect there clearly.

It is safe. The hard cutoff (not configurable) is around that voltage to ensure safety. However, by setting it at that level you may not get meaningful soft cutoff. With soft cutoff at 2.8V, when the battery gets very low/weak, instead of the DNA dialing down the power so you can extract the last 10% or so of battery life, it is just going to say Check Battery. And you will have to dial down the power manually. It isn't what I'd do. But, to each their own. I'd make it at least 2.9V to get the battery-extending of the soft cutoff. People often misunderstand the nature of soft cutoff. If you look at a battery discharge curve, with lines for 1C, 5C, 10C, etc., it isn't saying Check Battery at that voltage. Instead, you'll notice that the lines tend to crater in voltage at a particular mAh. What soft cutoff does is, when the battery is about to fall off at that voltage, it instead goes *horizontally* on that curve, to the right, toward lower C value curves that end at a higher mAh. The battery can't give full power at that point much longer, and if you try it's about empty, so soft cutoff kicks in and gives you a power level it can keep going on. For total battery life soft cutoff is your friend. Maybe we should have given it a better name...

The voltages are different between USB and the battery. It's best to use watts and watt-hours where possible, because of conservation of energy (watt-hours). To estimate charge times: Battery: 0.9Ah x 11.1V=9.99(A x V)h=9.99Wh. Basically a 10 watt-hour battery. USB: USB is 5V. At 500mA, 0.5A x 5V=2.5(A x V)=2.5W. That's about a four hour charge. At 1A, 5W will take about two hours. It will be a warmer charge at 1A, yes. Two things make the charge slower than the estimate above: (1) USB is nominally 5V at the charge port, but your USB cable may have some loss. If you look at USB Voltage in EScribe while charging full speed vs. not charging you can see this - the drop is proportional to USB current, V=I x R). This isn't something talked about much -- charging 1A with a lower quality cable that delivers 4V to the device will be 20% slower than a cable that actually gets 5V there. The other 20% is going to heating the room. (2) Once the charging voltage of the LiPo reaches 4.2V at any cell, the charger will lower current so as to ensure it does not go over 4.2V while charging. This occurs in the last 20% or so of the charge, and is for safety.

Bobby, what version of EScribe are you experiencing this on? The newest in Early Firmware should fix a good number of locale-related problems. If it does not, that is a bug. Janggut, do you mean the link at the top or the bottom of the screen? The link at the top is to update the DNA device's firmware. The link at the bottom is to update EScribe. Thanks! James