VapingBad

Try the Visual Basic 6 runtime https://www.microsoft.com/en-us/download/details.aspx?id=24417 it is a long shot, but one of the components EScribe uses may use something that references that. Also the Visual C++ redistributable, but ther are lots of releases http://www.howtogeek.com/256245/why-are-there-so-many-microsoft-visual-c-redistributables-installed-on-my-pc/ there are links to the packages near the end, the x86 ones would more likely be referenced by components. Both long shots, but if you are thinking about wiping your PC and starting over...

It could be almost anything https://www.google.co.uk/search?num=100&newwindow=1&q=.NET+Runtime++exit+code+80131506&oq=.NET+Runtime++exit+code+80131506&gs_l=serp.12...12495.14072.0.15343.2.2.0.0.0.0.75.146.2.2.0....0...1c..64.serp..0.0.0.4lDT6H5s-hI Are you running it in a language other than English, if so you try changing the Local to English the see if the translation is an issue.

That is the MS dot net common language runtime engine, it confirms that EScrib is encountering an error but not what it is, probably a version mismatch between EScribe and another component it uses. Try running the installer again with just services packs checked in the install options.

“Get Information” pull the data from Evolv's database from when the production utility was run, it's a different thing and not editable.

Yes, start EScribe before connecting your mod, once it is open plug your mod in and it should pop up.

Control panel - administrative tools - event viewer - application log It varies between windows versions, just have good look at errors and warnings.

Have you looked in the application event log? Also I wonder is any disabled services may affect it, my start menu would not open, notifications were not working plus a few other things in Win 10 with the firewall disabled. Also you could try .net fusion logging https://msdn.microsoft.com/en-us/library/e74a18c4(v=vs.110).aspx

lol you are not the only one, I put it in the DNA 200 software FAQ on this forum as well.

You name the mod in the connection pop up dialogue box click rename

You now need to go to the materials tab and import wire profiles there, then add them to the device and you can ten select them in a profile.

Very good point

I get grate reg at 0.19 ohm with the std 316 profile even with dual coils.

SS on the DNA 75 out of the box is fantastic, if the board is having trouble seeing the coils as temp sensing it is either a build issue, wire profile/TCR mismatch, not enough power or connection issue, typically it is not seeing the temp rise enough in the first second. I have never had ss drop out of temp limiting on DNA 75s or 200, but I have been using temp limiting since the DNA 40 was released so only use atties with decent connections and coiling for temp limiting is the norm for me. No preheat for non temp sensing wires evripdis, a good thing IMO as they can never be right for both warm and cool coils.

You could try running Windows update in case there is a versioning issue with the MS dot net framework.

I have not come across this so just guesses, make sure you are connected to the net when starting it could be trying to check for updates and check no firewall, anti malware or anti virus program is blocking it.

I believe they work the same as preheat needs temp sensing and doesn't even get used until the board is sure you have a temp sensing coil fitted. The non temp sensing wire is a new feature and it is probably that they didn't get time to hide the preheat settings when you click off.

Try installing it again, right click the setup file and choose run as administrator, it should not be necessary but worth a try.

I do that and it is very good for spotting fakes, I also would recommend a capacity test as well as IR on it's own is not so clear until it goes right up and then you know they are knackered anyway. It varies a bit between batteries but I find a capacity test is always a good test of battery health if you took one when that battery was in good shape. EG that battery I posted the plot for I measured IR when new as 17 milliohm at 3.65 V and 14 milliohm at 4.2 V, IR is quite sensitive to charge state and probably temp to. I also have another 25R from the same batch that measured 14 milliohm at 3.65 V and 12 milliohm at 4.2 V when new, so the variance between batteries in the same batch is also quite high.

I would avoid using a single value TCRs where possible, they are less accurate than the curves. If you are looking at the TCR value when you click advanced the value shown is not from the curve as they mostly can't be expressed as a single number and that is why you think they are the same that is not correct. I know it has confused people before, the TCR is one way, you can set it, but you cannot retrieve it. Just looking at the number on the right most data point on the curves you should see they are all different. I fined the built in SS316 is good for 316L, I got mine from StealthVape in the UK.

They have cleaned up the app to hide stuff that the average user does not need to mess with, you will need Manufacture to access that setting. From the DNA 200 sw FAQ on this forum EScribe now has 4 display modes accessible through the menu under Options - Interface. The differences in each mode compared to the previous versions are: Clean: no Mod or Research tabs and no Atomizer Analyzer. Advanced: no Research tab and only Charging Mode and Kanthal Power Limit on mod tab Researcher: only Charging Mode and Kanthal Power Limit on mod tab Manufacturer: same as the previous version with the Manufacturer settings on the mod tab expanded

The graphs should be different, are you selecting them from the list on the rhs so the wire is highlighted? Yes to load new wires just download the csv from SE, but you can also start Escribe without any mod connected, select default DNA 75 config and save the wire profiles from that to you hard disk if they have got corrupted.

Just hold [shift] while adding the bars, then [alt]+[PrtSc], then past into a post. Paste into post didn't work as it was too big I had to paste into mspaint and save to disk then add image to post. That is a May 2015 25R at only 3.54 V

I would advise 3.1 for LiPo, 2.75 for 18650s

I'm sure those will be genuine, they have a good reputation, but 26650 are not good for high power vaping they have too much internal resistance. You can see in your post #31 that they sag below 3 V only at 50 W so I doubt that will ever do 75 W for more than a few puff when fully charged. I think putting current on the plots would help you understand how much the battery is struggling. You have to open your pics in a image editor program to add pics. To everyone in this thread: These Escibe screen caps would be a more informative if they had the measuring bars, when DM is paused just click the line at the point you want to show values for, if you hold shift you can have multiple sets.

The ground pad, and output ground pad should be closed with the case, 510 -ve & lowest battery (top in the sketch) -ve. One of the screws for the battery bay provides the board ground, so if that is out for testing it would explain it.