James

Only thing I can think of, when doing GET requests, do (1) 'send query, wait for response, send query, wait for response, send query, wait for response'. Don't do (2) 'send query, send query, send query, wait for response, wait for response, wait for response'. It won't send a response until its send buffer is empty, so you won't improve update rate by doing (2) (in fact, you may fill up the DNA's receive buffer, waiting forever to send, while the DNA is waiting to finish sending back to you...) and your code will be more complex. Do it the simple way, (1).

Here are the main control commands. Enjoy Fire: F=#S Set Power Setting: P=#W Set Temperature Setting: T=#C or T=#F or T=? Set Profile: M=# (1 to 8) Get Power: P=GET Get Power Setting: P=GET SP Get Temperature: T=GET Get Temperature Setting: T=GET SP Get Voltage: V=GET Get Current: I=GET Get Profile: M=GET Get Battery: B=GET Get Battery Cell: B=GET CELL # (1 to 3) The Device Monitor works by issuing serial commands, so really anything it can do can be commanded.

Mm. That is definitely a different issue. If you have time at some point, try going to Help->About, left click the Evolv logo seven times -- that unlocks viewing what refinement is doing. In Device Monitor, you can Record Cold Ohms, Sample Ohms, Sample Ohms (TC), Sample Temperature, Board and Room Temperature, then you can get an idea whether it is sampling consistently. Something to try if you leave it for the night one day.

Jcca1973, what firmware version were you running?

No they aren't. Be good to yourselves. It's a reasonable deduction to make from living in the same town.

Say... from 0.08 to 0.13 and your dual coils... is it possible one of your two coils is coming out of contact?

That's correct, for TC coils the screen will show the cold Ohms. That's the room temperature (70F) value, and corresponds to what someone would measure with a meter -- after all, nobody's measuring while the coil's hot. It's important because the temperature measurement is based off of that. For instance Nickel at 410F has a live Ohms about twice its room temperature value. As it cools you can watch this with Atomizer Analyzer's Raw Ohms. The analyzer also shows you Cold Ohms (same as on the DNA's screen), it's just in smaller text. Logging refinement, it ought not to bounce around significantly. But if it does you can see it.

Hmm. That seems like a very large resistance change for a dirty coil... I wouldn't think it should vary that much. The Nautilus Mini I test with does not vary much. Atomizer Analyzer won't update resistance while firing, though Device Monitor will.

Hmm. Ok. Tell you what... Try updating the firmware on the popped-fuse board, just connected to USB (no battery). Then take the fuse from the high-bandgap one and put it on the popped-fuse board. Then you'll have one working board. Send us back the other one and we'll investigate what could have happened and send you a replacement. [If you're uncomfortable with swapping the fuse we can replace two of course.]

Hmm. Is this the same board that shorted out to case?

Hmm. How long had it been running on the old firmware before you'd updated?

Is the processor getting warm by any chance?

We've added the ability to swap Up/Down to the next firmware version.

With USB plugged in? (Without USB and with bandgap that high, it'll think the battery is extremely low, and will just turn itself off.) Also, just on the off chance it might be software, could you PM me the .ecig file you uploaded with profiles?

Well, that was an *especially* bad one. We puzzled over it for a while. IIRC it's what prompted us to *make* Atomizer Analyzer.

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).