Phone Guy

Have a fresh board in a 250c mod just built, everything is working fine. Connected to escribe and adjusted settings accordingly. But for some reason the board does not respond to the fire button being pressed half of the time? While connected to device monitor, I can see when it vapes correctly and everything looks right. When the misfire happens the only drop I see is the voltage but only for a split second. Just enough to let me know it recognized the button press. It takes two or three presses to vape. Ive built quite a few mods, never had this happen before and I am stumped. Any ideas on how to try and diagnose? Here is a picture from device monitor, the first dip is a button press with no vape, the next two are button presses with vape.

I'm retrofitting a DNA 250c board into a 2 cell enclosure. Will a 250c charge the 2 18650 batteries without the jst connected? (The jst that connects to the individual cells) If the jst is needed, I'm not sure how to wire them correctly? This mod (dovpo Riva something) has the bottom flap shorting the 2 cells to complete the circuit. So the + and - are connected on that flap.

Why not post it? Are you worried someone might say something about the color scheme? Something like that is a very bright color? Were you worried some one who knows you might say something? Someone who picks on you from time to time? I don't know? Someone like me!? ? LMAO. Seriously though, it's a cool looking box. I have a 3d printed box I liked a lot and the wife kind of took it over (ie: she stole it from me oh well). While I'm not a fan of 3d printed boxes in general, they are crazy light weight and that makes them great! At least in my opinion. I'm curious how you'll seal it, I have found that lighter colors pick up dirt, grime, oils, etc like a sponge. The one the wife has is dark so it holds up. But I'm no expert. Nice case overall. How do you like it?

Updated my Vaporshark Vaporflask 133 to SP3. This is the new flask I got directly from VS during the labor day sale. No problem except battery meter showed zero, instead of soft reboot, I tried to upload settings back, battery meter was still zero so I pulled a battery and put it back in and it came back to life (battery meter came back on). I tested the charger and it is charging at 2a.

I just wanted to keep everyone posted on this for those who are interested. I ordered another Vaporshark Vaporflask DNA 133 over the weekend. I emailed Vaporshark repeatedly asked if the shark flask 133 would safely accept the SP3 firmware without causing any issues. I was assured it could upgraded by the end user to SP3. For the record here is the email I received today. (I asked if they could upgrade the device for me and test it before sending it out, they could/would not)

I've got a couple of the older dna20 opus boxes with the temp wheel not the 2 up/down buttons. We've upgraded it from dna20 to dna30.. But couldn't go beyond that. Is it possible to use a potentiometer wheel dial on anything >dna30 (ie: dna40, dna60..?) Thanks.

FWIW, I contacted Vaporshark and they emailed me back saying the Vaporflask 133 would be able to be upgraded thru escribe 1.2SP3.

If that's the case, I can't imagine why specifically the vaporflask 133 would brick after upgrade. That even further makes me believe it was just random? Have others with a 2cell (133w) setup/configuration had issues after upgrading firmware? Can anyone verify?

Not only did I tell them the truth, THEY tried to update it and connect it to escribe in the store in an attempt to resurrect it. They downloaded a version of Escribe (I couldn't see which version), installed it, connected it, I know I heard them say something about "reset" (they were talking to each other in store) but I already knew none of their solutions would work since I had already tried (well documented above). The only thing I didn't specifically tell them was I tried several firmware's trying to bring it back to life (ie: downgrading, re-upgrading, etc) *IF* there is an issue specific to the VaporFlask 133 and firmware update's, I would SERIOUSLY like to know, because I fully intend to buy another one. I'm hoping for some Labor day online sales this week actually... if they would have had another one I would have exchanged it in a second... I was a little bummed getting a refund - but.... I am hoping someone here who either HAS a VaporFlask 133 who can verify an update process, or the Evolv guy's can verify the firmware update either works or doesn't work.

Returned the Vaporflask - had the option of getting a new one ordered in which would have taken a week, or refund - which is what I opted for. The folks who work there are nothing short of awesome. I'm still convinced it was just a bad board... Just a lemon. Honestly, if they had another unit in stock I would have simply exchanged it for a new one, but alas - that wasn't in the cards.

I've been searching around, and NO WHERE have I found anything that says to avoid upgrading the firmware on the vaporflask 133. In fact, in every listing it clearly says its firmware upgradeable via escribe and microusb. I can't seem to find any specific vaporshark or vaporflask firmware(s) anywhere...? @dwcraig1 - I guess it could be from the reboot? but I know on every mod I have upgraded thus far, they've all required a reboot or the battery meter shows 0% - and a reboot restores it to working order and no lingering problems (knock on wood). I did upgrade a DX200 and NOT reboot it in escribe, but I pulled the battery off and put it back on, the battery meter came back on properly. And YOU know me, I have a bunch of mods... A BUNCH.... at least a dozen DNA200's alone between me, the mrs, the sons, their wives... I've upgraded a bunch of mods. @chunkybutt200 - If the vaporflask 133 is so fragile that the user is not able to connect to escribe, well... that's unacceptable. Honestly the only complaint I ever heard about vaporshark was about the coating peeling off. But I have to be honest, I'm super disappointed in this whole transaction. I know I'm whining but I can't help it. to all you guys, I hope I'm not coming across as rude - not my intention.. just frustrated. THANKS FOR ALL OF YOUR HELP FELLAS!!!!!!!!!!!!

So has ANYONE with a Vaporshark made Vaporflask DNA133 successfully upgraded firmware to SP3? I see a few reports of the VS DNA200 (the square box mod), any successfully upgrade the Flask? Is this one a dud or is it the firmware is legitimately incompatible with something in the Vaporflask 133?

I can't tell you and everyone reading this how bummed out I am. I debated on buying this like a child, talked myself in to it, and it lasted about an hour. Now I have to go BACK to the store (45 mins away) and probably get some retail double talk about getting a refund... they'll probably try to talk me into getting in warrantied, etc... MAN! what a BS deal. OH WELL. For the record, I've been running SP3 on several other mods (all 3S lipo) without incident.

Battery pack info: Cell 1: 0.00v Cell 2: 5.19v Cell 3: 0.13v (bouncing around a lot) The 2 batteries in there are VTC5 fresh off the external charger, and I have verified each one is full on another mod. Also remember - the Vaporflask was working all the way home, with 2 batteries the store threw in for me. I vaped it 45 minutes or so home. The battery meter was full or near full (I don't remember if it was showing a % or not?) then when I got home I had the brilliant idea of upgrading to SP3, that's when this started happening. Again, I've gone thru 3 firmware upgrades/downgrades/installs... no change in behavior. Soft reboot, hard reboot, restore factory defaults, no change in behavior. The store said I had 7 days to return it for a refund, but I can't believe the Vaporflask 133 had some specialty firmware? and it wouldn't be compatible with Evolv updates? I mean if that is the case, then this mod is not for me anyways.... I upgraded 2 of my DX200's, ERM+ and a brand new Efusion DNA200 all the SP3 over the last couple of days, no issue whatsoever with the exception of having to soft reboot them - but after that, no problems whatsoever.