Jump to content

James Bellinger

Administrators
  • Posts

    49
  • Joined

  • Days Won

    15

James Bellinger last won the day on February 13

James Bellinger had the most liked content!

2 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

James Bellinger's Achievements

Member

Member (2/3)

28

Reputation

  1. That's correct. It's so themes don't have to have separate handling for temperature sensing and non-temperature sensing modes.
  2. If you want to experiment with coil materials with very little resistance change with temperature, you can go to Mod->Safety->Replay and choose "Allow on unlikely coils". It actually goes into a special Replay mode in this case if the other modes would not have allowed Replay on the coil. This is more for fun than everyday use, but if you want to, feel free
  3. If it works from EScribe, try opening Device Monitor. What does it say for its battery voltage? Are you able to fire with the Puff function from inside Device Monitor? (If so, the issue may be the screen.)
  4. Thanks for letting us know. This is fixed now.
  5. @stephanedegee: I noticed you mentioned in another post that one of your devices does it and another doesn't. Would you mind trying this when applying the firmware? Have Ctrl and Shift held down while you click Apply. It'll say "Core firmware can be updated, but doesn't need to be". Tell it yes so that it updates. The second time it'll ask the same (assuming it succeeds), and that time, tell it no, so that it finishes the update. I'm curious if there's some versioning issue going on here, as otherwise it's pretty strange how one device would work correctly and the other not. Thank you!
  6. Would you send me your .ecig file for that device so I can take a look? Thanks!
  7. @Magigamix, what device are you downloading settings from? That is not a Linux-specific error. Is it a DNA Go or Reflex by any chance?
  8. 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
      • 1
      • Like
  9. 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
  10. 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.)
  11. 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.
  12. 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
  13. 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
  14. 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!
×
×
  • Create New...