Daddi89 Posted October 7, 2016 Author Report Share Posted October 7, 2016 Hi guys, first post in here 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? Link to comment Share on other sites More sharing options...
Spector NS5 RD Posted October 9, 2016 Report Share Posted October 9, 2016 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. Link to comment Share on other sites More sharing options...
Daddi89 Posted October 9, 2016 Author Report Share Posted October 9, 2016 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 )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. Link to comment Share on other sites More sharing options...
VapingBad Posted October 9, 2016 Report Share Posted October 9, 2016 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. Link to comment Share on other sites More sharing options...
Daddi89 Posted October 9, 2016 Author Report Share Posted October 9, 2016 VapingBad said: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. Link to comment Share on other sites More sharing options...
Daddi89 Posted October 9, 2016 Author Report Share Posted October 9, 2016 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. Link to comment Share on other sites More sharing options...
VapingBad Posted October 9, 2016 Report Share Posted October 9, 2016 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. Link to comment Share on other sites More sharing options...
Daddi89 Posted October 9, 2016 Author Report Share Posted October 9, 2016 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! Link to comment Share on other sites More sharing options...
VapingBad Posted October 9, 2016 Report Share Posted October 9, 2016 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. Link to comment Share on other sites More sharing options...
Daddi89 Posted October 9, 2016 Author Report Share Posted October 9, 2016 VapingBad said: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. 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 etcPS: 510 is fine, atty as well, no trace of fabric debris! Link to comment Share on other sites More sharing options...
VapingBad Posted October 9, 2016 Report Share Posted October 9, 2016 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. Link to comment Share on other sites More sharing options...
Daddi89 Posted October 9, 2016 Author Report Share Posted October 9, 2016 VapingBad said: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. Link to comment Share on other sites More sharing options...
retird Posted October 9, 2016 Report Share Posted October 9, 2016 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... Link to comment Share on other sites More sharing options...
Daddi89 Posted October 9, 2016 Author Report Share Posted October 9, 2016 retird said: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... Link to comment Share on other sites More sharing options...
Daddi89 Posted October 11, 2016 Author Report Share Posted October 11, 2016 Soldered again the ground post (and the chassis as well), still same problem... Link to comment Share on other sites More sharing options...
Daddi89 Posted October 11, 2016 Author Report Share Posted October 11, 2016 here is a video captured from escribehttps://youtu.be/0jYGaPRBC50 Link to comment Share on other sites More sharing options...
dwcraig1 Posted October 12, 2016 Report Share Posted October 12, 2016 I'd open another ticket and include a link to the above post. Link to comment Share on other sites More sharing options...
FrankieS Posted October 16, 2016 Report Share Posted October 16, 2016 I started experiencing incorrect (continually changing, always much higher than actual) ohm readings with my S-Body Nuke after upgrading to SP3. After burning a few wicks, I opened the mod casing and tightened the 510 connection and upgraded to SP4 but still had the same issue. After downgrading to the 02/2016 version, its back to its rock solid self and working as perfect as my calibrated Ohm meter is. Link to comment Share on other sites More sharing options...
Daddi89 Posted October 16, 2016 Author Report Share Posted October 16, 2016 So I'm not the only one... Spoke (again) with evolv support who asked me to send the board in USA, living in UK would be expensive, so I prefer to wait a new firmware and in case proceed with the lost vape support, nick from evolv didn't have any clue about this problem cause of course sounds crazy and illogical. Frankie what atty are you using? Ps: nick confirmed me there weren't any changes to the ohms reading between the old and the new firmware. Link to comment Share on other sites More sharing options...
VapingBad Posted October 16, 2016 Report Share Posted October 16, 2016 Daddi89 said:So I'm not the only one... Spoke (again) with evolv support who asked me to send the board in USA, living in UK would be expensive, so I prefer to wait a new firmware and in case proceed with the lost vape support, nick from evolv didn't have any clue about this problem cause of course sounds crazy and illogical. Frankie what atty are you using? Ps: nick confirmed me there weren't any changes to the ohms reading between the old and the new firmware. It's not that bad I have sent one from the UK before and they pay the return postage. Link to comment Share on other sites More sharing options...
Daddi89 Posted October 16, 2016 Author Report Share Posted October 16, 2016 VapingBad said:It's not that bad I have sent one from the UK before and they pay the return postage. Didn't mention about the impossibility to remove the board from the case ?? Link to comment Share on other sites More sharing options...
VapingBad Posted October 16, 2016 Report Share Posted October 16, 2016 It is the retails responsibility, then maybe the mod makers, Evolv are going above and beyond here trying to help you when they don't have to. Link to comment Share on other sites More sharing options...
Daddi89 Posted October 16, 2016 Author Report Share Posted October 16, 2016 VapingBad said:It is the retails responsibility, then maybe the mod makers, Evolv are going above and beyond here trying to help you when they don't have to.Of course im not blaming Evolv, their support is amazing! Link to comment Share on other sites More sharing options...
FrankieS Posted October 17, 2016 Report Share Posted October 17, 2016 Daddi89 said:So I'm not the only one... Frankie what atty are you using? Ps: nick confirmed me there weren't any changes to the ohms reading between the old and the new firmware. For my tests, I tried the Kayfun v5 original and the SJMY clone with single, simple nickel and SS316 builds. The 0.09 ohm nickel coil was reading as high as 1.12 ohm. So to do further testing I also tried OBS Engine and Reaper Plus with dual SS316 builds, and got similar results. As for sending the board back to Evolv, right now its working ok with the old firmware. I figure I should leave it be and just use it until the new release. Link to comment Share on other sites More sharing options...
VapingBad Posted October 17, 2016 Report Share Posted October 17, 2016 What is your mod res set to? Try zeroing it. 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