User Tools

Site Tools


victronconnect:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Previous revision
victronconnect:start [2019-06-25 16:08]
victronconnect:start [2019-10-03 00:22] (current)
guy_stewart [4.3 Android devices]
Line 1: Line 1:
 ====== VictronConnect manual ====== ====== VictronConnect manual ======
-Welcome to the VictronConnect Manual. You can use VictronConnect to configure, monitor and diagnose all our products which have built-in Bluetooth Smart or are equipped with a VE.Direct Port. 
  
-  *For a list of products compatible with VictronConnect ​please see section:  ​[[#​10._Compatible_Victron_products|10. Compatible Victron ​products]]. +===== 1. Introduction ===== 
-  * Click [[https://​www.victronenergy.com/​live/​victronconnect:​mppt-solarchargers|here for the specific features available for MPPTs using VictronConnect]]. +Welcome to the VictronConnect ​Manual. Use the VictronConnect App to configure, monitor, update and diagnose the [[#​10._Compatible_Victron_products|VictronConnect compatible ​products]].
  
-VictronConnect ​can be used on devices running on Android, iOS, Windows, and macOS X.+VictronConnect ​is available for Android, iOS, Windows, and macOS X.
  
-{{:​victronconnect:​vcfamily_v4.png?​direct&​700|}} +It can connect to Victron products via Bluetooth, USB and WiFi/​LAN/​Internet. How to connect depends on the product, some product ranges have bluetooth, some do not. Some product ranges have WiFi, others do not. For details, see chapter 11. 
-===== 1. Download and installation =====+ 
 + 
 +=== Documentation === 
 + 
 +See the table of contents for all information covered in this document. 
 + 
 +Other relevant documents are: 
 + 
 +  * [[https://​www.victronenergy.com/​live/​victronconnect:​mppt-solarchargers|VictronConnect - MPPT Solar Chargers]]. 
 +  * [[https://​docs.victronenergy.com/​victronconnect-vebus.html|VictronConnect - VE.Bus Configuration guide]] - for MultiPlusses,​ Quattros, EasySolars and other inverter/​chargers. 
 + 
 +===== 2. Download and installation =====
  
 VictronConnect is available to users of Windows PCs, macOS X, iOS and Android phones, as well as tablets. ​ [[https://​www.victronenergy.com/​support-and-downloads/​software#​victronconnect-app|Use this link to download the app suitable for your device]]. VictronConnect is available to users of Windows PCs, macOS X, iOS and Android phones, as well as tablets. ​ [[https://​www.victronenergy.com/​support-and-downloads/​software#​victronconnect-app|Use this link to download the app suitable for your device]].
  
-===== 2. Connecting =====+===== 3. Connecting ===== 
 There are three ways to connect to a Victron product: There are three ways to connect to a Victron product:
 ^ Method ​                                    ^ iOS ^ Android ^ Windows PC ^ macOS X ^ ^ Method ​                                    ^ iOS ^ Android ^ Windows PC ^ macOS X ^
Line 23: Line 34:
  
 Use the [[#​Compatible_Victron_products|Compatible Victron products]] chapter to verify that your product is compatible. Use the [[#​Compatible_Victron_products|Compatible Victron products]] chapter to verify that your product is compatible.
-==== 2.1 Bluetooth Smart - Pairing and Connecting ====+ 
 +==== 3.1 Bluetooth Smart - Pairing and Connecting ====
  
   - Enable the Bluetooth setting on your device, but do not pair outside of VictronConnect.   - Enable the Bluetooth setting on your device, but do not pair outside of VictronConnect.
Line 36: Line 48:
 Note: Always connect from within VictronConnect. Do not connect from the device'​s system menu because VictronConnect will not find your Victron product. Note: Always connect from within VictronConnect. Do not connect from the device'​s system menu because VictronConnect will not find your Victron product.
  
-==== 2.2 Changing the Bluetooth Smart PIN code ====+==== 3.2 Bluetooth Smart - Changing the PIN code ====
 **To prevent unauthorised connections to your device we recommend you change the PIN code. Avoid using obvious PIN codes such as 111111 or 123456.** **To prevent unauthorised connections to your device we recommend you change the PIN code. Avoid using obvious PIN codes such as 111111 or 123456.**
  
-To change the PIN code: First complete your connection; then go to the **Product info** page. To access that page, click the button on the upper right. For some products it will be the settings icon: {{:​ve.direct:​wrench.png?​nolink|}}. After opening that menu press {{:​victronconnect:​vc4_ic_more.png?​nolink|}},​ and click **Product info**.+To change the PIN code, first complete your connection. Then go to the **Product info** page. To access that page, click the button on the upper right. For some products it will be the settings icon: {{:​ve.direct:​wrench.png?​nolink|}}. After opening that menu press {{:​victronconnect:​vc4_ic_more.png?​nolink|}},​ and click **Product info**.
  
 For other products you'll find the {{:​victronconnect:​vc4_ic_info.png?​nolink|}} button on the upper right, which takes you straight to the Product info page. For other products you'll find the {{:​victronconnect:​vc4_ic_info.png?​nolink|}} button on the upper right, which takes you straight to the Product info page.
-==== 2.3 Resetting the Bluetooth Smart pin code ==== 
  
-If the dongle ​PIN code is lost, it can be reset to 000000. The way you reset depends on which product you are using:+On this page, select the change pin code button. 
 + 
 +Note that after changing the pin code, all other phones, tablets, and laptops connected to the Victron product need to have their pairing information refreshed; and first, the old pairing information needs to be removed. See [[start#​removing_the_product_from_the_list_of_paired_devices | section 2.4]] to learn how to remove the pairing information. (TODO - improve this text) 
 + 
 +==== 3.3 Bluetooth Smart - Resetting the PIN code ==== 
 + 
 +If the PIN code is lost, it can be reset to 000000. The way you reset depends on which product you are using:
  
 === VE.Direct Bluetooth Smart dongle === === VE.Direct Bluetooth Smart dongle ===
Line 65: Line 82:
 On a desktop (Windows, Mac), 'right click' the product description instead of pressing and holding. On a desktop (Windows, Mac), 'right click' the product description instead of pressing and holding.
  
-=== Blue Smart Solar Charger ===+=== Smart Solar Charger ===
 On the device list: Press and hold the product description for which you would like to reset the PIN code. A menu will pop up offering a 'Reset PIN code' option. Click that, and enter the PUK code. The PUK code can be found on the product label, on the back of the product. On the device list: Press and hold the product description for which you would like to reset the PIN code. A menu will pop up offering a 'Reset PIN code' option. Click that, and enter the PUK code. The PUK code can be found on the product label, on the back of the product.
  
Line 79: Line 96:
  
 On a desktop (Windows, Mac), 'right click' the product description instead of pressing and holding. On a desktop (Windows, Mac), 'right click' the product description instead of pressing and holding.
-===== 3. Compatibility notes on operating systemsphones ​and tablets ​===== + 
-==== 3.1 Windows PC ===+==== 3.4 Bluetooth Smart - Removing from the list of paired devices ==== 
 + 
 +You may want or need to remove a product from the list of Bluetooth paired devices ​on your phone/​tablet/​laptop. For exampleif the PIN code of your product has been changed on a different device. 
 + 
 +To remove the pairing information you will need to go to your device'​s Bluetooth settings. Watch the videos below to learn how to remove the pairing information from iOS and Android devices: 
 + 
 +=== Remove Bluetooth pairing on iOS devices: ​=== 
 +(click to play, double-click to enter fullscreen mode) 
 + 
 +{{victronconnect:​video_unpair_ios.mp4?​175}} 
 + 
 +=== Remove Bluetooth pairing on Android devices: ​=== 
 +(click to play, double-click to enter fullscreen mode) 
 + 
 +{{victronconnect:​ video_unpair_android_cropped.mp4?​175}} 
 + 
 +===== 4. Phone, tablet and laptop compatibility ===== 
 +==== 4.1 Windows PC ===
 Windows 7, Windows 8, Windows 10 Windows 7, Windows 8, Windows 10
-  *(Downloads for VictronConnect for users of Windows XP / Vista are still available in archive - but unsupported.) ​+  *(Downloads for VictronConnect for users of Windows XP / Vista are still available in [[https://​www.victronenergy.com/​support-and-downloads/​software|archive]] - but unsupported.) ​
  
 On Windows, VictronConnect cannot use Bluetooth Smart to connect to a product. Therefore the only way to connect a Windows computer to a product is to use the VE.Direct to USB interface. On Windows, VictronConnect cannot use Bluetooth Smart to connect to a product. Therefore the only way to connect a Windows computer to a product is to use the VE.Direct to USB interface.
-==== 3.2 macOS X ===+==== 4.2 macOS X ===
  
 The earliest supported macOS version is: 10.10 (OS X Yosemite). The earliest supported macOS version is: 10.10 (OS X Yosemite).
Line 91: Line 125:
  
 To connect to a Victron device over Bluetooth, rather then via USB, the Mac needs to have Bluetooth 4.0 aka Bluetooth Smart. To connect to a Victron device over Bluetooth, rather then via USB, the Mac needs to have Bluetooth 4.0 aka Bluetooth Smart.
-==== 3.3 Android devices ===+==== 4.3 Android devices ===
  
-The minimum required ​Android version to run VictronConnect ​is 4.1.+Android ​5.0 is the minimum ​version ​required ​to run VictronConnect.
  
-The minimum required Android ​version ​to connect to a Victron product via Bluetooth is 4.3.+(An older version ​of VictronConnect that works for some users of Android ​4.3 (and greater) is still available in [[https://​www.victronenergy.com/​support-and-downloads/​software|archive]] - but now 4.x is unsupported.
  
-Required hardware is ARMv7 and later, as well as x86.+Required hardware is ARMv7 and later, as well as x86 or ARM64bit.
  
-=== 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 123: Line 150:
 No known issues, when Access to Locations services are enabled. ​ No known issues, when Access to Locations services are enabled. ​
  
-=== Access to location services required? ===+=== Why is Access to location services required? ===
  
 Android 5 and later requires access permission for VictronConnect to the (coarse) location services. Otherwise it can not scan for the Bluetooth devices. Android 5 and later requires access permission for VictronConnect to the (coarse) location services. Otherwise it can not scan for the Bluetooth devices.
Line 154: Line 181:
  
 *Assumes the device runs the latest firmware released by the manufacturer. *Assumes the device runs the latest firmware released by the manufacturer.
-==== 3.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 or later required)+VictronConnect works on the following iPhones and iPads running ​iOS 11 or later: 
-  * iPhone ​4S and later (due to Bluetooth Low Energy support+  * iPhone ​5S and later
-  * iPad, 3rd generation and later+  * iPad mini 2 and later 
 +  * iPad (5th generationand later 
 +  * iPod touch (6th generationand later
  
 Unfortunately Apple iPhone/iPad doesn'​t support USB OTG. Unfortunately Apple iPhone/iPad doesn'​t support USB OTG.
  
-===== 4. Application overview =====+===== 5. Application overview =====
  
-==== 4.1 Screenshots (click to enlarge) ==== +==== 5.1 Screenshots (click to enlarge) ==== 
  
 **Device list**\\ **Device list**\\
Line 247: Line 276:
 {{:​victronconnect:​vc4_mac_bluesolar_live.png?​direct&​600|}} {{:​victronconnect:​vc4_mac_bluesolar_live.png?​direct&​600|}}
 {{:​victronconnect:​vc4_mac_bluesolar_live_small.png?​direct&​200|}} {{:​victronconnect:​vc4_mac_bluesolar_live_small.png?​direct&​200|}}
-==== 4.2 Videos ====+==== 5.2 Videos ====
  
 **Blue Smart IP65 Charger ** **Blue Smart IP65 Charger **
Line 264: Line 293:
 {{youtube>​vZJA4eTd6vw?​medium}} {{youtube>​vZJA4eTd6vw?​medium}}
  
-==== 4.3 Renaming your devices ====+==== 5.3 Renaming your devices ====
  
 It is possible to change the name of your devices to make identification easier. This is especially useful if you have multiple devices, such as 3 MPPTs and 2 BMVs. It is not yet possible to change the name of Smart Lithium batteries. This will be available in the future. It is possible to change the name of your devices to make identification easier. This is especially useful if you have multiple devices, such as 3 MPPTs and 2 BMVs. It is not yet possible to change the name of Smart Lithium batteries. This will be available in the future.
Line 277: Line 306:
  
  
-==== 4.4 Importing and converting a GX Product Family database File ====+==== 5.4 Importing and converting a GX Product Family database File ====
  
 VictronConnect for Mac OSX and Windows allows you to import and convert the database log file (that is created by the VenusOS on the GX Product Family of devices) to a Microsoft Excel XLSX file. This can be useful if the site is remote and without an internet connection to upload the file to the [[https://​vrm.victronenergy.com|VRM Portal]]. VictronConnect for Mac OSX and Windows allows you to import and convert the database log file (that is created by the VenusOS on the GX Product Family of devices) to a Microsoft Excel XLSX file. This can be useful if the site is remote and without an internet connection to upload the file to the [[https://​vrm.victronenergy.com|VRM Portal]].
Line 290: Line 319:
  
  
-===== 5. Product alarms & errors =====+===== 6. Product alarms & errors =====
 Behind the scenes VictronConnect has a full monitoring system which checks for alarms and errors on the connected product. As soon as an alarm or error is reported by the product, the alarm/error and its description is shown on the live data page.\\ ​ Behind the scenes VictronConnect has a full monitoring system which checks for alarms and errors on the connected product. As soon as an alarm or error is reported by the product, the alarm/error and its description is shown on the live data page.\\ ​
 (Note that alarms and errors are only shown when the app is active.) (Note that alarms and errors are only shown when the app is active.)
Line 297: Line 326:
 {{:​victronconnect:​vc4_iphone_bluesolar_alarm_expanded.png?​direct&​150|}} {{:​victronconnect:​vc4_iphone_bluesolar_alarm_expanded.png?​direct&​150|}}
  
 +===== 7. Settings files =====
  
- 
-===== 6. Settings files ===== 
 This feature allows you to save product settings to a file so that they can be loaded onto the Victron product you are connected to ...or another product, at a later time. This feature allows you to save product settings to a file so that they can be loaded onto the Victron product you are connected to ...or another product, at a later time.
  
Line 341: Line 369:
 There is a constraint for opening files in this mode: The settings file must have been created using the same VictronConnect version that the one running on your phone/​computer. This means that if VictronConnect v5.0 is installed in your phone only settings files created with VictronConnect v5.0 can be opened. There is a constraint for opening files in this mode: The settings file must have been created using the same VictronConnect version that the one running on your phone/​computer. This means that if VictronConnect v5.0 is installed in your phone only settings files created with VictronConnect v5.0 can be opened.
  
-This constraint only applies when opening files from the settings file manager for inspection. Loading files from a product settings page to restore it is always possible as long as VictronConnect version is equal or greater than the one used to create the settings file.   +This constraint only applies when opening files from the settings file manager for inspection. Loading files from a product settings page to restore it is always possible as long as VictronConnect version is equal or greater ​ than the one used to create the settings file. 
-===== 7. Demo feature =====+ 
 +===== 8. Demo feature =====
  
 VictronConnect contains a library with demonstration settings for all the supported products. ​ VictronConnect contains a library with demonstration settings for all the supported products. ​
Line 363: Line 392:
  
 {{:​victronconnect:​vc4_settings_file_manager_options.png?​direct&​150|}} {{:​victronconnect:​vc4_settings_file_manager_options.png?​direct&​150|}}
-===== 8. Firmware updates===== +===== 9. Firmware updates===== 
-==== 8.1 Introduction & automatic updates ====+==== 9.1 Introduction & automatic updates ====
  
 __How can I see what firmware version is available?​__ __How can I see what firmware version is available?​__
Line 388: Line 417:
  
  
-==== 8.2 Updating to a self-supplied firmware file ====+==== 9.2 Updating to a self-supplied firmware file ====
  
 The previous chapter explained how VictronConnect will automatically update to the latest recommended firmware version. Besides that, it is also possible to update a product with a file that you supply your-self. The previous chapter explained how VictronConnect will automatically update to the latest recommended firmware version. Besides that, it is also possible to update a product with a file that you supply your-self.
Line 411: Line 440:
 Firstly, you need to add the desired firmware file to the VictronConnect firmware library. Firmware files can be added to the library from: an email attachment; web browser; Dropbox; file browser ...and any kind of app that can handle files. Firstly, you need to add the desired firmware file to the VictronConnect firmware library. Firmware files can be added to the library from: an email attachment; web browser; Dropbox; file browser ...and any kind of app that can handle files.
  
-**iOS**: The current version of Google Chrome for iOS fails to download "​.dup"​ files from the Victron Professional website - so we recommended using Safari instead.+**Note for iOS**: The current version of Google Chrome for iOS fails to download "​.dup"​ files from the Victron Professional website - so we recommended using Safari instead.
  
-Go to the app that contains the firmware file, tap on it, and open it with VictronConnect.+**Note for Android**: VictronConnect needs to be running before opening files. 
 +Open VictronConnect and, without closing it, switch to the app containing the file, select it and choose to open it with VictronConnect. 
 + 
 + 
 + 
 +On both iOS and Android, go to the app that contains the firmware file, tap on it, and open it with VictronConnect.
  
 {{:​victronconnect:​vc_ios_firmware_download.png?​direct&​150|}} {{:​victronconnect:​vc_ios_firmware_download.png?​direct&​150|}}
Line 419: Line 453:
 {{:​victronconnect:​vc_ios_firmware_mail_attachment.png?​direct&​150|}} {{:​victronconnect:​vc_ios_firmware_mail_attachment.png?​direct&​150|}}
  
-VictronConnect will be opened and should read: "File added to the firmware library"​. If the message doesn'​t appear repeat the previous step.+VictronConnect will be opened and should read: "File added to the firmware library"​. If the message doesn'​t appearrepeat the previous step.
  
 Go to the "​Product info" page and tap on "​Update firmware"​. Go to the "​Product info" page and tap on "​Update firmware"​.
Line 437: Line 471:
 {{:​victronconnect:​vc4_ios_firmware_updated.png?​direct&​150|}} {{:​victronconnect:​vc4_ios_firmware_updated.png?​direct&​150|}}
  
-==== 8.3 Troubleshooting firmware updates ====+==== 9.3 Troubleshooting firmware updates ====
  
-A troubleshooting guide relevant to firmware updates can be found in chapter ​9.3+A troubleshooting guide relevant to firmware updates can be found in [[#​problems_during_firmware_updating|chapter ​10.3]]
  
-==== 8.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. ​But don't worry, it is always possible to recover your product.  
 + 
 +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/​tablet/​laptop. 
 +Sometimes you may need to [[#​bluetooth_smart_-_removing_from_the_list_of_paired_devices|remove the Bluetooth pairing information from your device]] in order to be able to reconnect with your product. 
 + 
 +In the following listyou can check possible errors and descriptions
 + 
 +Check [[#​problems_during_firmware_updating|chapter 10.3]] of this manual for Troubleshooting firmware updates. When asking for help, make sure to always mention the error code.
  
 **VE.Direct products** **VE.Direct products**
 ^Error ​         ^Description^ ^Error ​         ^Description^
-             | No VE.Direct product(s) found. | +D3              | No VE.Direct product(s) found. | 
-             | 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 ​might be unusable. Check connection and power supply.\\ Try again and check the product settings once updated. | +D26             | Updating failed, communication lost. The product ​might be unusable. Check connection and power supply.\\ Try again and check the product settings once updated. | 
-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, ​the product is unusable. Try again and check the product settings once updated. | 
-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, ​the firmware is not for this product. | 
-91             | Could not start updating, unknown product found. | +D91             | Could not start updating, ​an unknown product ​was found. | 
-92             | Updating failed, erasing firmware failed. ​Product ​might be unusable. Try again and check the product settings once updated. | +D92             | Updating failed, erasing firmware failed. ​The product ​might be unusable. Try again and check the product settings once updated. | 
-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 ​configuration. | +D94             | Product updated successfullybut an error occurred ​reading ​the previous settings. Check the product settings. | 
-95             | Product updated successfully,​ but an error occurred restoring the settings. Check the product settings. | +D95             | Product updated successfully,​ but an error occurred restoring the previous ​settings. Check the product settings. | 
-96             | Updating failed due to version ​mis-match. Power cycle (off/on) your product and if that does not help try\\ updating again, and check the product settings once updated. | +D96             | Updating failed due to version ​mismatch. Power cycle (off/on) your product and if that does not help try\\ updating again, and check the product settings once updated. | 
-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,​ but an error occurred restoring the settings. Check the product settings. | +D99             | Product updated successfully,​ but an error occurred restoring the settings. Check the product settings. | 
-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,​ and VE.Direct Bluetooth Smart dongle ** ** Blue Smart Charger, SmartLithium,​ and VE.Direct Bluetooth Smart dongle **
 ^Error ^Description^ ^Error ^Description^
-| Error reading file. | +B1 | Error reading file. | 
-| 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. | 
-| 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. | 
-| The product disconnected unexpectedly. Perhaps the bond information is no longer valid? Please remove\\ ​ the product from the list of paired devices and retry. | +B4 | The product disconnected unexpectedly. Perhaps the bond information is no longer valid? Please remove\\ ​ the product from the list of paired devices and retry. | 
-| A write to the device failed. | +B5 | A write to the device failed. | 
-| The product did not activate its bootloader - although it should have. | +B6 | The product did not activate its bootloader - although it should have. | 
-| The product did not disconnect - although it should. | +B7 | The product did not disconnect - although it should. | 
-| Timeout waiting for access to the Victron BLE service. | +B8 | Timeout waiting for access to the Victron BLE service. | 
-| 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 ​dialog ​is shown? Please retry. | +B11 | Timeout while writing to the product. Perhaps a pairing ​dialogue ​is shown? Please retry. | 
-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 ​(Data size exceeds limits). 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. | 
-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 ​(Data size exceeds limits). Please send a service report to Victron Energy. | 
-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. |
  
-===== 9Troubleshooting =====+** VE.Bus Products **
  
-==== 9.1 Cannot find my device ​(Bluetooth) ===+^Error ^Description^ 
 +|V2  | No product detectedPlease 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. ​ Please check the connection and try again.|
 +|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.1 Common Bluetooth problems and how to solve them ===
 +
 +== I cannot find my device listed ==
   * Make sure that you have a "​Smart"​ Victron product. It needs to have a Bluetooth symbol.   * Make sure that you have a "​Smart"​ Victron product. It needs to have a Bluetooth symbol.
   * Make sure your device is in range.   * Make sure your device is in range.
-  * Only one device can be connected to a product. Make sure that no other device: phone/​tablet/​laptop is already connected.+  ​* If a firmware update failed, the device //Custom Name// might have reverted to its original name and serial number, check if that is the case. Once the update is completed, the //Custom Name// will be back. See more tips about troubleshooting firmware updates on [[start#​problems_during_firmware_updating | section 9.3]]. 
 + 
 +== I can see but not connect to my device ==  
 +  * Make sure you are trying to connect to the right device. See [[start#​renaming_your_devices | section 4.3]] to learn how you can give your device a //Custom Name//. 
 +  * Make sure your device is in range. It can be that you are close enough to see the device but not close enough to connect to it. 
 +  ​* Only one device can be connected to a product ​at the same time. Make sure that no other device: phone/​tablet/​laptop is already connected.
   * Make sure you are attempting to connect from //within// VictronConnect - not from the system menu of your phone/​tablet/​laptop.   * Make sure you are attempting to connect from //within// VictronConnect - not from the system menu of your phone/​tablet/​laptop.
 +  * Make sure that Bluetooth is still enabled in your phone/​tablet/​laptop. If Bluetooth was disabled after scanning, you may be able to see your device listed but you won't be able to connect to it.
 +  * The Bluetooth bonding information may be outdated. This happens when the PIN code has been changed in the device, or if your Victron device has been connected to too many phones/​tablets/​Laptops. The device will only remember the last 10 phones/​tablets/​laptops connected to it. To solve this, remove the pairing completely from your phone/​tablet/​laptop system menu. Then open VictronConnect and re-pair the product and your device. Watch these instructional videos to learn how to remove the pairing on {{victronconnect:​video_unpair_android_cropped.mp4?​linkOnly | Android}} or {{victronconnect:​video_unpair_ios.mp4?​linkOnly | iOS}} devices.
 +  * If you are using an Android phone/​tablet,​ check [[start#​bluetooth_connection_issues_on_android_devices| section 9.2]] below for issues particular to Android.
 +
  
-If none of the above helps, and if your device is already paired to a product, remove the pairing completely from your phone/​tablet/​laptop system menu. Then open VictronConnect and re-pair the product and your device. +==== 10.2 Bluetooth connection issues on Android devices ====
-==== 9.2 Bluetooth connection issues on Android devices ====+
  
 === Step 1: Check that your device is supported === === Step 1: Check that your device is supported ===
Line 535: Line 671:
  
 When successfully connected using another device, VictronConnect will automatically update the firmware in the Victron bluetooth device. After the firmware has been updated you may find that you can use the Android device with which you were experiencing difficulties. When successfully connected using another device, VictronConnect will automatically update the firmware in the Victron bluetooth device. After the firmware has been updated you may find that you can use the Android device with which you were experiencing difficulties.
-==== 9.3 Problems during firmware updating ====+==== 10.3 Problems during firmware updating ====
  
 First of all, its good to know that you can always restart the firmware update procedure. The update process will be restarted each time you connect to the product. First of all, its good to know that you can always restart the firmware update procedure. The update process will be restarted each time you connect to the product.
  
-If the firmware update stops at a random percentage during each retry, just keep trying - it will succeed eventually. Keep your mobile device as close to the product as possible. If the update fails even after many attempts, try using another phone or tablet ...if possible an Apple iOS device - they usually work without any issues. After the update, you may find you can use the phone with which you were having difficulty.+Keep your mobile device as close to the product as possible. If the update fails due to Bluetooth connectivity problems, and if your device is already paired to a product, try and remove the pairing completely from your phone/​tablet/​laptop system menu. Then open VictronConnect and re-pair the product and your device. 
 +Watch these instructional videos to learn how to remove the pairing on {{ :​victronconnect:​video_unpair_android_cropped.mp4?​linkOnly | Android}} or {{ :​victronconnect:​video_unpair_ios.mp4?​linkOnly | iOs }} devices 
 + 
 +If the firmware update stops at a random percentage during each retry, just keep trying - it will succeed eventually. If the update fails even after many attempts, try using another phone or tablet ...if possible an Apple iOS device - they usually work without any issues. After the update, you may find you can use the phone with which you were having difficulty.
  
 === Update stops at 4% or earlier === === Update stops at 4% or earlier ===
Line 561: Line 700:
   * The firmware update screen will appear again. You should now be able to update the dongle to the latest firmware version.   * The firmware update screen will appear again. You should now be able to update the dongle to the latest firmware version.
  
-==== 9.4 VE.Direct USB driver problem on macOS X 10.9 (Mavericks) ====+==== 10.4 VE.Direct USB driver problem on macOS X 10.9 (Mavericks) ====
  
 The driver included in macOS X 10.9 "​Mavericks"​ doesn'​t work properly with the VE.Direct USB cable. To fix this issue we recommend updating to a later version of macOS. The driver included in macOS X 10.9 "​Mavericks"​ doesn'​t work properly with the VE.Direct USB cable. To fix this issue we recommend updating to a later version of macOS.
Line 582: Line 721:
 VictronConnect should now show the connected products. VictronConnect should now show the connected products.
  
-==== 9.5 VictronConnect on Windows doesn'​t find VE.Direct USB connected devices ====+==== 10.5 VictronConnect on Windows doesn'​t find VE.Direct USB connected devices ====
  
 VE.Direct USB cable requires a driver to be installed. ​ VE.Direct USB cable requires a driver to be installed. ​
Line 588: Line 727:
 The necessary drivers are available in the [[https://​www.victronenergy.com/​support-and-downloads/​software#​victronconnect-app|software section]]. The necessary drivers are available in the [[https://​www.victronenergy.com/​support-and-downloads/​software#​victronconnect-app|software section]].
  
-==== 9.6 VictronConnect on Android doesn'​t show files oppened from email or file manager apps ====+==== 10.6 VictronConnect on Android doesn'​t show files oppened from email or file manager apps ====
  
 VictronConnect needs to be running before oppening files. VictronConnect needs to be running before oppening files.
Line 595: Line 734:
  
  
-==== 9.7 How to create a VictronConnect Service Report ====+==== 10.7 How to create a VictronConnect Service Report ====
  
 If you are experiencing issues with VictronConnect or your Victron product, you may be asked to create a "​VictronConnect Service Report"​. ​ If you are experiencing issues with VictronConnect or your Victron product, you may be asked to create a "​VictronConnect Service Report"​. ​
Line 612: Line 751:
 {{:​victronconnect:​victronconnect_service_report.jpg?​direct&​400|}} {{:​victronconnect:​victronconnect_service_report.jpg?​direct&​400|}}
  
-===== 10. Compatible Victron products =====+===== 11. Compatible Victron products =====
  
 ==== SmartSolar MPPT Charge controllers ==== ==== SmartSolar MPPT Charge controllers ====
Line 643: Line 782:
 ==== Blue Smart IP22 Chargers ==== ==== Blue Smart IP22 Chargers ====
 ^                               ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ ^                               ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^
-| Blue Smart IP22 Charger 12/15 | No             | Yes - Built in                       | +All Blue Smart IP22 Chargers ​| No             | Yes - Built in                       |
-| Blue Smart IP22 Charger 12/20 | No             | Yes - Built in                       | +
-| Blue Smart IP22 Charger 12/30 | No             | Yes - Built in                       | +
-| Blue Smart IP22 Charger 24/8  | No             | Yes - Built in                       | +
-| Blue Smart IP22 Charger 24/12 | No             | Yes - Built in                       | +
-| Blue Smart IP22 Charger 24/16 | No             | Yes - Built in                       |+
  
 ==== Blue Smart IP65 Chargers ==== ==== Blue Smart IP65 Chargers ====
 ^                               ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ ^                               ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^
-| Blue Smart IP65 Charger 12/4  | No             | Yes - Built in                       | +All Blue Smart IP65 Chargers ​ | No             | Yes - Built in                       |
-| Blue Smart IP65 Charger 12/5  | No             | Yes - Built in                       | +
-| Blue Smart IP65 Charger 12/7  | No             | Yes - Built in                       | +
-| Blue Smart IP65 Charger 12/10 | No             | Yes - Built in                       | +
-| Blue Smart IP65 Charger 12/15 | No             | Yes - Built in                       | +
-| Blue Smart IP65 Charger 24/5  | No             | Yes - Built in                       | +
-| Blue Smart IP65 Charger 24/8  | No             | Yes - Built in                       |+
  
 ==== Blue Smart IP67 Chargers ==== ==== Blue Smart IP67 Chargers ====
 ^                               ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ ^                               ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^
-| Blue Smart IP67 Charger 12/7  | No             | Yes - Built in                       | +All Blue Smart IP67 Chargers ​ | No             | Yes - Built in                       | 
-| Blue Smart IP67 Charger ​12/13 No             | Yes Built in                       | + 
-| Blue Smart IP67 Charger 12/17 | No             | Yes - Built in                       | +==== Orion-Tr ​Smart DC-DC Charger ​Isolated ==== 
-| Blue Smart IP67 Charger ​12/25 | No             | Yes - Built in                       | +^                               ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ 
-Blue Smart IP67 Charger 24/5  | No             | Yes - Built in                       | +All Orion-Tr Smart DC-DC Isolated Chargers ​  | No             | Yes - Built in                       | 
-| Blue Smart IP67 Charger 24/8  | No             | Yes - Built in                       | + 
-| Blue Smart IP67 Charger 24/12 | No             | Yes - Built in                       |+==== Phoenix ​Smart IP43 Charger ​==== 
 +^                               ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ 
 +All Phoenix ​Smart IP43 Chargers ​ | Yes            | Yes - Built in                       | 
 + 
  
  
Line 691: Line 823:
 | MPPT 150/70 Tr and MC4 VE.Direct (*) | [[https://​www.victronenergy.com/​accessories/​ve-direct-to-usb-interface|VE.Direct to USB accessory required]] ​           | [[https://​www.victronenergy.com/​accessories/​ve-direct-bluetooth-smart-dongle|VE.Direct to Bluetooth accessory required]] ​                      | | MPPT 150/70 Tr and MC4 VE.Direct (*) | [[https://​www.victronenergy.com/​accessories/​ve-direct-to-usb-interface|VE.Direct to USB accessory required]] ​           | [[https://​www.victronenergy.com/​accessories/​ve-direct-bluetooth-smart-dongle|VE.Direct to Bluetooth accessory required]] ​                      |
 | MPPT 150/85 Tr and MC4 VE.Direct ​ (*) | [[https://​www.victronenergy.com/​accessories/​ve-direct-to-usb-interface|VE.Direct to USB accessory required]] ​           | [[https://​www.victronenergy.com/​accessories/​ve-direct-bluetooth-smart-dongle|VE.Direct to Bluetooth accessory required]] ​                      | | MPPT 150/85 Tr and MC4 VE.Direct ​ (*) | [[https://​www.victronenergy.com/​accessories/​ve-direct-to-usb-interface|VE.Direct to USB accessory required]] ​           | [[https://​www.victronenergy.com/​accessories/​ve-direct-bluetooth-smart-dongle|VE.Direct to Bluetooth accessory required]] ​                      |
 +| MPPT 150/70 CAN-bus | Not compatible ||
 +| MPPT 150/85 CAN-bus | Not compatible ||
 | MPPT 150/100 Tr and MC4 | [[https://​www.victronenergy.com/​accessories/​ve-direct-to-usb-interface|VE.Direct to USB accessory required]] ​           | [[https://​www.victronenergy.com/​accessories/​ve-direct-bluetooth-smart-dongle|VE.Direct to Bluetooth accessory required]] ​                      | | MPPT 150/100 Tr and MC4 | [[https://​www.victronenergy.com/​accessories/​ve-direct-to-usb-interface|VE.Direct to USB accessory required]] ​           | [[https://​www.victronenergy.com/​accessories/​ve-direct-bluetooth-smart-dongle|VE.Direct to Bluetooth accessory required]] ​                      |
-(*) Note that we have two different models of 150/70 and 150/85 Solar Chargers: ​ [[https://​www.victronenergy.com/​solar-charge-controllers/​mppt-150-70|the models with a VE.Can port]], and [[https://​www.victronenergy.com/​solar-charge-controllers/​bluesolar-mppt-150-35| the models with a VE.Direct port]]. Only the models with the VE.Direct port can be used with VictronConnect and corresponding dongles. 
  
  
Line 768: Line 901:
 Note that switching between on/​off/​charger-only as well as setting the input current limit is not possible when there is a DMC or VE.Bus BMS installed. Note that switching between on/​off/​charger-only as well as setting the input current limit is not possible when there is a DMC or VE.Bus BMS installed.
  
-For systems with a [[venus-os:​start|Venus-device]] installed, and running firmware version 415 or newer, switching between on/​off/​charger-only and setting the input current limit IS possible.+For systems with a [[venus-os:​start|GX device]] installed, and running firmware version 415 or newer, switching between on/​off/​charger-only and setting the input current limit IS possible.
  
  
victronconnect/start.1561471700.txt.gz · Last modified: 2019-06-25 16:08 (external edit)