GaryP

So, in an act of awesomeness that defies all expectations, James pushed out an update to ECigStats within 45 minutes of being told about a bug that wasn't even his. My new copy of the software looks at the DNA Go board and says "yeah, sure buddy... whatever you say" and then promptly ignores the bad domain and inserts the correct one. I can't say for sure when he will have it posted to the website for download, but considering the speed of his code updates, I wouldn't be surprised if it is there already.

So James over at ECigStats is, like, really quick on response times. Apparently this is coming from the board itself and not any xref on their side.

I wonder... does ECigStats pull the reference domain from the device? Meaning... some firmware property is set wrong on these boards? Or does it pull the identifying board info and then perform a lookup against it's own internal/online x-ref tables which would mean a bad entry in a DB somewhere outside of Evolv's control?

Thanks, I've submitted a ticket. I was thinking there might be a way to update that value using EScribe. My guess is that Evolv isn't going to push out an updated SP just to fix a type-o.

When my DNA Go is plugged into my PC, the ECigStats app pulls a bad domain name from the device... Anyone know where/how to change this? I've got SP44 INT on the device. Thanks, -GP

Orion Plus will just flash white 8 times when I use the fire button on the device, but will actually fire correctly when told to do so from Escribe. I'm contacting Lost Vape about this as well, but wanted to see if anyone on here might have a trick up their sleeve to get this thing working correctly again. Version 1.1 SP44 INT and seemed to be working fine until sometime this past week.

Yup. Seems this was not so much a "cold coil" problem but rather the recently addressed "intermittent issue with output voltage boosting with the screen off." Thanks!

I change that setting to "unlikely" and had the same basic results. Interestingly the second and third puffs had a different power curve than before. I wonder if this means the coil is close enough to the noise floor when warm that the device uses what they call that "noise-resilient" mode. Regardless, I do not believe that explains why the first puff is so power restricted.

I can try it, but I thought that setting was unrelated to how Replay works once a puff is saved. I was under the impression that it only affects the threshold for resistance change needed to allow you to save a puff for later replay.

Nope. It's factory settings so currently restricted to viable coils.

I've got a Lost Vape Hyperion with the 100C and wanted to see if I could use Replay with a UB Pro pod tank coupled with the P3 coil. This coil is 0.3 Ohm SS904L mesh and, according to Lost Vape, should work OK in TC mode. My (limited) understanding is that Replay on the DNA will work as long as the coil has some TC properties. And, using the default theme, the mod will let me save my puff. However, the Replay doesn't seem to work when the coil is cold. The monitor capture below shows where I had a puff at 65 watts that I saved. I paused and let the coil cool down, then puffed again and the board maxed out at 25 watts. An immediate second puff and Replay started doing what it should. Let the coil cool again and took a few more puffs. Same thing. Is this expected behavior with "iffy" coils on Replay? Or is there something I'm doing wrong? Thanks, Gary

Did and done, thanks!

I appreciate that link, but unfortunately it doesn't seem to have the latest information. If I understand it correctly, the lower-right of the Device Monitor shows the version and service pack of the board, which for my DNA Go is 1.1 SP44 US. The last DNA Go update described in that forum post is firmware 1.1 SP38. It would be immensely helpful if the board service pack change logs were collected together in an official list, organized by type. Thanks, -GP

I just applied a service pack to my DNA Go... 4.something I think? Anyway, now when it charges it doesn't pulse. Is that supposed to happen? I have no idea because I can't find a change log for these service packs. Do those exist somewhere? Thanks! -GP