retird

This pdf may help..... there are a lot of safety features built into the board.... if the battery can't provide the power required for the example you give then the device will still fire but at a reduced wattage... https://downloads.evolvapor.com/dna75.pdf

Could be many things... bad battery, bad wiring, loose connections, shorted wiring, e-liquid inside the device, etc. Contact the vendor or the device maker.... Any warranty? If they don't help then file a ticket with Evolv and they will guide you and may have you send in just the DNA board so they can check it... Evolv warranty covers the board only for 1 year.

Notice the post referenced has a csv file for download....

There are a few mods I think that use connectors for the power leads and the battery balancing connector but I wonder about repeatedly changing batteries twice a day.... may be hard on the connectors and balancing connector on the board... I wouldn't recommend it but hey it's your choice... you will just have to google different devices and see which ones use connectors or others here may be able to help you....

Somebody post this recently... see Post #2... /topic/65641-topic/?do=findComment&comment=887339

Glad you found the loose connection..... also refreshing that you didn't immediately say the dna board must be the issue or there's a bug in the firmware/software... you did good....

Even with a broken screen it should vape....does it? Does it show normal readings while vaping with it connected to Device Monitor?

What wattage do you normally vape at?

What material (wire) are you using and what are the cold ohms of the atty's. I assume you are using spaced coils. Are you using a default profile or one from steam engine. Sometimes this issue is caused by poor connections of the 510 (mainly ground), poor connection between atty and 510 (or dirty connections), poor connections within the atty itself (such as where the center pin of the deck contacts the atty center pin) etc.? What does the Device Monitor screen show while firing the device?

I still don't understand why you don't contact VapeDroid... they can help you and may even fix it for you... You are spending a lot of time here and getting nowhere imo...

Evolv has those files.... fill out a ticket and they should help you... https://helpdesk.evolvapor.com/index.php?a=add&category=3

Also, unless I missed it you never mentioned if you were also getting a "weak battery" message..... From the Datasheet it says: Weak Battery: The battery needs to be charged, or a higher rate battery needs to be used. If this happens, the DNA 250 will continue to fire the atomizer, but will not be able to provide the desired wattage. The Weak Battery message will continue to flash for a few seconds after the end of puff.

I'm thinking the huge battery sag you are seeing won't let you achieve the 120 watts you want all the time...if the battery can't supply the 120 watts desired as the battery charge is reduced then yes you will achieve lower wattage only. Is that what you are getting at?

It may be beneficial to contact Vapedroid and explain what is going on with your device.... They may be able to guide you and/or address your issue.. Contact information given within this link...... https://www.vapedroid.com/product-page/531c96ba-5c27-51cc-a403-c2d736afd935

May be worth watching... https://www.youtube.com/watch?v=Nf5MhzKEhlc

You might check the Max Kanthal Power Limit... could be set lower than 120 watts...

Can you post a screenshot of Device Monitor showing the wattage, power set, power while firing the device.... check those boxes in the list on the left side of Device Monitor

or the wires are not wired to the proper terminals..

If you have a continuity tester (ohm meter) you could check the buttons with that... test board connection at 3 and 4 while pushing the button and see if you have continuity.... same with connection 5 and 6. Take out batteries first.

3 and 4 are for the down button 5 and 6 are for the up button You should check the wiring for all pins 3 thru 6 to make sure they go to the right buttons

Contact the vendor you got it from..... defective wiring or etc....

In EScribe under the Mod Tab and the Mechanical Setting what does it say, Normal or Swapped? Under the Screen Tab look at Display Settings and does it say Right or Left. Right and Normal - up and down buttons operate and are oriented to the way the screen faces Left and Swapped - up and down buttons operate and are oriented to the way the screen now faces Mixing any combination orients the screen one way and the buttons in the opposite orientation (up would be down opposing the way the screen faces). Maybe this may help if not set accordingly...

I run my 75's and 200's mostly under 40 watts and around 420F with about 60 watts preheat with SS316L material notch coils and notice no difference between the 75's and the 200's except battery life between charges which is understandable because 1 battery versus 3 in series... Neither the 75 nor the 200 are crap in my books. I run my coils at the same wattage and temp on both the 75 and the 200's. Have you ran case analyzer on your devices? May help if the settings were never put in correctly by the device maker.

I also use SS316L without issue. My thinking it is a build issue, connective issue, problem atty, wiring issue, etc. If it was a board issue I would think I would see it on one or all of my 5 DNA devices and would have seen it during all the beta testing also. SS316L tweaking in the firmware over the years greatly improved it's performance since it was first added as an available wire that can be used with DNA stuff. The majority (over 98%) of issues with dna devices are not board related. I also never lock my resistance. Refinement is there for a reason. EDIT: I also use the default wire csv for SS316L that comes with the DNA. I don't use a csv. from Steam Engine, nor tweak the default csv. @StressTest, can you post screenshots of your Thermal settings, profile settings, and a screenshot from Device Monitor while firing the device?

Not a problem with any of my "herd" of DNA's either....if this issue had been around for 2 years we would have seen numerous folks talk about it....and Evolv would have nailed it down before now...they take "bugs" seriously....