JoseD Posted February 9, 2022 Report Posted February 9, 2022 Yesterday I updated to latest firmware, but it seemed that after doing it, DNA was not recharging. To make sure, decided to go back to previous firmware, but for some weird reason it failed to complete. After that, I cannot get it to connect to escribe. Any solution, or is it bricked?
Wayneo Posted February 9, 2022 Report Posted February 9, 2022 Try using a different USB cable and see if that helps, ideally plugged in direct (no hub)
JoseD Posted February 9, 2022 Author Report Posted February 9, 2022 4 minutos atrás, Wayneo disse: Try using a different USB cable and see if that helps, ideally plugged in direct (no hub) Tried with several cables without success. Also no hub. DNA is not detected by PC. Will try on another computer to see if there is no problem with current one. (But I don't think there is)
JoseD Posted February 10, 2022 Author Report Posted February 10, 2022 New try, with several cables and the computer doesn't detect the board. Is there a way to force detection after a failed firmware update? Tried on Linux. Unsure if I can be more successful on windows...
Wayneo Posted February 10, 2022 Report Posted February 10, 2022 IIRC your mod should detect a failed update. I'm a Mac guy so no longer Windows savvy. You could/should a Help desk ticket with Evolv. Link in my signature. Good luck and let us know how you make out.
dwcraig1 Posted February 10, 2022 Report Posted February 10, 2022 You should still be able to apply service pack even though it's not connected to EScribe, it does still need to be detected by Windows though. Just apply the firmware update just as you normally would. Check in Window's Device Manager to see if Windows detects it. Then again maybe that's what your already saying that is not happening. There are some USB 3.0 controllers out there that seem to not get along with DNA boards.
JoseD Posted February 14, 2022 Author Report Posted February 14, 2022 Update on the current situation: After trying a lot, with one of the cables I was able to connect and finished update. Then I reverted to previous firmware and it seemed to work well. Later on I discovered that was not charging the 4 18650 cells, so I try to see on computer what was going on . Couldn't connect it once again, even with same cable (on Linux OS) Decided not to mess more with it, at least until I see if same behavior persists on a windows computer. But at least it works once again. Not a huge problem if i need to charge battery on external charger. One question: If battery is not married , it may happen that they are not balanced and DNA board doesn't charge (or charge so slowly that seems that is not charging)? Thanks a lot for you help
Wayneo Posted February 14, 2022 Report Posted February 14, 2022 2 hours ago, JoseD said: One question: If battery is not married , it may happen that they are not balanced and DNA board doesn't charge (or charge so slowly that seems that is not charging)? So if you have a 4 cell (battery) mod, if one or more cells is lower than the highest it can appear very slow as it's a balance charger. It would be much quicker to charge externally (even if it's just that once cell), to get them balanced again. escribe Device Monitor will show the volts of each cell, or maybe the theme on your mod EDIT: The DNA250C balances the charging for every cell count. 2-4 cells. Added for clarity.
JoseD Posted February 14, 2022 Author Report Posted February 14, 2022 Yup, it makes sense. I will try with 4 new cells just to make sure if that's not the case
dwcraig1 Posted February 14, 2022 Report Posted February 14, 2022 1 hour ago, JoseD said: Yup, it makes sense. I will try with 4 new cells just to make sure if that's not the case Buy a meter for $5 1
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now