Leaderboard

This is a straight fit as far as I experienced, only thing to watch out for is the screen “display area” is just a bit narrower than the dna60, so you have to make sure it’s lined up properly not to look wonky here’s my retrofitted BB - been running it as a daily for month now

EScribe Suite 2.0 SP69 For US-based customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP69_US_ServicePack.exe For US-based customers (Mac): https://downloads.evolvapor.com/SetupEScribe2_SP69_US.pkg For international customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP69_INT_ServicePack.exe For international customers (Mac): https://downloads.evolvapor.com/SetupEScribe2_SP69_INT.pkg If you would like the Oxva-specific version, https://downloads.evolvapor.com/SetupEScribe2_SP69_OXVA.exe For customers using Linux, see the beta thread. --- Oxva Pro 2 DNA --- This version may reduce the frequency of Fill Pod errors when using Replay, when Replay is set on the first puff after connection. This version also adds puff trace recording to Oxva. You can view puff traces on ECigStats. It records Power, Live Ohms, and Battery Voltage. (We're hoping to use this recording to see how effective the Fill Pod change is. That said, it's also a nice feature -- you don't have to be connected to USB any more to get a recording of your puffs!) Definitely let us know how it works for you! Enjoy --- EScribe Suite --- Bug fixes.

I've ported Linux EScribe SP68 from GTK 2 to GTK 3. Some newer systems didn't have gtk-sharp2 easily available, so this should make those systems usable. *This is still a test version*, but if you'd like to try it, let me know what bugs you run into! https://downloads.evolvapor.com/SetupEScribe2_SP68_INT_GTK_Test1.run The bugs I've found so far are: (1) Multiline labels such as in Atomizer Analyzer don't lay out correctly. (2) Text fields with escape codes (such as Format and Label on Small Screen Pod devices) don't save properly. (3) Occasionally, dialog boxes are misaligned relative to the window that is showing them. Enjoy God bless. James

I am going to post here software and firmware Service Packs before they go on EScribe Suite's auto-updater, for those interested in trying things early, and so if yall find a bug we don't release it to the auto-updater. We appreciate your help testing these. RECOMMENDED SERVICE PACK EScribe Suite 2.0 SP68 EARLY SERVICE PACK EScribe Suite 2.0 SP71.1

EScribe Suite 2.0 SP71.1 For US-based customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP71_1_US_ServicePack.exe For US-based customers (Mac): https://downloads.evolvapor.com/SetupEScribe2_SP71_1_US.pkg For international customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP71_1_INT_ServicePack.exe For international customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP71_1_INT.pkg If you would like the Oxva-specific version, https://downloads.evolvapor.com/SetupEScribe2_SP71_1_OXVA.exe For customers using Linux, see the beta thread. --- Oxva Pro 2 DNA --- Added an option in the Safety tab to adjust Fill Pod detection. --- Theme Designer --- Added an "Import Animation Frames" menu option for Meter and Picture controls on devices which support animations. (This saves you the trouble of creating a WebP file.) Fixed a bug introduced in Service Pack 69 which caused some themes (specifically, those with conditioned Labels with padding) to refuse to upload. Fixed a bug which caused some themes (specifically, those using known() and unknown()) to crash on older devices. --- EScribe Suite --- Fixed a crash when downloading settings on DNA Go and Reflex. Fixed a Linux (GTK 3) stability-related bug. Miscellaneous bug fixes and improvements.

@Magigamix, I'm glad it's working for you! Turns out the bug wasn't Linux-specific, and was a rather serious bug! Thanks for reporting it! @Alessandro D.... Wow, investigating on Debian 13, the installer script is looking for the package libgtk-3-0, which they have renamed libgtk-3-0t64. Also, they've removed the locate program from the default install, which was my fallback in case the package lookup didn't work. I'm not nearly smart enough to understand the wisdom of Debian, but, I'll change the script to look for libgtk-3-bin. That at least does not appear to have changed. Thanks for reporting this. It will be fixed in the next version. For what it's worth it would have also offered to install mono-complete if you hadn't installed it as well. ECigStats still seems to be broken. I'll need to investigate that.

EScribe Suite 2.0 SP66 For US-based customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP66_US_ServicePack.exe For international customers (Windows): https://downloads.evolvapor.com/SetupEScribe2_SP66_INT_ServicePack.exe If you would like the Oxva-specific version, https://downloads.evolvapor.com/SetupEScribe2_SP66_OXVA.exe --- Oxva Pro 2 DNA --- Added support for this pod device. It has power control, Replay, customizable color schemes, support for 11 languages, and ECigStats support. --- Experimental Prelease Devices --- Test if you're interested. DNA 55 Color: This has customizations appropriate for pod devices, such as automatically distinguishing between different atomizers by resistance ranges -- see Mod->Atomizers. There's support for power control and Replay. Like a Color DNA, the user interface can be edited with Theme Designer. The Theme Designer support is a work in progress but does have some new features. DNA 80 Color Pod: This has customizations appropriate for pod devices, such as automatically distinguishing between different atomizers by resistance ranges -- see Mod->Atomizers. (You can switch between Color and Color Pod by applying firmware.) --- EScribe Suite --- Production Utility has been upgraded to support scripting and higher throughput operation. Bug fixes.

Here you go

yes something is wrong somewhere, ive just soldered the 510 when checking with a meter earth and 510 pin no fire button pressed im getting voltage of 3.2v then press the fire button and no change, Ok it looks like im gonna have to pull it all out and see whats happening, Hopefully i notice something this has totally baffelled me. Thankyou both @dwcraig1 @Wayneo for your time and patience i will start testing connection when i get a bit more time and hopefully have a good outcome

It looks to be wired correctly to an Evolv C board. Avoid using a USB hub.

Yes, I understand the problem, but in my opinion you should focus on the board temp primarily. Afterwards we'll look at resistance. Plug in the 75C mod (nothing attached to the mod) How much does the board temp rise just sitting there and not being used? Note down temp after 2 minutes and 20 minutes after being plugged in. Leave mod and escribe running. Attach Bakx. How much does the board temp rise just sitting there and not being used? Note down temp now and 20 minutes after being plugged in. Report back those 4 temps like below , and battery description. 75C Nothing attached 2 minutes (temp here) 20 minutes (temp here) 75C bak attached 2 minutes (temp here) 20 minutes (temp here)

I would say there may be some resistance in the path of the power from the cell to the board. I say that because you said that you tried higher current cells. You have to have the power availible.

That is the default Evolv theme. Connect to EScribe, go to themes, save your existing theme if desired and select default theme and upload to device.

Sounds like your coil. Maybe a small hotspot has developed. You can run Atomizer Analyzer to look at the stability of the coil. It should fluctuate a few thousandths of an ohm once it's cooled down.

I think you are right about where the problem is. Take a good look at the solder joints on the board where the board half of the JST plug is soldered on.......for starters.

Thanks mate, me too. Something so simple as well.

We all have blonde moments, glad you got it working 🤙

@alsk1 Just spam, I removed the link. 😂 Normally we Just remove the entire post and ban them

That might work for now, but you should really dismantle and wipe off the board with isopropyl alcohol. The buttons on the board are 3 piece buttons that are easily dismantled. The outer silver with the rubber pointy sticking out. The outer steel can be removed with a flat screwdriver, which exposes the rubber portion, below that is like a silver wafer. Below that wafer is the hard plastic portion soldered to the board. Once you get escribe working, the bottom line in Device Monitor displays when a/if a button is pushed.

Hope you have a voltage meter. If they're both at 4.2V then you need to check and clean all the connections. Both the XT30/60 and the balance cable connector ends starting at the battery side. IIRC pin 0 (-)&1(+) would be cell 1, pin 1 (-) @2 (+) would be cell 2. Each should show 4.2V PIN 0, on the board is the tiny hole at the left when you're seeing the 2 inductors (or no visible buttons). This diagram is for the 250, you would not have pin 4 The photo below the diagram actually shows a DNA200, face/buttons up

At least 1 of the two batteries might be below ~2.8V.

And yes I will update as soon as I work out what is going on and the devices are recognised as connected

Then I have no idea. You can open a 'Help Desk' ticket and ask them. Link in my signature line.

Not possible, but (on your mod) you go to settings, then scroll up to the 4 dots at the top, push fire button, you'll see your puff count there. Reset using escribe.

So I didn't connect pin 15 because I thought it was only required for non Evolv boards. After connecting it works now! Silly me.

Is the USB port on the mod recessed more than normal? There have been reports of the USB plug not being able to go in the port far enough on some 3d printed mods to connect. What mod are you using?

Perfect. This worked. Thank you.

If you have connected this mod to EScribe on the computer that your using before a backup was made. You can find it by connecting to EScribe then under the "Help" tab you will find your backups under "Backups".Search by date and model from drop down window. Be sure to upload to device once you select it. While this isn't going to change the firmware version it will contain your .ecg file and theme. The .ecig file is your settings.

There's a whole lot of folks don't get it about amp draw from the battery vs amp output from the board

Your battery cells are so low that they can not be safely charged. Looks to be 18650s so an easy fix. Replace them. Probably why the screen doesn't work as well. Charging is suspended if a cell is under 2,5 volts.

Was it this way yesterday when you first purchased it? Yes. I believe if you purchase a new screen from Stealthvape in the U.K it should fix your color issues, and Stealthvape should be able to verify.

You have 8 profiles where the ohms and temp are written in case you set them up that way. You're seeing that with no atty. No, but whaetver firmware you choose you should use the International version (more features)

Hussar replaced/repaired the USB C port. It their own design not one like the charging board/USB C that Evolv can supply. I am now able to connect to Escribe using an Apple USB C - USB C cable as supplied with my new iPhone but using a small adapter to allow connection to my PC USB A port, so I have been able to make my usual adjustments to wire types and profiles etc……Hooray! Strangely my USB A to USB C cable from Anker didn’t work.

VC have battery life issues even with their own chips, I found this out after making this post. I supposed countless products in they would have fixed them but doesn't seem the case.

That's pretty funny considering these were 3 dudes with VC San Aio's. Then this happened.

The DNA80C doesn't have the ability to change the cell software cutoff through EScribe. Normally a hi amp round cell would be set to 2.75 volts. I believe it's set to about 3.2 volts via the firmware. You can use EScribe's Device monitor to see just what the voltage is when it throttles down. It appears to me that it is a connection problem between the cell and the board as your choice of cell is good. The San AIO has/had a similar problem because of the top plate. If your able to easily access the board make sure the 3 mounting screws are tight as that most likely is how they did the ground.

The power from the batteries have to make it to the board. A few things can stop this from happening correctly. Example, dirty batteriy contacts, loose fitting batteries, weak cell, bad solder joint ect. What board model?

Oh so that's how you hook up a charger board on a DNA60/60C that doesn't come with one or have room for one so that it can be connected to EScribe to make changes and/or update the firm ware.I was wondering how folks were doing it.

oh god. This burns my eyes to see. Please, nobody do this. how expensive is a replacement evolv charging board? I have a 250C so idk what they cost, however, I know it can't be that much that you should run janky as this pic. Not even any type of protective measure from shorting on the pins against each other? I wouldn't run something this janky and sketchy for money. No solder mask over the points of connection? Not even any electrical tape to spare? Whew, God bless you sir.

How can I help when that IS NOT an Evolv product? Find the pin layouts on line, or ask the manufacturer. This is now the third connector you are inquiring about, what happened with the connector from a few days ago?

Anybody ever try creating a portable version of EScribe? This would allow one to run EScribe on any PC without installing. Especially handy if it isn't your PC.

These are rough comparisons between the two boards screens and their physical sizes. Proper engineering diagrams would show exact dimensions, visible areas and bordering. NOTE: The "viewable" screen area on the DNA60C is the same size as the DNA60 and falls in the same location ⬇️ Black and white DNA60 ⬇️ ⬇️ Color DNA60C ⬇️

Please try to remember to update this post with the information from Hussar so other purchasers will know.

I AM STILL SURPRISED THAT A COMPANY AS SERIOUS AS EVOL DOES NOT HAVE A MANUAL FOR SOMETHING THAT IS ALREADY BEING MARKETED

It's great to have an exclusive mod with your own signature. After this, maybe you need a custom box for your vape accessories like me. 🤓😅😊🤭

no, i build coils at around cold 0.5ohm (mostly all of them) and all of them act strangely. i ll explain the whole procedure: i remove the atty, dissasemble it,remove coil(0.5ohm),wash it and let it dry. the settings on the device are tc 316 30w 260C preheat 45. i build another coil with the same wire same id same wraps, i get around 0.495-0.505 ohm on the ohmmeter, install everything and put the atty on the device. next i let the device cool down, resample the coil and start vaping but my old settings (30w,260C,45preheat) are too aggresive, so i need to lower the temp to 170C+. i vape a couple of days and start building another coil, same wire, same ohm and the device is too soft to boil the liquid so i invrease back to 260C.. it's werid

If you got the error on my Color Changer theme then the good news is it was indeed a bug in the theme & not your device. The theme had trouble remembering what parent screen to use after 6 consecutive color changes without going to another screen on the 100c or 7 straight color changes on the 250c. It was indeed a child/parent screen hang up but interestingly not from a missing or bad call. The same call worked as long as you didn't do 6 or 7 color changes back to back. It had to do with the chip memory being so maxed out imo. Rapid color changes would cause it to forget the needed parent & the error sort of reset it. Anyhow it is resolved now. Once I truncated some things, shrunk the theme, & got more headroom in chip memory it resolved itself. if you haven't updated do so & its fixed. I also came up w/ a better system to cycle colors more easily in general in newer versions. My new theme "The Giant" changes colors & is an all original theme that uses color combos tht you can cycle through. If you liked the Color Changer theme you'll likely enjoy "The Giant." Hope tht helps! If it wasn't my theme then I agree tht it's most likely an improper call between a child & a parent screen in the theme. It still isn't a flaw of your mod/DNA.

OK, that sounds good. I just was confused abbout the explicit mentioning of the 18650 in the battery settings. Then it would make sense to just mention Li-ION in that dropdown menu instead of mentioning a specific battery-size. With "my theme question" you mean my post in the themes section asking for confirmation that the "Simple Theme xxx.v.2.0.4" is working on the Therion ? *confused again!* 😉 ... anyway... Thanks for the clarification about the batteries !

I think I may have finally found a justification. I've wired up about 10 of these DNA's in my pre-production Round 1 and I've noticed that every time I go and wire the positive and negative to the board it sparks on the initial connection.. Is this due to the fact that its default is constant on? If the default was the chip being off and needing to be turned "on" would the initial spark connecting the leads happen? Thank you,