stuartro

Thanks for the help, Bill. My mod is currently stuck at 73% (showing charging current of 0.05A). I'll leave it charging overnight and see what happens---at the current rate it will probably still be balancing by morning. Is there a way to accelerate balancing? Also, I'm curious as to what is going on electrically as part of the balancing process. Is something that is specific to the DNA200 board, or a general LiPo thing? Thanks again.

Okay, I'll give it time and see what happens. Any idea why the cells would be unbalanced?

It's not "fully" charged (i.e. at 67%) as I've been using it a bit. Device Monitor currently shows the following: Pack: 12.14VCell 1: 3.99VCell 2: 40.8VCell 3: 4.08V Odd that the cells aren't all the same.

I have a VaporShark DNA200 (about 10 months old) that has started acting weirdly. I plug my mod in at night to charge and by morning it is at 100%. Until a few days ago it always charged to 100%. Then, 5 days ago I noticed that it was "stuck" at 72%---but still showing the lightning bolt icon on the battery indicator, with the fire button glowing red, indicating that it was still "trying" to charge. Three days ago I decided to see if the battery was flaky and installed a new FullyMax (from http://sweet-vapes.com/vaporshark-dna-200-lipo-battery.html) battery. On the first charge the device charged to 100% and I thought I was good to go. However, after using the device most of the following day and charging it overnight, it only charged to 69% (on the brand new battery). Now, today (still on the new battery) it only charges to 67% before getting stuck. Does anyone know what might be going on here?

Just installed the new firmware and it's working very well. I love the new "temperature dominant" checkbox... VERY cool that this (long requested) feature can be applied on a per-profile basis. And the new "Materials" section is very well done too. Kudos to Evolv! You guys have done a superb job on this. And, yeah, it was worth the wait :-) Only little issue I've run into is that custom screens for "hold to change temp" and "hold to change power" seem to be swapped around, showing the "power" image for temp, and vice versa. I just clicked "Default" for both for now, so that the standard "Hold..." text displays instead of my custom screens -- either a minor bug or misunderstanding on my part on how to set this up. Thanks again for this update!

I had this once when the adjustable centre pin on my Griffin was loose, and at other times when screws on nickel coils had worked loose over time (likely due to expansion and contraction of the wire due to heating and cooling). Might be worth checking your build deck / coil for loose connections, check screws on coil are tight, etc. Hopefully it's that simple and not a hardware issue.

Yeah, I know that (as, I'm sure, do all those who've posted on the "temp change" feature requests). Doing so multiple times per day gets to be tedious, though.

I also have a VaporShark and have a slightly different issue with the fire button. Sometimes, when I press it, it makes the usual audible click but the mod doesn't register the click. At other times, I press the fire button once, and find my device is locked--that is, the mod seems to have received 3 clicks. Makes me think the fire button is "loose" inside or has a partially faulty electrical contact. Haven't wanted to ask for a replacement, though, as it's my primary mod and don't feel like dealing with the hassle. Just learned to press the button harder when firing.

I recently became interested in tracking how many puffs I take per day and added the puff counter to the displayed fields. Super feature. It would be even better if I could reset the puff counter at the start of each day from the device itself. Would anyone else find such a feature useful?

No, my VaporShark is working the same as when I bought it. Which means that when I switch between RTAs (which I do frequently to avoid olfactory fatigue), I do the change temperature ritual frequently. My primary hope for an update is the ability to adjust temperature from the "main screen" while in TC mode.

I'd prefer *any* update... just some sign of life.

Add to that the fact that the Reuleaux RX200 has Mac OS X support for upgrading firmware. While I can appreciate that software takes time to create and needs to be carefully tested (I've spent 20+ years in software development), I am growing increasingly frustrated by the lack of any new releases addressing the requests / concerns raised by users on this forum. Previous "early releases" were released at an interval of roughly one per month, but it has now been 3 months since the last "early" release. Any word from Evolv on when we might see a new release will be much appreciated (though I understand, is probably unlikely).

+1 It speeds up too fast, and then rushes past the value I'm trying to reach. Rather annoying.

I agree. I'm guessing that Evolv care about these forums and have a moderator / admin—perhaps everyone's just away for the Christmas break?

This has been requested *so* many times, with no response (at least, that I've been able to find) from Evolve. There has been a long delay since the last beta firmware upgrade, so it's possible that Evolv are working on this (and other much-requested features), but the recent lack of response by Evolv on this forum has reduced the hope and excitement that I once had, and has me looking towards China for something with a better user experience.

This has been requested (multiple times) and there is a fairly long discussion about the request. See /topic/66948-topic/

A Mac version would be a really sweet Christmas gift . Though I'm not holding my breath...

I'm curious about the release schedule. Previously the release schedule showed roughly 2 releases per month, but since 21-Oct-2015 there have been exactly zero releases (unless I'm monitoring the wrong part of the forum?). Is Evolv planning a special "Christmas release", or will there be forthcoming (EScribe and firmware) updates at some point?

Good to hear I'm not losing my marbles . Does anyone from Evolv monitor these threads to keep track of bugs? If not, does anyone know how to make Evolv staff aware of this bug/regression?

I was under the impression that the resistance value specified in the Ohms section of each profile (under Settings > Temperature) was the actual resistance of a coil (at 70 F). Are you saying that it is a delta or threshold which, when passed, will cause Resistance Lock to "unlock"? That seems sort of counter-intuitive to me, as then each profile will pick up whatever resistance the coil is currently at---and attaching a warm coil will result in coil resistance being misread, with resulting mouthful of super-heated vapour. I've read through the eScribe Manual a second time (in detail, this time), but there is no clear description of what the resistance field beneath the "Ohms Locked" checkbox does. If I have misunderstood the purpose of the resistance field, please can someone from Evolv correct my understanding? If I have understood its purpose correctly, then switching from one profile to a profile that has the resistance locked and value specified (in the resistance field beneath the "Ohms Locked" checkbox) should cause the DNA 200 to use the specified value as the resistance and not auto-sense the attached coil's value. If my understanding is correct, then there is a bug in the latest (pre-release) firmware.

I, too, would like to be able to control temperature (instead of power) without having to lock, press and hold + and -, adjust temperature, and then unlock again. In TC "mode" (yes, I know there are no distinct "modes"), it makes sense (to me, at least) to have the + and - buttons adjust temperature, and have the "lock, hold + and -" thing adjust power. While when running in non TC "mode" have the + and - buttons adjust power.

For a long time I have fought a (seemingly losing) battle with my Kanger Subtank Minis, where resistance on my nickel builds slowly climbs from 0.12 ohms (to 0.14 ohms, then 0.15, 0.16, 0.17, etc. all the way up to 0.19 ohms at times). I have explored all sorts of root causes---loose connections, loose screws on the RBA deck, juice leaking (spitback from the coil down the bottom airflow hole, it seems), etc. I've experimented with various builds (single strand 28 gauge, twisted 30 gauge, vertical coils, etc.) and various wicking options (more cotton, less cotton, etc.). I bought a VaporShark DNA200 because of the resistance lock feature (which works, provided I don't switch tanks). Once I switch tanks (or, more accurately, when I switch back to a previously used tank), the resistance that is read is higher than the actual coil (e.g. switch back to a tank with a 0.12 ohm coil, but DNA 200 reads 0.17 ohms). So, I created a series of profiles with resistance locked at 0.08, 0.09, 0.10, 0.11 and 0.12 ohms. I figured that switching to one of these profiles would lock the resistance at the specified value. This seemed to work with the previous (30-Sept) firmware, but no longer works with the latest (21-Oct) firmware. Since installing the 21-Oct firmware, when switching to a profile with locked resistance (e.g. switching to a profile with resistance locked at 0.12 ohms) the DNA 200 ignores the resistance specified by the profile and simply sets itself to the read from the coil (e.g. 0.17 ohms). This should not be the case (in my opinion), as it defeats the point of having profiles that can "lock" resistance to a particular value. Also, as a side-effect, I've noticed that switching tanks causes the DNA200 to "forget" about the fact that I had resistance lock turned on (manually, not via a profile). Thus, as resistance begins to drift upwards, by the time I notice that resistance lock has turned itself off, I find that the resistance is high (e.g. 0.18 ohms). Turning on resistance lock at this point doesn't help, as the resistance is now too high. The only way I can work around this is to turn the temperature way down (I normally run it at ~ 450F, and have to turn temperature down somewhere between 280F - 330F). I'll be most grateful if this can be solved.