VapingBad

I don't think it is unsafe as the board will see how much it struggles to provide enough current and lower the power, but definitely not a suitable battery.

Yep https://evolvapor.forumchitchat.com/search?keywords=bluetooth+&searchin=message&member=&do=findposts&id=&replies=atleast&numreplies=0&daterange=0&custdatefrom=&custdateto=&sort=&order=desc&radio_showas=threads&btnSearch=Search&action=doSearch IIRC no in the short term focus had always been quality and readin between the lines it would raise price and design time while adding zero to vape quality, but not ruled out in the medium or long term. ETA that suites me fine, vape quality is king and glad they have USB memory flashing that can recover if something goes wrong and your device seems un-connectable.

Check the cell voltages in Device Monitor, it could be one cell is full.

It could be the watt hours are set too low, it has measured that you have used them up so shows 0, my rolo does this with one set of batteries, but I leave the watt hours as they are spot on for the other two sets of batteries I use in it.

It is the most likely reason, looking at your OP the contact could be getting better as the wire warms and expands so lowering the resistance, the res is so low on dual Ni coils that even a small contact resistance can give you issues.

0.06 sounds more likely to be correct with dual 10 wrap Ni coils then the other values, I would check all the coil connections are tight and gripping the wire properly.

You can only change preheat through EScribe, but you can base your profiles on different preheat settings and change most everything else when out and about like material, temp and power, but not temp dominant. It could be poor battery connection causing your other issues try cleaning them and checking tightness. From the common problems thread: Warranty Service Error Message: Warranty error means that the logic voltage regulator is running out of spec. That could be due to a soft short circuit somewhere in the logic circuitry, a total battery voltage under 4v, or similar. Verify cell voltages and replace battery if needed or send mod in for service if the battery is to spec.

Have you turned off temp protection?

IDK, it's a great resource, but you only need it for materials you don't already have or mixed material coils.

If it is a single material all you need is the correct material profile, I use the inbuilt 316 one for 316L.

IDK, but as I said if you look at the csv the voltage difference between 31.5% and 95.2% is only 0.07 V so it's going to be extremely difficult for any mod designed to use a 3.7 V Li battery to estimate a percentage with any accuracy in that range. The voltage sag during a puff would be far larger than that 0.07 V and may explain why the meter shows it as empty. Say before your puff the battery is 3.30 V about 77%, during the puff it sags 0.2 V to 3.1 V about 4% then recovers to 3.295 V after the puff about 73%. I am making the numbers up to illustrate how a tiny difference in that batteries voltage makes a far larger difference to the estimation of charge using the csv.

You can override ohms in Atomizer Analyzer or set and lock them in a profile.

The colour of the tabs is not enough to identify them /topic/66568-topic/

It could also be the screen brightness while firing, EScribe Screen tab. But most likely is the screen cable contacting the fire button actuator, in EScribe - Help - About EScribe click the logo 7 times to put in debug mode, then open Device Monitor and look at the value for Screen Disconnects it should be 0, if it is more the the cable is probably getting caught by the fire button actuator.

The main thing is not to charge the LiFePo on the DNA 75 as it will try and charge it to 4.2 V and as far as I am aware there is no way for a use to change that.

Had no issues with ss or new coil prompts with SP5 myself and had a dual triple twisted build running on during the beta and since release. It could be a connection or grouping issue I had similar issues last year with one atty when it cooled over night and cranking the coil grub screws with the L shape wrench cured it. I never lock the ohms so can't really comment on that other than sorting the fluctuating res will likely fix that.

Markyt123 do you have the same battery as one AMDtrucking used? The csv only acts as a look up for the board to estimate the battery level and will only be valid for that make and model of battery, it does not affect performance. By that csv the voltage difference between 31.5% and 95.2% is only 0.07 V so it's going to be extremely difficult for any mod designed to use a 3.7 V Li battery to estimate a percentage with any accuracy in that range. It is worth checking all your connections are clean and tight, and looking at the voltage sag in EScribe to better evaluate if your battery can work, but If it can't you can use a more standard battery so all is not lost. (The DNA 75 was not designed to use LiFePo4 batteries, they are not supported and you are in the at your own risk experimental zone, not saying it's impossible, just not supported.)

Just measure the cell voltages via the balance lead, each adjacent pair are one cell, if they match what EScribe says it is the battery.

Sorry been typing left when it should have bee right.

Your fw is up to date then, the version of fw the device is running is shown in the bottom left of Device Monitor, this shows the latest version.

It is more likely to be 5 clicks, watch the screen as you do it the display will change when it locks or unlocks.

The number of lock clicks is configurable, 5 is the default, you set it on the theme tab and it will still connect to EScribe if it locked. Don't forget to upload settings to device after making changes in EScribe.

The version of fw the device is running is shown in the bottom left of Device Monitor BTW. Enjoy your new mod!

Don't worry you can't brick them, the fw update process had been designed to be recoverable. 3rd section on the product page "Click Here to Download Escribe". Just install, connect your DNA (with or without batteries both work) and it should ask you if you want ot update the fw if it not already up to date, you can force it to update the fw by clicking apply service pack in the tools menu as well.

The current release is on the DNA 75 product page https://www.evolvapor.com/products/dna75 or you can try early versions at the link in my footer, but both are the same fw version for the 75 at the moment.