wojzilla

Same issue too - "unable to read eprom" Didn't think to check the original version but applying the service pack fixed it

Champion! Cheers

All makes sense to me, I just wish I paid more attention to the lipo battery levels to get a better understanding. Do they get less sag under load? What i'd like is for the battery level to show 10/20% before it hits "low battery" but i guess that's dependent on power being put through it.

So I've changed my mod to 2x18650 from lipo. I've loaded the LG HE2 curves in this thread and I'm finding I get "Weak Battery" warnings when the capcity is at 40% When I had a lipo i could "run it dry" ie down to 0% or close enough to. 2x Samsung 25R 2600 mAh Calculated capacity 21.84 Wh (2Cell) Voltage on Cell 1 3.71 Voltage on cell 2 3.71 Pack voltage 7.42 when firing Cell 1 3.09 Cell 2 3.16 Pack voltage 6.25 firing Watts 111.8 Looking at the cells when firing i can understand why i get weak battery warnings but the battery life seems so much shorer than when using a lipo - is this normal? Without hard stats it feels that the DNA doesn't last as long as say an x-cube 2 Does anyone have a curve for Samsung 25R batteries?

Ahh snap! I opened a support ticket with them last night, maybe do the same - forums would get less of a priority over tickets http://helpdesk.evolvapor.com/index.php?

I've got a support case open with Evolv, I need to solder a battery back in (wasn't keen to leave one hooked up with device doing odd things) and get back to them with the output of Device monitor as it auto fires. Hoping to get time tonight. Shame yours won't charge (mine appeared to be the same) Did it also stay on like mine (ie wouldn't go to sleep) or change Fingers crossed it's a software fix

yep 100% sure - even took it out of the bezel (using Mamu's off shapeways) and out of the enclosure. Thanks for the suggestion though - I have contacted Evolv's support - hopefully they have a fix. I have seen a few posts with similar (not the same) issues.

Presets checked, all looks fine - fires ok when controlled by EScribe, has issues when controlled by the board.

Can you fire it with EScribe? Be careful though - if the issue is the same as mine it will auto fire after you upload settings to it - I would make sure you can take the atty off quickly (and probably best not to have it on as you upload/restart the device) Here are my findings /topic/67248-topic/

By any chance is your issue similar to mine here. /topic/67248-topic/

Battery unsoldered and board removed from enclosurestill flashes Check Atomizer when plugged in to USB (same as observed in my first post)Fire button = no change on screenUp = Check Atomizer (as if it's trying to fire)Down = check atomizer (as above)Rolled back firmware to 2015-08-07 Ideas?

EDIT: In my haste i posted in the wrong subforum - could a mod please move me where I need to go? Hi All, I have a custom built DNA 200 that auto fired (ended up pulling the RDA off) It worked fine the following day but now it is very slow to register button presses (if at all). Using the device buttons I can't lock/fire/adjust watts/temperatureWhen I control it with E-Scribe it works fine (firing/adjustment)The display doesnt go to sleep - stays at full brightnessWhen charging the display doesn't change to the charging screen either.I have tried a soft boot and hard bootThe battery is soldered onto the board so I haven't tried cutting power.If I have an RDA connected it will auto fire after i upload settings to device or if there's no RDA connected it will flash check atomizer 19 times.No idea what wattage it fired at (set to 80 watts) however the dual Stainless Steel coil ended up melting at the screw terminals rather quickly (and thankfully stopping firing)Atomizer Analyzer always reads 0.2 ohms, screen shows 0.00 Firmware version installed 2015-08-21