Jump to content

DNA75c discharge probrem.

Recommended Posts


My board is currently experiencing problems.

That is the discharge of the battery.

1. The board does not enter sleep mode
 * In the non-charging state, the batteries decrease when locking and not locking.
 * VTC4 It has changed from 99% to 70% by leaving for 2 hours.
 * USB connection, board is generating heat even in non-charging state.
2. The board will use the battery until the end voltage of the battery.
 * If left unattended, I will use the battery until it is empty.
 * About 0.9 V or so.

My board was not originating from the beginning.
Perhaps, after doing "restore default", it seems that a phenomenon is occurring.

My board does not use production utility.
The default setting is the initial state.
Items other than "Theme" are not operated.

Board Information:
Evolv DNA 75 Color
Device Information
Serial Number    YBAK FGEW PKWY
Production History
Friday, April 21, 2017, 3:53 PM
     Board programmed


Thank you.

Link to comment
Share on other sites

@eucalyptus. does the problem resolve itself if you re-install the firmware or perform a hard reset? if not, i would open a help ticket with Evolv. the board should never let the battery pack go below 2.5v. is it possible to examine the board for damaged or missing components? could you have accidentally made a mistake when soldering in board?

  • Like 1
Link to comment
Share on other sites

Thanks for reply!.

I have examined it in more detail.

1. F/W
I tried reinstalling Rev 19 and Rev 20, but there was no change.

2. Current
I compared it with a new board.
· High current consumption
· Low end voltage (approx. 1.2V)
· It does not become standby
Therefore, not only F/W but also element failure is suspected.

Attach the measurement result.
Oscilloscope: rigol DS 1054 Z
Voltage source: DDC
Current probe: Hantek CC-65

tr_standby.png: trouble DNA75c standby
tr_endv.png: troble DNA75c end-voltage.
nm_standby.png: New DNA75c standby.
nm_endv.png: New DNA75c end-voltage.





Link to comment
Share on other sites

We found and fixed the firmware bug that could cause this with some combinations of atomizer resistances and settings. 

The good news is the error was in firmware, so installing SP 21.1 fixes the problem. The error has been lurking for a while, but really only manifested itself badly when we corrected the overvoltage case throwing check atomizer rather than limiting the output recently. 

The bad news is if the clock already took damage due to the bug, like in your case) the damage is in hardware and you will (eventually) need to have the RTC chip replaced. That's covered by the warranty of course. 

Fortunately there are VERY few of these in user hands yet, so the extent of the problem should be limited. 




Link to comment
Share on other sites

Thank you for your response.
I am sad that symptoms have occurred on my board, but it is good news that I found a bug earlier and that I can improve with software.
However, since it is a problem related to the battery end voltage, I urged the firmware update.

Link to comment
Share on other sites

  • 1 year later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...