Leaderboard
Popular Content
Showing content with the highest reputation since 02/18/2025 in Posts
-
5 points
-
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.4 points
-
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.3 points
-
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. James3 points
-
Oh how I was wrong LoL. The Evolv DNA 60C is awesome and Evolv, with a keen eye on safety, performance and reliability, has allowed for ALL vaping persuasions. Sometimes devices don't arrive perfectly configured from a manufacturer or vendor, but that isn't Evolv's fault. The possibilities are there for the choosing in EScribe. With invaluable help here, I've gone through the bonding phase and have my device dialed in perfectly. I apologize for my earlier naive, newbie observation. D'OH2 points
-
Under the escribe 'safety' tab are options to lower or even turn off 'fill pod' warnings. There are ranges of resistance for what the coil Ω's displays as. Yours is now in the 1.2Ω range by 2 hundredths of an ohm. Your 'wrong ohms' issue is harder to explain but could be due to your coil raising its resistance due to getting crusty/carmelized from use and/or dirty contacts. Those factors or others, have raised the resistance to be in the 1.2Ω coil range My simple explanation - https://forum.evolvapor.com/topic/76108-oxva-xlim-pro-2-dna-resistance-issues/#findComment-945868 More detailed explanation (same post) - https://forum.evolvapor.com/topic/76108-oxva-xlim-pro-2-dna-resistance-issues/#findComment-9459332 points
-
There are a couple things that I would try if it were mine. 1st I'd copy the .ecig file using EScribe. Using Escribe do a hard reboot. Still not good restore to factory defaults. Use Evolv's default theme. EScribe creates a backup so either with that or your saved ecig file you can always return it ti as before your changes were made.2 points
-
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.2 points
-
2 points
-
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.12 points
-
@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.2 points
-
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.ecigcolors2 points
-
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.2 points
-
2 points
-
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 outcome2 points
-
It looks to be wired correctly to an Evolv C board. Avoid using a USB hub.2 points
-
It's a 3 cell battery. That's 3@1200mAh, so 3,600mAh total or about a single 21700 battery. Your vaping habits will dictate length of usage. LiPo's will have lower voltage sag overall compared to a round cell (all things being equal). You are limited by the cavity size for what will fit inside. If you're lucky you might find a bigger cell but it would probably only be an extra 100-200 more mAh. Hobbyking has a LiPo sizer. I'd look at the dimensions of that Turnigy and use the sizer for other 3S batteries, or Amazon or an RC store. Edit: Your picture of yours looks like an OG 'Fullymax' battery, used by many vendors, including the Steamcrave Hadron Pros, but hard to find at retail. I have 6 LiPo mods and can say they like to be used, as they can easily get out of balance a little. Like your cell 1 which in all screenshots is 0.03V lower. That might add 10 minutes extra charge time.1 point
-
Did not matter at all. It's just the sum of the 3 cell voltages. If you look, they're all pretty much the same and your mod is charging ~1A. All looks good. At lower voltages that charging would be closer to 2A, and will now continue to decrease from 1A the closer it gets to full. Full could be 4.1V or 4.2V, depending on how the mod was setup. After it's fully charged, while plugged in, you could also enable 'Power' and 'Power set', take a puff, pause the screen and that will show how each individual cell is operating. You could post that screenshot if you want us to look at it.1 point
-
1 point
-
You're welcome. I'm gonna change the subject title to better reflect the issue. Hope you don't mind.1 point
-
Were both batteries charged externally? And what make and model are they? Look at each battery's voltage right now. Unplug your mod, and swap the battery positions in your mod. If cell 1 (old cell 2) still shows lower than cell 1, then we know something is wrong with that area. Either way you might want to clean all their contacts with Isopropyl alcohol (IPO), or even better, semi dismantle the mod and look for ejuice and wipe down the area around the bottom of the board (both sides), those 2 fatter connections and those 5 small ones. There might be white connector which you can pull apart off the board. Wipe down everything. Looking at your screenshot, ideally/regularly they should be parallel. When you take a puff they should both dip/sag equally. No, it's not dangerous, but it should be fixed. Because that % is based on the lowest cell, your mod will give you a weak or check battery much sooner than it should, and stop working.1 point
-
Thanks, great. Your cell 1 is only at 3.5V. That % is based on the lowest cell. Charge both fully, hopefully externally and try it then.1 point
-
In normal usage the ambient temp is pretty flat, but it will change. It really only matters if you are a TC vaper. When you put cells back in, it also re-reads the resistance of your coil.1 point
-
The wick had time to re-saturate perhaps. I'm going to send you a message.1 point
-
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.1 point
-
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 Si1 point
-
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.1 point
-
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.1 point
-
Edit : So I've now mounted the board and type c board in place, I am running 2x18350 Batteries in parallel, plugged it into escribe and it will not recognise the board saying please connect a device 🤔 All I have left to connect is the 510 - and + with the batteries inserted i put a meter on the positive and negative and without pressing the fire button it's showing 3.2v when I press the fire button there is no change in the voltage. I have spent hours building the mod and searching the forum for an answer but to no avail, would anybody have any ideas or suggestions please I'm about to call it a day as it's eating into my long weekend off work. Have attached some pics...... Cheers Simon1 point
-
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).1 point
-
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.1 point
-
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.1 point
-
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?1 point
-
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.1 point
-
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.1 point
-
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.1 point
-
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; David1 point
-
Hey guys. I've been smoking for about 9 years, So now I want to quit and start vaping. What suggestions do you have?1 point
-
I would not use the word 'stack', but yes you could use 2@18350. THAT would be the main problem for me.1 point
-
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.1 point
-
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 ohm1 point
-
1 point
-
No, 2 battery minimum. 6V input minimum. https://downloads.evolvapor.com/dna250color.pdf1 point
-
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.1 point
-
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.1 point
-
1 point
-
Download new theme Start escribe with mod plugged in. Go to theme -> Load theme (Select theme you just downloaded) choose 'Open' (on a Mac) Then 'Upload Settings to Device' <- Most important thing 😉 A theme also includes the following screen behavior fields Active time, Idle Time, Fade-In, and Fade-out time. <- If you don't like any of the 4, change it yourself. Under the Language Tab are short forms for messages. If you don't like them, change them BUT if you want to report an issue you need to use the long form, or the default Evolv short-forms. After you've done it a few times, there is a quicker way by just starting escribe, then 'Theme Designer' immediately.1 point
-
1 point
-
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.1 point
This leaderboard is set to Detroit/GMT-05:00