victronconnect:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| victronconnect:start [2019-09-17 08:23] – [9.3 Troubleshooting firmware updates] evandromr | victronconnect:start [2019-09-21 12:15] – [4.3 Android devices] guy_stewart | ||
|---|---|---|---|
| Line 127: | Line 127: | ||
| ==== 4.3 Android devices === | ==== 4.3 Android devices === | ||
| - | The minimum required Android version to run VictronConnect is 4.1. | + | The minimum required Android version to run VictronConnect is 5.0. |
| - | The minimum required Android version to connect to a Victron product via Bluetooth is 4.3. | + | Required hardware is ARMv7 and later, as well as x86 or ARM64bit. |
| - | + | ||
| - | Required hardware is ARMv7 and later, as well as x86. | + | |
| - | + | ||
| - | === Android 4.1 and 4.2 === | + | |
| - | + | ||
| - | You may find that USB On-The-Go (USB OTG) does work on devices with Android 4.1 or 4.2. | + | |
| - | + | ||
| - | Even though some devices have Bluetooth 4.0 aka Bluetooth Smart hardware, Android versions earlier than 4.3 are not implemented such that they can be used by VictronConnect. If you are using a device running on version before 4.3, VictronConnect will not be able to see, nor connect to Victron Bluetooth Smart products. | + | |
| - | + | ||
| - | === Android 4.3 and 4.4 === | + | |
| - | + | ||
| - | No known issues. | + | |
| === Android 5 === | === Android 5 === | ||
| Line 189: | Line 177: | ||
| *Assumes the device runs the latest firmware released by the manufacturer. | *Assumes the device runs the latest firmware released by the manufacturer. | ||
| ==== 4.4 Apple iOS iPhones and iPads === | ==== 4.4 Apple iOS iPhones and iPads === | ||
| - | VictronConnect works on the following iPhones and iPads, which have Bluetooth 4.0 (BT LE).\\ (iOS 8 or later required): | + | VictronConnect works on the following iPhones and iPads running |
| - | * iPhone | + | * iPhone |
| - | * iPad, 3rd generation and later | + | * iPad mini 2 and later |
| + | * iPad (5th generation) and later | ||
| + | * iPod touch (6th generation) and later | ||
| Unfortunately Apple iPhone/iPad doesn' | Unfortunately Apple iPhone/iPad doesn' | ||
| Line 481: | Line 471: | ||
| ==== 9.4 Error codes ==== | ==== 9.4 Error codes ==== | ||
| - | In spite of our painstaking efforts, sometimes errors occur. In the following list you can check possible errors and descriptions. | + | |
| + | In spite of our painstaking efforts, sometimes errors occur. | ||
| + | |||
| + | In most cases, errors are caused by communication problems. Always make sure to check all cable connections and, if you are using Bluetooth, stay as close to the product as possible and check that the Bluetooth function is enabled on your phone/ | ||
| + | Sometimes you may need to [[# | ||
| + | |||
| + | In the following list, you can check possible errors and descriptions. | ||
| + | |||
| + | Check [[# | ||
| **VE.Direct products** | **VE.Direct products** | ||
| ^Error | ^Error | ||
| - | | 3 | No VE.Direct product(s) found. | | + | | D3 | No VE.Direct product(s) found. | |
| - | | 4 | Unknown error occurred. Try again and check the product settings once updated. | | + | | D4 | Unknown error occurred. Try again and check the product settings once updated. | |
| - | | 10 | Error closing com port. | | + | | D10 | Error closing com port. | |
| - | | 20 | Could not start updating, no updatable product found. | | + | | D20 | Could not start updating, no updatable product found. | |
| - | | 26 | Updating failed, communication lost. Product | + | | D26 | Updating failed, communication lost. The product |
| - | | 29 | Could not start updating, the firmware file is corrupt. | | + | | D29 | Could not start updating, the firmware file is corrupt. | |
| - | | 31 | Updating failed, product is unusable. Try again and check the product settings once updated. | | + | | D31 | Updating failed, |
| - | | 32 | Could not start updating, entering boot mode failed. | | + | | D32 | Could not start updating, entering boot mode failed. | |
| - | | 33 | Could not start updating, the firmware file is not found. | | + | | D33 | Could not start updating, the firmware file is not found. | |
| - | | 90 | Could not start updating, firmware is not for this product. | | + | | D90 | Could not start updating, |
| - | | 91 | Could not start updating, unknown product found. | | + | | D91 | Could not start updating, |
| - | | 92 | Updating failed, erasing firmware failed. | + | | D92 | Updating failed, erasing firmware failed. |
| - | | 93 | Error starting firmware after updating. Power cycle (off/on) your product and if that does not help\\ try updating again, and check the product settings once updated. | | + | | D93 | Error starting firmware after updating. Power cycle (off/on) your product and if that does not help\\ try updating again, and check the product settings once updated. | |
| - | | 94 | Could not start updating, error reading | + | | D94 | Product updated successfully, but an error occurred |
| - | | 95 | Product updated successfully, | + | | D95 | Product updated successfully, |
| - | | 96 | Updating failed due to version | + | | D96 | Updating failed due to version |
| - | | 97 | Dup executable too old. | | + | | D97 | Dup executable too old. | |
| - | | 98 | Firmware file is not a valid dup file. | | + | | D98 | Firmware file is not a valid dup file. | |
| - | | 99 | Product updated successfully, | + | | D99 | Product updated successfully, |
| - | | 100 | Cannot migrate settings because the application is not active. Manual action required. | | + | | D100 | Cannot migrate settings because the application is not active. Manual action required. | |
| ** Blue Smart Charger, SmartLithium, | ** Blue Smart Charger, SmartLithium, | ||
| ^Error ^Description^ | ^Error ^Description^ | ||
| - | | 1 | Error reading file. | | + | | B1 | Error reading file. | |
| - | | 2 | Victron BLE service not found. Please remove the product from the list of paired devices and retry. | | + | | B2 | Victron BLE service not found. Please remove the product from the list of paired devices and retry. | |
| - | | 3 | Dfu BLE service not found. Please remove the product from the list of paired devices and retry. | | + | | B3 | Dfu BLE service not found. Please remove the product from the list of paired devices and retry. | |
| - | | 4 | The product disconnected unexpectedly. Perhaps the bond information is no longer valid? Please remove\\ | + | | B4 | The product disconnected unexpectedly. Perhaps the bond information is no longer valid? Please remove\\ |
| - | | 5 | A write to the device failed. | | + | | B5 | A write to the device failed. | |
| - | | 6 | The product did not activate its bootloader - although it should have. | | + | | B6 | The product did not activate its bootloader - although it should have. | |
| - | | 7 | The product did not disconnect - although it should. | | + | | B7 | The product did not disconnect - although it should. | |
| - | | 8 | Timeout waiting for access to the Victron BLE service. | | + | | B8 | Timeout waiting for access to the Victron BLE service. | |
| - | | 9 | Timeout waiting for access to the Dfu BLE service. | | + | | B9 | Timeout waiting for access to the Dfu BLE service. | |
| - | | 10 | Timeout waiting for a response. | | + | | B10 | Timeout waiting for a response. | |
| - | | 11 | Timeout while writing to product. Perhaps a pairing | + | | B11 | Timeout while writing to the product. Perhaps a pairing |
| - | | 96 | An internal error occurred (Opcode not supported). Please send a service report to Victron Energy. | | + | | B12 | Device was no longer found. Perhaps out of range? Please retry. | |
| - | | 97 | The requested encryption is not supported by the product. Please send a service report to Victron Energy. | | + | | B96 | An internal error occurred (Opcode not supported). Please send a service report to Victron Energy. | |
| - | | 98 | An internal error occured | + | | B97 | The requested encryption is not supported by the product. Please send a service report to Victron Energy. | |
| - | | 99 | The product could not store the firmware in its memory. Please retry, and if the problem persists, please contact Victron Energy. | | + | | B98 | An internal error occurred |
| - | | 100 | An internal error occurred (CRC error). Please send a service report to Victron Energy. | | + | | B99 | The product could not store the firmware in its memory. Please retry, and if the problem persists, please contact Victron Energy. | |
| - | | 101 | An internal error occurred (Data length error). Please send a service report to Victron Energy. | | + | | B100 | An internal error occurred (CRC error). Please send a service report to Victron Energy. | |
| - | | 102 | An internal error occurred (Not allowed). Please send a service report to Victron Energy. | | + | | B101 | An internal error occurred (Data length error). Please send a service report to Victron Energy. | |
| + | | B102 | An internal error occurred (Not allowed). Please send a service report to Victron Energy. | | ||
| + | ** VE.Bus Products ** | ||
| + | |||
| + | ^Error ^Description^ | ||
| + | |V2 | No product detected. Please check all the cable connections and try again.| | ||
| + | |V3 | An unexpected timeout was triggered. Please check all the cable connections and try again.| | ||
| + | |V4 | Incomplete vff file. Nonce missing. Please make sure you selected a valid update file and try again.| | ||
| + | |V5 | Incomplete vff file. EEPROM lines missing. Please make sure you selected a valid update file and try 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. Please make sure you selected a valid update file and try again.| | ||
| + | |V8 | Device calibration data size bigger than expected. Please make sure you selected a valid update file and try again.| | ||
| + | |V9 | Bootloader did not respond to bootloader setup. Please check all the cable connections and try 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 type.| | ||
| + | |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 command. Please check all the cable connections and try 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. Please check all the cable connections and try again.| | ||
| + | |V22 | Invalid response received to code write command.| | ||
| + | |V23 | The MK2/MK3 did not respond. Please check all the cable connections and try again.| | ||
| + | |V24 | The connected product does not match the specified model in the file. \\ Please make sure you selected a valid update file and try again.| | ||
| + | |V25 | The hardware revision specific eeprom defaults data is corrupt. \\ Please make sure you selected a valid update file and try again.| | ||
| + | |V26 | Updates can not be performed with a VEBUS BMS connected.| | ||
| + | |V27 | Updates can not be performed with a DMC connected.| | ||
| + | |V40 | Failed to start Update. could not allocate memory. Malloc error.| | ||
| + | |V50 | Failed to start Update. File open error. Please check the file location and access permissions.\\ Make sure you selected a valid update file and try again.| | ||
| + | |V51 | Failed to start Update. File write error. Please check file location and access permissions.\\ Make sure you selected a valid update file and try again.| | ||
| + | |V52 | Failed to start Update. File read error. Please check file location and access permissions.\\ Make sure you selected a valid update file and try again.| | ||
| + | |V53 | Failed to start Update. File checksum error. File corrupted or not a valid VFF file.\\ Please make sure you selected a valid update file and try again.| | ||
| + | |V54 | Failed to start Update. File has an incompatible version number.\\ Please make sure you selected a valid update file and try again.| | ||
| + | |V55 | Failed to start Update. File section not found. File corrupted or not a valid VFF file.\\ Please make sure you selected a valid update file and try again.| | ||
| + | |V56 | Failed to start Update. Format error. File corrupted or not a valid VFF file.\\ Please make sure you selected a valid update file and try again.| | ||
| + | |||
| + | ** All other products (XUP update files)** | ||
| + | ^Error ^Description^ | ||
| + | |X3 |Invalid updater state. Please try again.| | ||
| + | |X4 |Firmware not for Product (Id). Please make sure you 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 error. | ||
| + | |X8 |Update (xup) file format not supported. Please make sure you 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 selected a valid update file and try again.| | ||
| + | |X10 |File Error. Invalid instance Blob attribute. Please make sure you selected a valid update file and try again.| | ||
| + | |X11 |File Error. Instance Blob defined more than once. Please make sure you selected a valid update file and try again.| | ||
| + | |X12 |File Error. No Firmware Version for instance found in the update file. Please make sure you 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 |Fail on Minimum Firmware Version check. Please make sure you selected a valid update file and try again.| | ||
| + | |X16 |Failed to Begin Update. Please check the connection and try again.| | ||
| + | |X17 |File Error. No/invalid Firmware data found for instance in the update file. Please make sure you 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 Error. Invalid Firmware Version Ack. Please check the connection and try again.| | ||
| + | |X23 |Verification Error. Invalid UDF Version Ack. Please check the connection and try again.| | ||
| + | |X24 |Verification Error. Invalid instance field in Minimum Firmware Version Ack. Please check the connection and try again.| | ||
| + | |X25 |Verification Error. Invalid instance field in Firmware Version Ack. Please check the connection and try again.| | ||
| + | |X26 |Verification Error. Invalid instance field in UDF Version Ack.\\ Please check the connection and try again.| | ||
| + | |X27 |Failed to verify Minimum Firmware Version.\\ Please check the connection and try again.| | ||
| + | |X28 |Failed to verify Firmware Version. Please check the connection and try again.| | ||
| + | |X29 |Failed to verify UDF Version. Please check the connection and try again.| | ||
| + | |X30 |Failed on Minimum Firmware Version verification. Please check the connection and try again.| | ||
| + | |X31 |Failed on Firmware Version verification. Please check the connection and try again.| | ||
| + | |X32 |Still in Bootloader Mode after the update. Please try again.| | ||
| + | |X33 |File Error. No Product Id found in the update file. Please make sure you selected a valid update file and try again.| | ||
| + | |X34 |File Error. No VE.Direct baudrates found in the update file. Please make sure you selected a valid update file and try again.| | ||
| + | |X35 |File Error. No Xup Format Version found in the update file. Please make sure you selected a valid update file and try again.| | ||
| + | |X36 |File Error. 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 found in the update file. Please make sure you selected a valid update file and try again.| | ||
| + | |X38 |File Error. The update file does not match XML standard. Please make sure you 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. Failed to set baudrate. 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 error. Please check the connection and try again.| | ||
| ===== 10. Troubleshooting ===== | ===== 10. Troubleshooting ===== | ||
victronconnect/start.txt · Last modified: 2021-01-11 13:04 by boekel