James
-
Posts
722 -
Joined
-
Days Won
112
Content Type
Profiles
Forums
Downloads
Posts posted by James
-
-
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 PACKEARLY SERVICE PACK
-
9
-
4
-
-
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?
Feature suggestion
in General Discussion
Posted
What kind of variables are you thinking of/which screens?