Auto fired and now not responsive

[wojzilla]

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/temperature
• When I control it with E-Scribe it works fine (firing/adjustment)
• The display doesnt go to sleep - stays at full brightness
• When charging the display doesn't change to the charging screen either.
• I have tried a soft boot and hard boot
• The 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

[wojzilla]

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

Ideas?

[Podunk Steam]

Check your presets for wonky settings? 

[wojzilla]

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

[blueridgedog]

And you are certain that the assembly is not putting pressure on the fire button...i.e. you can press it and note that it is "clicky" and not depressed constantly?  If it auto fires and there is no actual pressure on the button, then you will need to return the chip/mod.

[wojzilla]

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.

[raul_q]

Hey did evolv answer you about the problem? I'm having the same issue here.

[badow24]

Hey got the same problem wojzilla. Ever figure out your problem?