

mstave
Members-
Posts
68 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Everything posted by mstave
-
I have the same issue with the mod reading ohms 0.3-4 ohms too high and jumping around. Emailed Nick to ask if I should send it in to Evolv, or just send it back
-
I have had this problem with wire that read off what Steam Engine reports. If you want to use the wire, try this - set up the Wire Wizard page with a dual strand of twisted 30 wire, using the smaller guage wire than yours, same ID and # of wraps - use 316L for one and then try 430 for the other - if the resulting coil resistance is close to yours, note the TCR reading, and then put a new profile in your mod, set the material to the TCR from Wire Wizard, then try the vape. If the resistance isn't close to yours, try lowering the guage of the SS430.
-
ChunkyButt's right - mine reads 0.004 (I have the tool)
-
Update - there are several settings that sort of look like each other - found another one that indicated count since reset, and that that one worked! Thank again - you were right the first time
-
I'll check, although I would've thought that the escribe stat reset would zero out that no matter what the theme used OK, changed the setting to ->since reset - no change in behavior. Reset stats from escribe - no change Good thought though, and I thank you for the suggestion
-
When I select 'Yes' on reset stats screen - nothing happens, puff count does not go to zero. When I reset statistics within escribe, am asked if I'm sure, I select yes, it tells me stats are reset - no change on the puff counter. Anyone know what's happening here?
-
Looks pretty good (can't see the material curve from that screen). Your pre-heat is set for 120W and 2s - unless you are using coils with a lot of metal, that's likely a bit of over kill. Connect your mods to escribe, invoke device monitor and check to see how the coils behave under that pre-heat - could be good, could be too much - then adjust if necessary
-
SS430 in TC Mode - Steam Engine curve not as good as using TCR?
mstave replied to mstave's topic in General Discussion
Turns out other dia. SS430 wire works well with the dna curve. I suspect I got a bad batch of wire -
SS430 in TC Mode - Steam Engine curve not as good as using TCR?
mstave replied to mstave's topic in General Discussion
I replaced the Steam Engine Wire Wizard DNA Curve with a TCR value of 0.0014, and am getting a much more satisfying vape. Device Monitor showed the mod hitting 500F very quickly, and provided an anemic vape. Before changing to the TCR, I carefully checked to ensure that what was on the mod was the same as what the site showed. Anyone have any ideas about why? or what might be happening, or had a similar experience? -
That was my thought, and with Fasttech offering it on pre-sale for $109, I ordered it. I have several HCigar dna board mods and they have good build quality.
-
Latest SP seems to have bricked my VT166
mstave replied to mstave's topic in EScribe, Software and Firmware
Nick has just advised me that my mod issues were related to a bad board, and not, in his opinion, to he SP. They have replaced the board and are sending me the mod back, and asking engineering to review the bad board to figure out what happened. Overall, great service and I am happy. Gonna install the service pack in my new THerion 167 EDIT: Installed the new SP, went perfectly, new mod is ticking away with no difficulties from the SP -
Latest SP seems to have bricked my VT166
mstave replied to mstave's topic in EScribe, Software and Firmware
Update on my Mod (VT 166). Sent it in to Nick at Evolv to look over. Just got the word that they are "working to repair it" and will send it back to me when finished. No word on what they found, as of yet. Beginning to think this may not be an issue with the SP, but not yet ready to install the latest SP in my newly arrived Therion 167....... -
Latest SP seems to have bricked my VT166
mstave replied to mstave's topic in EScribe, Software and Firmware
No update yet, just posted the mod to Evovl, hasn't arrived to them yet -
Latest SP seems to have bricked my VT166
mstave replied to mstave's topic in EScribe, Software and Firmware
Evolv has giving me an RMA number and they will test and, hopefully, fix this issue. I will post updates as I get them -
Latest SP seems to have bricked my VT166
mstave replied to mstave's topic in EScribe, Software and Firmware
Already tried both rolling back to previous SP and the latest. Beginning to suspect I have a hardware issue and the firmware upgrade was sort of coincidental. But I'm now in email communication with Evolv and we shall see -
Latest SP seems to have bricked my VT166
mstave replied to mstave's topic in EScribe, Software and Firmware
1_2_SP5 dated 12/22/16 -
Latest SP seems to have bricked my VT166
mstave replied to mstave's topic in EScribe, Software and Firmware
SP is listed as 5.2, and I installed it at the suggestion of Escribe. -
Latest SP seems to have bricked my VT166
mstave replied to mstave's topic in EScribe, Software and Firmware
I haven't yet, but will. Thanks for the suggestion Edit - Hard Reboot changed nothing, but it was worth trying. -
Latest SP seems to have bricked my VT166
mstave replied to mstave's topic in EScribe, Software and Firmware
Ticket submitted - we shall see -
Latest SP seems to have bricked my VT166
mstave replied to mstave's topic in EScribe, Software and Firmware
Applied the pack, connected the mod (which I had just been vaping on), went to device monitor, which reported that one cell is a 0.001V and the other is a 5.23V. Swapped out the batteries with freshly charged cells (all batt are 1-2 month old HG2), same issue. Any and all help gratefully appreciated (really unhappy camper here) -
Version 1.2 Service Pack 5.2 ????
mstave replied to DNA Papst's topic in EScribe, Software and Firmware
I applied this, attached my VT166 to escribe and the device (which was working less than 3 minutes earlier) now reports that one cell is at 0.001V and the other at 5.23V - both are freshly charged HG2. Emailed Brandon, but I am seriously unhappy, and looking at this SP as the culprit