Reuleaux DNA200 wattage mode ramp up???

[CloudChaser89]

Hi guys im a newb here to dna devices . Im having trouble understanding my dna device .so far i have the basics down such as button functions .but one thing thats driving me insane is im running a rda on my dna mod. and im in normal wattage mode with temp control turned completly off .i have my wattage set at 75w but when i fire it to take a vape it ramps up like in temp mode?? It does it quickly which is hardly noticeble .but annoying because it displays 0w than 55.2 sometimes 55.3w than 75w. the hit is super smooth and perfect but im just wondering if this is normal?? In wattage mode ? Now i did get this device used.so i dont know if any escribe software has been changed. and i dont have a computer to confirm this or is this just normal function for this mod/chip? Ive called a few local vape shops with no avail.except one person who says some are set up that way from factory/versions there using.so please any info would be a excellent for this dna noob thanks in advanced .

[dwcraig1]

I'm going to just have to guess at this one, I'd say the display just isn't keeping up with what the board is doing. EScribe will sort that for you when you get to it. Like I said , just guessing here.

[CloudChaser89]

dwcraig1 said:

I'm going to just have to guess at this one, I'd say the display just isn't keeping up with what the board is doing. EScribe will sort that for you when you get to it. Like I said , just guessing here.

its a better guess than what i was thinking thanks alot bud. Any other suggestions guys?

[VapingBad]

The displayed values are a rolling average by design, IIRC the average for the last 250 milliseconds, because some values would change so fast the display would be hard to read and it would also use some processor time to redraw the screen each time, so you don't want to do it more than necessary.

[CloudChaser89]

VapingBad said:

The displayed values are a rolling average by design, IIRC the average for the last 250 milliseconds, because some values would change so fast the display would be hard to read and it would also use some processor time to redraw the screen each time, so you don't want to do it more than necessary.

awesome man but honestly im a noob lol i really didnt understand what u were saying about using it more than necessary could u explain umm in noob lol sorry

[CloudChaser89]

CloudChaser89 said:

awesome man but honestly im a noob lol i really didnt understand what u were saying about using it more than necessary could u explain umm in noob lol sorry

and vaping bad what ur saying by the wattage changing on my screen is normal?just let me know im going mad over this lol

[VapingBad]

Yeah I try, I mean the programming of the chip updating the screen more than necessary.  The chip or central processor can do a fixed number of operation every second, redrawing the screen needs to processor to convert text to pixel on and off values which takes a lot more time than doing math or reading sensors.  At some point that will get in the way of the other functions, although I'm sure they are nowhere near that, it is just good practice.  I think the display rate is far more to do with what is comfortable for a human to read than performance or resource usage.

[CloudChaser89]

VapingBad said:

Yeah I try, I mean the programming of the chip updating the screen more than necessary.  The chip or central processor can do a fixed number of operation every second, redrawing the screen needs to processor to convert text to pixel on and off values which takes a lot more time than doing math or reading sensors.  At some point that will get in the way of the other functions, although I'm sure they are nowhere near that, it is just good practice.  I think the display rate is far more to do with what is comfortable for a human to read than performance or resource usage.

ok thanks a ton man . So u dont think theres a issue with the device? Or me using it? Its my only dna mod as of now and once i get on escribe do u think that will fix the issue thanks again

[VapingBad]

It is just they way it works, for really looking at your vape in real time device manager will give far more information than you will ever get on a mod screen.  So you have all the tools to check out a new build, new atty or and issue at the PC and once you have that sorted you don't really need it day to day IMO, but have a smaller set of info available through the device screen

[CloudChaser89]

VapingBad said:

It is just they way it works, for really looking at your vape in real time device manager will give far more information than you will ever get on a mod screen.  So you have all the tools to check out a new build, new atty or and issue at the PC and once you have that sorted you don't really need it day to day IMO, but have a smaller set of info available through the device screen

Ok got yah. Thanks alot for all the info i really do appreciate it its been the most and best help ive had so far thanks again

[CloudChaser89]

Ok guys wanted to update everyone who was following. i went to my inlaws house today and installed escribe i set the mod back to default settings. and even did a hard reset screen still ramps up i even did a update to the mod that was avalible but still does. it mod works perfect its just doing things a little different i guess lol.any help again here guys on other thoughts of why it could be doing this? Thanks in advance

[VapingBad]

As I understand it you are getting a smooth vape and your issue is the wattage reported on the device screen is other than you expected.   If you could post a device manager screen shot or recording of it doing this with pack, voltage, current, power and live ohms selected we may be able to explain it better.  Also what sort of coils are you running?

[CloudChaser89]

VapingBad said:

As I understand it you are getting a smooth vape and your issue is the wattage reported on the device screen is other than you expected.   If you could post a device manager screen shot or recording of it doing this with pack, voltage, current, power and live ohms selected we may be able to explain it better.  Also what sort of coils are you running?

like i said mod is working flawless just ramping up to 75w i can use dual kanthal claptons to a premade coil its doing this with every single rda/tank/rta /build lol now as for screen shots on device manager i cant do im not at the inlaws any more but i can post some when im up there way again i could try and take a video of numbers ramping up but i dont know if i can post it also i wanted to add that my set wattage is 75 watts when i first hit the fire button it shows on the screen 0 watts than 53 watts than 75 watts but it feels like a constant 75 watts the whole time i inhale like i have it set so what could that issue be? If i set it to 100 watts or any wattage for that matter it does the same thing but feels like the wattage i have it set too any info guys thanks again lol

[gratefulbuddy]

VapingBad gave the best (and most direct) answer already:

VapingBad said:

The displayed values are a rolling average by design, IIRC the average for the last 250 milliseconds, because some values would change so fast the display would be hard to read

So for a split second you are seeing the display show you the average of "0" (because the device was not firing) and the power that is just starting to be applied.
No amount of updating/downgrading of the fw or hard/soft reboots will change the display behavior you are seeing. 
It is normal and nothing to worry about or try to "fix"

[CloudChaser89]

gratefulbuddy said:

VapingBad gave the best (and most direct) answer already:


So for a split second you are seeing the display show you the average of "0" (because the device was not firing) and the power that is just starting to be applied.
No amount of updating/downgrading of the fw or hard/soft reboots will change the display behavior you are seeing. 
It is normal and nothing to worry about or try to "fix"

thanks alot that honestly was the only answer i was trying to get . If it was normal or not and if not if it could be fixed so i guess than im good since there is no issue lol thanks again to all who helped now my mind is at peace lol now time to learn more about dna devices

[SteveF]

Thanks Cloudchaser....this was the post I was about to make, all three of my DNA200s are doing this now in wattage and seem to be taking their time ramping up too. I'm using a single 0.34 ohm parallel clapton at 70w and the display is holding for a moment at 44.5w, sure its its smooth but not what I have become used to with 11-12v and 50 A in reserve. its definitely a two stage event.
I used a steam engine profile for Nichrome and Kanthal to see if they were any different to the new 'watts' material setting. No change.

And call me a 1/1000 difficult customer because I have noticed it since the latest SP3 update.  I still keep losing the battery meter when I update profile settings on Escribe and the I still can't measure the internal resistance because it just registers ???? 

Has the DNA board somehow been newtered by refining TC modes?

is there any way of actually removing ALL of the SP firmware? I've tried stepping it back and I'm left with the new SS, Ti and Watts profiles and I'm still experiencing the niggly bugs that came with it.

[CloudChaser89]

SteveF said:

Thanks Cloudchaser....this was the post I was about to make, all three of my DNA200s are doing this now in wattage and seem to be taking their time ramping up too. I'm using a single 0.34 ohm parallel clapton at 70w and the display is holding for a moment at 44.5w, sure its its smooth but not what I have become used to with 11-12v and 50 A in reserve. its definitely a two stage event.
I used a steam engine profile for Nichrome and Kanthal to see if they were any different to the new 'watts' material setting. No change.

And call me a 1/1000 difficult customer because I have noticed it since the latest SP3 update.  I still keep losing the battery meter when I update profile settings on Escribe and the I still can't measure the internal resistance because it just registers ???? 

Has the DNA board somehow been newtered by refining TC modes?

is there any way of actually removing ALL of the SP firmware? I've tried stepping it back and I'm left with the new SS, Ti and Watts profiles and I'm still experiencing the niggly bugs that came with it.

wow you sir could not have said it better i thought i was losing my mind here lol. They said that it was normal .imo its not but im a noob so who knows lol me myself i can see this happening in temp mode but cmon wattage mode with a normal kanthal coil thats bizzare to me lol btw i did a device monitor on escribe and had my mod set to 75w hit the fire button and every time it was consistent 75 w lowest was 74.9 w so its showing its not ramping up at all like the screen is showing the firmware mine is updated to has watts nickel stainless steel and titanium so if firmware is the issue maybe it has reached a few other firmware updates as well regardless of issue or not when you spend ur hard earned cash on a dna device imo the bugs and quirks should be non exsistent

[VapingBad]

Remember the display on the mod is a rolling average of IIRC 250 ms, you can see what the power delivery is in detail in device monitor, don't read more into the device screen than it actually shows.

The larger the coil or coils are the longer it takes for the heating energy (watts) to bring them up to temperature and start to vaporise your liquid.   The Reuleaux dies not have the thickest wiring or the best 510 either.

The board has not been neutered by refining TC modes, for one thing there are not any TC modes, it is a single mode device using the same hard and firmware for power regulation for both temp limited and non temp limited operation.  The temp limiting is like another layer of control put on top of that which is just skipped when temp limiting is disabled.  There have been adjustments that affect atty analyser causing some of us with 200s, me included to get a ? when the mod resistance is very low since V1.2.  You can step back firmware to any previous version if you want to compare performance between them.

Some other mods are differently.  Pulse width modulated Mods will seem harsher and hotter.  Some give an arbitrary power boast at the front of the puff (I had an IPV that did this), while that does heat a cold coil faster, it overcooks a warm one more often and is a flavour spoiler IMO.  Many don't even do real power control, but only set the voltage at the beginning of the puff according to the selected watts and the current resistance (I had an SX Mini M Class that did this) so you can get SS coils running at lower power after they heat and increase res, so DNAs will give you fixed wattage with SS and temp  limiting disables while many mods will give you decreasing power.  You will also get reduced power if loops short between each other.  Many will deliver more power down low to inaccuracy and less at high watts due to poor wiring, measuring power at the board and hiding the drop due to weak battery.  The only one of these that DNAs do is sometimes hide that weak batteries are causing a weaker vape, more so since the changed the battery earnings in response to customer demand. 

[SteveF]

VapingBad said:

Remember the display on the mod is a rolling average of IIRC 250 ms, you can see what the power delivery is in detail in device monitor, don't read more into the device screen than it actually shows.

The larger the coil or coils are the longer it takes for the heating energy (watts) to bring them up to temperature and start to vaporise your liquid.   The Reuleaux dies not have the thickest wiring or the best 510 either.

The board has not been neutered by refining TC modes, for one thing there are not any TC modes, it is a single mode device using the same hard and firmware for power regulation for both temp limited and non temp limited operation.  The temp limiting is like another layer of control put on top of that which is just skipped when temp limiting is disabled.  There have been adjustments that affect atty analyser causing some of us with 200s, me included to get a ? when the mod resistance is very low since V1.2.  You can step back firmware to any previous version if you want to compare performance between them.

Some other mods are differently.  Pulse width modulated Mods will seem harsher and hotter.  Some give an arbitrary power boast at the front of the puff (I had an IPV that did this), while that does heat a cold coil faster, it overcooks a warm one more often and is a flavour spoiler IMO.  Many don't even do real power control, but only set the voltage at the beginning of the puff according to the selected watts and the current resistance (I had an SX Mini M Class that did this) so you can get SS coils running at lower power after they heat and increase res, so DNAs will give you fixed wattage with SS and temp  limiting disables while many mods will give you decreasing power.  You will also get reduced power if loops short between each other.  Many will deliver more power down low to inaccuracy and less at high watts due to poor wiring, measuring power at the board and hiding the drop due to weak battery.  The only one of these that DNAs do is sometimes hide that weak batteries are causing a weaker vape, more so since the changed the battery earnings in response to customer demand. 

could be one mod, the lipo is nearly 12 months old now, perhaps the VCT5s in the Rolo are getting tired but I don't thrash them and tbh they really don't even get constant use as it only gets used odd evenings, fairly new lipo in #3.

Coil appears OK, wouldn't be surprised by an imbalance with a dual coil set up but not so much a single parallel. No apparent shorts between wraps on dry burn, plenty of solid clamping on the Aeronaut and the contacts are clean.
I'll run escribe again and check for any cell drops or resistance changes.
Still not utterly convinced that the SP3 update hasn't made lasting changes to the non-user progammable side of things.

[CloudChaser89]

SteveF said:

could be one mod, the lipo is nearly 12 months old now, perhaps the VCT5s in the Rolo are getting tired but I don't thrash them and tbh they really don't even get constant use as it only gets used odd evenings, fairly new lipo in #3.

Coil appears OK, wouldn't be surprised by an imbalance with a dual coil set up but not so much a single parallel. No apparent shorts between wraps on dry burn, plenty of solid clamping on the Aeronaut and the contacts are clean.
I'll run escribe again and check for any cell drops or resistance changes.
Still not utterly convinced that the SP3 update hasn't made lasting changes to the non-user progammable side of things.

im still thinking it has to do with the firmware updates imo

[VapingBad]

If you guys think it is the fw why don't you load an earlier version and compare?

[CloudChaser89]

VapingBad said:

If you guys think it is the fw why don't you load an earlier version and compare?

i cant currentlly no computer

[gratefulbuddy]

I can verify this behavior has occurred on every fw revision I have used since 08/2015. As I said before this is not a defect/shortcoming/bug or problem. Several people here have given in-depth technical explanations of the display behavior that is described in this thread.
@Cloudchaser89 - I thought you already verified that your device is outputting the full requested voltage from the instant you are pressing the fire button by using escribe?

[CloudChaser89]

gratefulbuddy said:

I can verify this behavior has occurred on every fw revision I have used since 08/2015. As I said before this is not a defect/shortcoming/bug or problem. Several people here have given in-depth technical explanations of the display behavior that is described in this thread.
@Cloudchaser89 - I thought you already verified that your device is outputting the full requested voltage from the instant you are pressing the fire button by using escribe?

from what its showing on escribe yes it supposidlly is .my main thing here is i dont want to see the screen ramp up for no reason everytime i take a vape .how do i fix that or have it say from the second i hit the fire button 75 watts imo its quite annoying for false readings on my screen and if theres no way to fix this issue please explain in a simple to understand way why it does this on my screen thanks

[gratefulbuddy]

Did some digging and found the answer from Evolv :
[QUOTE=James]The actual ramp up is in the milliseconds. What you are seeing is that the screen is updated four times per second with the average values from the past quarter second. So if you start firing half-way through that quarter second, the average will be between 0 (not firing) and your wattage, and that screen update will be at a midpoint. Take a look at Power in the Device Monitor to see what I mean. [/QUOTE]

EDIT : Notice the date of his post is 10/29/2015 - quite a while before any of the fw updates you are referring to.