KTMRider Posted August 7, 2016 Report Share Posted August 7, 2016 Why wouldn't you roll back until a new firmware comes out? It fixed my VS. Link to comment Share on other sites More sharing options...
dropdlicious Posted August 7, 2016 Report Share Posted August 7, 2016 My VS200 is going back tomorrow so I'll let y'all know what they find as well. This has been going on 3 weeks waiting on a VS evolv firmware update but it seems as if evolv truly only found out a few days ago. Haha figures. I'll report back! Link to comment Share on other sites More sharing options...
mactavish Posted August 7, 2016 Report Share Posted August 7, 2016 KTMRider said:Why wouldn't you roll back until a new firmware comes out? It fixed my VS. First of all I don't need this mod right now. Secondly, I have bad experiences in doing such in the past. And mostly, I'd like to see how Evolv handles this. I assume a quick new version of the software/firmware to be offered. It's great that you and I participate in forums like this and ECF, but many users may simply update via Escibe or just somewhere on the net, and have a VaporShark DNA200, and will have a bad experience. I doubt Evolv wants to put out buggy software/firmware and then have to explain a work around as to make it work properly. I applaud your efforts, and perhaps what you have done will help them figure out the bad code. If it were my only mod, or it made my computer stop working, I would have followed your discovery already. Let's see how fast Evolv fixes this, they mentioned having Apple Mac software out in late 2015, or first quarter of 2016. Last I looked, it's the 3rd quarter, and we're behind! Link to comment Share on other sites More sharing options...
retird Posted August 7, 2016 Report Share Posted August 7, 2016 dropdlicious said:My VS200 is going back tomorrow so I'll let y'all know what they find as well. This has been going on 3 weeks waiting on a VS evolv firmware update but it seems as if evolv truly only found out a few days ago. Haha figures. I'll report back! I think your issue is different than the one being discussed now... yours is that your VS arrived DOA... Link to comment Share on other sites More sharing options...
dropdlicious Posted August 8, 2016 Report Share Posted August 8, 2016 True true. The actual mod fires up and lights up and all just the battery arrived DOA so I guess it's got just enough juice to come on but won't charge. Hoping to find out Tuesday or Wednesday what went down with it. Link to comment Share on other sites More sharing options...
KTMRider Posted August 8, 2016 Report Share Posted August 8, 2016 mactavish said: First of all I don't need this mod right now. Secondly, I have bad experiences in doing such in the past. And mostly, I'd like to see how Evolv handles this. I assume a quick new version of the software/firmware to be offered. It's great that you and I participate in forums like this and ECF, but many users may simply update via Escibe or just somewhere on the net, and have a VaporShark DNA200, and will have a bad experience. I doubt Evolv wants to put out buggy software/firmware and then have to explain a work around as to make it work properly. I applaud your efforts, and perhaps what you have done will help them figure out the bad code. If it were my only mod, or it made my computer stop working, I would have followed your discovery already. Let's see how fast Evolv fixes this, they mentioned having Apple Mac software out in late 2015, or first quarter of 2016. Last I looked, it's the 3rd quarter, and we're behind! Me either but I like all my mods to be working. I'm not a fan of rolling back software usually but I have complete faith in Evolv so if it does damage my mod, I know they would help resolve the issue. The software is marked Early release so we kinda like beta testers. I think Mac users are a small percentage and there are work arounds. With the FDA crap, I'm sure they have prioritized what they need to work on and a Mac version of the software isn't high on the list, IMO. And it's still the 2nd quarter (calendar) . Link to comment Share on other sites More sharing options...
comat Posted August 8, 2016 Report Share Posted August 8, 2016 hi, does DNA200 have update firmware temperature-sensing like DNA75? Link to comment Share on other sites More sharing options...
SteveF Posted August 8, 2016 Report Share Posted August 8, 2016 Ok so the new update is ok but kind of PITA?You need to go to OPTIONS-USER INTERFACE-MANUFACTURER to access battery settings. then so far on all three of my mods it has wiped the battery charge and both escribe and mod are now showing the battery as 0%. you need to reset the WH total otherwise the battery will probably continue to charge? Link to comment Share on other sites More sharing options...
VapingBad Posted August 8, 2016 Report Share Posted August 8, 2016 Here are the differences in each mode compared to the previous versionsClean: no mod or research tabs and no atty analyser.Advanced: no research tab and only charge mode and Kanthal power limit on mod tabResearcher: only charge mode and Kanthal power limit on mod tabManufacturer: same as the previous version with the Manufacturer settings on the mod tab expandedIf you hold shift down in Device Manager you can get multiple measuring bars clicking on the plot area.@Comat yes it has lovely smooth ss regulation like the 75. Link to comment Share on other sites More sharing options...
SteveF Posted August 8, 2016 Report Share Posted August 8, 2016 VapingBad said:Here are the differences in each mode compared to the previous versionsClean: no mod or research tabs and no atty analyser.Advanced: no research tab and only charge mode and Kanthal power limit on mod tabResearcher: only charge mode and Kanthal power limit on mod tabManufacturer: same as the previous version with the Manufacturer settings on the mod tab expandedIf you hold shift down in Device Manager you can get multiple measuring bars clicking on the plot area.@Comat yes it has lovely smooth ss regulation like the 75.yes the 316 profile is superb, running dual 0.5mm coil 0.14ohms @100w and its almost faultless.........'temperature protection' doesn't flash up to show that its working.....but it is Link to comment Share on other sites More sharing options...
Wingsfan0310 Posted August 8, 2016 Report Share Posted August 8, 2016 Thanks for the update, It has really smoothed out TC on SS316L and 317L. My question is with the regs taking effect: Are you still going to be able to release firmware updates? I do believe that's the $64,000 question!Cheers,Steve Link to comment Share on other sites More sharing options...
mknight Posted August 8, 2016 Report Share Posted August 8, 2016 I hope they can.. I miss my 2a charging Link to comment Share on other sites More sharing options...
James Posted August 8, 2016 Report Share Posted August 8, 2016 Someone try this. It's a single value change, nothing big. The current sense amp and charger are right next to each other on the VaporShark board, so the code was getting confused by a bit of electrical noise. Easy fix. Let me know if this works for you and if so, I'll put it in a quick update tonight.EDIT: Need to make one for both variants of the VS board. Link to comment Share on other sites More sharing options...
Spirometry Posted August 8, 2016 Report Share Posted August 8, 2016 I tried it from my office computer. I'm getting an error that my device is not connected even though escribe and device monitor work fine.I'll try it again tonight from my home computer that I normally use. Link to comment Share on other sites More sharing options...
KTMRider Posted August 8, 2016 Report Share Posted August 8, 2016 I just tried (apply service pack) and it doesn't recognize the VS. I can see it in Device Monitor and upload/download the config. Do I need to upgrade to 1.2 first? Link to comment Share on other sites More sharing options...
dwcraig1 Posted August 8, 2016 Report Share Posted August 8, 2016 Should it only work on a Vapor Shark?I thought I'd give it a try (on my VT133)here is snip:Should it only work on a Vapor Shark? Link to comment Share on other sites More sharing options...
retird Posted August 8, 2016 Report Share Posted August 8, 2016 KTMRider.... I tried to install service pack on my non-VS device using 1.2 and got same error message.... noticed while extracting the Zip file it didn't give the normal Evolv logo icon on the desktop file... Link to comment Share on other sites More sharing options...
James Posted August 8, 2016 Report Share Posted August 8, 2016 Ah, I see. Disregard that update, it's only for one of the two variants of the VS board (the one I was able to reproduce the problem on). I suppose most people do have the other one. I'll post a different one later today. Link to comment Share on other sites More sharing options...
Spirometry Posted August 8, 2016 Report Share Posted August 8, 2016 Thanks again James for trying to get this problem worked out. Link to comment Share on other sites More sharing options...
retird Posted August 8, 2016 Report Share Posted August 8, 2016 Noticed this on file properties.... Link to comment Share on other sites More sharing options...
VapingBad Posted August 8, 2016 Report Share Posted August 8, 2016 retird said:Noticed this on file properties.... That's just a missing file association and will not affect the update process. They are just a record in the Windows registry that tells it which programs can work with the file if you try to open, run or edit it directly. It doesn't prevent a program loading. Link to comment Share on other sites More sharing options...
txmonkey214 Posted August 8, 2016 Report Share Posted August 8, 2016 Hi, Yes, the battery goes to 0% when you load 1.2. All I had to do to restore the battery setting was a soft reset. Link to comment Share on other sites More sharing options...
Nick Posted August 8, 2016 Report Share Posted August 8, 2016 SteveF said:yes the 316 profile is superb, running dual 0.5mm coil 0.14ohms @100w and its almost faultless.........'temperature protection' doesn't flash up to show that its working.....but it is I actually noticed this on the first one we made as soon as I hooked it up and vaped it for initial testing.I investigated this with James a bit, and the reason is not because it isn't working, it is because it is actually working so well now that it doesn't hit the threshold required to trigger the message in many cases.This was a very satisfying revelation on our end for what we originally thought could have been a bug. We hope you guys are as satisfied as we are with the results of our work on this. Link to comment Share on other sites More sharing options...
mactavish Posted August 8, 2016 Report Share Posted August 8, 2016 Nick said:I actually noticed this on the first one we made as soon as I hooked it up and vaped it for initial testing.I investigated this with James a bit, and the reason isn't because it isn't working, it is because it is actually working so well now that it doesn't hit the threshold required to trigger the message in many cases.This was a very satisfying revelation on our end for what we originally thought could have been a bug. We hope you guys are as satisfied as we are with the results of our work on this. I have come to rely on the TC notification. And have defended it to so, so many that originally see it as a WARNING, and not a notice that your device is working properly and just letting you know you have achieved the temperature you set it to. And then in future updates you allowed the TC message to be turned off, for those that did not care for it. My point being, while I'm certainly happy for a better vape experience, you have also introduced another variable. I can see folks saying, sometimes I get the TC message on screen, sometimes I don't! Personally I think if possible there should be a consistently of the TC message, and that if the user, like me has it set for on screen display, then I expect it to display every time I hit the temp target I set it to, regardless of the current wire material. Does this not seem logical? Link to comment Share on other sites More sharing options...
retird Posted August 8, 2016 Report Share Posted August 8, 2016 Nick said:I actually noticed this on the first one we made as soon as I hooked it up and vaped it for initial testing.I investigated this with James a bit, and the reason isn't because it isn't working, it is because it is actually working so well now that it doesn't hit the threshold required to trigger the message in many cases.This was a very satisfying revelation on our end for what we originally thought could have been a bug. We hope you guys are as satisfied as we are with the results of our work on this.That's exactly what I noticed with the latest update "Early Release" firmware for the DNA200 with SS316. Smooth temp graph and Temp message sometimes displays but Device Monitor shows almost straight line temp variance at temp... Heck, I can't see my display while vaping anyway. Very satisfied that the 75 and 200 both work great with SS316... Note highlighted in blue: Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now