John

Yes, though I can't see a lot of reason to use a 7.4v lipo pack over an 11.1v one.

2s works fine with smaller lipo packs too, its just that 3s works better (more power, more flexibility) so I don't see as compelling a case for it, but hey, options never hurt.

It isn't impossible, we like to keep a good mix of people in our betas, and we are always working on new things.

Yeah something very untoward definitely happened to those resistors. Is there any chance you had the tap connector backwards at any point? We will fix or replace it at no charge either way, just trying to work out the cause. Everything except the highest cell resistor looks burned, and correct main voltage/ reversed tap connector is the only way I could see that happening.

Can you post a picture of the solder joint for your OUT wire? It is possible to make this happen if there is conductivity between the output terminal and one of the vias somewhat near it that carries the fire button signal. Or, go to escribe, go to about, left click on the Evolv logo seven times quickly ( the screen should disappear) to enable the debug options. Then go into device monitor, fire the mod from device monitor (bottom right hand menu) and see if the "buttons" value changes. If there is a short between the output and the fire signal, then pressing the button will fire the mod, and the mod firing keeps the button pressed. Or with a typical .25 ohm atomizer, see if a 1 watt output sticks, or if not there will be a minimum voltage to do it.

What happens if you update the software? It won't try to push an update if you already have the newest.

We will either have reference cases for sale or we will case up boards and have reference mods for sale. Possibly/likely both at various times. I have a couple hundred cases at the moment that I will need to do something with. But we are primarily a board manufacturer, we can make about 20 times as many DNA 200s as we can make reference cases, so case and mod availability directly from us will be pretty spotty.

It is really hard to say if the resistors are correct based on the picture. If you measure across each of the three capacitors to the left of the resistors in that picture, do you get your expected 3.5v cell voltages? Or a sharper picture would help a lot. The screen should come on either way, though, unless there is some sort of cascade failure going on. To make it through test the cell balancer had to be reading right at some point. The ones with the resistor knocked off on the edge I understand, but three existing but white resistors... A sharper picture and an overview pic of the board would probably help diagnose.

For lack of a better reference point, the 900 will give you about the same runtime as a single good 18650. An 1800 mah pack will give you about the same runtime as two 18650s. A 2200 is about the same as two 26650s.

The difficult we do immediately. The impossible might take a few days. Seriously, though, it wasn't a huge change, because we already do everything on a per-cell basis anyway, and the board runs fine from 2s at reduced power. We're are just testing the update and making a battery curve for a representative 18650 and then it should be available to download.

Return to researcher? How on earth did you get THAT? Were you even on the research tab? Which firmware version was this? Also, which mod was this? Return to researcher would be if you were running a research study and wanted it to shut off after, say, 15 minutes, or 100 puffs, or whatever.

You connect the cell 3 tap and the cell 2 tap wires together, set the settings, and otherwise it runs just like normal. It limits to 133 watts, 6 volts max, but still does cell by cell monitoring and still does a balance charge.

Have you tried Tools... Reboot Device... Hard Reboot?

Just to try things, try setting your active, idle and charging brightness all to 100% Also, you're running in profile 8 presently, correct? That was the only one that wasn't set to the default 8.5 watts in the settings file you posted.

BlackouTT, thing is, there isn't a server side of Escribe, except to check for updates, restore defaults, check the history/authenticity of the DNA 200, etc. Everything is client side.

Nope, that's the way to flash it... What happens if you click "Restore Defaults" on the General tab of Escribe. It'd be very easy to explain what you're getting if it never showed the screen, then it would be hardware (or a broken screen cable, or the screen pulled out of the connector) but if it is showing the upload settings screen properly, then it has to be settings.

BlackouTT is yours running really slowly, or is it not running at all? Does it run normal speed if the DNA 200 isn't attached to USB?

2 3500 mAh batteries are 25.2 watt hours. For a similar run time, you'd want a 2200 mAh 3s pack. That is 24.42 watt hours, which should give you equivalent results. Or sit tight for a couple hours and we'll have a 2s compatible firmware up for testing here, then just use your same 2 26650 batteries in series.

Can you save your settings file in Escribe and post it here? If it shows the screen when you are uploading settings, then it sounds like some unfortunate combination of settings. When you put it into stealth mode, did it show "stealth mode"? When you put it back did it show "normal mode"? What firmware version are you running?

Okay, I'm seeing 4 puffs, with a cold resistance of .092, a hot resistance of .162, which is 350 degrees or so, and 35ish watts of power. That all seems pretty normal. What were you getting out of it for these four puffs?

.25" spades will do 25 amps, and are not as expensive as XT30. Something along the lines of http://www.digikey.com/product-detail/en/42100-2/A27936TR-ND/288361

Zip it then upload it. =) But five seconds at 35 watts-ish and you don't get vapor?

Those are better if they're appropriately sized. Use 18 gauge or heavier wire.

Well, two of the three I have were definite clearance issues. The other was likely also, but I cut the board apart looking at it, so it is getting a brand new board.

You have battery voltage too. It isn't hurting anything, but the less items you're graphing the faster it updates. The .csv file should let us see exactly what it is seeing as it fires.