skineedog

Same atty, same mod. Different wires & coil resistance. The mod is set to the correct wire when this happens. Take a look at how wire 1 bounces around when hitting temp and wire 2 is much more stable or smooth. Any idea why? I have ensured contacts are clean & screws are tight. If it matters, wire one is SS 304. Wire 2 is NiFe30. I should add that this atty has been consistent with NiFe. This is the first time I have used any other wire with it. I'm wondering if the atty being made of what I assume is SS430 is causing some sort of 'conflict' or if SS304 just isn't a good choice in wire? I have some titanium I've yet to try...

I too seem to be suffering issues. My first was a VT200 that died the first day I owned it. The replacement has lasted about 2 months but temp control is spotty, moody at best. I can't determine if the problem is Hcigar, Evolve, or me?....

My guess is that there are still issues that AREN'T fixed. Search for "Hard Reboot for Temp Control" I as well as a few others have this problem. Admin "James" asked a few questions and for my settings file with which I responded and have heard nothing back about. I still suffer this issue.

Well, that answers one question I asked in another post a moment ago. So if the build doesn't matter, should the atty make a difference? I am using 3 attys with the same NiFe30 wire from Stealth. One of the attys works fine, as I expect. The other two are bit moody. Starts out hot as hell & tasting burnt. Reaches temp limit almost immediately. If I keep vaping it, the temp settles down and is usable. This is with out changing any settings between switching attys. Hard booting sortta resolves the issue for one of the 3. I have another issue where the mod doesn't recognize the TC wire. Hard booting the mod via escribe ALWAYS resolves this.

I have several questions/problems that I can't seem to figure out. I hope someone here has my answers. 1.) When setting up a new wire, what is the best route? Using a TCR file from SteamEngine or using the wire wizard via SteamEngine. I notice when using the TCR, changing the resistance, changes the file's values. Using the wizard, the values appear to remain the same. Is this correct? Am I doing this wrong? I have tried both with the TCR files and the wizard with slightly better results with the wizard. 2.) I have setup 3 different types of attys. Each has the same wire type with roughly the same resistance. I have a profile setup using a wizard generated file. One of the attys seems work as I expect. Nice vape, not too hot.... When I switch to either of the other two attys, with the same profile, same temp setting, the vape gets very hot to the point that the wick tastes burnt almost immediately. Hard rebooting MIGHT resolve the issue for ONE of the attys but not all 3. If it makes any difference the 3 attys this is happening with are: Smok TFV4 <- Worst offender Tob Supertank RBD <-Works perfect (or as expected) every time Kanger mini <-Works most of the time I posted about this in another thread and thought it might get some traction as an admin here going by James asked some questions and for my settings file but I have not heard anything back.

James, thanks for taking an interest. I have the default display changed so my device doesn't display the temp but rather battery charge. This change was due to the initial issues I was experiencing with the Hcigar's battery. This has been resolved by changing the default values as found elsewhere in this forum. My battery last all day now. As for the ohms changing, they do but I figured this was supposed to happen as this is how temp is monitored? The ohms seem to go up with use and back down as the device cools. Using the atomizer analyzer just now, this coil seems to be quite stable between .081 & .082. Firing it & they go up to ~.142 or so and drop rapidly when I stop firing. Atomizer Analyzer reads cold ohms @ .076 which I believe to be what it read when first installed. I have uploaded the escribe settings I believe you want. This seems to happen no matter which TC wire I am using but the last few days I have been using profile 2 which is NiFe30. When I notice it happen again, what do you suggest I do to record the occurrence for your purpose of troubleshooting? Many thanks for the assistance. This has been very frustrating as I thought I was doing something wrong. I have tried many different builds with several different TC wires. For some reason, I thought I'd try the Windows fix-all of rebooting and this seems to work every time. Go figure! escribe.zip

Thought I'd have a full day without having to reboot but alas, t'was not to be... Tried previous suggestions to no avail. Hard reboot via escribe was required.

Just so happens I am also using the VT200. Wonder if that is a coincidence or if the issue is related to the device.....?

Wonder if I am the lone ranger or if anyone else is experiencing: TC works okay for awhile and then the device no longer detects the wire as a TC wire. A hard reboot via escribe resolves this and TC works properly again. I am unable to determine any pattern. Happens with TI, SS, & Ni. I am using FW 9.30. Until this is resolves, does anyone know if rebooting the device without escribe is possible? Many Thanks in Advance!

WileE - Thanks for the reply. I was educated in another post regarding NiChrome. I shoulda done my homework... Personally I don't care for the taste of nickel. Some of my nickel builds turn out ok but most have a taste which I really don't care for.... Regarding NiFe 52; Why the preference for 52 vs 30? I read on another forum someone swearing by 30.

Implementation of an option to charge at 2 amps instead of 1? Seems like it should be possible with firmware? 1 amp is pretty fast but faster is better, right?

Well, I guess I shoulda done my homework.... Thanks...

I appreciate your response but if the TRC was the problem, wouldn't escribe show something for temp rather than nothing? And wouldn't/shouldn't it do so consistently? It's as though the device is ignoring the TRC completely. Until I attach other attys and then reattach the NiChrome coil.

Can someone provide the TRC for NiChrome 80 that is currently working for them, please. The one I downloaded from Steam may be causing issues I am experiencing.... Thanks!!

Yet another test convinces me there is something up with either the device or escribe: I attached an atty with an SS coil and switched to the appropriate profile. Temp control functions as expected and is reflected in escribe. Did the same with an Ni200 coil with the same results. Switched once more back to the Nichrome coil and escribe & the device seem to be functioning and registering temp as expected. What is the issue? I am running firmware 9-30 with escribe version 1.0.35.2.

Just after the initial posting above, escribe & the device are no longer registering temp? Nothing has changed. I set the device down long enough to write the post, finished and tried vaping again. The device vapes fine but not temp is being registered.

Wrapped my first coil with NiChrome 80. .52 ohms stable per the MOD and escribe. Uploaded the TCR from Steam both from the Wire Wizard and the old TCR. The coil is installed in a Kanger submini. Values loaded from Steam are: Temperature (degF)Electrical Resistivity-1000.98965118400.9957387237012001.0079133074001.019927866001.0329486278001.047827768 In device monitor, with temp monitoring mode enabled (temp limit disabled) the device/coil performs as expected. As soon as I enable temp limit, the temp registers all over the place which obviously cuts power to the coil. I have tightened both the coil & atty base several times to no avail. This is only happening with NiChrome. Any insight would be greatly appreciated.

It would be less expensive to use Parallels. I am running Parallels 10 on El Capitan with no problems although I cannot get VB to connect to the device. This leads me to believe El Capitan may not be the offender. In either case, I think having to buy additional software or hardware is a poor implementation. I have no experience with other devices but have heard that others have better, easier to navigate menus and all options can be configured directly on the device. This cannot be done on the DNA 200 without the use of Escribe. Can anyone briefly layout the benefits the DNA 200 has over other such devices?

Makes sense. Many thanks for the responses. Maybe this is something that will come in the future?

Maybe a silly question which is already answered somewhere.... Is the device capable of automatically switching materials? If I have entered the required data for titanium (or others) in one profile, can the device detect which material is being used regardless of the profile selected? Or, can only one material be used per profile? If I select a profile that has been setup for Ni200 and use an atomizer with TI, what happens? Does the device realize the material being used and utilize the curve data for the TI? Does it ignore it? Does it use the curve data for Ni200? It seems as though the device can detect whether the material being used is kanthal or not so, as long as the TCR is present for other materials, it should be able to detect which one is present and adjust appropriately. Can anyone confirm?

Same issue as others: Running VB 5.08 with the 5.08 ex pack on El Capitan. The DNA is seen by the host and VB but receive "Received no response from the device." error from EScribe. If it makes a difference, I am running Vista.

Yes, I am running 9/30.

I had one die after only one day of use. Was fortunate enough to get an exchange and the replacement has been in service exclusively for about 2 weeks.

The spec sheet clearly states that the typical input power is 9 amps & the minimum is .5 which would be inline with most phone chargers. I think many people would use a phone charger since they have one. I specifically purchased higher amp charger(S) for the device only to learn/discover that it does not charge over 1 amp. Why can a device that outputs this much power and has such a large battery as an obvious requirement not charge above 1 amp? An iPad can handle 2 amps... I've watched a few reviews of devices containing the DNA 200 with the reviewers stating the same so, if I am misunderstanding the spec sheet, I am not the only one... Clarification form the chip manufacturer would be nice... and appreciated.

I too am experiencing this issue although I cannot seem to determine a pattern. Not sure if the device is rebooting or simply waking from sleep. I may go hours without using the device and it fires immediately. Other times after as little as 30 minutes of being idle, the device displays the welcome screens as you described. The device also does not always seem to recognize when a new coil is present. Sometimes it does, other times it does not. This also seems to be very random...