James

This test version fixes the USB HID issue, but it's also based off a slightly newer, intermediate version. So, there are a few bugs. Still, if you're interested, give it a try. https://downloads.evolvapor.com/SetupEScribe2_2020-06-22_US_test.run https://downloads.evolvapor.com/SetupEScribe2_2020-06-22_INT_test.run

@blueridgedog: https://www.lvevapor.com/box-mod/

The problem with EScribe on Linux is (technical explanation follows): in its library HidSharp. Specifically, since Mono (and Xamarin) were purchased by Microsoft, they've been making the code on Mono act more like Windows. They altered how ICustomMarshaler operates on Mono (now its behavior matches Windows), and it broke HidSharp on Linux. Newer versions of HidSharp fix it. It's working fine on Linux in my development version. We could make an intermediate release for Linux, as long as folks are fine with it being explicitly a test version. Well, I guess this thread has always been named Beta Thread? :)

If that coil is 0.658 Ohms cold, the limit they have set of 0.7 Ohm will (if it is a temperature-sensing coil) not produce significant vapor. Is it marked as a 0.5 Ohm coil? If so, perhaps you got one that was well outside the appropriate variance. You could try upping the limit from 0.7 Ohm to 0.8 Ohm and see. (At your own risk.)

What is the resistance of the coil? Go to the Mod tab and click Atomizer Analyzer to see. You'll need to set EScribe to at least Advanced mode (Options -> User Interface -> Advanced). What is the coil rated at? There it looks like it's at about 0.67 Ohm.

The libudev crash, at least, I have fixed and just need to release a new update. (It appears Mono borrowed an implementation difference on ICustomMarshaler from .NET recently.)

If you go into Serial Terminal, what do you get as responses to these commands (after trying to fire)? I=GET OFFSET V=GET OFFSET Thanks!

What mod are you using? Also, would you please send the .ecig file of your settings? Thanks!

@AMDtrucking, you are still running SP35? Does it occur with SP38 for you?

On SP38? What theme are you running, out of curiosity? Could you message me your .ecig settings? Thanks!

When does Error Press Up happen for you on SP38? Is it after it has slept for a while, during firing, or..? Thanks!

@vaperneto, what firmware version is the 250C running?

I've updated the download. SP19 should be faster now than before. Let me know how it works for yall

I've updated the download. SP19 should no longer be extremely slow. Let me know how it works for yall

Unresponsive in what way? Just slow? Hmm. I've switched to a new code obfuscator and a newer compiler.

I've posted up SP19. This fixes a few small bugs in EScribe. It also includes early firmware for DNA 250 Color and DNA Go.

EScribe Suite 2.0 SP19 For US-based customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP19_US_ServicePack.exe For US-based customers (Mac): https://downloads.evolvapor.com/SetupEScribe2_SP19_US.pkg For international customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP19_INT_ServicePack.exe For international customers (Mac): https://downloads.evolvapor.com/SetupEScribe2_SP19_INT.pkg For customers using Linux, see the beta thread. --- DNA 250 Color (firmware 1.1 SP38) --- Fixed a firmware crash that could occasionally come up when the device had been idle for a while. Fixed spurious Temperature Protected errors that could crop up in certain high-CPU themes with Replay off. --- DNA Go (firmware 1.1 SP38) --- Fixed a firmware crash that could occasionally come up when the device had been idle for a while. --- EScribe --- In Display tab -> Device Monitor, 'Remove Readout' no longer crashes. --- Production Utility --- Firmware -> Browse no longer crashes. DNA Go now does Fire Tests correctly.

@mrphilip, the new version of EScribe Suite is compatible with Mojave, but it *should* work all the way back to MacOS Lion 10.7. Let me know if it does not.

@AnnaR., when are you seeing the Error Press Up in SP38? When the device starts up after a long sleep, or...?

Hmm. If you go into Tools->Serial Terminal, try the command X=READ BMS. That will clear out whatever battery-management errors it may have had in the past. Wait a while and send that same command again. What does it respond with?

If you would like to try it, this experimental firmware (SP38) may fix the DNA 250C Error Press Up bug that was introduced in SP35. Let me know if you still get Error Press Up when using it.

@mrdidit, do you mean Puff Count Since Reset? If you do "Reset Puffs", this goes to zero.

If you are encountering the issue mentioned in this thread -- spurious Temperature Protetected messages when using a high-CPU theme like Gauges, with a low-Tcr material [, and possibly, high Preheat settings... any of these three could cause the problem on their own, but it's much less likely] -- when using Temperature Protection but not Replay, and would be willing to try an experimental firmware, give one of these a go: https://downloads.evolvapor.com/DNA250Color_v1_1_SP38_US_test.sw-service (US Edition) https://downloads.evolvapor.com/DNA250Color_v1_1_SP38_INT_test.sw-service (International Edition) This won't help if your problem is related to your 510 connector or electrical grounding. Anyway, let me know how it works for you, if you run into any new bugs, etc. Thanks!

By any chance do you have Ohms locked on your wattage profile? What are your settings for that profile in EScribe?

@maximumsport, what device and firmware version? Thanks!