James

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.

Preheat Punch is a relative temperature (relative to the setpoint - 160F below at 1, 100F below at 5, and 10F below at 11). Preheat Temperature is an absolute temperature. If you use the Preheat Temperature setting, it is really only appropriate to set it to the liquid's boiling point. By doing so, preheat reduces time-to-vape while keeping the mass flow rate mostly based on the power setting. Most folks are not testing thermodynamics, however, so Preheat Punch is friendlier and generally good (it can't be misconfigured horribly). The option existed in all earlier version of EScribe 2.0 as well. It's just specific to DNA 75 Color.

Hi Lowbytes. Don't worry. On Windows, we support back as far as is practical - XP Service Pack 3. I intend to do a similarly good job of compatibility on MacOS. Guess I'll need to set up some virtual machines to test old versions of MacOS.. Hmm. Go to Applications with Finder, right click EScribe Suite.app and click Show Package Contents. Then, go to Contents, MacOS, and double click RunProgram. Doing this shows more information while the program is starting. What error (if any) does it show when you do this? Thanks! James

I've posted a beta version: It's restricted to DNA 75 Color at present. We will widen it to all DNA devices after working out most of the bugs public testing will inevitably find. Keep a Virtual Machine handy just in case, but this version has been fairly usable in my testing.

Hello all, For some time now, as time has permitted, I've been separating out and making platform-independent the Windows-specific portions of our EScribe code. About a month ago I finished this, and began porting EScribe to MacOS. Today, I believe the Mac port has few enough bugs to be usable. I expect this will have bugs. Please let me know what you run into. Also, I don't use Mac on a daily basis, so if there is anything that seems unnatural to you relative to ordinary Mac look-and-feel, please mention that as well. https://downloads.evolvapor.com/SetupEScribe2_SP13_US.pkg https://downloads.evolvapor.com/SetupEScribe2_SP13_INTL.pkg Enjoy James Revision information: SP13 - Updated to SP13. SP8 - Updated to SP8. SP6 - Updated to SP6. b13 - Updated to SP5.2. Fixes a number of MacOS-specific bugs. b12 - Fixes a DNA 75 Color SP25 scale bug. b11 - Fixes minor DNA 75 Color SP25 bug, and extends the beta to support DNA 75 and 200. b10 - Updated to SP5.1. This version fixes Available Materials not saving, ECigStats minimizing to the Dock, and other bugs. Includes DNA 75 Color SP25. b9 - Updated to SP5. This is the first version to also support ECigStats. Includes DNA 75 Color SP24, and extends the beta to support DNA 250. b8 - Updated to SP4.2. Includes DNA 75 Color SP23. b7 - Supports dragging files onto EScribe (.ecig), Device Monitor (.py), and Theme Designer (.ecigtheme). Includes revised DNA 75 Color SP22. b6 - Supports OS X High Sierra. Includes revised DNA 75 Color SP22. b2 - Supports OS X versions earlier than Sierra. b1 - Initial test release.

Do they have an About screen on this mod that shows what Service Pack it is running?

Send a serial command. F=60S will do a 1-minute puff, for example. On monochrome DNAs, F=#S (# being the number of seconds) sets a countdown timer. So, while it is firing, you can keep sending F=60S to extend the puff. F=0S stops the puff immediately.

Yes, the debug setting doesn't retain after power-off. It looks like the steady state power is different slightly. Am I seeing that correctly? Also, could you try an in-between value such as 0.04?

Howdy @ndb. Give this firmware a try. I think the issue is current offset when it's down at 0.5W. In Serial Terminal, X=GET COB gets the current offset. It is 0.025 by default on DNA 75 Color. On a DNA 75, it is 0.0625. Try X=0.0625 COB and see if it fixes the oscillation. I suspect it will. Thanks! DNA 75 Color v1_1_SP22_Beta2p2.sw-service

OK. Well that rules out X=READ DEBUG being the problem. Out of curiosity, what power level is it dropping to there? (To get to the recording, go to Device Monitor -> History -> Download All Recordings). It looks like a current offset issue, to be honest.

@ndb, if you go to Tools->Serial Terminal after having it pulsing like that, what does it say if you send the command X=READ DEBUG? Thanks! Also, for the rest of the folks trying that firmware, I'd be real curious what you get for that value after a while of normal use. (Sending the command resets it for the next time it's sent. No need to measure it every puff. I am wondering after a session what it is.) I'm expecting around -0.14 for temperature-protected coils, much less for Kanthal.

The attached beta firmware fixes the loss of Room Temperature modeling after uploading settings. Since folks tend to edit settings when things go wrong, this should mean a lot less incorrect 90F measurements. DNA 75 Color v1_1_SP22_Beta2.sw-service

With that firmware, you should certainly use a normal TCR like you would on a DNA 75. What are the board temperatures doing while the room temperatures are measuring like that, out of curiosity? Personally, I would try our default case thermals. I'm actually fairly skeptical of the DNA 75 Color Case Analyzer as it is implemented in the current Service Pack. In my opinion, its numbers are unreasonably high, and incorrectly aggressive thermals can definitely do what you are seeing. When I get time, I am going to investigate that. FWIW, if I am reading what you are doing right, you should know: when you measure Cold Ohms, it automatically takes Cold Temperature from Room Temperature. You don't need to do that manually.