All Activity

Okay, so I'm thinking maybe there's a "never mind" due LOL I couldn't wrap my head around how a software setting could affect something that seemed hardware related, so I took the Sentinel back apart. On the back of the fire button was a sticker. A not well centered sticker on the back (inside) of the fire button and similar in diameter as the button. I took that sticker off and the Sentinel is more clicky now. I think that sticker may have been ever so slightly interfering with the fire micro switch and circular rubber mount around it. And in doing so, the mod was glitchy. Sometimes not firing and sometimes when I tried to fire, I would find the DNA 60C locked. The button seems to work better now and my mind is trying to reason why that sticker was on the back of the fire button to begin with. If I shake the mod deliberately, I can hear a faint rattle. At first I thought maybe the sticker had some needed insulation value since the button is metal. But now I think the sticker was a silencer. With the sticker in place, perhaps no rattle when deliberately shaking the mod. Since shaking the mod is not something I routinely do, it's a non factor, and without the sticker the mod functions well. On the other hand if anyone has any anecdotal information they've found with the fade-in and fade-out settings, do chime in. Thank you.

REF: DNA 60C on a Cthulhu Sentinel mod ~ only used in Watts mode. 1.8Ω at 7W First thing I did when I got the mod was download EScribe and start leaning as I went along, how to modify settings to the style I wanted. No matter if I came up with a custom theme or the default theme that came with the Sentinel, I always changed the active time from the default 30sec to 7sec. On the same page, I tried to change the fade-in and fade-out time to 0sec but EScribe always defaulted to a minimum value other than zero for each and I would save upload those values. Over the course of using the Sentinel, I experienced random glitches. A press of the fire button might not actually fire the mod and sometimes I'd press the fire button only to find the device locked. The random glitches became annoying. I tried over and over, rotating between service packs, my custom theme and the theme that came with the Sentinel. Each time I tried those things, I always set the active time to 7sec and fade-in and fade-out to as low as EScribe would allow. The random glitches continued and I became annoyed to the point of taking the Sentinel down to parade rest to see if I could spot an obvious problem with the device itself and found nothing wrong. I reassembled the Sentinel and still experienced random glitches to the point of almost ready to toss the mod. For grins and giggles I decided to leave the fade-in value that came with the Sentinel at 1sec. And I changed the fade-out from 2.98sec to 2sec. That was a couple of days ago and since making that one change to my pattern of settings modifications, I have not experienced any random glitches at all ... knock on wood. So you tell me, the Sentinel fixed itself? ... taking it apart and putting it back together eventually changed something? OR ... the screen fade-in and fade-out value had something to do with it? I can't wrap my head around how those fade-in and fade-out values could impact mod firing and readiness, but there it is. Those values are the only thing I tired in EScribe when all else failed to correct random glitches. I'm using the latest service pack, active time is 7sec, Fade-in is 1sec and Fade-out is 2sec. Works every time all the time now. I guess I could test it and try zeroing out the Fade-in and Fade-out to near zero as I always had previously to see if the glitches return but decline to do so.

thanks a lot for your help , I wrote them an email, but I haven't received any answer yet.

Thank you vers much, Sir.

5V should be fine. If it had put 9V or 12V onto USB (these do exist in the wild, even though they shouldn't), both the screen and FET driver would both be damaged by this. I can't speak for that particular charger, but contact Oxva for a repair/replacement.

5V 2A . is an original charger from another pod mod (KIWI) and i use for all the pod mod i have (including 2 more xlim 2 no DNA ) and in few years i never had any problems with the other device .

The charger you used, what does it say on the label for voltage and current?

If you click the icon to the left of "Puff" to bring up the button simulator, and click Fire, does the screen turn on? That'd tell us if there's an issue with the physical buttons. aswer: not Also, before you start Device Monitor (make sure it is closed), go to Help->About in EScribe and left click the logo seven times. This will close the window and put the program into Debug mode. Then, start Device Monitor. answer: Done If you do this, click the "Debug" group on the left to bring it up. What does "Buttons" say? answer: 0 buttons As to 4.16 Ohms, PWM devices like Oxva can't read over 4 Ohm. 4.16 Ohm is probably the 4 Ohms limit with calibration applied. This almost certainly means it's not reading the pod resistance, or the connection has become very bad, but clearly it's detecting that there _is_ a connection, or it wouldn't have tried to measure it at all.

If you click the icon to the left of "Puff" to bring up the button simulator, and click Fire, does the screen turn on? That'd tell us if there's an issue with the physical buttons. Also, before you start Device Monitor (make sure it is closed), go to Help->About in EScribe and left click the logo seven times. This will close the window and put the program into Debug mode. Then, start Device Monitor. If you do this, click the "Debug" group on the left to bring it up. What does "Buttons" say? As to 4.16 Ohms, PWM devices like Oxva can't read over 4 Ohm. 4.16 Ohm is probably the 4 Ohms limit with calibration applied. This almost certainly means it's not reading the pod resistance, or the connection has become very bad, but clearly it's detecting that there _is_ a connection, or it wouldn't have tried to measure it at all.

Hello, thanks for your answer , in attachment the screenshot of Device Monitor .4,16 ohm of resistance looks really stange and not i cant fire with puff function in escribe: when i try appear one message "check atomizer"

That's correct. It's so themes don't have to have separate handling for temperature sensing and non-temperature sensing modes.

If you want to experiment with coil materials with very little resistance change with temperature, you can go to Mod->Safety->Replay and choose "Allow on unlikely coils". It actually goes into a special Replay mode in this case if the other modes would not have allowed Replay on the coil. This is more for fun than everyday use, but if you want to, feel free

If it works from EScribe, try opening Device Monitor. What does it say for its battery voltage? Are you able to fire with the Puff function from inside Device Monitor? (If so, the issue may be the screen.)

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.