Problems with Valence software scanning battery

[Graphiciron]

I woke up this morning and was having some communication issues myself for whatever reason. went to bed and everything fine, woke up and having troubles seeing all the batteries in the string. I messed around with the connector for a while and hooked the batteries up in a different order and seemed to work.

I would check to make sure your drivers are installed correctly, make sure all your connections are good, restart your computer, check everything and try again. I would also try switching your communication wires around and see if that helps. the "change module ID" is always 1 unless you change it. Are you sure the battery is actually number 1? usually they have different ID numbers unless someone has already changed it, or it was really the first battery in the string. My batteries all have stickers on them that have the serial number and the module ID number on it. double check everything cause you are almost there.

 

[ericgrand]

I had to test 2 adapters before finding one which work... The one ordered from Aliexpress https://fr.aliexpress.com/item/33025022759.html?spm=a2g0s.9042311.0.0.27426c37UYzDiT was not working...

 

[Hobbsy]

I may also have this issue however it relates to a particular battery (36v version). The same cable and software work ok on a 12v version but on the 36v I can locate battery and perhaps change the ID but when I hit Read I get the same error as the OP. I think I have an older version of the software I can try. As the fault follows the battery I'm worried that the BMS Comms hardware might be damaged? Either that or it has newer firmware that my software doesnt support.

What is the very latest version of the Valence software?

Thanks

 

[Travis]

If anyone needs a working RS 845 to usb adapter with the right connector for the battery already wired to it I sell them for $35. The wires are molded into the USB connector so there's no tiny screws to come loose. So many other possible issues to cause it not to work it's best to get a cable from me so you know for sure the cable is not the problem. I'm in the USA

 

[Hobbsy]

Hi. There is no problem with my cable as it too is soldered and Raychem adhesive lined heatshrunk. I can offer these cables for £29.95 posted in the UK. Would offer Europe for a fiver more but Brexit and paperwork it is too much hassle until they streamline it a bit!

 

[Hobbsy]

I suspect the battery or the software application version as it works flawlessly with 12v ones

 

[Abex]

Has anybody seen this issue?
View attachment 39469
I'm running as Administrator, with a single battery connected. When I hit "Scan", a battery with module ID 1 shows up immediately, but when I hit "Start Read" with Module ID 1 selected, I always get the error message "Please check the Com Port or ModuleID".
It's clearly communicating fine since it returns the battery serial number and other info with a Scan. The battery itself has a flashing green light that transitions from every 30s to every 5s when it gets scanned, so that seems fine too. Any ideas?

Did you find out why this is happening? I have the exact same problem with a P30-36C. Comms is definitely working. Locate Battery works. Scan works; it finds the ID, serial number, F/W rev& date. But hit "Start Read" and it returns "Please check the Com Port or ModuleID" I'm guessing the battery is incompatible with this version of the Valence Module Diag program. Can anyone shed any further light on this? Thanks!

 

[TomF]

Did you find out why this is happening? I have the exact same problem with a P30-36C. Comms is definitely working. Locate Battery works. Scan works; it finds the ID, serial number, F/W rev& date. But hit "Start Read" and it returns "Please check the Com Port or ModuleID" I'm guessing the battery is incompatible with this version of the Valence Module Diag program. Can anyone shed any further light on this? Thanks!

I think you are right in that the battery firmware version and the Diag program are incompatible. I have not found a way to update the battery firmware or even if it is possible. It would be great if someone knowledgeable could chime in.

 

[Travis]

I think you are right in that the battery firmware version and the Diag program are incompatible. I have not found a way to update the battery firmware or even if it is possible. It would be great if someone knowledgeable could chime in.

I know all the knowledgeable people in this area and although it may be possible to decompile and reflash the firmware from the green battery into the black ones I don't think anyone sees enough value in figuring it all out. Better to just delete the internal board in the black battery and replace it with an aftermarket BMS.

I think they increased the size of the bleed off resistors in the green batteries so the hardware is also different which means you have to rewrite the whole code in order to run the green software in the black battery. And trust me that's not going to happen. If the same amount of temperature sensors and same values are present there though maybe the board from the green battery could be installed into the black battery? But where oh where might you find boards from Green batteries?

 

[iamburgerking37]

I was cursed by this "everything works, but it won't connect" thing today. Thanks for all the other helpful comments.

What fixed mine was those little pins in the tyco connector were backing out when I pushed the whole connector onto the battery's connector.

I took a precision flathead screwdriver to the back of my homemade connector and pushed them in one by one. Voila! The program connected.

Hope this helps someone.