rusirius one of the things that is different is your resistance went down ours is raising but our atty and mod were in the cold. i ended up going to town again .... this time i kept hitting my mod and it was fine until i left it again briefly while i got 2 gallons of gas it again went up but only to .17 causing it to give a burnt hit if i were to hit it i didnt i turned my watts down again. so for whatever reason the cold is causing mine to behave in a way id call a problem figuring out the problem though is it the board is it the build. works just fine in my house/.
Indeed.
Just for fun, since I knew it was going to get very cold last night, before I went to bed I threw my mod and atty in the truck. It was running a big dripper with a .18 build.
When I got up this morning it was 27 degrees. I picked it up and fired it and the vape was perfect. Checked the resistance and it was spot on .18.
Now I've given this a lot of thought, and I think I've come up with a couple of fairly good explanations for why this is happening to some.
First let's understand how the DNA40 works in terms of it's power usage. We'll start from a completely fresh battery install.
The mod first fires, gives the logo on the screen and while it's doing so it reads the resistance and sets that as it's base resistance. This is what it uses for all temperature calculations. Now, you vape away happily and everything is perfect. Then you sit the mod down.
After a few seconds it dims the screen, then after 30 seconds or whatever it is, it turns off the screen. At this point the mod is still working exactly as normal, it just has the screen turned off. You pick it up again and fire it and everything works just fine.
Now you sit it down again. This time it dims, then turns off the screen. After 5 minutes of being idle it puts the MCU in a sleep state. Essentially it powers down. When you pick it up again and fire it, it re-reads the base resistance.
Now normally this works perfectly fine, because after 6 or 7 minutes the atty and board are at the same temp again. BUT....
I only ever ran one build using 28awg. It was also in my big dripper. The way the BD is designed, to get the coils down in front of the air holes you have to push them way down into the juice well after they are wicked. (The lip of the well is actually higher than the through holes on the posts.) Because of this the wick get's packed in pretty well around the coils. The problem I had with it was that if I fired it cold and used it it was great. If I was working on something though, set the mod down for 5 minutes or so, then picked it up and fired it again the vape would be considerably hotter. Sometimes to the point of burning if the wicks weren't really saturated.
What I determined was that it was due to the heat retention... In other words, because the wick (rayon) was packed in so tight around the coil, it was acting as a great insulator. That combined with the extra heat capacity of the 28awg meant that after 5 minutes the mod had cooled down, but the atty was still warm. So it would read the base resistance again after it's sleep, but this time it would read it one or two hundredths of an ohm higher, which allowed the temp of the coil to climb well past the temp displayed on the TP.
To resolve that issue, I just started using 30awg. As soon as I did the problem went away. Most likely because now when it re-reads the resistance the coils have had time to cool down more and are closer in temp to the board.
Now, one other thing to mention here. I've mentioned the several strange quirks I had with my first board which exhibited the screen glitch. One of those issues was that after a sleep cycle it seemed to take longer to re-read the resistance. In fact, it seemed to fire the coil BEFORE it read the resistance. In other words, if the mod was sitting in sleep and I picked it up, it seemed to apply power the moment the fire button was pressed, but then there was a "pause" before it read the resistance. So I would have what is described here happen. I'd pick it up in the morning for that first morning vape for example, and suddenly my .12 coil was reading as a .15 coil and I'd get a horrible dry burnt hit. While I was still using the bad board doing testing, how I got around this was to get into the habit of always tapping the button VERY quickly when I first picked it up. This allowed it to read the resistance without actually firing the coil. Then all would be well. Well, as well as it got with that quirky thing. Perhaps whatever shorting or whatever was causing the screen glitch was also causing a lag between firing and reading the initial resistance. I dunno, I'd have to see the code and have a much better understanding of the board to be able to speculate on why that was happening. All I know is the symptoms it produced and a fairly good understanding of why it was happening.
I'm probably going to catch some flak for this, but I'm still going to have to insist that the problems with the DNA40 are much wider spread than being let on. The fact that TheKiwi had what? 3 or 4 different mods that all had the screen glitch issue? That's either really high odds of getting a bad board, or some TRULY horrendous luck on his part. Couple that with the fact that Evolv has apparently been pretty inundated lately. In the beginning there were lots of reports of emails being responded to very quickly, people getting personal phone calls from Brandon, etc. Very shortly after it all seemed to change. I know my first email to them took almost two days for them to respond to (in the middle of the week) and when they did there was no communication at all. Just an attached RMA form that said to fill out the form and send it back and it would be replaced or repaired. No apology or explanation, despite the details and questions I asked in my email. No response to the questions at all. Just a "send it back". I also saw a post (not sure if it was here or somewhere else) where someone said they spoke to someone at Evolv and was told that they have been slammed trying to deal with the RMAs. I'm sorry, but it's not a few boards out there acting weird... It's a LOT of boards out there acting weird.
In consideration of that, think of this. With my first board, as flaky as it was and as badly as it glitched. If I ran a kanthal build (or turned TP off) and ran it at a low wattage setting (lets say 12 watts) the screen wouldn't glitch. Turn TP on and run the watts really low and it wouldn't glitch very often. Turn TP on and run 40W and it would glitch almost EVERY single time on the first fire. The point is, even for as bad as my board was, if I had run a kayfun at 12W who knows if I even would have noticed the glitch on the screen. Yet the other wonky behavior may have very well been there. If the board wasn't as bad, who knows, I might have been able to run 20W or 30W and never seen a screen glitch but still had other issues. Who knows.
It just makes me wonder about some of the strange things we see happening here. Yes, there are is doubt that some issues can be caused by poor connections or whatever, but I've seen far too many descriptions that go beyond that. Sometimes it's difficult to weed out, but some are pretty obvious. I mean even VF and Evolv set up a separate RMA form / agreement for dealing with JUST the glitched boards. Do you really think they'd do that if it were only a few out there? They would just handle them like any other RMA, not create a whole separate form just for that issue. I just honestly think it's a lot more widespread than is being let on and I think that's starting to show.