All Activity

Sounds like the DNA60c isn’t detecting the RBA properly — usually a loose 510 connection or faulty coil contact causes it to read but not fire

thanks for your answer, actually after a day plugged into usb , finally an hour ago, lighted up, and got recognized in escribe. I applied an update and i will leave it charging... If it will fail I'll drop a ticket. Thank you once more

Open a ‘Help Desk’ ticket with your suggestion Click Here

Hi guys! I bought Parsons SBS and got the following problem: The battery indicator after fully charged battery is full. After couple of puffs at 17 watts, the indicator shows one bar drained. After one tank /4ml/ battery indicator shows completely drained battery, but when i decided to test how long it will go on before cut off, i managed to vape almost one full tank before it cut off the power. The strange thing is that after i put it on charger through the usb-c, after whole night of charging, in the morning the battery level was at only 2 bars and was stopped charging. Can you please give some solution or consider an update. The battery is Sony VTC6 3000mah used areound 6 months without any previous problems.

Open a ‘Help Desk’ ticket ⬇️ Link in my signature line. ⬇️ Report back with their answers

Hello, I bought a reflex about a year ago for my father, which he did not used it at all.. I got it back in its case but i see that it cannot charge at all. As i can understand the battery voltage is now below the security mark of 3.2or 3.1V. Is there a way to charge it and make it functional again? From usb does not charge at all and escribe cannot recognize it. Also how can I open it in order to boost or change the battery? (as I wrote is practically brand new and i don't want to "mark" it by opening it without knowing how) Thank you

i have the same problem with my oxva xlim 2 pro dna, after i put the device in charge (with the same charger that i used in the past and that i used for all my oxva device) the mod dont switch on. the strange stuff is that is recognize from escribe ....

You can lower or turn off 'fill pod' in escribe - safety tab. Load the latest firmware first.

Hello All! Any fix for the fill pod issue ? Tried different watts / coils / liquids, even thought the pod is full it sometimes shows the fill pod message. Cleaned connectors and no fix yet. Thank you in advance for your support !

@dwcraig1 Understood. Thank you for response.

The charger is a separate board for DNA60 and DNA60. Since the charger is not on the board there is no communication.

Unfortunately that didn't work. What also did not work: ECig['USB Current'] = 0.0 The only parameter available out of 3 (current, power & voltage) is voltage (5V in my case) - it's not possible to change that either, only read (understandable though). Dissapointing. I've specifically ordered the most modern DNA board mod in hope all of the features I read on this forum are going to be there. The mod is capable of charging through USB-C, yet you cannot control the USB current unlike older board versions. P.S. regarding not being able to connect board as CDC device ESP32-S2 - it's possible, just had to ground USB-ID GPIO pin for ESP32 talking USB host mode and turn on VBUS GPIO pin so that DNA board wakes up and enumerates itself.

If that feature works on the 60C you can try the serial command u=0 A to disable charging.

I don't see such options on DNA60C (Cthulhu Sentinel). None of mentioned menus exist in my Escribe: "Device Monitor - Diagnostics - Disable USB Charging" ❌ escribe -> mod -> battery tab - Max USB Charge Rate: 1.5 ❌ Please help me locate the menu. Serial command would be OK too. More info: I'm using a ESP32-S2 board trying to read stats from DNA60C by reading it as CDC device. Seems like current/voltage from ESP32 is not enough to make mod become available as CDC device (at least to show charging status). This is why I want to try disabling USB charging.

You can set a clock or date in escribe but the DNA60c will not showing it. Wether date or time

Thank you very much! I will give it a try! 👍

I have no clue about the OXVA quality control. What I can say is I consistently get more than double your 2,000 puffs on the 0.6 pods, and my wife gets more than double what I get on the 0.8 pods. No sweetener DIY ejuice.

Hi Wayneo, Thanks for the explanation, I get your point. However, my current cartridge is only at around 600 puffs. Is it normal for residue to build up that quickly? It feels a bit random to me. Sometimes a cartridge can last up to 2,000 puffs with stable resistance, but other times the resistance changes after just 800-ish puffs. Is the quality consistency of OXVA cartridges usually like this? Thanks again.

Read the post below and try the firmware if you want. https://forum.evolvapor.com/topic/76162-possible-bug-or-board-problem-and-firmware/

Hello, I own a DNA60c and I'm having a problem where the mod locks itself after a certain amount of time (key lock). "Auto Lock when idle" is disabled in Escribe. This only happens with firmware 1.1 SP84; it doesn't happen with firmware 1.1 SP75. With 1.1 SP84, it happens daily, practically every time I vape; the key lock is active again the next time I try to vape. For this reason, I'm using 1.1 SP75 again.

Does anyone have a source for the UP/DOWN and or FIRE buttons for Billet Boxes? Preferably in the US. I have several BB clones I would like to upgrade with DNA60C boards but, unfortunately the mods I want to upgrade have failing/faulty UP/DOWN or FIRE buttons.

In the Linux Mint distro world (and many others) under a similar software release philosophy, they call it a BETA release. Been that way for well, always. Available to anyone who would like to have it for testing and evaluation before posting a finalized update release to their servers. Beta / Early ... same difference I guess. I'm just becoming familiar with "your" terminology and semantics. Thanks

oxva dna البود المستخدم هو مضاد للحرق المخصص ل oxva xlim pro 2 . البود السابق كان يعمل بأمتياز.اما هذا البود و هو من ذات العلبه لم يعمل ك بود مضاد للحرق.ولقد حدثت برنامج الجهاز الى 130.1

Early firmware gets released there first. If there's no mass yelling and screaming, escribe (out in the field) will then notify users when it's next started by each user of an available update. Even the 10+ year old DNA60 got an update a year or two ago. It's been that way for over 10 years.