Early Firmware and EScribe Suite Discussion Thread

[retird]

BevoLatte said:

All I changed was the mod resistance and thermal settings.

Did you run Case Analyzer to get the thermal settings and did you zero out the Mod resistance and use a "tool" to get the true Mod resistance?

Sounds like therein lies your issue....  What were the setting before changing them?  And after changing them?

[Phone Guy]

At a loss here...

Just got a brand new vaporflask dna133 from the vapor shark store. It was working fine, I vaped on it all the way home with ZERO issues.  Got home and hooked it up to escribe 1.2SP3 to update the firmware, it connected and updated firmware no errors.  Now it only stays on when the fire button is pressed or the usb cable is connected to escribe.

As soon as you let go of the fire button the mod and screen dies... press and hold the fire button again, the board initializes - I see the vaporshark welcome logo, and if I continue to hold the fire button down, it come up and initializes fully, I see all the screens and it will flash check atty since I'm firing it with no atty attached, but as soon as I let go of the fire button it goes out (dies) like I pulled out the batteries.

If I fire it with an Atty attached it says CHECK BATTERIES.

I have verified the cells are set for 2-cell operation, I have tried soft reboot, hard reboot options in escribe, new batteries, etc... (and yes these batteries are fully charged)

The get information button says mod was configured June 1 2016, board programmed January 15 2016. 

So far I have tried SP3, SP2 and 02-23-2016 (all 383k each file)... the other 2 firmwares in the folder which are 192k each will not program to the board.  The 02-23-2016 firmware gets the board stuck on UPLOAD SETTINGS screen and won't change, so I have to install SP2 or SP3 - neither of which work.

Everything was fine before the firmware update. Now the mod is useless.  ANY SUGGESTIONS?

[Spector NS5 RD]

Phone Guy said:

At a loss here...

Just got a brand new vaporflask dna133 from the vapor shark store. It was working fine, I vaped on it all the way home with ZERO issues.  Got home and hooked it up to escribe 1.2SP3 to update the firmware, it connected and updated firmware no errors.  Now it only stays on when the fire button is pressed or the usb cable is connected to escribe.

As soon as you let go of the fire button the mod and screen dies... press and hold the fire button again, the board initializes - I see the vaporshark welcome logo, and if I continue to hold the fire button down, it come up and initializes fully, I see all the screens and it will flash check atty since I'm firing it with no atty attached, but as soon as I let go of the fire button it goes out (dies) like I pulled out the batteries.

If I fire it with an Atty attached it says CHECK BATTERIES.

I have verified the cells are set for 2-cell operation, I have tried soft reboot, hard reboot options in escribe, new batteries, etc... (and yes these batteries are fully charged)

The get information button says mod was configured June 1 2016, board programmed January 15 2016. 

So far I have tried SP3, SP2 and 02-23-2016 (all 383k each file)... the other 2 firmwares in the folder which are 192k each will not program to the board.  The 02-23-2016 firmware gets the board stuck on UPLOAD SETTINGS screen and won't change, so I have to install SP2 or SP3 - neither of which work.

Everything was fine before the firmware update. Now the mod is useless.  ANY SUGGESTIONS?

i think if you roll back the firmware to before the "SP" ones and it gets stuck on upload settings, i think you have to actually press "upload settings" in the older version of escribe (2-23-2016). i think that's what i did and it worked. but what's strange is why the SP3 didn't work. you're sure it was set for two cell AND UPLOADED TO YOUR FLASK? maybe it just said 2 cell in escribe and it accidentally got changed in the mod. i dunno, i'm grasping at straws here.  

[Spirometry]

To go back to 02-23-2016,  you need to remove the "Watts" material off of the device. You can go into the materials tab and remove it manually or you can do a Restore Defaults.

Don't mess with sp2, it has a problem with Vaporshark's 2 amp charging.
 

[Phone Guy]

ChunkyButt200 said:

i think if you roll back the firmware to before the "SP" ones and it gets stuck on upload settings, i think you have to actually press "upload settings" in the older version of escribe (2-23-2016). i think that's what i did and it worked. but what's strange is why the SP3 didn't work. you're sure it was set for two cell AND UPLOADED TO YOUR FLASK? maybe it just said 2 cell in escribe and it accidentally got changed in the mod. i dunno, i'm grasping at straws here.  

I have tried that, I even used another laptop with escribe 1.0.42, uploaded the pre-sp# firmware (02-23-16), same thing.  I did a restore defaults, no change.

I have manually set the battery to 3-cell then uploaded, reboot the mod... then set to 2-cell, reboot the mod... so I know for a fact the mod is set to 2-cell, but there is no change in the behavior... still doesnt power up. It is acting like its stuck on 3-cell mode (I guess?)

[Phone Guy]

Spirometry said:

To go back to 02-23-2016,  you need to remove the "Watts" material off of the device. You can go into the materials tab and remove it manually or you can do a Restore Defaults.

Don't mess with sp2, it has a problem with Vaporshark's 2 amp charging.
 

I never even added watts to the device in materials. But I verified its not there. as I mention above, I have let both the newest escribe SP3 and 1.0.42 do firmware upgrades and FACTORY DEFAULTS, but nothing changes on the mod - still acts the same way.  I have updated several DNA200 to SP3 without any incident whatsoever. The only thing I've ever had to do was reboot the mod under tools...soft reboot, thats it.  I've done at least 5 or 6 mods all DNA200.

This one completely crapped out on me and I literally bought it and drove home with it... also for the record, it was new from the vaporshark store (which I didn't know we had a real vapor shark store here? lol) I paid retail plus tax. I'm incredibly bummed out right now.

[dwcraig1]

Are your cells/pack showing correct voltage in Device Monitor?

[Spector NS5 RD]

will the mod connect to escribe with or without batts? what are your cells reading in device monitor? pack voltage?

well....if you can't get it straightened out, i know VS has a great warranty service. up to you whether or not to tell them your situation about the sudden death with the FW update. not sure if VS approves of the SP3 update. but it's basically the same board as the VS 200 just configured for 2S operation. i'm running SP3 on my VS 200. it's working just fine. so why it's not working is very strange.

[Phone Guy]

here is a video of what its doing.... I will check voltages in a second.


[video]https://www.youtube.com/watch?v=ZtaUTGr3VtY[/video]

[Phone Guy]

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.

[dwcraig1]

Of coarse it needs to be returned to the store. It compares to what happened to my VT133 a couple of days ago. It was already running SP3 for awhile. My cells look the same, I have narrowed it down to the actual DNA board. 

[Phone Guy]

dwcraig1 said:

Of coarse it needs to be returned to the store. It compares to what happened to my VT133 a couple of days ago. It was already running SP3 for awhile. My cells look the same, I have narrowed it down to the actual DNA board. 

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.

[Phone Guy]

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?

[Spector NS5 RD]

it seems the battery management ic or it's supporting components near the usb is extremely fragile/sensitive. at least this is the conclusion i've come to when the board fails to read the cells correctly with a battery change, FW update or just from normal use.

sucks man, i feel for ya.

[dwcraig1]

I'm looking at it from happening due to rebooting more than from the FW upgrade, but really don't have any real knowledge about it.

[Phone Guy]

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!!!!!!!!!!!!

[retird]

Let us know how it goes when you take it back for replacement.....

[joe ky]

James said:

I don't think the internal resistance has changed. 1.2 SP3 may have trouble reading resistances that low, probably due to some of the extra protection code we added. I'll have to look at it this coming week. Other than this issue, I am glad it is working well for yall.

Hey James, let me say first that the SP3 update has been fantastic for me! I've used SS 316L for a while now and I think the change in the firmware update for SS is great. I'm having the same issue several others have described about the mod resistance after the upgrade. I've got 5 200/133's. Only one reads the same resistance now that it read before the update. The others will bounce around all over the place or just show a "?." This is using the copper tool. So for the time being I've just made sure they are set at what they were before the update. So with all this said, I was wondering if you have had a chance to check this out? Thanks, Joe

[Phone Guy]

retird said:

Let us know how it goes when you take it back for replacement.....

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.

[Spector NS5 RD]

Phone Guy said:

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.

did you tell them the situation or just tell them it died. i'm curious. 

[Phone Guy]

ChunkyButt200 said:

did you tell them the situation or just tell them it died. i'm curious. 

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.

[Spirometry]

If you go to Evolv's web page (not the forums) and download Escribe, no matter what device you choose, you'll get 1.2 SP3

So wouldn't be safe to say that 1.2SP3 is now the recommend software?

[VapingBad]

Spirometry said:

If you go to Evolv's web page (not the forums) and download Escribe, no matter what device you choose, you'll get 1.2 SP3

So wouldn't be safe to say that 1.2SP3 is now the recommend software?

Very good point

[Phone Guy]

Spirometry said:

If you go to Evolv's web page (not the forums) and download Escribe, no matter what device you choose, you'll get 1.2 SP3

So wouldn't be safe to say that 1.2SP3 is now the recommend software?

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?

[Phone Guy]

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