blueridgedog

I am thinking of giving this a try: http://www.eciggity.com/billow-v2-rta-by-ehpro-eciggity/ I have only done dual coils in a dripper, but I bet this would be interesting.

Ok, so if my RTA could flow more juice, I would get more vapor as it would use the wattage available as it sagged in temp, so folks with say drippers would dial back the wattage and just vape under the set temp so not to blow big clouds? Personally I would love, LOVE to find an RTA that would flow more. I like my Tailfun's but would love to get some more vapor from time to time. Any recommendations as I am a tank guy for certain.

When in TC mode why would you ever change your wattage? Why also would you not simply set your TC mod to its max wattage? (non-rhetorical...curious) I am set at 200 and vape at around 20 or so to keep my set temp. The one reason not to I guess is in the event that it may jump out of TC mode, but I have never seen that to be the case with the 200 and a standard nickel coil. What am I missing?

If they fit the hole and have the same rear offset so there is room for them, yes.

Perhaps this has been addressed and I missed it. In TC mode, why is the default up down action changing wattage? When in TC mode the only thing I adjust is temp. I generally set it to 200w and let the chip do the rest. However, changing the temp is a long process.

Unplugging the battery is a manual reboot. So it fails to charge on a wall plug and a PC port and the PC can't see it as a device...after a hard reboot? I would open a ticket.

My bad then. I thought you were dealing with a Hana that omitted it, using the case as a ground.

I am still using Virtualbox for settings adjustment, but will only flash with a PC now. I hope there is a mac version one day....

Through updating firmware in a Virtual machine, my chip became unrecognized. I was able to restore it with a windows system and a manual firmware upload.

Personally, at the discharge rates being used, I am not that concerned with swelling.

I and others have found an intermittent pulse in using a guest OS (parallels, Virtualbox, VMware). So far it looks like 8 of 10 flashes will work, put it will occasionally crash mid firmware flash. In my case, I needed a windows system to resurrect it.

I get that in XP as well, not in 7,8 or 10.

I just can't fathom the reverse install of the dean's plug, but the chassis is really great IMHO.

James: Is the chip still calculating a "remaining" graphic based on load/ohms of the atomizer?

I have thought about this a bit as well, but my reluctance has been that this is still an evolving (no pun intended) technology. Have we hit the platform that will be around long enough to design to and develop for? Perhaps, but perhaps not. To me the 200 is second generation TC, i.e. it takes the ground breaking offerings from the 40 and enhances/extends them significantly. How far along the innovation J curve are we? Is the 200 still at the lower end prior to rapid development phase of vaping engineering or is it in the middle or top end? My opinion is that the industry as a whole is in a period of rapid development and we are going to see significant technology brought to the table in the next few years. I would think that the concept of a "developer's port" is ripe for the DNAXXX that would represent 3rd gen TC.

What are the cell voltages in device monitor?

...and it can be if they fix these issues. It is a good design and the case is well made, just shoddy assembly.

What is the battery reading? What is each cell showing in device monitor?

I was thinking custom screen too. Possibly new/old coil.

Given the safety issue, you should cut off each end and put on a connector correctly.

Did you add a ground wire?

Good catch...they put the deans on backwards...wow.

Is that virtually none in the 430 to 450 range?

This is an intermittent USB connection issue with virtualbox (on the Mac, not tested it on Linux yet). Just a word of caution that if it "pauses" while you are updating firmware, you will need to potentially manually update it. I also had an issue where after a failed firmware update, virtualbox would not see the device to restore the firmware, but a PC could.

I just ran a test with the current VirtualBox and a good cable. I get intermittent "phase out" that you can see in device monitor. This is worse if the host is emulating USB3 and is least at USB1.1. I suspect this impacted the last firmware update.