audiovicious

This is in temp mode. I just got done checking it again, and it still shows 0.004 when screwed in all the way without cranking down on it, it shows 0.005 right before that, so I tried that and the 0.13 coil read 0.10 instead of 0.11. I've cleaned all of the contacts/screws aside from the internal 510, but it looked plenty clean and I wasn't too sure on how to properly clean it so I left it alone. It works, it fires, it just feels a little off.

The mod resistance is set at 0.004, I got that number by using one of the 99.9% copper plugs sold here on the forums. I've run the case analyzer, but a long time ago. I may need to recheck the values.

I finally got around to this and the build that would initially read .10, then to .09, was now .08. I built what should have been .13, I know it should be, and the device reads it as .11. I can just set it in eScribe, but whatever is causing it is a pain to locate.

It's an Evolv reference mod. When I first got it the resistances were flying around all over the place and I made a post here asking what was up, I believe it was you that recommended I tighten the 3 screws mounting the board to the box itself, fixing it. That fixed it, and it read fine from that day, until it started reading low about a month ago. When they were all loose (extremely), it was always high. I had the issue where shortly after getting it aswell, my screen fell in and I couldn't get the tape to hold it again no matter what I did, and ended up using some double sided sticky tape to just kind of mount it to the board, then have it held in place once the board was secured into the box, kind of like a press fit. I checked the mod resistance after this, and it had not changed, and it worked fine for several months prior to that, so I doubt that's related.

I've been having this problem for a little while, I didn't at first, and nothing changed in my settings (Which I consider myself pretty familiar with.) I've only ever used the same build at .10, and now anytime I put it in, the mod wants to read it at .09. The build hasn't changed, the RDA hasn't changed, no settings changed as mentioned before. The band aid is to go in and manually set the ohm resistance to the .10 I know it should be at, and was previously reading it at. I even tried a few different builds when I noticed it, and they were all off by the -.01. The mod resistance is set properly, so I'm not sure where the error is coming from. I haven't tried a different RDA, though it was working fine with this one for awhile (I settled on the current one I'm using and gave the rest away, I really only keep one I like at a time, and my friends get gifts), though I did clean out the 510 from the top, I'm hoping it's not a connection issue in the mod itself as this is already a replacement mod. It's not a HUGE issue, as I can lock what I KNOW it should be, but it's kind of a pain and it'd be nice to know that it just worked the way it was supposed to. It's been happening for awhile and I haven't been TOO bothered by it, but I figured I'd finally come and ask. Any help, as always, is appreciated. Thanks.

I should add that tightening those let me go in and use the copper plug and instead of values jumping all over, it just consistently read 0.004 right off the bat. So all of my problems are fixed now. Thanks to Evolv for sticking by it, helping the first time, and then continuing to provide support, and to the forums for the expert advice. I'm beyond pleased with it now.

VapingBad, First off, you have ended hours and hours of me trying to figure out what the problem was. I figured something was loose, but never opened it because I was going to leave that to Evolv, and I didn't know what it was anyway. I was able to open it, tighten the screws, and put your value in, and for the first time since I've had it, it read the resistance right right off the bat. The vape was consistent, and I've had no problems. The 510 threading I'm not going to be sending back over, as I've already smoothed them out and everything screws down by hand now, it was just the initial issue. It looks like everything is working now, thanks so much man. EDIT: What case are those results for? I have the black reference mod. I kept trying to run the case analyzer and it would never go past 'Waiting for steady temperature...'

EDIT: Issue seems to be fixed so far. Removing long, ranty post.

I received a black DNA reference mod for a busted mod I had to return and one thing I've been unable to nail down is the strange mod resistance on it, but I may have found a solution to that (If you have one though and you read this, feel free to let me know what you found to work for yours.) The problem is, every time I wake the device up, with the resistance locked, it's displaying the NEW/SAME coil prompt and I never had this on the old DNA mod I had. Any help would be appreciated. Thanks.

I had an HCigar VT200, a month to the day I got it, it went poof. Burned up, smelled like electrical fire, melted some of the plastic internally, all that fun jazz. The vendor and HCigar were not existent in helping me, and that was after I waited that 2 week dark period for the Chinese New Year, Evolv agreed to let me send it in. For this, I'm very grateful, them covering what could have potentially been a manufacturer error. I was just curious if anyone knows the turnaround time for repairs/replacements. I know I'm not the only person they have sending units in, and I don't mind being patient, but from when it broke to now, it's been almost as long as I've been without (almost a month) it as I was with it at this point, and after being spoiled by a DNA 200 unit, it's hard to use my old 2 year old backup VW mod. I'm not even sure if they notify you when it's been sent back out or I'll just get a surprise. No rush, don't mind being patient, but be nice to know a time frame. The last response I got said that an estimate said I should have it back by this week, but being Wednesday and not having heard anything yet, I wasn't sure. USED: 31 days ERROR OCCURED: 30~ days (Waiting for CNY, etc) P.S. Huge thanks again to Evolv for being such a fantastic company. This isn't a callout or a complaint, just a question.

I woke up about 5 days ago, and went to grab my HCigar VT200 from the charger and the screen just read WARRANTY SERVICE. Once it was removed from the charger, the message went away and the screen displayed the usual settings, but the battery meter showed as empty, though the device would fire. Eventually, the meter came back after so much of the battery depleted or some time passed, I'm not sure what caused it. Then it would boucne between showing the battery bar, not showing the battery bar, and the warranty message (the warranty message only showed when it was plugged in though). Over the past few days, it seemed like it was getting gradually better. The battery meter almost always showed and drained, and it hadn't shown that error screen, it was working regularly aside from the battery meter showing empty rarely. Then today, it started showing the empty battery meter much more often again. I took this screenshot of it sees the charge as very low, but the voltage on the cells as plenty high. I've been keeping an eye on this while I was trying to resolve it just to make sure my LiPo pack wasn't over charging. I sent a ticket to Evolv and they were awesome enough to answer and provide some help, but I've been busy and will be going out of town soon so haven't been able to send it off yet, it happened a month to the day that I got the device and the seller was not being very helpful, while Evolv replied right away and offered to have a look at it for free. I'll probably end up sending it in, but it'll have to wait until my business trip is over. Can someone make sense of this though, or is there a known fix for this kind of issue?