I have a 2014 Hyundai Veloster base model (non-turbo), last week I started to feel that the battery are dying till 2 days ago the battery completely failed. So, I went to a battery shop and bought a new battery. I used to put 60Ah normal acid filled battery, but since I installed new headlights (last month) that has an extra load and wired directly to the battery using a wiring harness I sought it's better to go for a higher capacity and that's what I did I bought a 70Ah EFB battery. From here the issues started first the guys who did the battery change for me disconnected the old battery while the car was on when I found out I quickly shut the car down and then he installed the new battery after that all are good the car are working fine no issues. Later I wanted to check the battery voltage with the headlights on using an OBD2 scanner (vGate) and the car are on when I connected it to the OBD2 port all hell broke loss the cluster started acting weird the temperature gauge went to zero as if the car are not running the rpm gauge same thing goes to zero the gear status desepere and some other lights turned on, after that I quickly removed the it and all went to normal (in the cluster) and immediately connected another OBD2 scanner (Autel AP200) nothing happened to the cluster as the other scanner but some codes appeared and it took a lot of time to extract the codes that usually takes less than a min the codes are:
U0100 (CAN TIMEOUT)
U0101 (Lost comm with TCM)
U0155 (Cluster comm error)
B2500 (Warning lamp glitch)
B1625 (ECM data error)
So, I cleared the codes and it took almost 5mins to do so and in the process the OBD2 scanner (Autel) disconnect and connect again in it's own (usual it doesn't do that). After that I did connect the vGate same issue so went back to the Autel and cleared the codes and after some googling I found that it might be an issue with the CAN-BUS and someone said to disconnect the battery to reset the memory of the ECM, TCM, and the cluster so I did that disconnected the battery and waited for 30mins while bleeding all the charges using the break pedal. After that I connected the battery and started the car and used the vGate same issue again so switched to the Autel and same scenario it took a lot of time to communicate with the modules and disconnect and connect a lot til I cleared the codes.
Now, some points I need to mention
All the issues started happening after the battery change.
The car works no problem.
The OBD2 scanner (vGate) used to work no problem in my car before the battery change and I tested it today on a friends car and it worked flawlessly.
The OBD2 scanner (Autel) takes a lot of time in the communication phase that it didn't do that before.
I don't know if what happened fried something I hope not but I don't know.
I tried all possible solutions I could find online that deals with disconnecting the battery and connecting it again with no luck.
I am not that much electricity good so I am in great need of help to figure out what's happening.
Looking forward for your reply and help and I am really sorry for the long text.
Saturday, November 22nd, 2025 AT 4:11 PM





