The following was provided by Moderators on Evolv Forum


Common Troubleshooting Steps

Screen is blank, but device functions:

  • Verify that it is not in stealth mode:  Lock the device and hold power and down until “Normal Mode” is displayed.
  • Verify that screen is not pinched by the fire button, if so, return to manufacture for service.
  • In Escribe - Help -About EScribe  click the logo 7 times then open Device Monitor and look at the screen disconnects.  If that is > 0 it is a screen connection issue, could be the cable has come out of the socket or the cable is damaged. 

Device powers on only when connected to USB power:

  • Fuse is blown:  Visually inspect fuse or test with ohmmeter.  Return for repair if blown.
  • Battery is dead or low or a single cell is dead or low:  View cell charge levels in Escribe to verify that the device sees a three cell pack and that each cell is charged above 2.00 volts

Battery Meter is inaccurate/Battery % Jumps Down:

  • Watt-Hour setting in Escribe is incorrect.  Calculate Watt Hours using battery analyzer and enough coil wire to form several large loops to dissipate the heat.  The pack you are using likely has less watt-hours than estimated.
Weak Battery displayed when battery has sufficient charge:
  • Launch Device Monitor and view each cell’s charge level for sagging during vape. 
  • Verify watt-hour setting for your Lithium Polymer pack is set correctly.

Battery won’t charge to 100%:

  • Using the watt hour calculator to guess at a figure will at times result in a number that is actually in excess of the real life figure for the pack.  Run battery analyzer to get a correct figure or simply reduce the rating.

 Warranty Service Error Message:

  • Warranty error means that the logic voltage regulator is running out of spec. That could be due to a soft short circuit somewhere in the logic circuitry, a total battery voltage under 4v, or similar.   Verify cell voltages and replace battery if needed or send mod in for service if the battery is to spec.

 EEPROM Programing/Read Failed:

  • Escribe attempted to write/read to/from the device but failed.  Typically related to a poor USB cable or a computer with considerable lag, causing slow USB response.  Use a known good cable, eliminate running processes and manually try a firmware update via Tools and “Update Firmware”.

 Device won’t connect to Escribe:

  • Inferior USB cable – half of the diagnosed connection issues can be traced back to a poor quality cable or one lacking the wires for data (a cable sold for cellular device charging).

Device Autofires:

  • Generally caused by a short from the “OUT” connection to the atomizer and board ground (due to poor soldering or erosion of board coating).

Ohms showing 0.00 with new atomizer:

  • Ohms will display 0.00 until the fire button is depressed with a new atomizer.

Resistance is variable and results in poor vape:

  • The ground path is crucial.  Some mods (like the Hana) did not install a ground path and relied on the 510 connection to the case which could be unreliable.  Install a dedicated ground connection to the board.
  • Many atomizers are poorly suited to vaping in TC mode.  They have springs or loosely threaded center pins that can cause big swings in resistance.  You can fix some of this by unscrewing the pin, cleaning it and then re-installing and potentially leaving more exposed so there is more pressure on the 510.  You can also increase the pressure of the 510 spring.

 Temperature Control Not Working:

  • See the variable resistance issue.

 Once Cell of the Three Cell Pack fails to Charge:

  • There is a rare board assembly error where one of the four resistors near the USB plug will be omitted or poorly attached.  This can be seen with a visual inspection.  If one of them is missing or not installed correctly, RMA the board.  
  • If the board is functioning and the onboard resistors look intact, then one cell of the pack may be bad.

 The mod will not charge and cell voltages read low:

  • The device will not charge cells below 2 volts.  To try and recover an over drained pack, in Escribe select Device Monitor, Diagnostics, Advanced and “Perform USB Recovery Charging”.  You may need to do this multiple times.
The custom fields I chose to display while charging do not display:
  • Check the screen brightness is greater than 0% for charging in Escribe, they only display when in idle about 30 seconds after connecting the cable.
USB port gets hot while charging:
  • Check for blown fuse by looking at battery voltage in Escribe or general mod operation.
Device will not fully charge:
  • Verify you have the right battery type selected.  If using a Lipo pack, but lipo4 is selected it will only charge partially.
USB Recovery Charge Fails:
  • USB recovery charge only works for cells that are above 1 volt
  • USB recovery charge will not work if the mod internal temperature is over 130F
  • USB recovery charge may need to be run multiple times
  • The pack may not be recoverable
What initial setup items are essential?:
  • The main things it to do: connect to Escribe update the firmware, check the battery Wh are correct, increase the max Kanthal watts if required, choose between "max puffs" and "max recharges" battery options, set the charge screen brightness above 0% and put USB current in one of the custom fields so you can see if you have used a 1 A USB supply to charge.
Why is my VT200 battery meter dropping so fast?:
  • Some of the packs shipped with this mod have less than the advertised 14.43 watt hours.  One users tested theirs to be 10.7 watt hours.  Putting 11 in the pack rating will result in a more accurate batter meter.  It is also suggested you test your pack with the battery analyzer tool.
I can't get over 100w:
  • There is a non-TC limit of 100w as the default in Escribe.  You can set it higher if needed.
I am having issues with Stainless Steel:
  • Stainless steel is an alloy and has issues being used as a TC control wire.  At a minimum start with a good TC atomizer and a known mod resistance.  Read this great write up by James (Evolve):
Escribe won't update:
Device will not stay in temperature mode:
  • Jumping out of TC mode is typically related to the use of low TCR wire with an inaccurately entered mod resistance value.  If you have a low resistance build, say .08, and a very low TCR wire like stainless and have a mod resistance of .008, but it is not entered, the combined resistance of your wire and your mod, .088, coupled with the low TCR value will cause the DNA200 chip to fail to see enough of a percentage change in the wire to justify TC mode.  If you are using low TCR wires then you must put in a VERY accurate mod resistance and TRY to build higher resistance coils.

Higher coil resistances limit the max power with two cells or Max resistance is lower for two battery cell operation
  • The DNA 200 is a step down converter designed to run from 3 Li cells is series and is limited to a max output voltage of 9 V.  Evolv released firmware that allowed it to operate from 2 series cells at reduced power (133 W).  The max output voltage has also changed to 6 V (2 cells in series).  This changes the resistance range usable to between 0.0532 ohm and 0.27 ohm for 133 W (max power). 

DNA 200 with firmware V1.2SP3 the battery bar shows empty after updating firmware and sometimes after uploading settings or disconnecting the battery. 
  • This is a known issue Evolv are working on, it will not damage the mod or battery and normally recovers after the mod goes into sleep mode, you perform a soft or hard mod reboot or upload settings.