James
-
Posts
714 -
Joined
-
Days Won
106
Content Type
Profiles
Forums
Downloads
Posts posted by James
-
-
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 PACKEARLY SERVICE PACK
-
9
-
3
-
-
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?
-
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?
Atomizer Analyzer - override ohms
in Report a Bug
Posted
Yes, thanks.
That was a very good catch.