James

Could you try (from Tools->Serial Terminal) sending I=GET OFFSET and V=GET OFFSET commands on the downgraded version? I am wondering if your particular mod has a high offset. Thanks!

Does this happen in other profiles, or just Watts? Thanks!

Just want to rule something out... If you go into Tools -> Serial Terminal, what does it say if you send the commands I=GET OFFSET V=GET OFFSET ? (You will need to have fired a coil at least once for these values to not show up as 0.000.) Also, how did you power-up your device from cold? From USB? Fire button not connected to USB? Most importantly, what happens to the current and voltage offsets above if you send the command R=SAMPLE OFFSETS ? I get -0.101A and -0.033V the first time around, and -0.109A and -0.031V the second. Thanks!

Out of curiosity, what theme are yall running? Does this happen when you are not charging on USB?

Hmm. I know DNA Color allows puffs over 20 seconds. I'd thought monochrome DNAs allowed it too. That said, you can extend a puff by reissuing the fire command. F=15S, sent more often than every 15 seconds, will fire continuously for instance.

SP23 should fix the battery meter issue. PC: Mac:

For those interested, I've posted up a new early version, EScribe Suite 2.0 SP4.2. It includes SP23 for DNA 75 Color, as well as some improvements to Device Monitor. Let me know if you run into any bugs. Enjoy James

I've posted up a new test version. The link is on the initial post in this thread. It brings the Mac version up in line with EScribe Suite SP4.2 on PC. Let me know if you run into any bugs. Enjoy James

Yes, the early firmware SP22 has a bug in its Battery % (Cell Voltage should be fine). I had rewritten some of the code relating to that, and forgot to make it calculate Battery % when not connected to USB. Sorry about that. If all goes well (it is in testing), I'll be releasing a fixed version tomorrow.

We had to have a menu for the Mac version (folks expect Quit Device Monitor to be an option for the program menu, instead of clicking X like on Windows), so I decided to move a number of options up there. CSVs have been moved to the Recording menu. Time scale has been moved to the View menu.

Hi all, I've put in the Dutch and Portuguese translations. They are included in EScribe 2.0 SP4 (see the early firmware thread). A lot of people will be very happy you've done this. Thank you! @pol, I would like to include your Polish translation as well, but I have some concerns. For example: msgid "&Connect..." msgstr "&Połącz przez USB..." msgid "If you connect a temperature-sensing coil..." msgstr "Konfiguracja trybu kontroli temperatury - TC // Wstępne rozgrzanie - Preheat //" msgid "Temperature Coefficient of Resistance (Approximation)..." msgstr "Współczynnik temperaturowy rezystancji TFR (przybliżony)" Connect doesn't necessarily imply USB. We may have other means of connecting to devices in the future. I'm not sure what is meant in the middle one, but I notice preheat.. What is the connection? The last of these generates a material curve from a TCR. Thanks! James

Coil resistances change, for example as the coil ages. Also, between different coils. Power ("wattage") is a thermodynamic variable. Voltage is not. Disregarding losses, once you are at the liquid's boiling point, the mass flow rate of a vape should be the the power divided by the specific heat of vaporization. Consistent power makes a consistent vape. With variable voltage you end up having to mess with resistance, and you aren't going to pull out a multimeter while the coil is hot. With variable wattage you should get a consistent vape. There are unaccounted-for variables, like the heat losses of the tank, etc. but it's a lot better.

I've posted EScribe Suite 2.0 SP4 as an early version. It includes SP22 for DNA 75 Color, which resolves a few issues mainly seen with Stainless Steel coils. A lot of low-level rework has been required to support the upcoming Mac version, so definitely let me know if this version acts quirky in any way. Enjoy, James

Battery curves affect the battery meter accuracy but do not affect battery life or performance at all. Weak Battery means the battery voltage has dropped down to 2.75V (Mod -> Battery -> Soft Cell Cutoff) and the device is reducing power to a level the battery can handle so that it can use the rest of the battery's charge. Hmm. Looking at https://www.e-cigarette-forum.com/forum/attachments/image-jpg.523804/ the 30A discharge barely touches 2.75V except at the end. The 15A discharge, https://www.e-cigarette-forum.com/forum/attachments/image-jpg.523764/, should hold 35-40W all the way to the end of its capacity. (Are you sure the batteries you got are genuine and brand new? Hmm, other ways you could get voltage losses... is the battery contact good and the wiring reasonably sized?)

Could you PM me your .ecig file? Curious if there is anything unusual with your settings.

Hmm. Does Atomizer Analyzer consistently say 0.609? Also, is it a commercial atomizer? If so I'll order one for testing. What kind of resistances are you seeing while firing?

Could you try resampling your Cold Ohms?

This is happening because, when the device just powers on, it assumes it has been off for a while, meaning that the device is basically at room temperature, and so the room temperature is the board temperature. SP4 (early firmware thread) fixes the loss of room temperature after uploading settings. Hmm. Loss of room temperature at battery swap is a tricky one. I'll have to think on it. We do have a real-time clock on the DNA 75 Color, so I probably could do *something* about this.

What are you trying to do? I can't see any vaping-related reason to use voltage instead of wattage. That said, it's more of a debug feature, but on DNA 200 or 250 running 1.2 SP3 or newer, you can limit the maximum voltage. Sending the serial command V=6V, for instance, clamps the voltage limit at 6V. You can then set the power high enough that it always hits the voltage limit.

I've posted up a version that should be compatible with OS X High Sierra b3. @ndb, let me know if it fixes your firing problem, by the way. Thanks!

Mm. OS X High Sierra b3 evidently breaks all 32-bit MonoMac applications: https://bugzilla.xamarin.com/show_bug.cgi?id=58110 Hopefully they'll fix the bug before release. On the plus side, I don't use Core Location at all in EScribe, so for now I'll work around it by changing the MonoMac binding.

@ndb: I found what I believe to be the root cause of the issue you're having with it failing to fire. We are testing it now. @peraspera: You can exit the program by clicking the red X. I'll see what I can do, though, as it strikes me that's how folks quit programs on Windows, not Mac. @GamulinAO, @znapr: Could you try going to Applications in Finder, right clicking, selecting Show Package Contents, and let me know what error you get from running Contents/MacOS/RunProgram? The error message from that will tell me more definitively what the problem is. Thanks!

Hmm. Thanks for reporting this. I had noticed an occasional Temp Protect myself, and have noticed Peak Temperature occasionally reading wrong. I think it might be misreading when it's down at 1W or less before firing. Will investigate on Monday. In the meantime, FWIW, the Mac version should run on SP21 just as well.

Excellent! I am glad it seems to work on 10.9. I don't know of anything that shouldn't work at least back to 10.8, but like the El Capitan compatibility issue, it remains to be seen. I've set the Mac version to offer a new Service Pack download now, to test the updater functionality. The Service Pack extends the beta to support DNA 60, so that we can work out bugs on the monochrome side as well.

@peraspera, @Lowbytes: I've updated the link with a version that supports OS X El Capitan. Let me know how it works for you @ndb: EScribe caches data the first time it downloads it to speed up future downloads. (Though, I should probably include a pre-filled cache with the download.) So, the first time it is fairly slow. COB is 0.63? It should be 0.063.