Client context request timed out while connecting

VictronConnect manual

9.1. Introduction & automatic updates

What about updating the firmware of VE.Bus products such as MultiPlus and Quattro?

Please follow this separate firmware guide to update products like MultiPlus and Quattro that use VE.Bus connection via MK3 USB adapter instead of VE.Direct or Bluetooth.

How can I see which firmware version is available?

First, connect to the product, then go to the Product informations side. Under the firmware version you will see a text informing you whether you are using the latest available version or whether an update is available. If a new version is available, you can start the update process by pressing the "Update" button.

Some firmware versions are mandatory. When you connect to the product, VictronConnect will prompt you to update immediately if a mandatory version is available.

Or, if you are not near the product, open the demo library and select the product. The product information page shows the latest available version that ships with VictronConnect.

Do I need to be connected to the internet to update the firmware?

No. To update the firmware is no Internet connection required, the latest firmware files are already loaded in VictronConnect on your phone. All firmware files are automatically updated when the app is updated.

How does it work?

After you've connected your product, VictronConnect will automatically check for a mandatory update available, and if so, it will walk you through the update procedure before doing anything else.

If an update is available but not required, you can see your product's overview page, but you cannot change any settings, and the Settings page will prompt you to update the product. You can update to the latest version using the dialog on the page Settings start or you go to Product information and press the "Update" button.

A firmware update - if available - must be carried out in order to change the settings on your Victron product with VictronConnect.

Will I have to reconfigure my MPPT or BMV after the update?

No. The settings of your VE.Direct and Bluetooth products are not affected by the firmware update ... so you do not have to reconfigure your product after the update. In addition, the history data of BMVs and MPPTs will be retained during a firmware update.

9.2. Update to a firmware file provided by yourself

The previous chapter explained how VictronConnect is automatically updated to the latest firmware version. It is also possible to update a product with a file that you provide yourself.

This is not needed very often. Some reasons for such an approach could be:

  • Update to a very current version that is already available on Victron Professional, but has not yet been delivered with VictronConnect. Note that instead of going through this effort, you can wait a little longer for a new version of VictronConnect to be released.

  • Update a product to a special or unreleased version.

Instructions for Windows and MacOS computers

With your phone and Victron product connected to VictronConnect, go to the Product Info page, click Update, and open the correct firmware file.

You don't have to worry about using the wrong file - VictronConnect will always check that the file matches the product first. And if it is wrong, it will show an "Error in the wrong firmware file".

Instructions for Android and iOS phones and tablets

The procedure is slightly different from the Windows / MacOS routine as there is no file browser on a mobile device.

First you need to add the desired firmware file to the VictronConnect firmware library. Firmware files can be added to the library through an email attachment, web browser, Dropbox, file browser, and any type of application that can handle files. For both iOS and Android, the process of adding the file is the same: go to the application that contains the firmware file, tap it and open it with VictronConnect. VictronConnect opens and shows: "File added to firmware library".

If the message doesn't appear, repeat the previous step or try opening the message from another application (e.g. Dropbox instead of the Internet or email).

If you're not sure which file to use, adding multiple files to the library is no problem. In the next step, VictronConnect automatically only shows the files that match the connected product.

  • Note for iOS: The current version of Google Chrome for iOS cannot download ".dup" files from the Victron Professional website - so we recommend using Apple Safari, the default iOS browser, instead.

  • Note for Android: VictronConnect must be running before opening files.

Open VictronConnect and, without closing it, go to the application that contains the file, select it and choose to open it with VictronConnect.

Here are screenshots showing the detailed steps:

Now that you've added the firmware file to the library, go to the Product Info page and tap Update Firmware:

Select the desired file from the list, see the next screenshot - an entry is displayed in the list:

Note that the update mechanism detects and rejects firmware files that are not intended for the current product: you don't have to worry about the wrong firmware file being loaded.

Once selected, you will be guided through the update process:

9.3. Troubleshooting firmware updates

Instructions for troubleshooting firmware updates can be found in Section 11.3

Despite our best efforts, mistakes sometimes occur. But don't worry, your product can always be restored.

In most cases, errors are caused by communication problems. Always check all cable connections. If you are using bluetooth, stay as close as possible to the product and check that bluetooth is enabled on your phone. Sometimes you may need to clear the Bluetooth pairing information on your phone in order to reconnect with your product.

Check section 10.3 of this manual for troubleshooting firmware updates. Always mention the error code when asking for help.

VE.Direct products

error

description

D3

No VE.Direct product (s) found.

D4

Unknown error occurred. Try again and check the product settings after the update.

D10

Error closing the COM port.

D20

Update could not start, no updatable product found.

D26

Update failed, communication lost. The product could be unusable. Check the connection and the power supply. Try again and check the product settings after the update.

D29

Update could not start, firmware file is damaged.

D31

The update failed, the product is unusable. Try again and check the product settings after the update.

D32

Could not start the update, entry into boot mode failed.

D33

Update could not be started, firmware file was not found.

D90

Could not start the update, the firmware is not suitable for this product.

D91

Could not start the update, an unknown product was found.

D92

Update failed, firmware deletion failed. The product could be unusable. Try again and check the product settings after the update.

D93

Error starting firmware after update. Turn your product off and on again, and if that doesn't help, try the update again and check the product settings after the update.

D94

The product was updated successfully, but there was an error reading the previous settings. Check the product settings.

D95

The product was updated successfully, but there was an error restoring the previous settings. Check the product settings.

D96

The update failed due to version differences. Turn your product off and on again, and if that doesn't help, try the update again and check the product settings after the update.

D97

Dup executable too old.

D98

Firmware file is not a valid dup file.

D99

The product was updated successfully, but there was an error restoring the settings. Check the product settings.

D100

Settings cannot be migrated because the application is not active. Manual action required.

Blue Smart Charger, Smart Lithium and VE.Direct Bluetooth Smart Dongle

error

description

B1

Error reading file.

B2

Victron BLE service not found. Please remove the product from the list of paired devices and try again.

B3

Dfu-BLE service not found. Please remove the product from the list of paired devices and try again.

B4

The product separated unexpectedly. Maybe the binding information is no longer valid? Please remove the product from the list of paired devices and try again.

B5

Writing to the device failed.

B6

The product did not activate its bootloader - although it should have.

B7

The product was not separated - although it should.

B8

The Victron BLE service access timed out.

B9

The access to the Dfu BLE service has timed out.

B10

The reply has timed out.

B11

The product timed out while writing to it. Maybe a pairing dialog is shown? Please try again.

B12

The device was no longer found. Maybe out of reach? Please try again.

B13

The product did not start the new firmware. Please try again. If you continue to have problems, please submit a service report to Victron Energy.

B14

Could not start the update, the firmware is not suitable for this product. Please make sure you have selected a valid update file and try again.

B96

An internal error has occurred (opcode is not supported). Please send a service report to Victron Energy.

B97

The requested encryption is not supported by the product. Please send a service report to Victron Energy.

B98

An internal error has occurred (data size exceeds limits). Please send a service report to Victron Energy.

B99

The product was unable to save the firmware to its memory. Please try again and if the problem persists please contact Victron Energy.

B100

An internal error has occurred (CRC error). Please send a service report to Victron Energy.

B101

An internal error has occurred (data length error). Please send a service report to Victron Energy.

B102

An internal error has occurred (not allowed). Please send a service report to Victron Energy.

B103

An internal error has occurred (unexpected data length). Please try again. If you continue to have problems, please submit a service report to Victron Energy.

B104

An internal error occurred (unsupported data). Please try again. If you continue to have problems, please submit a service report to Victron Energy.

B105

An internal error has occurred (different versions). Please try again. If you continue to have problems, please submit a service report to Victron Energy.

B106

This firmware is too old. Make sure you have the latest version and try again.

VE.Bus products

error

description

V2

No product recognized. Please check all cable connections and try again.

V3

An unexpected timeout was triggered. Please check all cable connections and try again.

V4

Incomplete vff file. Nonce is missing. Please make sure you have selected a valid update file and try again.

V5

Incomplete vff file. EEPROM lines are missing. Please make sure you have selected a valid update file and try again.

V6

The vff file contains more EEPROM data than is supported. Please make sure you have selected a valid update file and try again.

V7

The calibration map in the file exceeds the device calibration map. Please make sure you have selected a valid update file and try again.

V8

The device calibration data size is larger than expected. Please make sure you have selected a valid update file and try again.

V9

The boot loader did not react to the setting up of the boot loader. Please check all cable connections and try again.

V10

Boot loader response to version request failed.

V11

Incompatible boot block. Function version invalid.

V12

Incompatible boot block. Version invalid.

V13

The boot loader was not started after the boot block was updated.

V14

Incompatible boot block type.

V15

No or unexpected response to the target ID query.

V16

No or unexpected response to EEPROM read action.

V17

No or unexpected response to the query on the calibration card.

V18

The firmware supplied contains new, unsupported calibration values. The updater doesn't know how to deal with it.

V19

No response to EEPROM write command received. Please check all cable connections and try again.

V20

Invalid response to EEPROM write command received. Please check all cable connections and try again.

V20

Invalid response to EEPROM write command received. Please check all cable connections and try again.

V21

No response to the write code command received. Please check all cable connections and try again.

V23

The MK2 / MK3 did not respond. Please check all cable connections and try again.

V24

The connected product does not match the model specified in the file. Please make sure you have selected a valid update file and try again.

V25

The EEPROM specification data specific to the hardware revision is corrupt. Please make sure you have selected a valid update file and try again.

V26

Updates cannot be carried out if a VE.Bus BMS is connected.

V27

Updates cannot be performed when a DMC is connected.

V40

Update could not be started. Couldn't allocate memory. Malloc error.

V50

Update could not be started. Error when opening the file. Please check the storage location of the file and the access rights. Make sure you have selected a valid update file and try again.

V51

Update could not be started. File write error. Please check the storage location of the file and the access rights. Make sure you have selected a valid update file and try again.

V52

Update could not be started. Error reading file. Please check the storage location of the file and the access rights. Make sure you have selected a valid update file and try again.

V53

Update could not be started. File checksum error. File defective or not a valid VFF file.Please make sure you have selected a valid update file and try again.

V54

Update could not be started. File has an incompatible version number. Please make sure you have selected a valid update file and try again.

V55

Update could not be started. File section not found. File defective or not a valid VFF file. Please make sure you have selected a valid update file and try again.

V56

Update could not be started. Format error. File defective or not a valid VFF file. Please make sure you have selected a valid update file and try again.

All other products (XUP update files)

error

description

X3

Invalid updater status. Please try again.

X4

Firmware not for product (id). Please make sure you have selected a valid update file and try again.

X5

Updater (version) too old.

X6

Communication error. No callback handler connected. Please check the connection and try again.

X7

Communication error. Vreg ack-ed with an unexpected bug. Please check the connection and try again.

X8

Update (xup) file format is not supported. Please make sure you have selected a valid update file and try again.

X9

File error. No instance blob could be found in the update file. Please make sure you have selected a valid update file and try again.

X10

File error. Invalid instance of blob attribute. Please make sure you have selected a valid update file and try again.

X11

File error. Instance blob defined more than once. Please make sure you have selected a valid update file and try again.

X12

File error. No firmware version was found for the instance in the update file. Please make sure you have selected a valid update file and try again.

X13

Communication error. Unexpected Vreg Ack received. Please check the connection and try again.

X14

Communication error. The instance could not be reached. Please check the connection and try again.

X15

Checking the minimum firmware version failed. Please make sure you have selected a valid update file and try again.

X16

Update failed to start. Please check the connection and try again.

X17

File error. No / invalid firmware data was found for the instance in the update file. Please make sure you have selected a valid update file and try again.

X18

Update error. Invalid ack on non-final update data. Please check the connection and try again

X19

Update error. Invalid sequence # in update data ack. Please check the connection and try again.

X20

Update error. Invalid instance # in update data ack. Please check the connection and try again.

X21

Update error. Invalid ack on final update data. Please check the connection and try again.

X22

Verification failure. Invalid firmware version Ack. Please check the connection and try again.

X23

Verification failure. Invalid UDF version Ack. Please check the connection and try again.

X24

Verification failure. Invalid instance field in the minimum firmware version Ack. Please check the connection and try again.

X25

Verification failure. Invalid instance field in firmware version Ack. Please check the connection and try again.

X26

Verification failure. Invalid instance field in UDF version Ack. Please check the connection and try again.

X27

Verification of the minimum firmware version failed. Please check the connection and try again.

X28

Verification of firmware version failed. Please check the connection and try again.

X29

Checking the UDF version failed. Please check the connection and try again.

X30

Verification failed with the minimum firmware version. Please check the connection and try again.

X31

Verification of firmware version failed. Please check the connection and try again.

X32

Still in bootloader mode after upgrading. Please try again.

X33

File error. No product ID found in the update file. Please make sure you have selected a valid update file and try again.

X34

File error. No VE.Direct baud rates found in the update file. Please make sure you have selected a valid update file and try again.

X35

File error. No version in Xup format was found in the update file. Please make sure you have selected a valid update file and try again.

X36

File error. No minimum update version was found in the update file. Please make sure you have selected a valid update file and try again.

X37

File error. No firmware (product) version found in the update file. Please make sure you have selected a valid update file and try again.

X38

File error. The update file does not conform to the XML standard. Please make sure you have selected a valid update file and try again.

X39

Communication error. Vreg-Ack timeout. Please check the connection and try again.

X40

Communication error. No product found. Please check the connection and try again.

X41

Communication error. Comm port error. Please check the connection and try again.

X42

Update error. The baud rate could not be set. Please check the connection and try again.

X43

Update error. Update in progress on another interface.

X44

Update error. Invalid instance # in Ack. Please check the connection and try again.

X45

Update error. Vreg-Ack Error: Invalid Instance. Please check the connection and try again.

X46

Update error. Vreg-Ack failure. Please check the connection and try again.