You could prove it yourself by opening Escribe and selecting Power, Current, Live Ohms & Voltage and start a recording while firing a few times then calculate your power with the recorded results. If the logged data is accurate your Power calculations should all be equal to the logged power using any variation of the power formula, Power = Current * Voltage, Power = Voltage^2 / Resistance, Power=Current^2 * Resistance. Charted you should expect to see a singular line overlaying each other from each of the calculations. Here's an example of what I see.
DNA 200 Watt
- Thread starter MegaVap
- Start date
- th_trl_thread_readers 0
- Status
You could prove it yourself by opening Escribe and selecting Power, Current, Live Ohms & Voltage and start a recording while firing a few times then calculate your power with the recorded results. If the logged data is accurate your Power calculations should all be equal to the logged power using any variation of the power formula, Power = Current * Voltage, Power = Voltage^2 / Resistance, Power=Current^2 * Resistance. Charted you should expect to see a singular line overlaying each other from each of the calculations. Here's an example of what I see.
I see no reason why should I expect exactly same charts from all calculations. I am not certain that all of this information is measured at the same point on the board, therefore I cannot expect the information being 100% accurate. If you know anything about electronics (or elementary physics), you should know that measurements taken from two different points cannot be the same. On top of that once again, we are talking about a pocket size device, so if you know about a multimeter which is perfectly accurate and in a size of a box mod, please share. The point is to get an idea what is happening, and unless there is a difference in 10s of percent, there is no point in questioning the accuracy.
^ yeah, that's definitely sampling/data acquisition/communication lag stuff. A lot of the things the DNA 200 and Escribe will do aren't exactly real world useful, still a magnificent board and a huge leap forward in vaping technology. Don't know about you guys, but I tweak the vape by flavor, leave the laptop at home.
Yep... no need to take the laptop...having many profiles tweaked via Escribe settings I just pick the appropriate profile. Easy-peezy....
Let us know how it goes when it lands....Still looking forward to that, efusion on the way from UK
Quick question I will ask here and on the VS DNA 200 thread. I've had the vs200 vt200 and the reuleaux. The vs200 has been saying check atty all of a sudden then I plug it into escribe and then it works. Then a hour later the same deal. I've tried 10 rdas that work on all of my other devices and unless I plug it in they won't work. After I plug it in and unplug the device it will work for a short time then it keeps repeating. I've had the worst luck with these DNA 200's and I baby them all never dropped any of them and no juice or liquid overflow at all. I also am very careful with the 510 so it's not like I went crazy tightening it down. If anyone has any advice that would be awesome thanks.
The only thing I can think of is to hook it up to Escribe and under tools do a hard reboot. You are having bad luck, I've had 3 for awhile without any problems. Good Luck and let us know if you get to the bottom of your problem!
Cheers,
Steve
PS The only other thing you might try is cleaning your 510 connector with a q-tip with a little rubbing alcohol. Then turn over the q-tip and wipe it with the dry end. Let it air dry for a few minutes. Since it works after plugging it in, I don't really think that's going to take care of the problem. It never hurts to clean the 510 though.
, I've had 3 for awhile without any problems. Good Luck and let us know if you get to the bottom of your problem!Cheers,
Steve
PS The only other thing you might try is cleaning your 510 connector with a q-tip with a little rubbing alcohol. Then turn over the q-tip and wipe it with the dry end. Let it air dry for a few minutes. Since it works after plugging it in, I don't really think that's going to take care of the problem. It never hurts to clean the 510 though.
Last edited:
I'd start by actually measuring just how far down in the 510's positive pin is compared to the other mods. I screwed in an Infinite clone dripper with an extra long 510 on one of mine and it pressed the 510's insulator down about 1 mm.
Thanks everyone for the help. I love my Aeolus's and its has a long 510 pin so as soon as I get home from work I'll clean the 510 then check the 510's insulator. If that doesn't help I'll do the hard reboot. And if all else fails it's goin in to be repaired hopefully under warranty. If the 510's insulator is pushed down what should I do just try to bring it back up? Or is there another way to get it back to where it was?
Rockwell,
I just know someone is going to tell you to pry it up like we used to do in the "olden days" but don't, send it in for repair if it turns out the pin has pressed down.
If you pry it up it is just going to get pushed back down and you will be in a rut of pulling it back up until something breaks.
This is one view of it and it kinda looks pushed down a little.The second picture looks better but I figured I would post both. Does this look like that's the problem. And I won't try to pry it up I'll just hope I am good with warranty. Does anyone know if this would fall under vaporsharks 25$ repair? I think it does by how they word it but either way I think I'm still in the warranty period.
I don't have a VS so I can't tell you whether it looks normal. What I do when I clean my DNA200 mods is gently press down on the pin and make sure it springs back up freely. I'm assuming the VS 510 pin is spring loaded.
Cheers,
Steve
Cheers,
Steve
Yeah it springs up freely. I just think it's odd when I plug it in it fixes itself for a hour or so. That's the confusing part to me. If it was constant I would say it's a error with the mod but because its intermittent it makes me wonder if it's the board.
Try the hard reboot if that doesn't do it try a Soft reboot. I was having some trouble with my VT200 picking up the fact that I was using TC wire I did a hard reboot nothing then did a soft reboot and it has been working ever since - "Go-Figure".
I believe there is some chatter about this sort of thing on the Evolv Early Adopters forum.
That 510 looks fine. Are you using a Beta Firmware from the eaf or the scheduled fw? If the boots don't do it, try re-flashing the FW update or upgrading to the beta from the Evolv site
Everyone knows the DNA200 is far superior than the Yihi SX350j chip. Those that try to argue in Yihi's defense is obviously in denial. I sold both SX350j mods is because the only thing it did better than my DNA200's is burning my wicks no matter what settings were set at.My DNA-200 is better than your M Class. You mad, Vlad?
@Rockwell222 - I'm sticking to my original assessment. If it was an issue with the bushing, you would have to unscrew the atomizer and reseat it. You're just plugging it in to escribe to make it work again which is something else. Either a cold solder joint or bad chip. Either way, VS will take care of you.
Mechanical problem inside the mod or chip issue...let VS do the troubleshooting.
- Status
Similar threads
