Victron VRM Remote Firmware Update Troubleshooting

Key Takeaways

• The most likely cause for a failed remote update is missing prerequisites like a connected GX device, internet access, or correct VRM Portal settings.
• The first check should be to ensure your GX device is online, communicating with the VRM Portal, and has "Full" access enabled in its settings.
• Do not update a running system unless there are specific problems that the update is intended to fix.
• Stop DIY troubleshooting and contact a technician if you are updating a critical component like a Lynx BMS and cannot ensure the GX device is powered correctly, as this can lead to system shutdown.

Why is my Victron device not updating remotely via VRM Portal?

The most common cause for a Victron device failing to update remotely via the VRM Portal is a lack of necessary prerequisites. This includes the device not being connected to a GX device, the system lacking internet access, or incorrect VRM Portal access settings. First, verify your GX device is online and configured for "Full" VRM access.

Diagnosis

Follow these steps to diagnose issues with your Victron VRM remote firmware update.

1. Verify GX Device Connection and Internet Access:

• • Check: Ensure your Victron device is connected to a GX device (e.g., Cerbo GX). Confirm the GX device has a stable internet connection and is actively communicating with the VRM Portal.
  • Meaning: The functionality requires the device to be updated to be connected to a GX device. The system must be connected to the internet and communicating to the VRM Portal. If these conditions are not met, the remote update will not be possible.

2. Confirm VRM Portal Access Setting:

• • Check: On your GX device, navigate to Settings -> VRM Online Portal -> VRM Portal. Verify that the access setting is set to "Full". For firmware versions prior to v3.50, ensure "Two way communication" is enabled.
  • Meaning: The "Full" access setting is required for remote firmware updates. If this setting is not enabled, the VRM Portal will not have the necessary permissions to initiate an update.

3. Locate the Update Button on VRM Portal:

• • Check: Log into your VRM Portal account. Navigate to the "Firmware updates" section. Look for a green "Update" button next to your device.
  • Meaning: The VRM Portal will clearly indicate when a newer firmware version is available for your device by displaying a green "Update" button. If this button is not present, either no update is available or the system is not recognizing the device correctly.

4. Review Error Codes if Update Fails:

• • Check: If you attempt an update and it fails, note any error codes displayed.
  • Meaning: Specific error codes can point to the exact problem. For example, Error 1341 indicates the device is likely not a Victron product, while Error 1343 means the product is blacklisted for remote updates.

Cause/fix table section

Compatible Devices and Settings for Remote Firmware Updates

The Victron VRM Portal supports remote firmware updates for a wide range of Victron Energy products, provided they are connected to a GX device and meet specific communication and power requirements.

Compatible Victron Devices

Remote firmware updates are possible for products connected via various communication ports:

• VE.Direct communication port:
• • MPPT Solar Charge Controllers, including MPPT RS
  • BMV Battery Monitors
  • SmartShunts
  • Inverter VE.Direct
  • Smart IP43 Charger
  • Orion XS
• VE.Can communication port:
• • MPPT Solar Charge Controllers
  • Skylla-i battery chargers
  • Inverter RS
  • Multi RS
  • MPPT RS
  • Lynx Smart BMS
• VE.Bus connected devices:
• • Victron Energy Multis
  • Quattros
  • Other VE.Bus-connected Inverter/chargers
  • VE.Bus BMS V2
• Specific Lynx Ion BMS models:
• • Lynx Ion BMS 150A, 400A, 600A and 1000A model

Required VRM Portal Settings

For successful remote firmware updates, specific settings must be configured on your GX device:

• VRM Portal access setting: The "Full" access setting, which is on the GX device menu -> Settings -> VRM Online Portal -> VRM Portal must be enabled.
• Two way communication (for firmware versions prior to v3.50): For firmware versions prior to v3.50, the required setting is called "Two way communication" and must be enabled.
• GX device power for Lynx BMS update: When updating a Lynx BMS, make sure that the GX device is powered on the "Aux-power output". That is the only port that will remain powered during the firmware update process.

The VRM Portal has all the latest firmware files available, so you do not need to find them yourself. The system will clearly indicate when a newer version is available. You can initiate the update by pressing the green "Update" button in the "Firmware updates" section of the VRM Portal.

Safety

Use the remote firmware update feature with care. Victron Energy advises that newer firmware is not always better, and you should not update a running system unless there are problems with it.

When updating a Lynx BMS, specific safety precautions are critical:

• Ensure the GX device is powered on the "Aux-power output". This is the only port that will remain powered during the firmware update process.
• All other ports (main contactor, and also Allow-to-charge and Allow-to-discharge signals) will disconnect. This will cause Multis and also loads to switch off during the update. Be aware of the potential for system downtime and ensure any critical loads are safely handled before initiating a Lynx BMS update.

When to call a technician instead

Remote firmware updates can be complex, especially for critical system components. You should call a qualified technician if:

• You are unsure about the implications of a firmware update for your specific system configuration.
• You are attempting to update a Lynx BMS and cannot ensure the GX device is powered correctly via its "Aux-power output", or if you are concerned about the system shutdown that will occur.
• A VE.Direct MPPT Charge Controller update fails, and you are unable to reconfigure the device locally.
• Your system is functioning correctly without any issues, as the general advice is not to update a running system unless problems exist.
• You encounter persistent errors (like Error 1341 or 1343) that you cannot resolve using the provided troubleshooting steps.