James Bellinger

I've updated the Web version of ECigStats to fully support Oxva Pro 2 DNA. In the event that you don't have a PC with EScribe available, you can now use it to look at your puff history, etc. (Previously Web ECigStats only supported the device summary, and barely that.) Obviously, unlike the PC version, it can't stay installed on your system to automatically synchronize puffs when you connect, so it only synchronizes them when you visit the website. But, it might still be useful to you. *shrug* This is compatible with any WebHID-enabled browser, which effectively means Brave, Chrome, Edge, and Opera on desktop operating systems (PC, Mac, Unix, etc.). It's at https://www.ecigstats.org, or the "My Devices" link in the upper-right corner of the Evolv website. Definitely let me know if you run into any bugs with it -- wildly incorrect timestamp recovery, duplicate puffs, etc. Enjoy God bless. James

Hmm. What firmware version is your Pro 2 DNA running? If you go to EScribe and click Tools -> Show Diagnostic Information, it will show the firmware version. If it is Service Pack 128 or newer, it records puff traces. It'd be useful to look at those. If you wouldn't mind, go to Tools -> ECigStats, and let it sync your puffs. Then click Link to Account, and then "Share with Evolv Support". If you enable that, we could take a look at the puffs and see if any information can be gotten from that. (You are definitely using the "Anti-Burn" coils, yes?) If you are running an older Service Pack, if you could update it to that one and take some puffs, and then plug it in and let ECigStats sync those, we could look at them. You can look at them too actually if you want to. In ECigStats, if you click My Device after it's synchronized, it'll show the puffs and when you click on them, it'll show their traces. The device can store a few hundred, so if synchronized fairly regularly it won't lose puffs. By the way, have you tried the Replay feature? How did it work for you? Thanks! God bless. James

By the way, have you been encountering "Fill Pod" errors on the Pro 2 DNA, outside of when the pod really needed filling / was an old pod? (I made a separate test version to address that. I am wondering if it'd be worth making a Linux version of it.)

Hmm. I have some concerns about the stability of the GTK 3 version. I haven't seen it arbitrarily close outside of firmware update, so I may have to dig into that. The problem didn't exist in the GTK 2 version -- that was solid.

All right. Let's try this again. I found that the Debian and Arch versions of GTK Sharp 3 were seemingly not compatible in some ways. So, this version gets rid of the dependency on distribution versions of GTK Sharp, and instead includes the GTK Sharp fork on GitHub, which doesn't depend on distribution-specific files. It's got its own set of bugs, but it *may* be consistent across Linux distributions. I tested it on Mint Linux and Manjaro Linux, and it worked on both of those. Here's the download: https://downloads.evolvapor.com/SetupEScribe2_SP69_INT_GTK_Test2.run Known bugs: ECigStats seems to not even run in this version. Let me know what bugs you run into. Thanks! God bless. James

That's very interesting. When this happens, do you have it charging from USB? If so, when updating firmware, which version are you updating it to? (Tools->Diagnostics->Show Diagnostic Information) Have you tried the firmware update included with EScribe Service Pack 69 yet, or are you running an earlier EScribe (Help->About)? Also, have you tried a hardware reboot on the device? (Remove the pod and disconnect from USB. Then hold the Fire button until it reboots. It should take about 10-15 seconds.) Thanks! God bless. James

SP69 adds trace recording (showing the actual puff waveforms... well, a 8 Hz version of them). If you sync your puffs with ECigStats, what do you get for the puffs that say Fill Pod? Could you click "Download Puff" for the particular puffs and attach the CSV files here? Thanks!

@John R: Thanks! I've fixed it.

I've posted SP69. It corrects one possible cause of Fill Pod messages on Oxva Pro 2 DNA, which could occur if Replay is activated on the first puff after connecting a pod. It also adds puff trace recording support. This records Power, Live Ohms, and Battery Voltage for puffs sent to ECigStats, so, you no longer have to be connected to USB to see your puff trace. Let me know how it works for you. Enjoy

EScribe Suite 2.0 SP69 For US-based customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP69_US_ServicePack.exe For US-based customers (Mac): https://downloads.evolvapor.com/SetupEScribe2_SP69_US.pkg For international customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP69_INT_ServicePack.exe For international customers (Mac): https://downloads.evolvapor.com/SetupEScribe2_SP69_INT.pkg If you would like the Oxva-specific version, https://downloads.evolvapor.com/SetupEScribe2_SP69_OXVA.exe For customers using Linux, see the beta thread. --- Oxva Pro 2 DNA --- This version may reduce the frequency of Fill Pod errors when using Replay, when Replay is set on the first puff after connection. This version also adds puff trace recording to Oxva. You can view puff traces on ECigStats. It records Power, Live Ohms, and Battery Voltage. (We're hoping to use this recording to see how effective the Fill Pod change is. That said, it's also a nice feature -- you don't have to be connected to USB any more to get a recording of your puffs!) Definitely let us know how it works for you! Enjoy --- EScribe Suite --- Bug fixes.

This was my concern about porting to GTK 3. The C# bindings have been in beta forever (effectively abandonware), so each distribution is likely to have a different version with different functions. Give this a try: https://downloads.evolvapor.com/SetupEScribe2_SP69_INT.run I changed how I register for the monitors changed event. I'll bet you'll have some other error, but it should take care of that one. My version of GTK Sharp 3, on Mint, is 2.99.3-4. What does it list as your version? Also, what's the specific OS version, etc.? I've not used Arch Linux before, but certainly could give it a try in a virtual machine. Thanks! God bless. James

I've ported Linux EScribe SP68 from GTK 2 to GTK 3. Some newer systems didn't have gtk-sharp2 easily available, so this should make those systems usable. *This is still a test version*, but if you'd like to try it, let me know what bugs you run into! https://downloads.evolvapor.com/SetupEScribe2_SP68_INT_GTK_Test1.run The bugs I've found so far are: (1) Multiline labels such as in Atomizer Analyzer don't lay out correctly. (2) Text fields with escape codes (such as Format and Label on Small Screen Pod devices) don't save properly. (3) Occasionally, dialog boxes are misaligned relative to the window that is showing them. Enjoy God bless. James

By any chance, is there a contact pin on your Oxva that is stuck down? We saw that once -- it caused poor electrical contact -- and because the electrical current is higher on the Stainless pods, the power losses from poor electrical contact are higher.

That's only 19% over cold, so it shouldn't be hitting any limits. I see you're using 1W extra -- do you find the coils taste about the same at that level? You still have headroom to increase it if need be.

Would you mind checking Cold Ohms and Live Ohms as well for the recording? It only has Power right now, from which I can't make a huge number of conclusions. (It only records the columns you have checked in Device Monitor, plus time.) Is your Power Setpoint 18 in all of these? (It's not recorded.) I do notice in the "Worst Mod" cases, the power is clearly declining, which suggests it is hitting a limit of some kind, but hard to tell only from that. What will be interesting to see is what the percentage difference is from Cold Ohms to Live Ohms in the "Good" case. That'd tell you how close you are to the "edge" (24% for the Stainless coils at current presets). Thanks!