blueridgedog

I have an evolve reference enclosure. Can anyone post their case analyzer results for me to us? I can't run the case analyzer due to USB disconnects associated with running the process via a virtualbox host on my mac. Thanks.

This has just come up in what has been an otherwise correctly working mod. The above shows what the mod looks like when the issue arrives. It is a .17 ohm build, but the board will occasionally see it as .23. How can it read .186 and calculate a cold ohm value of .234? Giving it a hard reboot, resets it: Is this a case calibration issue or???? The issue is a PITA as it requires a computer to overcome, or a manual change to the set temp to keep vaping. I know my way around the board and building TC atomizers and this one has me stumped.

Shampoo: Ti can be hard if the atomizer or mod has variable resistance. Have you looked at device monitor to get an idea of what is sees? Have you plugged in an accurate figure for mod resistance? If it is still at 0, then any mod resistance will be added to the coil when the board looks for resistance changes to determine if the coil is TC capable.

Certainly looks shorter...ha. Curious about the color as well.

Deep frustration here regarding the screen issue. My first build had a poorly routed screen whip. Builds after that did not. I like the form factor and like having the screen on the face of the device, so there appears to be only two options: assemblers manage the "extra" screen whip or a display with a shorter whip is custom made. One assembler who is by no means a mass producer had an assembly jig made, where by a screen is inserted, a block of adhesive foam, then a board fitted to the jig. The result is a correctly aligned screen, with free whip. The whip is then routed and secured and the connector fastened. If this can be done for a person making less than a 100 mods, then certainly the companies making 1000's should have a similar setup.

Some strongly recommend drastically lowering preheat with Ti and I have blown several Ti coils...I have stopped using pure Ti as it is a pain in the rear for those reasons.

Great...sent you a PM.

I use that atomizer. It is a good one for TC vaping - being very stable in terms of resistance. I also use Ti. I have a much more stable vape than you are showing. Your video shows very little power and extremely erratic temperature. If it were my mod, I would look very hard at the 510 connector and it's wiring (ground). I think your mod is seeing internal resistance changes (510 and ground) that it is assuming is happening in the coil. If you are not "handy" then I would certainly send the unit back as something internally to the wiring of the mod is incorrect.

You need a windows environment on an x86 or an AMD64 processor. If you have a compatible processor, then you can get your windows environment with a variety of methods. First is a direct install of windows to the hardware, the second is a install of a windows "guest" OS via one of the common virtual OS solutions (VirtualBox, VM Fusion). To my knowledge, ChromeOS can't support the hosting of virtual OSs via a software program like VirtualBox or VM Fusion.

Yea...I want to be clear that these are gleaned from this forum and are intended to be a "one stop" collection of helpful facts or solutions. Any additional suggestions are welcome and I have solicited review from Evolv staff. I am not trying to put "my" spin on solutions, but to collect items in one place as it is otherwise hard to locate them.

Feel free to suggest updates/expansions. They are a collection of solutions gathered from this forum and are open to any edits you want to suggest.

An you have verified your balance connector wiring?

Thanks Nick...I am not certain why such a topic specific forum is such a target. A method of reporting such posts so you and your team can make chips and not babysit a forum may help.

Lets clear out this new round of spam....

Updated for the new ability to look for screen disconnects.

I too would like to see more individuals who think they have this issue describe it. Thus far, every "out of TC mode" issue I have had could be traced back to to high or variable mod/atomizer base resistance, i.e. I was able to fix it.

I think the official word is that there are no plans for an OSX version. Though I am a Mac user, I understand this as the number of DNA200 owners globally that use a Mac is likely small vs the time to develop a port. Two other points: Mac users are generally smart about running the occasional windows program. Any port of escribe, IMHO, should likely be to a web based platform so it becomes platform agnostic.

Ok. Put in a value in "mod resistance" in escribe. You want to mimic the resistance drop that the 40 is seeing but not compensating for. Start with .007 and test. Move the figure up and down and see the result. In wattage mode, the only issue should be that the DNA200 has a factor for the resistance of the mod that it subtracts from the resistance of the total to arrive at the resistance of the coil.

A diagnostic tool built into escribe would be an interesting ad-on. Right now we have to use data from device monitor to deduce issues, but some form of diagnostic would be useful.

A good step in looking at this would be a device monitor screen shot after it goes to sleep showing resistance/wattage/temp then a comparative one after it is rebooted. What could be happening?: After sleep the board fails to see the combination of atomizer and wire as acceptable for TC mode, i.e. it can't detect enough resistance changes to conclude that it is TC wire. What could cause this?: Changes in atomizer resistance coupled with some atomizer state re-read from the sleep state. A programing defect in the board such that sleep mode triggers a non-tc state. If this is only with low TRC wire, then the first thing I would try and do is reproduce it with Ni200. If it can't be reproduced with higher TCR wire, then it is likely tied to the total TCR value of the wire used being on the margin of triggering TC mode and some issue with sleep triggering a state re-read.

By verify wire, I mean that it is indeed Ni200 wire. Also, what you are seeing could easily be caused by a hot spot or hot let. A good Ni TC coil is spaced (not touching anywhere) and firmly held in place.

Vape it in the dark, no atomizer cover, looking for hot spots or hot legs. Sounds like a small portion of the coil is getting hot.

Updated for jumping out of TC mode when using low TRC wire types.

I would verify the wire as well as the mod resistance. Ni has enough of a TCR value that it should show more change.

Plug it into escribe and take a vape while device monitor is up. Is it in TC mode? What is the wattage doing? SS has such a narrow TCR that it may fall out of TC mode if your mod resistance is not set spot on.