Greetings All,
I have 4P4S 920ah 12v LiFePo bank with a REC Active BMS, Cerbo GX, 1200w of solar with 4 MPPTs, MultiPlus-II and a WS500/Balmar XT-250. I have had my system working on my boat for over a year without issue.
I recently purchased a WS500 Pro during the recent sale. I wanted to turn my current WS500 (non pro) into my spare and use the bluetooth feature on the Pro to monitor the alternator and make changes without having to remove the cover. I'm sure most of us have been waiting for this feature for sometime. For the past two weeks I have been trying to get this thing to work with no luck. I have been updating firmware and changing settings on the ABMS, Cerbo GX and WS500 Pro. I keep getting the #42 fault, required sensor is missing. The only required sensors I have enabled are:
1) Require a CAN connected BMS?
2) Override default Require Sensor behavior (Do hard fault)?
I also tested to see what would happen if I unchecked the BMS requirement, the #42 fault went away.
So tonight, without changing any wiring or settings in the Cerbo or REC, I plugged my old WS500 back in using the same wiring harness and CAN cross over cable. After it booted up it went into slave mode with the amber light flashing as it has done for the past year. I used the app to update the firmware on both units to the most recent 2.6.0. Both units are configured identically aside from the enable wireless communication for the Pro.
Has anyone else been able to get a WS500 Pro to connect to their REC BMS?
We havent done any testing with the Pro yet so I am going to include Al from Wakespeed in this thread and hopefully he will have some insight.
@Al Thomason
Disclaimer: Al from Wakespeed.
Sorry to hear you are having issues, let me look into this some. Should of course be transparent, as the source code is common. But let me set up a REC in the lab and see if I can find anything...
@Al sounds good, thanks for looking into this. Let me know if you need more details on my setup to try to replicate the fault condition on your end.
@Rance Kilbourn
(Disclaimer: Al from Wakespeed).
OK, we have found something in the WS500-PRO code that looks to be your issue. Or at least, could well be… It is related to the 11-Bit drivers in the underlying CAN subsystem.
I have a test -DEV firmware that you can use, but am unable to figure out how to attach it to this post. @Rick-admin , any ideas?
Or you could send an Email to support@wakespeed.com , mention this and me, and we can get you the test firmware that way. If you are willing to give it a go.
Assuming so, once you get the file you will use the Wakespeed app to update your WS500-PRO:
- Copy the .BIN file to your phone/tablet
- Connect via BLE to the WS500-PRO (Device screen)
- Toggle on Expert Mode
- On the Device Screen, select Update Firmware
- Select 'Chose Other file'
- Select the firmware .BIN file you copied in step 1.
- Perform update wirelessly via BLE (OTA)
If you would give it a try and reply back if it works that would be appreciated. We will be including the patch in the next firmware update.. If it does not fix our issue, then we can take a more direct step to getting things resolved.
But let see how to get you the patched firmware, either via support@wakespeed.com, or if Rick has some hidden way to allow me to attach / or directly send a file here for your use.
Thank you,
-al-
@Al Thomason
Thanks for the quick response Al. If you email it to me at support@ogm-energy.com I will see that Rance gets it.
Best of the season!
Rick
@Rick
@Al
Thanks to you both for the quick response. I did the update and now it seems to be stuck unresponsive with a very dim green led when in running mode. The app doesn't recognize it via usb and bluetooth is not on.
I got it in DFU mode with the app to try to restore the firmware, but it doesn't recognize the WS500Pro file from the previous install folder as a compatible device. I flashed the non pro WS500 firmware but it is still not connecting with the app. I also tried the Windows utility tool but there was no system change. Maybe I would need the .DFU version of the test -DEV firmware file to flash it that way?
I'm happy to keep working on this if you have suggestions.
Happy Holidays!
-Rance
Problem solved! The -DEV firmware mentioned above did not work but after a few emails and phone calls, Al got me sorted out with a patched firmware.
They are working on releasing the new revised firmware soon, but if you need help in the mean time just send the guys an email at support@wakespeed.com along with posting here. They are very responsive and helpful.
Thanks Al & Matt!
-Rance
