Everest

I made a post in the 'connectors, components and accessories' foum, but after doing some searching I found some threads using the keyword 'autofire' in this forum and thought I'd x-post here (hopefully a moderator can delete my thread in the other forum). I was sitting at my desk today, and suddenly my RDA erupted into flames. I yanked the side cover off my enclosure and pulled out the battery (a 3S 1300mAh lipo pack) and found it to be cool - I still chucked it out on the porch to be safe. Disassembling the device, no components seem to have fried, the fuse is intact. Checked function of the 'fire' button and it is correctly open/closed like a switch should. Then I checked continuity between the battery connector and the 510 connector - low and behold there is no resistance between negative battery / negative 510 and positive battery / positive 510. I de-soldered all the connections (board to 510, battery connectors) to check the naked board - and sure enough there is continuity between the battery +/- straight through the device to the output pads. According to some other threads, autofire can be caused by a connection between the via at the edge of the board and the output pad to the 510 connector. I cleaned up my pad with some de-soldering braid, and lo and behold they are solidly connected. The mod has been in service for ~8 months - what would cause these two to short? That solder pad shouldnt be getting that hot or anything. I'm thinking I need to cut the trace / use an exacto to separate the connection between those two pads. Anybody have any thoughts/tips for me?

I am not sure if this is the correct forum for this, apologies if I've posted it in the wrong place. The device is a DNA200 I was sitting at my desk today, and suddenly my RDA erupted into flames. I yanked the side cover off my enclosure and pulled out the battery (a 3S 1300mAh lipo pack) and found it to be cool - I still chucked it out on the porch to be safe. Disassembling the device, no components seem to have fried, the fuse is intact. Checked function of the 'fire' button and it is correctly open/closed like a switch should. Then I checked continuity between the battery connector and the 510 connector - low and behold there is no resistance between negative battery / negative 510 and positive battery / positive 510. I de-soldered all the connections (board to 510, battery connectors) to check the naked board - and sure enough there is continuity between the battery +/- straight through the device to the output pads. Any ideas regarding what component might have failed? So strange that it was literally just sitting on the desk, hadn't taken a puff in ~10 minutes, and it just went off.

Which firmware are you using? My DNA200 ignores serial commands for puffs in excess of 20 seconds.

I am interested in removing the 20 second per-puff activation limit. Is there a way to put the device in continuous operation mode?