since I uploaded new Cerbo GX firmware (v3.41), I cannot acces VEConfigure files anymore (need to install update with ESS details).
I get error code 1392
I checked the 2-way communication on GX and this is fine…
What is the firmware on the inverters?
552 on multiplus2 (48/5000/70)
This should be latest version. I updated all at the same time 2 days ago.
PS. Also the firmware update doesn’t work anymore. Error message regarding
2-way communication…
But as said in the original question, I checked these settings in VRM and
it is enabled.
Odd. I just tried one of mine and it is fine.
Has everything been rebooted?
Nothing except the gx is connected to the ve bus?
Do you have an mk3 to usb adaptor for these situations?
You may want to ssh to the cerbo and check that it has not run out of disk space.
If all else fails, consider reflashing the GX.
I have following configuration:
- Victron MP2 and MPPT connected to GX (via 2 different cables, but I never remember how these cables are called…)
- DIY 16cell LFP and JK BMS connected to GX via serial to usb adaptor
- Vanderwall software loaded into GX to read JK information
- All connected wireless to my (mini) WiFi router and also wireless to my laptop
This has worked past year, but not anymore since last update.
Unfortunately I’m not a software genius so I do not understand every detail of the SW… I can upload things and expect this to work (hopefully). Troubleshooting on SW is another thing…
As I have no connection to the GX anymore, I think I will have to get back to factory setting SW on my GX and restart from zero.
(As suggested by Nick)
What holds me a bit is that the whole system is working. I would just like to change some setting in the ESS assistant loaded into the GX.
On the other hand, there will come a time I will need/want to update firmware on the Victron components anyhow and then I have no connection either. So I would need to restart from zero anyhow.
Do you have installed any third-party software on the GX device?
Yes.
I have dus-serialbattery SW from Louis Van Der Walt (via GitHub).
But this has never influenced any updates in the past. Why now ?
There are alot of changes to the GUI and various others for control changes. It really is never a good idea to update the system is doing what you want/need it to do.
Its not like computers that need security updates.
The process for validating an issue would be to reproduce it without modifications. This can be a pain but is necessary for beta testing.
@jan_DB
The first place I’d head is checking the Wifi pages in the GX. These fields should all be populated…
The Cerbo lan/wan features are quite comprehensive. The manual worth a look if this is your issue.
There are some reports that third-party software causing the system partition to fill up slowly and if it is full it can cause several problems.
I rebooted the GX with a USB stick and reinstalled Firmware version v3.40
(after I disconnected the Serial Bus connection)
All works again, except I have no info coming from my BMS anymore.
Need to check Github website about the “Louis Vanderwalt driver”.
See if there are any modifications done which would not be compatible with GX Firmware v3.41.
(I’ll add to this thread if any update about the issue arises when reinstalling the LouisVDW driver on the GX again)
Thanks to all for your support !
Some update:
A newer version of the dbus-serial battery SW is installed again on Cerbo GX.
The GX is still running v3.40, and all seems to be just fine.
I have again access to VEConfigure files. So I can modify my ESS Assistant again …
Happy me !
I wait till next WE to update the GX to v3.41 and see if the newer version of dbus-serial battery continues to be operational and does not block access to VEConfigure files.
To be continued
As i was saying. We do have a similar set up with the jkbms. And didn’t have the same issue. Have updated to beta and reversed it. Something must have been lost in the ether somewhere when your update ran.
Thanks Alexandra for the info. I must have misunderstood your initial reply…
Good to know that the recent version of GX firmware should work in combination with the latest version of the dbus-serial battery SW. I’ll give it a try next days…
My issues might be caused that the older version of dbus-serial battery SW I ran on the GX was not compatible with the newer version of GX firmware I installed yesterday.
I’m not going to worry anymore… my system is up and running again.