James

Submit a warranty request at: http://helpdesk.evolvapor.com/index.php?a=add Give them the link to the thread as well.

AllenH: Yes you can. EScribe uses USB HID to communicate, leaving the USB serial port free for your use. You can issue commands as well as queries.

? The fuse should be quite cheap. How is it $30? If you want, send us the board and we'll put a replacement one on for you.

Given that it's at 3.76V while charging, 25% sounds about right, honestly. That said, the charging code does not read the battery meter. It looks at the cell voltages (and a few other things, such as the board temperature, USB current and voltage...). The LiPo pack we tested gets 4.20V at 100% and 3.65V at 7.6% when not under load. LiPo packs are better in this way than 18650s from what I've seen. A LiPo pack will hold its voltage quite well until it is nearly drained.

Feklar, did the new version with the timeout make any difference? If not, what all USB devices do you have connected? Anything unusual? I am wondering if one is getting it stuck while looking for DNA 200s.

Use 80% or 90% of what you measure, btw. You really do want some stability margin. And the 7/29/2015 (or newer) firmware from /topic/66731-topic/

Two points about Mod Resistance: (1) If you are experimenting with Mod Resistance, I'd strongly recommend giving the 7/29/2015 (or newer) Early Firmware I posted a try. Mod Resistance directly affects the DNA's resistance reading, so in certain corner cases there's a bit of 'here be dragons'. I've added some extra protections so you can't get the DNA in too bad of a spot. (2) Always make sure the Mod Resistance you have is conservative -- keep the value you enter at or lower than the real Mod Resistance. If the value you enter is higher than the real Mod Resistance of the device, it can negatively affect the stability of the temperature protection system. It's best to measure it if you can, honestly. And then use, say, 80% of that value to give yourself some margin. Having a fairly accurate Mod Resistance will deliver a more accurate power and temperature. The compensation is really only notable in extremely low Ohm coils where the 510's resistance is significant though.

Added a link above to the 7/29/2015 EScribe version. Main feature: Stealth mode doesn't keep the screen off when you're choosing a profile. Kind of hard to switch profiles otherwise.

Added a link above to the 7/27/2015 EScribe version. Main feature: 2S support.

That looks perfectly fine. Guess I need to buy Windows 8.1 to test. For reference, are you on the 32 or 64 bit version of Windows? The other possibility is it's freezing looking through the list of connected USB devices for DNA 200s. Do you have any unusual USB devices hooked up by any chance?

The updater is already on a background thread. Which is why this is odd to me. Feklar, odd question but, do your EScribe tabs have left/right scroll arrows on the right by any chance? I found a "slows down massively" case involving that yesterday. That said, we ought to have timeouts. I will add a 60 second timeout to the next version, so we'll see if that's the problem. Need to find a proxy to test with as well.

What kind of variables are you thinking of/which screens?

druckle, if when cranking down that hard the resistance jumps up a lot higher than it should, that means it's getting poor contact for whatever reason when cranked down that hard. I'd recommend not cranking down that hard: a 50% error in resistance like that will make a huge difference to the effectiveness and accuracy of temperature control, as that resistance is most likely due to a contact issue and not Nickel, so it introduces significant bias. Perhaps the contact issue is specific to that atomizer? Or do you get it with everything? I don't have this with my test atomizer no matter how hard I turn it.

MADMODDER: How are you doing the switch to a new coil? By any chance are you firing, accepting new coil, and after that, switching profiles? Normally if you switch profiles first, it will not ask you about a new coil. Is the resistance locked on either of the profiles by any chance? SSV: Mm, yeah, if you had locked the resistance and accidentally short part of it, it's going to take your word for it about the resistance. I can't see any logical reason you would have to pull the battery though. Just unlock it, possibly disconnect/reconnect, and let it resample.

Hi Patrick.N. What does your board show for Room and Board Temperature?

Hello MADMODDER. What firmware version are you running? (You can see in Device Monitor.)

alee132, it will not show Kanthal Power Limit if it has detected as temperature-controlled. Are you running a very high-thermal-mass atomizer at a low wattage by any chance?

68F will be fine. You do not need to normalize to 70F with the more recent firmwares. It's a good idea to normalize to *some* temperature, though, as the EScribe curve editor only ranges from 0.1 to 10. We can handle as many points as the internal curve storage allows. The storage space is shared between the curves of all profiles and the battery discharge curve. Our default Ni200 curve has 6 segments (7 points), and I was able to split to 22 before it ran out of space. So the practical limit is 8 segments (9 points) before you'll run out of space if you load the curve onto all 8 profiles. If you don't need it for all profiles, of course, you can do more. There is a feature presently hidden that you may find useful: Go to Help->About and left click the Evolv logo seven times. That will unlock the "Reduce Number of Points" option in General->Material Profile->Special. When it removes points, it chooses segments that are closest to linear first, so that you don't end up losing meaningful detail.

No smoothing is applied to the curve. It returns the measurement at the time it receives the command. As far as polling rate, the less things that are checked, the more samples you'll get for what is checked -- it queries checked items round-robin as fast as it can. Presently, as an implementation detail (threading-related), it updates a bit faster if the window is smaller.

Yes, thanks. That was a very good catch.

Try the 7/16 firmware (in the "Early Firmware" thread right now). That fixes the Override Ohms bug.

shzrocka, there is no need to uninstall the old version -- the new version will replace it. As for separate firmware downloads, the new firmwares often come with new features in EScribe. I could make a smaller download (about 10MB) if we didn't include the .NET Framework each time. For updates that wouldn't be wild.

I am going to post here software and firmware Service Packs before they go on EScribe Suite's auto-updater, for those interested in trying things early, and so if yall find a bug we don't release it to the auto-updater. We appreciate your help testing these. RECOMMENDED SERVICE PACK EScribe Suite 2.0 SP68 EARLY SERVICE PACK EScribe Suite 2.0 SP71.1

Device Monitor demonstrates pretty well what can be done. It's actually limited by its paint code being on the same thread as the query code (and Microsoft's .NET Windows Forms not using hardware acceleration for drawing...). Be kind to it ( at a certain point you might be slowing it down), but you can push substantially more than 30 queries per second. You can also set Serial Output in the Research tab to CSV (Excel). That is a 50 Hz output of all of the important values. It did slow the device down by a few percent in my tests (a candidate for future optimization), but you can get a boatload of data points...

What happens if you apply power to it? Screen is pushed all the way in?