Bobby

Great! Thanks. Just a tip for non-English users: If you get a screwed up discharge profile after you have loaded the file: a. set your Windows country settings to English (decimal sign should be "." and thousand seperator should be "," (normally your numbers would be eg. 1.234,56 but now they should be 1,234.56). b. restart Escribe c. Load the esig file d. restore your windows setting.

Did not find it but I did find the esig file for the Efusion that Evolv created and posted, here on the forum. See: /topic/67562-topic/

Version 1.0.35 is a pre-release and not yet in the autoupdater. See first post of /topic/66731-topic/

As far as I know, in Escribe version 1.0.35 the range is 0.0008 - 0.0100. See /topic/67814-topic/?do=findComment&comment=910399

Between 0.0008 and 0.0100?? When I try to enter 0.00094 for SS316L, Escribe tells me that the minimum value I can enter is 0.001...[/QUOTE] I have Escribe version 1.0.35 and I get this:

Why do you think that you are limited to thousandths? I can input TCR values with far more digits than only n.nnn, including your value of 0.00105. (Entering an invalid value returns the warning that the limits are set between 0.0008 - 0.0100) Did you find somewhere in the manual or the spec's that only thousandths are used by the DNA200 in measurements and calculations or are you just assuming this because Escribe displays some values in hundredths or thousandths in the graphs.

@derichio02: Sorry, I was off line so did not read your request 'tiil now, but glad to see that you got the info anyway.

@dasfast: Thanks for the link. I did not use their ecig file but manually copied their case analyzer results. (Hopefully they will upload version 2.0 soon since in this v1.0, the mod resistance value is still the default "0" and the battery discharge curve is not correct).

a 2500 mAh 18650 has 9.25 Wh which is slightly less than the Lavabox a 2700 mAh 18650 has 9,99 Wh which is the same as the Lavabox a 3000 mAh 18650 has 11,1 Wh which is slightly more than the Lavabox the efficiency of the DNA200 is 97% which is in the top regions for mods, so that's no issue here. So I think that your experience is typical (if you are using an 18650 of >2700 mAh in the comparison mod). Edit: I'm not a Lavabox owner, I hope you'll forgive me ;-)

OK. I haven't done the recovery (and don't want to since I do not have a problem) so I do not know how it is suppose to behave. I only know it can be used to recover a deeply discharged pack. I hope for you someone else has more tips otherwise it probably is a warranty case. Edit: Oh, I don't think it will solve your problem but maybe you can try recovery with another USB cable to rule the cable out?

I thought that the resistance of the 510 (and of the mod and all the other metal between the coil and the measuring points) is put out of play by the DNA board storing the 'cold' ref resistance. Only the TCR of the metal paths (from the coil down to the measurement points) will introduce an error. So if this is the case, the difference should be small at the first vape and increasingly get worse (<- English?) as the 510 and metal in the paths, heat up. Or do I make a mistake in my thinking (I know a bad 510 also introduces errors due to varying contact pressure but leave that out for now)?

I assume you did upgrade the firmware to the latest release and set the battery capacity to (3 cell LiPo and) 14.43 Wh? I guess you can try a USB recovery charge (Device Monitor -> Diagnostics -> Advanced -> USB recovery charge)? Edit: Corrected the recovery path

Well... I guess 'fairly' is the right term ;-) I added 86 MsgID's more (of which the previously mentioned 16 are not recognized). I took them out and put them in a text file: http://s000.tinyupload.com/?file_id=20146860099364243548

I just added v1.7 of the Dutch translation (see post #3). The following MsgId's are not accepted and are therefor not translated: #. General tab -> Atomizer Analyzer (already reported) msgid "For an atomizer to work reliably with temperature ............. being used for power control only." msgid "Many atomizer designs provide stable Ohms, but .............. will measure once per second." msgid "To test, slowly change how tightly screwed in your ..............atomizer Ohms should be stable." msgid "Note: Recent puffs may mean the atomizer is still ................will slightly warm the atomizer." msgid "{0} (Kanthal), {0} (Temp)" msgid "&Lock Ohms" msgid "&Unlock Ohms" msgid "&Override Ohms" #. Device Monitor --> Debug msgid "Bandgap:" msgid "Sample Ohms:" msgid "Sample Ohms (T.C.):" msgid "Modeled Temp:" msgid "Screen Disconnect:" msgid "Timer:" #. (The next two are not absolutely necessary but would make it perfect) #. General tab -> Ohms locked msgid "? (70 °F)" #. Theme tab msgid "All default screens Copyright 2015 Evolv Inc. For use only in Evolv electronics." Suggestion: If temperature is "off" in the profile, hide all the Material and Preheat settings. It would also be nice with future Escribe releases to include a full English EScribe.po file with all MsgId's. It would be a huge timesaver.

Yes/no, for the duration of the preheat time limit it will apply the preheat power but regulates this down if the temp minus 10 degrees is reached. After that it will regulate the power to keep the temperature, with the power of the profile as maximum limit.

I found the following in the video tutorial (so to add the numbers to the excellent explaination of VapingBad): The Preheat punch setting runs from 0 = 160°F to 11 = 10°F under the set temperature. EDIT: removed my wrong train of thought.

You did not do anything wrong: 2015-10-21 is the latest EScribe version (v1.0.35.2). 2015-09-30 is the latest firmware version. (these are pre-releases. In the first post you can find what is officially released)

In the device monitor; The position on the Y-axis where the measured values are positioned, is fixed. It would be nice to be able to set the position on the y-axis. E.g. by dragging the starting point along the y-axis to the point where you want. This request comes from the fact that If you change from Fahrenheit to Celsius, the resolution of the graph is dropped to about 50% (since 400F = 204C) I need to look at the puff duration to get an idea about the time scale. So another nice-to-have would be a time axis at the bottom, running along with the live measurements. (Off course this time axis needs to adjust according to the Graph Options -->Set Time Scale value) I know there are more important features that the developers need to be working on, so these can be put on the nice-to-have list and hopefully can be added sometime in the future.

I also see the "temperature protected' message more as information (that the temperature is regulated), than as an error message. In my opinion the biggest advantage of TC is not Dry-hit/high-temp prevention while trying to get the biggest clouds but hitting the sweetspot of evaporation for the duration of the puff (and thus getting the best flavor out of the juice). I made the simplified picture below explaining this benefit on a Dutch forumboard some time ago. Off course, this is my opinion. Everybody can use the settings he/she likes best.

Interesting idea but I can see the headlines in the Sun already: "Man gets stuck in a Park for 2 days because an E-cigaret drained his electric wheelchair". Lol

Hmm, before it was multiple lines in one msgID. Anyway, that did the trick. One down, one to go

Nice James, I feel honored. I have added the extra entries of EScribe v1.0.352 to the Dutch translation (file v1.6 see my post #3). I cannot get the following translations to work: Nothing connected window: everything except button labels (you already know this) Atomizer Analyzer window: explanatory text and button labels

Thanks for the input. I changed it in file v1.5 to "TFR-curve" and to avoid confusion, I also changed the "TCR-wikkeling" (=TCR coil) to "Temperatuurvoelende wikkeling" (=Temp sensing coil).

Couldn't find it in the spec's or on the forum but I'd like to know, just out of curiosity; what is the resolution of the resistance measurement? 0,001 ohm or even smaller? Off course the reason I couldn't find it might be that it is commercially confidential. In that case: I promise I won't tell anybody .

Thanks James. You're right 'look and fee'-entries were missing the colon's/period's at the end. I've corrected this in file v1.4 of the Dutch translation (see /topic/65610-topic/?do=findComment&comment=886856).