James
-
Posts
714 -
Joined
-
Days Won
106
Content Type
Profiles
Forums
Downloads
Posts posted by James
-
-
Your problem is not the room temperature reading.
In the Mod tab, is a mod resistance set? If not, does anyone know what it tends to be on a VT200? -
Hello,
Thought I should clarify one thing:
I noticed Material Profile is translated as TCR-curve. This is not technically correct: a graph of temperature coefficient of resistance would be the derivative of this graph. With a constant TCR, a TCR-curve would be flat, but our curve (the scientific term of the Y axis is electrical resistivity) is linear in that case. Steam Engine has been calling this table TFR ('temperature factors of resistance'). We called it Material Profile. TCR-curve would be a different curve.
James -
Bobby, good catch on the Nothing Connected window.
Watts Press Increment should be localizable. It needs the : at the end, though: msgid "Watts Press Increment:" Similarly with those other three. -
The reason the room temperature stops reading at that point is that the board heats from firing, so the board temperature doesn't reflect the room temperature. It waits until the board is idle again for a reasonable amount of time before sampling again. It may be climbing a few degrees due to body heat.
The Case Analyzer can help if the temperature is off when charging or right after taking it off charging.
How far off is your ohm reading? It may not be due to the room temperature measurement. -
Hello copyman,
Thanks for this!
A question:
The Plural-Forms: line in the header of your .po file says Bulgarian has three forms of plurals for numbers ("nplurals=3;"), like jQuery's Russian translation. However, msgid "{0} second" only has msgstr[0] and msgstr[1]. It is missing msgstr[2]. Does Bulgarian do numbers differently from Russian?
James -
Hello jQuery!
Thanks for this! I have included it in EScribe 1.0.35.1.A question: I was looking at your translation with Google Translate, and "Break Research Seal", the 'seal' in the English is an analogy to the seal on an unopened medicine bottle. It just tells researchers that the seal has been broken or is intact. (Settings cannot be changed without breaking the seal.) It does not change any data other than that, does not destroy any data.
James -
Hmm. What version of EScribe are you running that works? 9/3 and 9/30 both time out and do not work for you? (What firmware version right now?)
-
What firmware are you running? What does the temperature show in Device Monitor? Can you post what the Cold Ohms, Live Ohms, Temperature and Power look like?
-
VapenHippie, to set a custom (non-Nickel 200) material for a profile, it's Material->Custom, then click Load CSV to load in the CSV file SteamEngine makes for the DNA 200. Nickel 200 you don't need to do anything.
You could do one profile per material configuration, or one profile per atomizer. The latter is nice if you have particular wattages, temperature limits, etc. that you prefer for different atomizers.
To access it on the device, hold up and down for a few seconds to get the device into Power Lock mode. Then you can switch between profiles by pressing up or down twice, and Fire to select the new profile. This is nice because if you have specific settings you like for each atomizer, you never have to come out of Power Lock mode, and can change atomizers by just, up-up-fire, or whatnot. -
Hmm. I was going to make a small EScribe update on Monday. "EEPROM read failed" is a very generic error -- nearly all underlying errors while uploading/downloading will give it. I'll add a debug feature to Monday's release to make it possible to get at the underlying error message. All other functions - Tools->Reboot Device, Tools->Show Serial Number, etc. all work perfectly? Does Device Monitor say 'error' in the fields at any consistent rate?
-
Interesting. How far along in the status bar does it go before you get the error? And what other errors are you getting?
-
punksofada, what firmware is your device running? (What version in Device Monitor?)
If it is 2015-06-02, you will definitely need to update your firmware before uploading/downloading. That was a beta firmware that manufacturers were supposed to update to release firmware before shipping. A few didn't, unfortunately. Manufacturers are supposed to run all their mods through Production Utility as well for final functional test, which would specifically prevent this, but, again, a few don't. Most do, thankfully... So, update your firmware, and it will work perfectly.
If your firmware is fairly recent, try the 9/3 or 9/30 EScribe in the Early Firmware thread. Those have longer timeouts for slower PCs and for computers running Windows under virtualization (Macs for instance). -
9/30 adds the ability to customize the scroll increment.
-
It's in the Early Firmware thread, if you want to try it. We have not pushed it to everyone yet.
-
dc601, thanks for letting me know about this. I submitted a false positive report to Symantec yesterday. Today I received their response:
Upon further analysis and investigation we have verified your submission and, as such, the detection(s) for the following file(s) will be removed from our products:
3E7B7632B24E605A892E97FF25E7EE3C - UpdateES_2015_09_30.exe
The updated detection(s) will be distributed in the next set of virus definitions, available via LiveUpdate or from our website at http://securityresponse.symantec.com/avcenter/defs.download.html
Heuristic scanners are along the lines of "I say neither" "Socrates says neither" ... Norton Security: "I has been detected as HEUR.Socrates". In a Venn diagram sense...
We had this happen with one AV when we added the Chinese translation, so yes, translations may very well be where it comes from. -
The Kanthal Nominal Ohms is the resistance for a coil that is not temperature-sensing. So, the raw Ohms minus the mod resistance.
The Temp Nominal Ohms is the resistance the coil, if temperature-sensing, would read at 70 Fahrenheit. We normalize it to this standard temperature (this is what it would show on-screen as well) because otherwise one cannot really compare coils. -
The screen does change between showing voltage and temperature based on whether it has detected a temperature-sensing coil, so that is understandable. Still, a burnt hit doesn't come a mode change in the the control system.
-
The DNA does not have modes. It has a single unified control system.
When we detect a temperature-sensing coil, the only difference is that we enable preheat to improve the experience from cold. Preheat ups the maximum power delivered power until the coil is at the appropriate temperature or after the preheat time has passed.
The temperature protection code is in effect at all times. If you have it set to 40W and 400F, with no preheat, it will happily deliver 40W until it reaches 400F, and then lower the power so as to stay within safe temperatures. It has to know the correct cold resistance, though.
If you are getting burnt hits, the cold resistance from the DNA to the coil may not be a single stable resistance. This is usually caused by an unstable connection or a badly-designed 510.
If the hits become burnt half-way through usage, the cold resistance may have changed. This can be caused by coils shorting, unstable connections, or wires that are undersized for the amount of power being thrown around (this last one can be... interesting... if you watch the resistance in Device Monitor... creatively bouncy, let's say?).
Dual coils are a special challenge, because if the two coils do not have exactly matched cold resistance, you are going to get differing amounts of power going through each of them, and one is going to be hotter than the other.
James -
Hi Feklar,
Could you give links to where to purchase those? If we can find a system that actually has this problem reliably, we can fix it.
Thanks!
James -
Unfortunately we have a limited amount of space allocated for screens.
We thought we'd have more than enough -- there's room for only 1 or 2 more right now.
To be fair, there are ways around it -- they are stored uncompressed right now. -
Do you have the Watt-hours set correctly for the battery? Normally, it will only correct if the voltage reading differs significantly from what it expects based on usage. Alternatively, your battery may have a different low battery falloff from the standard LiPo curve we include with EScribe.
-
E is actually a bit different:
E=GET MFR
E=GET PRODUCT
E=GET FEATURE (1 to 7)
E ("e-cigarette") and S ("statistics", because E=GET FEATURE returns St) support the ECigStats command set. -
Please try the EScribe I posted in the Early Firmware thread. It should fix it.
-
Are you charging with a 24-gauge cable? Many USB cables aren't capable of pushing 2 amps. Some sub-$1 6ft ones I use for other purposes top out at 0.3A or so.
Monoprice's 24AWG micro B will definitely work. They're only about $1.50 on Monoprice's own website. Kind of bulky though.
I would give you a link but it appears the "free" forum service we are using replaces Amazon links with Wal-Mart links. Grr.
I like their $3 "premium" USB cables as well, though I haven't tested a 2A charge with them. Really, any 24-gauge cable will do.
Also, when the battery is nearly full, charge will be put in more slowly so as to not overcharge the cells. We don't let any of the cells go over 4.20V.
Early Firmware and EScribe Suite Discussion Thread
in EScribe, Software and Firmware
Posted
Conan, the version information is in Help->About, near the OK button.
If your resistance is jumping that much, your 510 may have a bad or dirty connection. If it is coming out of unlock, that suggests a pretty large change in resistance (over 25%), which should not happen with a solid connection.