Evolv DNA Forum
Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 1 of 3      1   2   3   Next
Daddi89

Junior Member
Registered:
Posts: 26
Reply with quote  #1 

Hi guys, first post in here [smile]

Few weeks ago i updated my halcyon to 1.2 sp3, few days later after i start to vape i was getting continuous shorted error message and the tc was pretty messed up.
Start to digging in, coil was fine, all screws on the atty (tsunami 24) were fine, tried on the efusion duo and no problems at all, while i was checking the atomizer analyzer the ohm value was jumping crazy from 0.10 to 0.35 (when it should be 0.35), this atom on the efusion (updated as well to 1.2sp3) and on the vt75nano had no problems at all, rock stable at 0.35 ohm.
Im vaping only in tc and use only ss (430 most of the time) all the coils and all the attys (limitless plus, griffin 22 and 25, bachelor pro) i had were giving this problem just on the halcyon, strangely the only atty (tsunami 22) with a clapton kanthal reading was rock stable on the halcyon.

Downgraded to the February firmware and no problems so far, how is it possible this?

ChunkyButt200

Avatar / Picture

Administrator
Registered:
Posts: 1,516
Reply with quote  #2 
hi daddi89. strange, you were having trouble with the SP3 update. i currently run that FW version on all of my dna 200's. haven't had any issues with TC after the update. have you tried reflashing the SP3 update or the new SP4 update? maybe give the new SP4 escribe a shot.
__________________
1.21 JIGAWATTS............GREAT SCOTT!........WHAT THE HELL IS A JIGAWATT?
• I am not employed by nor do I represent Evolv Inc.  All opinions are my own, they are just opinion not fact and can be wrong •
Latest versions of EScribe: DNA 200 • DNA 75  Common problems
EVOLV HELP DESK - https://helpdesk.evolvapor.com/?a=add
LOST VAPE WARRANTY REPAIR - http://www.lostvaperepaircenter.com
Daddi89

Junior Member
Registered:
Posts: 26
Reply with quote  #3 
hey ChunkyButt200, situation its really strange, im running sp3 on my other dna 200 flawlessly and im in love with the better temperature control with ss coils.
Am i wrong or the sp4 is just for dna 250? i dont want to risk to brick my dna.

Ill try to explain better what is happening coz yesterday i had some spare time to mess around with it.
Device is a Lost vape halcyon (dna200) with a tsunami 24 (that doesnt mean anything cause i have the same problem with others attys as well) built in clapton ss430 27/31 dual coil, .35 ohm rock stable on another dna200 (on sp3) and a dna75.
Untill im on the 2016.02.23 fw ohms are stable to .035 even after a long idle time (as it supposed to be [smile] )
So yesterday i started to mess around it, did an hard reset, reset the defaults values, hard reboot again, and the device was clean as came out from the manufacter, updated to sp3, everything is working, tc is working better with the new firmware.
Happy enough i start to play a little bit on fallout4 while a was vaping the other dna, after an hour i opened escribe and i start to notice that the ohm were not stable as before, on a minute time check i had like 5/6 times ohms dropping to 0.29/0.30 for a sec and came back to 0.35, had some vape and device was working fine, noticed that since the coil is warm/hot (so ohms are over 0.36/0.37) there weren't any problem on the reading.
Went to sleep, woke up this morning, and... resistance ohm was down to 0.17, tried to vape, error message: shorted.
Opened escribe and now the resistance was read between 0.11 to 0.29 jumping every second between these values, plus sometimes having a question mark.
Went back to the old fw, working fine, re-update, same problem, downgrade again everything fine.

There are no problem with the atty, both 510 threads are immaculate and shiny.
Few weeks ago i opened a ticket for this issue, but it has been closed down because i sorted out by downgrading it.
VapingBad

Avatar / Picture

Administrator
Registered:
Posts: 2,449
Reply with quote  #4 
Try setting your mod res to 0, then hard reboot, then download setting to check it has saved, it sounds like a connection issue, but then it would be similar with all fw versions.
__________________
• I am not employed by nor do I represent Evolv Inc.  All opinions are my own, they are just opinion not fact and can be wrong •

Latest versions of EScribe: DNA 200/250DNA 75
Common problems
Daddi89

Junior Member
Registered:
Posts: 26
Reply with quote  #5 
Quote:
Originally Posted by VapingBad
Try setting your mod res to 0, then hard reboot, then download setting to check it has saved, it sounds like a connection issue, but then it would be similar with all fw versions.


Thanks mate, I'll try later (working now)
What I can see, I couldn't believe is a hardware fault, or I should get the same issue on the old fw as well.
It's a shame, being a ss tc user, sp3 is phenomenal.
Daddi89

Junior Member
Registered:
Posts: 26
Reply with quote  #6 
It didn't work, still the same problem...
Really dont know what to do at this point outside of keeping it with the old fw.
VapingBad

Avatar / Picture

Administrator
Registered:
Posts: 2,449
Reply with quote  #7 
If it is just that the mod res reading is ? and you can get a stable reading with the old fw then I would just use that value with the new fw, I do in fact with no issues.  It is only an extra feature and it reading ? will not cause issues with anything other that trying to read the mod res.  It is a very different scenario from it tracking the resistance of an atomiser, you would never try and vape a coil that was below 0.01 ohm.
__________________
• I am not employed by nor do I represent Evolv Inc.  All opinions are my own, they are just opinion not fact and can be wrong •

Latest versions of EScribe: DNA 200/250DNA 75
Common problems
Daddi89

Junior Member
Registered:
Posts: 26
Reply with quote  #8 
Apart from the ohm reading, biggest problem that's after the coil cooled down I'm getting a shorted error, mod won't fire then!
VapingBad

Avatar / Picture

Administrator
Registered:
Posts: 2,449
Reply with quote  #9 
That sounds more like an issue with the 510 or atty, have you connect it to EScribe to get a live resistance reading when it does it?

I don't think the atty analyser issue and it saying shorted are connected.  I have read about people who have found tiny bits of machine swarf in their 510s causing strange problems, that or damaged insulator or damage wiring are the most likely thing I can think of ATM.

__________________
• I am not employed by nor do I represent Evolv Inc.  All opinions are my own, they are just opinion not fact and can be wrong •

Latest versions of EScribe: DNA 200/250DNA 75
Common problems
Daddi89

Junior Member
Registered:
Posts: 26
Reply with quote  #10 
Quote:
Originally Posted by VapingBad
That sounds more like an issue with the 510 or atty, have you connect it to EScribe to get a live resistance reading when it does it?

I don't think the atty analyser issue and it saying shorted are connected.  I have read about people who have found tiny bits of machine swarf in their 510s causing strange problems, that or damaged insulator or damage wiring are the most likely thing I can think of ATM.


How is it possible that with the old firmware (02/23) reading is rock solid as is supposed to be and with the SP3 (and SP2, tried just now) i have this silly reading?
ill attach some pictures ive just got of the board posts and 510.
IMG_20161009_174636.jpg  IMG_20161009_174623.jpg

While im using the SP3 readings are literally jumping from ? to the coil effective resistance, every second i have a different value, like ? .075 .150 ? .298 etc etc

PS: 510 is fine, atty as well, no trace of fabric debris!


VapingBad

Avatar / Picture

Administrator
Registered:
Posts: 2,449
Reply with quote  #11 
I know, but just the fw causing it seems even more unlikely to me, I understand that that is the only thing that has changed and a logical conclusion, but if it were just the fw loads more people would have the same issue.  It is also possible there is a hardware issue and with the new fw you get these issue that don't show up with the old fw, still very strange I know.   Sorry, wish I had a better answer for you, I would open a ticket with Evolv to see if they can help.
__________________
• I am not employed by nor do I represent Evolv Inc.  All opinions are my own, they are just opinion not fact and can be wrong •

Latest versions of EScribe: DNA 200/250DNA 75
Common problems
Daddi89

Junior Member
Registered:
Posts: 26
Reply with quote  #12 
Quote:
Originally Posted by VapingBad
I know, but just the fw causing it seems even more unlikely to me, I understand that that is the only thing that has changed and a logical conclusion, but if it were just the fw loads more people would have the same issue.  It is also possible there is a hardware issue and with the new fw you get these issue that don't show up with the old fw, still very strange I know.   Sorry, wish I had a better answer for you, I would open a ticket with Evolv to see if they can help.


I did, they closed it after few replies since I sorted out by downgrading... My hopes are with the next update, I don't want to send it for RMA.
retird

Avatar / Picture

Administrator
Registered:
Posts: 1,187
Reply with quote  #13 
Been following this conversation and from the picture of the 510 it seems there may be a cold solder at the 510 to chassis.  I know pictures may deceive.... firmware seems unlikely to me at this point...
__________________
I am not an employee of and do not represent Evolv Inc.  My opinions are just that and are not meant to be fact or even correct.

Daddi89

Junior Member
Registered:
Posts: 26
Reply with quote  #14 
Quote:
Originally Posted by retird
Been following this conversation and from the picture of the 510 it seems there may be a cold solder at the 510 to chassis.  I know pictures may deceive.... firmware seems unlikely to me at this point...
This is what I'm thinking as well, just asked to a guy on fb to send me a picture of his one. I don't have any clue regarding how to disassembly the box and get access to the 510. So I think I won't be able to do that so...

edit: found it, had to remove the carbon fibre and there is a little slot to give access to the 510, soon ill try to solder both.
but still i cant understand how is possible that this firmware is giving problems while the old one is perfectly fine and stable...
Edit2: tested with a multimeter the 510, from the ground post to the outer 510 solder is fine, but the upper ring (chassis part) is not coming out at 0 with the 510. Tomorrow I'll solder it again... Hope is gonna work...
edit3: before re solder the ground i decided to check if that was the problem, put a little wire between the chassis and the ground 510... and... rock stable after 2 hours of idle! tomorrow morning ill get the confirm if that was the problem so i will proceed to re solder it, but ATM im quite sure about this. Thanks @retird for point me out on that!
edit4: no way, found her this morning jumping between ohms as always, ill try to solder it any way...
Daddi89

Junior Member
Registered:
Posts: 26
Reply with quote  #15 
Soldered again the ground post (and the chassis as well), still same problem...
IMG_20161011_173714.jpg

Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.