the Device Reported an Unexpected Error During the Flash Procedure

9 . Firmware updates

9.1 . Introduction & automated updates

What about updating Firmware on VE.Double-decker products such as MultiPlus and Quattro?

Delight follow this seperate Firmware guide for updating products such as MultiPlus and Quattro that use a VE.Bus connexion via an MK3-USB adaptor, instead of VE.Straight or Bluetooth.

How tin I see what firmware version is available?

First, connect to the product, then go to the Product info  page. Under the Firmware version you will see a text informing you if yous are using the latest available version or if at that place is an update bachelor. If a new version is available you can first the update process by pressing the "Update" push button.

Some firmware versions are mandatory. When yous connect to the product, VictronConnect volition prompt to update immediately in instance at that place is a mandatory version bachelor.

Or, when not close to the production, open up the Demo library, and select the production. The Product info page will show the latest available version that is shipped with VictronConnect.

Practise I need to be connected to the internet for updating firmware?

No. Updating firmware does not  require an internet connexion, the latest Firmware files are already loaded inside VictronConnect, on your phone. When updating the app, all firmware files are updated as well automatically.

How does it work?

After connecting your product, VictronConnect will automatically check whether a mandatory update is available, and in that instance, you will be guided through the update process before doing anything else.

If an update is available but is not mandatory, you volition be able to see your product'south overview folio, but you won't be able to alter whatsoever settings and the Settings page volition prompt you lot to update the product. You tin first the update to the latest version via the dialog on the Settings  folio, or going to the Product Info  folio and pressing the "Update" button.

A firmware update - when available - will need to exist completed in club to change settings on your Victron product using VictronConnect.

Will I demand to reconfigure my MPPT or BMV afterwards the update?

No. The settings of your VE.Direct and Bluetooth products volition non exist afflicted past the firmware update …and so you volition not demand to reconfigure your product after the update. Likewise, the History information of BMVs and MPPTs will be preserved throughout a firmware update.

ix.ii . Updating to a cocky-supplied firmware file

The previous affiliate explained how VictronConnect will automatically update to the latest firmware version. Likewise that, information technology is also possible to update a production with a file that you supply yourself.

This is non needed very often. Some reasons to practice then could exist:

• Update to a very recent version, that's already available on Victron Professional person but non still shipped with VictronConnect. Note that instead of going through this effort, you can besides wait a scrap 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 telephone and Victron product continued to VictronConnect, get to the "Product info" folio, click on "Update" and open the correct firmware file.

There is no need to worry about using a wrong file - VictronConnect will e'er kickoff check if the file matches the product. And if incorrect, information technology volition evidence a "wrong firmware file fault".

Instructions for Android and iOS phones and tablets

The process is slightly different from the Windows/macOS routine, equally there is no file browser on a mobile device.

Firstly, you need to add the desired firmware file to the VictronConnect firmware library. Firmware files tin be added to the library from an electronic mail zipper, web browser, Dropbox, file browser, and whatsoever kind of app that can handle files. For both iOS and Android the procedure to add the file is the same: go to the app that contains the firmware file, tap on it, and open up it with VictronConnect. VictronConnect will exist opened and show: "File added to the firmware library".

If the message doesn't appear, repeat the previous step or endeavor opening from a different app (for example, Dropbox instead of the internet, or Email).

In case you are non sure which file to utilise, it is not a trouble to add together multiple files to the library. In the next footstep, VictronConnect volition automatically only show the files that friction match with the connected product.

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

• Note for Android: VictronConnect needs to be running earlier opening files.

Open VictronConnect and, without closing it, switch to the app containing the file, select information technology, and cull to open information technology with VictronConnect.

Here are screenshots showing the detailed steps:

Now, after calculation the firmware file to the library, get to the "Production info" page and tap on "Update firmware":

Select the desired file from the list, see side by side screenshot - it shows one entry in the listing:

Note that the update machinery will notice-and-decline firmware files which are not targeted for the current product: there is no need to worry about loading a wrong firmware file.

Once selected you will exist guided through the update procedure:

9.3 . Troubleshooting firmware updates

A troubleshooting guide relevant to firmware updates tin be found in affiliate 11.3

nine.4 . Mistake codes

In spite of our painstaking efforts, sometimes errors occur. Simply don't worry, information technology is always possible to recover your product.

In most cases, errors are caused past communication problems. Always make sure to check all cablevision connections and, if yous are using Bluetooth, stay equally close to the product as possible and cheque that the Bluetooth role is enabled on your telephone. Sometimes y'all may need to remove the Bluetooth pairing information from your phone in order to be able to reconnect with your product.

Bank check chapter 10.3 of this manual for Troubleshooting firmware updates. When asking for help, make sure to always mention the fault code.

VE.Direct products

Error	Description
D3	No VE.Straight product(s) found.
D4	Unknown error occurred. Try once again and check the product settings once updated.
D10	Error closing com port.
D20	Could not outset updating, no updatable product constitute.
D26	Updating failed, advice lost. The production might be unusable. Cheque connection and power supply. Endeavour over again and cheque the product settings in one case updated.
D29	Could non start updating, the firmware file is decadent.
D31	Updating failed, the production is unusable. Try again and check the product settings once updated.
D32	Could not starting time updating, inbound boot way failed.
D33	Could not beginning updating, the firmware file is non establish.
D90	Could not start updating, the firmware is not for this production.
D91	Could not start updating, an unknown product was constitute.
D92	Updating failed, erasing firmware failed. The product might be unusable. Effort again and check the product settings once updated.
D93	Error starting firmware after updating. Ability bike (off/on) your product and if that does not assist, endeavor updating again, and check the product settings once updated.
D94	Production updated successfully, but an error occurred reading the previous settings. Bank check the product settings.
D95	Production updated successfully, only an fault occurred restoring the previous settings. Check the product settings.
D96	Updating failed due to version mismatch. Power bicycle (off/on) your product and if that does not help try updating once more, and check the product settings once updated.
D97	Dup executable besides onetime.
D98	Firmware file is not a valid dup file.
D99	Product updated successfully, but an error occurred restoring the settings. Check the product settings.
D100	Cannot migrate settings because the application is not active. Transmission action required.

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

Error	Description
B1	Error reading file.
B2	Victron BLE service not institute. Please remove the product from the listing of paired devices and retry.
B3	Dfu BLE service not found. Please remove the product from the listing of paired devices and retry.
B4	The product asunder unexpectedly. Perhaps the bond data is no longer valid? Delight remove the production from the list of paired devices and retry.
B5	A write to the device failed.
B6	The product did not activate its bootloader - although information technology should have.
B7	The production did non disconnect - although it should.
B8	Timeout waiting for access to the Victron BLE service.
B9	Timeout waiting for admission to the Dfu BLE service.
B10	Timeout waiting for a response.
B11	Timeout while writing to the production. Perchance a pairing dialogue is shown? Please retry.
B12	Device was no longer institute. Mayhap out of range? Please retry.
B13	The production did non starting time the new firmware.  Please try again. If you are yet having problems, ship a service study to Victron Energy.
B14	Could not offset updating, firmware is not for this production. Delight make sure you selected a valid update file and try again.
B96	An internal error occurred (Opcode not supported). Please send a service report to Victron Energy.
B97	The requested encryption is not supported past the product. Please send a service report to Victron Energy.
B98	An internal error occurred (Information size exceeds limits). Please send a service report to Victron Energy.
B99	The product could not store the firmware in its retentivity. Please retry, and if the problem persists, please contact Victron Energy.
B100	An internal error occurred (CRC fault). Please transport a service report to Victron Energy.
B101	An internal fault occurred (Information length mistake). Delight send a service report to Victron Energy.
B102	An internal error occurred (Not immune). Please transport a service written report to Victron Energy.
B103	An internal mistake occurred (Unexpected data length). Please try over again. "If you lot are still having issues, send a service report to Victron Energy.
B104	An internal error occured (Unsupported information). Please try once more. If you are still having issues, send a service report to Victron Energy.
B105	An internal error occured (Version mismatch). Please try again. If you lot are still having issues, send a service report to Victron Energy.
B106	This firmware is too old, brand certain yous have the latest version and attempt over again.

VE.Bus Products

Error	Description
V2	No production detected. Delight bank check all the cable connections and try again.
V3	An unexpected timeout was triggered. Please check all the cablevision connections and effort again.
V4	Incomplete vff file. Nonce missing. Please brand sure y'all selected a valid update file and try again.
V5	Incomplete vff file. EEPROM lines missing. Please make sure you lot selected a valid update file and endeavor once again.
V6	The vff file contains more EEPROM data than supported. Please make sure you selected a valid update file and try again.
V7	The calibration map in the file exceeds the device calibration map. Delight make certain y'all selected a valid update file and try over again.
V8	Device calibration data size bigger than expected. Please make sure yous selected a valid update file and endeavour once again.
V9	Bootloader did not answer to bootloader setup. Please check all the cable connections and try over again.
V10	Bootloader response to version request failed.
V11	Incompatible bootblock. Function version invalid.
V12	Incompatible bootblock. Version invalid.
V13	Bootloader did not start after bootblock update.
V14	Incompatible bootblock blazon.
V15	No or unexpected response to target id query.
V16	No or unexpected response to EEPROM read action.
V17	No or unexpected response to calibration map query.
V18	The supplied firmware contains new unsupported calibration values. The updater does not know how to handle them.
V19	No response received to EEPROM write control. Please check all the cablevision connections and effort over again.
V20	Invalid response received to EEPROM write command. Delight bank check all the cablevision connections and attempt again.
V20	Invalid response received to EEPROM write command. Please check all the cable connections and try again.
V21	No response received to code write command. Delight check all the cablevision connections and effort once more.
V23	The MK2/MK3 did not respond. Please check all the cable connections and endeavor again.
V24	The connected product does not match the specified model in the file. Please make certain y'all selected a valid update file and attempt again.
V25	The hardware revision specific EEPROM defaults data is corrupt. Please make sure you lot selected a valid update file and try again.
V26	Updates tin can non be performed with a VE.Double-decker BMS connected.
V27	Updates can not be performed with a DMC connected.
V40	Failed to start Update. Could non allocate memory. Malloc mistake.
V50	Failed to offset Update. File open fault. Delight bank check the file location and access permissions. Brand sure you selected a valid update file and try over again.
V51	Failed to start Update. File write error. Delight cheque file location and access permissions. Make sure y'all selected a valid update file and endeavor again.
V52	Failed to kickoff Update. File read error. Delight bank check file location and access permissions. Brand certain you selected a valid update file and try again.
V53	Failed to showtime Update. File checksum fault. File corrupted or not a valid VFF file. Please make sure you selected a valid update file and try again.
V54	Failed to offset Update. File has an incompatible version number. Delight brand sure you selected a valid update file and endeavour once more.
V55	Failed to kickoff Update. File section not found. File corrupted or not a valid VFF file. Please make sure yous selected a valid update file and effort once again.
V56	Failed to start Update. Format error. File corrupted or not a valid VFF file. Delight brand sure y'all selected a valid update file and try again.

All other products (XUP update files)

Error	Description
X3	Invalid updater state. Please endeavor over again.
X4	Firmware not for Product (Id). Please make sure you selected a valid update file and try again.
X5	Updater (version) besides erstwhile.
X6	Advice Error. No Callback handler connected. Please cheque the connexion and endeavour again.
X7	Communication Error. Vreg ack-ed with an unexpected fault. Please check the connexion and try again.
X8	Update (xup) file format not supported. Please brand sure y'all selected a valid update file and effort over again.
X9	File Error. No Instance Blob could be institute in the update file. Please make certain you selected a valid update file and try again.
X10	File Fault. Invalid case Blob aspect. Please brand certain yous selected a valid update file and try again.
X11	File Error. Instance Blob defined more than than once. Delight brand sure you selected a valid update file and try once more.
X12	File Error. No Firmware Version for instance establish in the update file. Please make sure you lot selected a valid update file and try over again.
X13	Advice Fault. Unexpected Vreg Ack received. Please bank check the connectedness and attempt once more.
X14	Communication Mistake. The instance could not be reached. Please cheque the connection and endeavor over again.
X15	Fail on Minimum Firmware Version check. Please make sure y'all selected a valid update file and try again.
X16	Failed to Begin Update. Please check the connectedness and effort again.
X17	File Error. No/invalid Firmware information found for instance in the update file. Please make sure you selected a valid update file and endeavour again.
X18	Update Mistake. Invalid Ack on non-last Update Information. Delight check the connection and effort over again
X19	Update Mistake. Invalid sequence# in Update Information Ack. Please cheque the connection and try again.
X20	Update Fault. Invalid instance# in Update Information Ack. Please bank check the connection and endeavor again.
X21	Update Mistake. Invalid Ack on last Update Data. Please check the connection and endeavour again.
X22	Verification Error. Invalid Firmware Version Ack. Please check the connectedness and effort once more.
X23	Verification Fault. Invalid UDF Version Ack. Please cheque the connection and try again.
X24	Verification Mistake. Invalid case field in Minimum Firmware Version Ack. Please check the connection and try again.
X25	Verification Error. Invalid instance field in Firmware Version Ack. Delight check the connection and endeavor again.
X26	Verification Error. Invalid instance field in UDF Version Ack. Please check the connexion and try over again.
X27	Failed to verify Minimum Firmware Version. Please check the connection and try once again.
X28	Failed to verify Firmware Version. Please cheque the connection and effort again.
X29	Failed to verify UDF Version. Please check the connectedness and try again.
X30	Failed on Minimum Firmware Version verification. Please cheque the connection and attempt once again.
X31	Failed on Firmware Version verification. Please bank check the connectedness and endeavour over again.
X32	Still in Bootloader Style after the update. Please endeavor again.
X33	File Error. No Product Id found in the update file. Please make certain you selected a valid update file and try over again.
X34	File Fault. No VE.Direct baudrates plant in the update file. Please make sure you selected a valid update file and try once again.
X35	File Error. No Xup Format Version found in the update file. Delight make certain you selected a valid update file and try again.
X36	File Fault. No Minimum Updater Version found in the update file. Please make sure you selected a valid update file and try again.
X37	File Error. No Firmware (product) Version plant in the update file. Please make sure y'all selected a valid update file and try again.
X38	File Error. The update file does not lucifer XML standard. Delight make sure you selected a valid update file and try again.
X39	Advice Error. Vreg Ack timeout. Please cheque the connectedness and try over again.
X40	Communication Mistake. No product establish. Please check the connectedness and attempt once again.
X41	Advice Error. Comm port error. Please check the connection and attempt again.
X42	Update Error. Failed to set baudrate. Please bank check the connection and effort again.
X43	Update Fault. Update in progress on some other interface.
X44	Update Mistake. Invalid case# in Ack. Delight cheque the connection and try again.
X45	Update Error. Vreg Ack error: Invalid instance. Delight check the connexion and try again.
X46	Update Error. Vreg Ack error. Delight check the connexion and try once more.

schwartzprobjecre.blogspot.com

Source: https://www.victronenergy.com/media/pg/VictronConnect_Manual/en/firmware-updates.html

Share this post