James

Oh, I see what you mean. I thought you meant the dock icon. Yes, it appears to show on the right side. I'll have to fix that.

@embe71, it doesn't show in the dock for me in Sierra. What version are you running? I've fixed ECigStats on Safari. Thanks.

I've posted SP5 as an early release. It includes SP24 for DNA 75 Color, which improves resistance sampling accuracy. The Mac version (in a separate thread) supports ECigStats now, and also DNA 250. @MacVap, this version should fix your firewall issue.

Well, I finally got ECigStats ported over, so the Mac version is nearly feature-complete at this point. We haven't run into nearly as many bugs as I thought we would, or at least, nobody has reported them yet. *knock on electronics* There are a few cosmetic issues that annoy me, and Serial Terminal is not fully functional, but so far, no show stoppers. If I had to guess, I'd say about a week.

I've posted Mac EScribe beta 9, which is EScribe Suite 2.0 SP5, in the first post of this thread. It extends the beta to include DNA 250 and adds ECigStats support.

@Lowbytes, out of curiosity, what is V2ASteam? Is this the same curve you are using on other devices? It is not SS316.

@Lowbytes, could you attach your .ecig file? I am wondering if your material curves are somehow off.

@Lowbytes, what do your other DNAs read? Also, what is your preheat punch set at? (I am guessing 11?)

Could you save and attach your settings .ecig file? Thanks!

@Nicolasan, It stores Ohms in 1/8192ths. That is actually 25/8192, rounded up for display.

@67exec, make sure you resample Cold Ohms. The correction is small enough it won't necessarily ask New Coil? on its own. With incorrect Cold Ohms from earlier Service Packs it will be slightly cold. Also, do your other devices have a mod resistance set? We default the 75 Color to 0.004 Ohms.

Here is a firmware to try, SP24. We'll be including it soon with EScribe Suite SP5. It fixes some issues with resistance sampling, which may help here. DNA 75 Color v1_1_SP24.sw-service

The device can't measure USB current. It estimates it by the USB voltage. Current is conserved so there is no such thing as missing amps. The estimate may not be perfect for some chargers, though. It doesn't affect the vape. That said, I've ordered an AmazonBasics charger so I can take a look at what it does.

To be fair, the USB current on 75 Color is an estimate based on voltage drop, mostly there to help the case thermals. Most of mine were more consistent than that, though. I'm going to order some of the chargers you mentioned.

USB voltage drops as charging increases, so it's not surprising to get 5.246V (that is as high as we can read) when it is not charging. There isn't anything necessarily wrong there. I've ordered the US version of that travel adapter.

I've found and fixed the bug where adjusting one field can sometimes shift to adjusting another. (As an aside, this bug looks to be older than SP23.) The fix will be in the next Service Pack. Thanks for reporting this!

This morning I've coded named pipe support on Windows, so it'll use that instead of running a local-only server to communicate between the parts of EScribe. Let me know if the next version still has this problem.

What firewall are you using? I'm really shocked any would block loopback binding. The particular error you are seeing is not EScribe trying to access the Internet. It is a loopback bind operation -- running a server that can only be connected to from the same computer. For portability with Mac, we can't multithread the user interface any more, so instead I split apart each program into its own process (like Google Chrome does for tabs). For instance, when you click Device Monitor, EScribe binds a local socket and runs a server on it, creates a new copy of itself to run Device Monitor, and tells the new copy to connect to that server. Upon connection, it is told what device to connect to. Theme Designer needs to pass back the theme being edited to EScribe, etc.

Hmm. Well, if you could find out the specific charger I'd appreciate it. I found out that the Charge Status coming from our charging chip was not always accurate (for example, previously it would not switch back to Charging if it finished charging and you kept using it without plugging back into USB), so I now calculate whether or not it is charging. This is a bug fix, and should work better. The chargers I am using all work, but if I can find a charger it does not work on, I can fix it. Thanks! James

What charger is he using? I will order one to test. Thanks!

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.