question

eugenebatterydoc avatar image
eugenebatterydoc asked

Revov RCU not seen in GX device after update to v2.62

Hi,

We have got a couple of sites with Revov Lithium batteries installed. Since yesterdays update(V2.62) on the GX devices, we can’t see the Revov RCU’s in the device list. Is it something that can be sorted out with the next update?

gx device
2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

2 Answers
Guy Stewart (Victron Community Manager) avatar image
Guy Stewart (Victron Community Manager) answered ·

Hi @eugenebatterydoc,

I moved this question to the modifications space as it's about a battery that isn't on the compatible batteries list.

You will need to contact whoever sold/supports your battery and work with them.

2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

sheedl avatar image
sheedl answered ·

The Revov RCU v1 (the smaller 12v plastic version) pretends to be a BMV700 unit, as it pretends to be PID 0x203

If you take a look at the serial logs for the service, seems like it doesn't respond properly to the queries sent to it - the get 034F fails, so the device doesn't get added on the dbus and so isn't listed in the UI.

See a sample log below (in black)


2022-04-28 12:11:53.503358500 982.835 INF.VE.Text: PID=0X203

2022-04-28 12:11:53.503575500 982.835 INF.VE.Text: V=54130

2022-04-28 12:11:53.503691500 982.835 INF.VE.Text: I=000

2022-04-28 12:11:53.519721500 982.851 INF.VE.Text: P=0

2022-04-28 12:11:53.519856500 982.851 INF.VE.Text: CE=0

2022-04-28 12:11:53.519948500 982.852 INF.VE.Text: SOC=1000

2022-04-28 12:11:53.520036500 982.852 INF.VE.Text: TTG=-1

2022-04-28 12:11:53.534877500 982.866 INF.VE.Text: ALARM=OFF

2022-04-28 12:11:53.535031500 982.867 INF.VE.Text: RELAY=OFF

2022-04-28 12:11:53.535121500 982.867 INF.VE.Text: AR=0

2022-04-28 12:11:53.551193500 982.883 INF.VE.Text: BMV=700

2022-04-28 12:11:53.551304500 982.883 INF.VE.Text: FW=0308

2022-04-28 12:11:53.551396500 982.883 INF.VE.Text: H10=1

2022-04-28 12:11:53.962825500 983.294 WRN.vd2veti: Received VdHexTimeout. Retrying.

2022-04-28 12:11:53.962993500 983.295 INF.vd2veti: Performing action: get 034F

2022-04-28 12:11:53.963090500 983.295 INF.service: 0x4248c: sending 11 :74F0300FC

...

2022-04-28 12:12:08.455624500 997.787 INF.VE.Direct: TEXT RegId=ED8D Value=00001526

2022-04-28 12:12:08.455722500 997.787 INF.bmv: itemUpdate ED8D 00001526 1

2022-04-28 12:12:08.455818500 997.787 INF.bmv: Found item Dc/0/Voltage

2022-04-28 12:12:08.455932500 997.788 INF.items: Setting item Dc/0/Voltage to value 54.139999

2022-04-28 12:12:08.456026500 997.788 INF.service: registerAllowed 0104 FAIL


I suspect its because the firmware on the RCU doesn't cater for whatever is now being asking in the newer firmwares - the get 034f bit or the registerAllowed 0104 FAIL.


Might be worth getting in touch with JJ Fischer who wrote the code for the RCU - jj@solar4life.co.za

Or check on powerforum.co.za if anyone has documented the issue. I'm "shanghailoz" on powerforum.


2 |3000

Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Related Resources

Additional resources still need to be added for this topic