James

AllenH, are you getting the 0.13 in the Atomizer Analyzer, or is it displaying that on-screen? Cold Ohms are only shown when in TC. Kanthal displays live Ohms. This is a cosmetic difference -- if it has the wrong one, it should switch over quickly. Unrelated to Ohm lock generally, but I did find a bug in Atomizer Analyzer's Override Ohms, by the way, and we are testing a fix for that now. Good find. Next time you leave it overnight, you could try logging refinement to see what it's getting. In Help->About, left click seven times on the Evolv logo. Then, go into Device Monitor. I'd log Sample Ohms, Sample Temp, Cold Ohms, and probably Board Temp and Pack Voltage for good measure. Have it Record to a CSV. Those should be able to tell you if the refinement is getting values that are at least consistent. Another thing you might want to look at is resistance stability. Try going into Atomizer Analyzer and screwing in your atomizer. I actually tested an atomizer at one point where too loose *and* too tight would cause poor contact, and resistance would even change significantly over a quarter turn. Was eye-opening. Atomizer Analyzer'll sample it while you do that so you can play around and see if that's an issue.

Well that isn't wild. What is your core voltage reading? (see circled pad)

Wow, 1.534V! What is your battery reading? (With a multimeter.) Against the case... Mm, doing that would definitely pop the fuse.

Hmm. Blinking like that would suggest the processor is browning out, actually. "Warranty Service" would show for that case as well. When you plug into USB, try this: left click seven times on EScribe's logo in Help->About. Then go into Device Monitor. What is Bandgap reading? (If Bandgap is off, all the other readings will be too. My Bandgap reads 1.03V -- it should be generally around a volt). What do you mean by 'popped the fire button', by the way?

Did you upload the firmware before or after it said Warranty? What firmware were you running before?

Roger is a friend of Brandon's, and they are from the same town. Opus isn't owned by Evolv. I think people assume this because both live in Ashtabula, but it is not the case. twages, we can replace the board for you if the board failed. Mostly, it would be quicker for us to find out what went wrong.

We've never had a report of this happening during firing. Send it to us. We'll take a look at the board. 899 Moe Drive #21 Akron, OH 44310 Thanks! James

druckle, first thing to try... revert to the old firmware (Tools->Update Firmware) and see if the problem goes away. Thanks

What firmware version were you running? Did it fail while firing at 55W, or after setting it down for a bit and then trying to fire again?

What do you mean by standard creep in refinement, by the way? If your connection is good, your resistance should be more or less stable. How far is it moving? Incidentally for the beta we did make a custom 510 connector because we found some 510s had abominable resistance stability (also, 200W sustained is too much for many).

AllenH, when are the Ohms changing exactly? Atomizer Analyzer shows raw (not cold) resistance, so when the coil is hot it will show a higher resistance. Or are yours all over the place while the atomizer is completely cold? Locking Ohms will cause it to ask you less about whether it's a new coil, but it cannot fix the underlying problem if your cold Ohms are bouncing all over the place. That would indicate a bad connection, most likely.

Incidentally, in your video... when you switched to Kanthal, it removed the Ohm lock?

Hmm. I will look into this. Just out of curiosity though, why are you needing Ohm lock at all for normal vaping? (Much less Override Ohms, which is for an even more specific case, and really for testing?) Incidentally, what Atomizer Analyzer shows large the raw Ohms, not the 70 Fahrenheit (cold) ohms.

I've put up a new firmware, July 9, and a new EScribe, 1.0.23. On the EScribe side: - Live View looks better. - LiFePO4 batteries have a default discharge curve. - There is a new Battery Analyzer for those interested (requires the newest firmware). - The watt-hour calculator will offer to fill in the field for you instead of making you type it. On the firmware side: - Fixes a bug that could affect reliability. Worth the update. - Optimizes the code quite a bit, which should make the device more responsive. - You can rearrange default fields just like custom fields now. Enjoy James

Hi Justin, If you are able to repeat it, could you paste in the text it gives in Details of the error message? I am guessing it is throwing an exception. Thanks James

The DNA 200 communicates over USB HID, as well as supplying a standard USB CDC serial port (/dev/ttyACM0 on Linux). We intentionally chose standard protocols so as to not require drivers on less common platforms. If you want to get it running on Wine, you'll want to contribute USB HID support to that project. Wine has needed that for a while -- it could use Dymo scales, many embedded programming tools, etc. if it had it. I don't think it would be a very large project, as the kernel hidraw is very similar to Windows's HID.

The reason for an accessory board is to provide reverse voltage protection for each cell. Otherwise you could damage your board and/or batteries in the event you put one in backwards.

Set Display->Battery Meter to On All Screens to display it on top of your custom screen.

I should add that while the Windows serial driver is proprietary, the protocol it speaks is standard USB CDC serial. So Linux will recognize it without a driver. Because the device is composite, the CDC serial must have an Interface Association Descriptor, which makes the serial not work with Mac OS X (no IAD support). But, the HID-tunneled serial will work on every platform.