Jump to content

James

Moderators
  • Posts

    722
  • Joined

  • Days Won

    111

Everything posted by James

  1. 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.
  2. Added a link above to the 7/27/2015 EScribe version. Main feature: 2S support.
  3. 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?
  4. 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.
  5. What kind of variables are you thinking of/which screens?
  6. 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.
  7. 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.
  8. Hi Patrick.N. What does your board show for Room and Board Temperature?
  9. Hello MADMODDER. What firmware version are you running? (You can see in Device Monitor.)
  10. 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?
  11. 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.
  12. 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.
  13. Yes, thanks. That was a very good catch.
  14. Try the 7/16 firmware (in the "Early Firmware" thread right now). That fixes the Override Ohms bug.
  15. 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.
  16. 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 SP57 EARLY SERVICE PACK EScribe Suite 2.0 SP57
  17. 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...
  18. What happens if you apply power to it? Screen is pushed all the way in?
  19. 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).
  20. 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.
  21. 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.
  22. Jcca1973, what firmware version were you running?
  23. No they aren't. Be good to yourselves. It's a reasonable deduction to make from living in the same town.
  24. Say... from 0.08 to 0.13 and your dual coils... is it possible one of your two coils is coming out of contact?
  25. 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.
×
×
  • Create New...