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

So depending on how much wire was left on the board and room in the enclosure, you can either solder to the board again or use a connector to match the battery connections. XT30 is a 30Amp connector and the XT60 is 60Amps, but there are many.

My 2010 Darwin still works and got me off cigarettes. Here is a 13 year old video and pictures of my 15 year old Darwin that still works as good today as when new.

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.

This version of the Oxva DNA theme was created solely for a simpler, more contemporary look. Please feel free to download it if you like it. tema cold.ecigcolors

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.

The wick had time to re-saturate perhaps. I'm going to send you a message.

Let me give you a general explanation based on what you have written. Replay wants to recreate the puff you saved. Your coil/mesh will raise its resistance when you fire it, and lower its resistance as it cools back to ambient temperature. When in your 'Replay' mode, but NOT enabled, the mod keeps track of that resistance curve created by your puff. And when you click 'Save Puff' your mod tries to recreate that curve. Sometimes exactly, or at lower wattages. Your mod 'right now' shows 'boost:Punch' at 3 (but not on), 'warmth' at 1. So right now you get no boost of watts initially, and it's just 50 watts. Once you click 'save puff' warmth now enters the picture. IF you were chain vaping your coil before enabling replay and your coil has cooled to ambient you will get even more watts than 50 but not too much. That's warmth. OR depending on different factors you definitely get less watts than what you initially set. Like if your coil is not as saturated as when you enabled replay. You can actually vape that mesh almost DRY without a dry burn. If you have any questions or want me to clarify anything let me know. Or if I have cleared up your understanding.

Hi all I making my own mod have soldered everything where I believe it should be using a 2amp charging board for the dna60c, plugged it into escribe it detected the board then said no device connected. Have tried several USB cables but no difference, it connected one time started to up load the settings and stopped at 6% and wont go no further and escribe just has the spinning wheel I can't even Close escribe. I'm using windows 10, Any help would be appreciated as I am gutted was the last thing to do to complete the build. Have attached a pic below just incase someone can see something I've missed Cheers Si

The situation where you have 3.2 volts between output and ground is troubling. This is something that I have no experience with so I measured the voltage between output and ground on two of my DNA60s and my one DNA60C, all three read about the same, just over 0.7 volts. And no change if fire button pressed.

IMHO you've gotta meter out all your connections. For the USB-C you know it has worked outside the box. I'd lift that off and see if it connects, then lift at the board end if it still didn't connect. What else could it be? Same thing for the battery. Using 1 battery, measure it externally then in each slot at all the connection points to the board. Then do the other battery slot. Same thing for the fire button and up/down.

B- and G ground is cell 1 negative. Pin 1 is cell 1 positive and cell 2 negative. Yes, Pin 2 is cell 2 positive and needs to be bridged to 2-4 plus B+ like you have. But you need to clean it up. I also worry about all that exposed wire on the red. When you're done, use your multimeter and measure Ground + Pin1 (cell 1 voltage), then Pin1 + Pin2 (cell 2 voltage).

You're seeing the 'batt' warning because you're hitting the 'low voltage' warning because the battery is sagging down to ~2.9v. Look at your Room vs. Board Temp at 150°F. A lot of heat is being generated internally trying to give you that 60watts. Isn't that the solder/wire free mod where everything is just screwed down? If it is, see if any are loose and can tighten them up. P.S Screenshot instructions in my signature line for the future.

The setting for 18650 is correct for a 21700. The difference between the settings is the Cell Soft Cutoff of which an 18650 and 21700 are the same. The items in Device Monitor with the ? mark fill out only when firing. As far as what's on your screen goes that is Theme dependent. You might save your theme and try another one. I recommend starting with Evolv's stock theme. Having all the boxes in Device Monitor checked is quite confusing. I edited your post as it needed it.

Restart your PC and escribe. Use the cable that worked. No image shown. Don't drag and drop, just choose and upload image (do not insert image). Is it the evolv USB-C board?

The bottom of the board has like a little longer section. Is there a white (JST) connector there, or are there some thin wires directly attached to the board? Just a photo or 2 of that area would be good.

Definitely not a bug, not a board problem. Wiring or connector problem. Do you have a multimeter? I have never seen the innards of a Riva, but you could check the voltage shown for cell 2, and what the board sees.

Thank you. There's all sorts going on there. You need to change your battery specs back to normal. For 'size class' that should be back at 'normal', and 'cell soft cutoff' 2.75 volts. Then 'upload settings to mod' From 'Device Monitor', look at your 'cell 2' it's showing 1.1v. That is the problem. Unplug mod, physically swap your battery positions in the mod. Plug mod back in restart esribe -> device monitor. If cell 2 still shows a low voltage it is your mod wiring or connection. If cell 1 is now low it is a dead battery.

Okay, the "Rubber Duck Debugging" worked fine... 🙃 I have checked my profiles and just changed the current profile to "Profile 1 - Replay". Now the Dovpo works as it should. No plan, why the Profile 8 did such strange things. Thanks @Wayneo for your input! 🫣 Greetings; David

Hey guys. I've been smoking for about 9 years, So now I want to quit and start vaping. What suggestions do you have?

I would not use the word 'stack', but yes you could use 2@18350. THAT would be the main problem for me.

Yes. When tmd boro was used, the ohms of the device were displayed about 0.15 higher than the coil. So I adjusted mod resistance, but now I'm back to the default setting of 0.004. This rba is also steamshell.

Your mod resistance of 0.15 ohm is way off from what would be expected, how did it get set to that? Default setting is 0.004 ohm so actual measurement shouldn't be very far from that. I can imagine something like 0.012 ohm but not 0.15 ohm

@nicoparkk Check your coil. No problem with your chipset.

No, 2 battery minimum. 6V input minimum. https://downloads.evolvapor.com/dna250color.pdf

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?

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

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 !

If you're soldering a complex surface mount chip then you might need a hot air rework station, but just to solder the wire to the tab an iron will do. I'm sure there are others here who are much more experienced at soldering than I am and can probably give better tips, but what i do is to tin the wire first then "paint" the tab with some liquid flux, apply a bit of solder paste to the tab, place the wire against the tab and paste, put a blob of solder onto the tip of the iron and then touch the molten solder to the wire/tab/paste. That generally gives me a nice clean solder that sticks to the tab first time.