blueridgedog

Though you are going to RMA it, did you check the fuse?

So are your ultimately going to swap out the board due to the bad button? Cool solution though.

We have a new version of VirtualBox...and the El Capitan problem persists...I did a clean install of El Capitan and VB just to test...still not an option. VM Ware Fusion seems to work.

As KTM put it...why do you want a prompt when you are in wattage mode?

When it is plugged in, what USB devices are seen by your computer? You should be able to get a list in device manager.

@vapingbad: Not enough power to get the coil up to temp is a good addition. I have not considered that one, but some may be running way to low to trigger TC mode.

TC has a learning curve. My wife vapes TC, but I have to do the work. I invested in TC so that I could make vaping safer (we are doing it as an alternative to smoking, not as a stand alone hobby). Is it as easy and potentially flavorful as kanthal? Not as easy, but potentially as flavorful. I could go on, but others have said it. For me the real track is getting the chip, 510 and atomizer to all play well with TC. We have the chip, we now have the 510, but we still need a reference atomizer that is perfect for TC.

I do not have experience with lifepo4, but I am surprised that cell two is so much lower than the others.

They are working on a research project, digesting the first round of research into DNA200 issues and about to release a new firmware...patience grasshopper.

What do you mean sliding doors? I have done a fair bit of stabilized wood skins on a metal frame, but the door issue is always a PITA. Love to see what you came up with. Great looking mod and though I have made all my current vape gear, I would love a PM if you decide to make a batch.

Interesting thought, but coming from the open source world, it is only useful if it can lead to an extension of the item. In this instance, I not certain there could be a great deal of community extension. It is also likely that the firmware conversion will be used for future boards and it would be hard to make the 200 OS even when it is long obsolete.

Good news. Thanks for the update. Having to beat the natives down with a stick.

I would start with the manufacture and get the process started for a warranty repair.

I take it you are out of the US and a warranty swap with Evolv is not attractive due to postage?

I recommend you open a ticket with Evolv and give them the benefit of your observations and repairs. I suspect they will replace the chip and learn from what you have done. The issue you described seems to be a common one among a certain class of failures (not a big number, but among those discussed here, similar symptoms).

There has been several version of escribe and lots of beta firmware on this forum. Failing to address this issue, in your opinion, negates the responsiveness of the firm entirely? This is a significant change and will probably be rolled out, but right now I know that Evolv is working on a research project, digesting the draft FDA rules and analyzing the first corpus of significant data from the first round of chip replacements. This request has to be important, but admittedly of low priority at the moment.

I too have a sampling of the chips (five I think) from various times. The one I have from the first batch is a work horse. Even survived a bad encounter with some bar room rage.

Removed and reseated the board. Issue persists. Mod resistance measures .012 with a dead short at the 510. I think the chip has gone south.

That was the first thing I tried...will pull them all the way out tomorrow and wiggle the board.

It is one of the Evolv reference cases....I am going to look at the 510 retaining clip...after that I will swap out the chip.

Soft reboot fixed it once. But did not on subsequent tries. It is happening now on all atomizers...odd.

I also put the 9/30 firmware on while messing with it.

I will try soft next time as well as atomizer removal. Right now I am just starting to chase this down as it manifested itself just two days ago. I am still not certain why the room temp is also so far off, but I can't run case analyzer due to USB disconnects that happen with a virtual OS.

I have the SSV wire csv on one of my profiles, but it is useless. I just use the standard Ti csv and it works great.

The only theory I have right now is that the mod goes into "ohms lock" mode. I just went into that profile and clicked unlock and it behaved as it it was locked previously. We could use some indication (on the mod?) if it is in locked mode. I don't use ohms lock as I just usually toss atomizers that require it into the trash, so if that is the issue, I have no idea how it arrived there.