victronconnect:start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
victronconnect:start [2020-07-01 15:24] – [9.2 Updating to a self-supplied firmware file] evandromr | victronconnect:start [2021-01-11 13:04] (current) – link was incorrect boekel | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== VictronConnect manual ====== | + | Moved to: https:// |
- | + | ||
- | ===== 1. Introduction ===== | + | |
- | Welcome | + | |
- | + | ||
- | VictronConnect is available for Android, iOS, Windows, and macOS X. | + | |
- | + | ||
- | It can connect to Victron products via Bluetooth, USB and WiFi/ | + | |
- | + | ||
- | + | ||
- | === Documentation === | + | |
- | + | ||
- | See the table of contents for all general VictronConnect information covered in this document. | + | |
- | + | ||
- | Other product specific relevant documents are: | + | |
- | + | ||
- | [[https:// | + | |
- | + | ||
- | [[https:// | + | |
- | + | ||
- | [[https:// | + | |
- | ===== 2. Download and installation ===== | + | |
- | + | ||
- | VictronConnect is available to users of Windows PCs, macOS X, iOS and Android phones, as well as tablets. | + | |
- | + | ||
- | Also, [[https:// | + | |
- | + | ||
- | See [[# | + | |
- | + | ||
- | ===== 3. Connecting ===== | + | |
- | + | ||
- | There are three ways to connect to a Victron product: | + | |
- | ^ Method | + | |
- | | Products with built-in Bluetooth | + | |
- | | [[ve.direct: | + | |
- | | [[https:// | + | |
- | + | ||
- | + | ||
- | (1) Requires a USB On-The-Go cable. These cables are available in mobile phone and phone-repair shops, as well as on the internet. | + | |
- | + | ||
- | Use the [[# | + | |
- | + | ||
- | ==== 3.1 Bluetooth Smart - Pairing and Connecting ==== | + | |
- | + | ||
- | To connect to your Victron product, over Bluetooth, always connect from within VictronConnect. Do not connect from the phone' | + | |
- | + | ||
- | Here is how to connect: | + | |
- | + | ||
- | - Enable the Bluetooth on your phone. | + | |
- | - Open VictronConnect, | + | |
- | - On a phone or tablet, pull down the screen, or tap the refresh button to initiate a scan. | + | |
- | - On a computer or laptop: click the "Scan or Refresh" | + | |
- | - The first time you attempt to connect the phone will ask to pair with the Victron product. Enter the PIN code. The default PIN code is 000000 | + | |
- | - The connection is complete. | + | |
- | + | ||
- | If the connection was not successful please refer to section [[# | + | |
- | + | ||
- | ==== 3.2 Bluetooth Smart - Changing the PIN code ==== | + | |
- | + | ||
- | To prevent unauthorised connections to your Victron product 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: {{: | + | |
- | + | ||
- | For other products you'll find the {{: | + | |
- | + | ||
- | On this page, select the change PIN code button. | + | |
- | + | ||
- | Note that after changing the PIN code, all other phones connected to the Victron product need to have their pairing information refreshed; and first, the old pairing information needs to be removed. See [[#3.4 Bluetooth Smart - Removing from the list of paired devices | section 3.4]] to learn how to remove the pairing information. | + | |
- | + | ||
- | ==== 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 === | + | |
- | Reset the PIN code by pressing and holding the 'Clear PIN' button. After holding the button for 5 seconds, both LEDs will blink twice. This indicates that the PIN code has been reset. | + | |
- | + | ||
- | === Blue Smart Chargers IP65 === | + | |
- | Reset the PIN code by pressing and holding the ' | + | |
- | + | ||
- | === Blue Smart Chargers IP22 === | + | |
- | On the device list: tap or click the three-dots menu on the right side of the product description. 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. | + | |
- | + | ||
- | It can also be done on the charger itself:\\ | + | |
- | Reset the PIN code by pressing and holding the ' | + | |
- | + | ||
- | === Blue Smart Chargers IP67 === | + | |
- | On the device list: tap or click the three-dots menu on the right side of the product description. 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. | + | |
- | + | ||
- | === Smart Solar Charger === | + | |
- | On the device list: tap or click the three-dots menu on the right side of the product description. 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. | + | |
- | + | ||
- | === BMV-712 Smart === | + | |
- | On the device list: tap or click the three-dots menu on the right side of the product description. 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. | + | |
- | + | ||
- | === Smart LiFePO4 Batteries === | + | |
- | On the device list: tap or click the three-dots menu on the right side of the product description. 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. | + | |
- | + | ||
- | === SmartShunts === | + | |
- | On the device list: tap or click the three-dots menu on the right side of the product description. 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. | + | |
- | ==== 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. For example, if the PIN code of your product has been changed on a different phone. | + | |
- | + | ||
- | To remove the pairing information you will need to go to your phone' | + | |
- | + | ||
- | === Remove Bluetooth pairing on iOS devices: === | + | |
- | (click to play, double-click to enter fullscreen mode) | + | |
- | + | ||
- | {{victronconnect: | + | |
- | + | ||
- | === Remove Bluetooth pairing on Android devices: === | + | |
- | (click to play, double-click to enter fullscreen mode) | + | |
- | + | ||
- | {{victronconnect: | + | |
- | + | ||
- | ===== 4. Phone, tablet and laptop compatibility ===== | + | |
- | ==== 4.1 Windows PC === | + | |
- | + | ||
- | VictronConnect requires Windows 7, Windows 8 or Windows 10. For older Windows versions, XP and Vista, check our [[victronconnect: | + | |
- | + | ||
- | Note that on Windows, VictronConnect cannot use Bluetooth Smart to connect to a product. Other connection methods, such as USB, or LAN and WiFi do work properly. | + | |
- | + | ||
- | ==== 4.2 macOS X === | + | |
- | + | ||
- | Todays version of VictronConnect requires macOS version is 10.12 (OS X Sierra), or later. | + | |
- | + | ||
- | For the older macOS 10.11/ | + | |
- | + | ||
- | To connect to a Victron product with Bluetooth, the Apple Laptop needs to have Bluetooth 4.0 aka Bluetooth Smart. | + | |
- | ==== 4.3 Android devices === | + | |
- | + | ||
- | Android 5.0 is the minimum version required to run VictronConnect. | + | |
- | + | ||
- | An older version of VictronConnect that works for some users of Android 4.3 and 4.4 is still available in [[https:// | + | |
- | + | ||
- | The required hardware is ARMv7 and later, as well as x86 or ARM64bit. | + | |
- | + | ||
- | === Notes for Android 5 === | + | |
- | Android 5 devices with a 64bit CPU will experience a crash at startup due to an issue in the libraries we use to develop VictronConnect. This is not expected to be fixed. A workaround for this issue is to manually install the VictronConnect APK that can be downloaded in the [[https:// | + | |
- | + | ||
- | The pairing does not work on some phones running Android 5. The PIN code popup does not appear, or it appears without a text field to enter the PIN code. If you have this situation, your phone might report that it has been paired with the Victron product - but it has not. | + | |
- | + | ||
- | Unfortunately, | + | |
- | + | ||
- | Devices where we have seen this issue are: | + | |
- | * Asus Zenfone 2 with 5.0 <- Android 6 is available, update the phone to solve the issue | + | |
- | * Motorola Moto G 2 <- Android 6 is available, update the phone to solve the issue | + | |
- | * Medion tablet with Android 5.0 | + | |
- | + | ||
- | === Notes for Android 6 and later === | + | |
- | + | ||
- | No known issues, when Access to Locations services are enabled. | + | |
- | + | ||
- | === 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 products. | + | |
- | + | ||
- | Besides permitting access to its data, the location services also need to be enabled in many (but not all) cases. | + | |
- | + | ||
- | Note that after enabling location services, the GPS itself, can be switched off again: the Android location services are more than GPS. Bluetooth, and WiFi-, scan results can technically also be used to approximate the phone' | + | |
- | + | ||
- | Despite the above, you can be sure that Victron is not interested in, nor tracking your location. | + | |
- | + | ||
- | Being sensitive to privacy issues at Victron ourselves, we are not happy with this requirement. But there is nothing we can do about it, unfortunately. More information about why it is needed to enable the location services is [[https:// | + | |
- | + | ||
- | === List of known non-compatible Android devices === | + | |
- | ^Manufacturer ^Model | + | |
- | | HTC | One+ | ? | No | | + | |
- | | HTC | One M7 | ? | No | | + | |
- | | Huawei | + | |
- | | Lenovo | + | |
- | | Samsung | + | |
- | | Samsung | + | |
- | | ZTE | Telstra Max | ? | No | | + | |
- | + | ||
- | === List of known compatible Android devices === | + | |
- | + | ||
- | We have tested the following Android devices and can confirm that they are compatible with VictronConnect*: | + | |
- | + | ||
- | Google Nexus 6P; LG G4; Sony Xperia Z5; HTC One M9; HTC One S9; OnePlus 3T; Asus Zenfone 2; Samsung Galaxy S5; Samsung Galaxy S5 mini; Samsung Galaxy S7; Samsung Galaxy S8; Samsung Galaxy Tab E 9.6. | + | |
- | + | ||
- | *Assumes the phone runs the latest firmware released by the manufacturer. | + | |
- | ==== 4.4 Apple iOS iPhones and iPads === | + | |
- | VictronConnect works on the following iPhones and iPads running iOS 11 or later: | + | |
- | * iPhone 5S and later. | + | |
- | * iPad mini 2 and later | + | |
- | * iPad (5th generation) and later | + | |
- | * iPod touch (6th generation) and later | + | |
- | + | ||
- | Unfortunately Apple iPhone/iPad doesn' | + | |
- | + | ||
- | ==== 4.5 Linux ==== | + | |
- | + | ||
- | Details [[https:// | + | |
- | + | ||
- | ==== 4.6 Archive of previous versions ==== | + | |
- | + | ||
- | It would be nice to forever support all existing versions of Android, iOS, Windows, and other systems. But unfortunately, | + | |
- | + | ||
- | In such a situation, we recommend updating your phone to the latest OS. For situations where that is not possible we make these older versions available: | + | |
- | + | ||
- | **Warning: | + | |
- | + | ||
- | |**OS Version** | **Download link** | | + | |
- | | Windows XP and Windows Vista | [[https:// | + | |
- | | Android 4.3 to 4.4.4 armv7 architecture | [[https:// | + | |
- | | Android 4.3 to 4.4.4 x86 architecture | + | |
- | | macOS 10.9 (OS X Mavericks) | [[https:// | + | |
- | | macOS 10.10, 10.11 & 10.12 (OS X Yosemite / Sierra) | [[https:// | + | |
- | + | ||
- | + | ||
- | ===== 5. Application overview ===== | + | |
- | + | ||
- | ==== 5.1 Screenshots (click to enlarge) ==== | + | |
- | + | ||
- | **Device list**\\ | + | |
- | + | ||
- | LOCAL - This page shows all the Victron products that have been discovered by your phone, and to which a connection can be made. Click on the desired product. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | VRM - This page will show a GX product if it is connected to your VRM account. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | **Battery Monitor pages**: | + | |
- | Clicking on ' | + | |
- | *To access ' | + | |
- | From ' | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | **Solar Charge Controller pages**\\ | + | |
- | Clicking on your Solar Charge Controller product allows you to view the current charging status. | + | |
- | *To access ' | + | |
- | ' | + | |
- | + | ||
- | For a full explanation of the Solar Charge Controller options follow [[https:// | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | **Phoenix Inverter pages**\\ | + | |
- | Clicking on the Phoenix Inverter allows you to view dynamic data such as power-draw of connected loads; a power bar will show how hard your inverter is working, and you will find information such as battery voltage, etc. | + | |
- | *To access ' | + | |
- | ' | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | **Blue Smart IP65 charger pages**\\ | + | |
- | The Blue Smart IP65 battery charger comes with Bluetooth already built-in. When the Blue Smart charger is powered-up it will be discoverable using the VictronConnect app on your phone. (Except Windows PC - See **3.1 Windows PC**, above). | + | |
- | + | ||
- | The ' | + | |
- | + | ||
- | *To access ' | + | |
- | + | ||
- | From here you can choose a preset charge algorithm, you can select the charge current; and you can choose to employ the charge algorithm for a Li-ion battery when that is appropriate. | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | **Lithium Batteries Smart**\\ | + | |
- | Lithium Batteries Smart have Bluetooth built-in. Clicking on the Lithium battery from the Device list will allow you to view live data about the battery status, voltage, and temperature. You will also see the voltage of each cell - which is an essential guide to battery health. | + | |
- | *To access ' | + | |
- | From ' | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | **Peak Power Pack**\\ | + | |
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | **Windows**\\ | + | |
- | Here is a VictronConnect app screenshot from a PC using a version of the Microsoft Windows operating system showing information from an MPPT. | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | **macOS X**\\ | + | |
- | Here is a VictronConnect app screenshot from a PC running the Mac Operating System showing information from an MPPT. | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | ==== 5.2 Videos ==== | + | |
- | + | ||
- | **Blue Smart IP65 Charger ** | + | |
- | + | ||
- | This video will show you how to download the VictronConnect app onto a smart phone (in the video we use an iPhone). It will also show you how to use the app to view information and control the settings of a Blue Smart IP65 charger. | + | |
- | + | ||
- | + | ||
- | {{youtube> | + | |
- | \\ | + | |
- | + | ||
- | **BlueSolar MPPT** | + | |
- | + | ||
- | This video will show you how to download the VictronConnect app onto a smart phone (in the video we use an iPhone). It will also show you how to use the app to view Live Data and historical information from your Victron MPPT Solar Charge Controller. A full description of all the settings available on our Solar Charge Controllers can be found on [[https:// | + | |
- | + | ||
- | + | ||
- | {{youtube> | + | |
- | + | ||
- | ==== 5.3 Renaming your products ==== | + | |
- | + | ||
- | It is possible to change the name of your Victron product to make identification easier. This is especially useful if you have multiple products, such as 3 MPPTs and 2 BMV' | + | |
- | + | ||
- | To change the name: 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: {{: | + | |
- | + | ||
- | For other products you'll find the {{: | + | |
- | + | ||
- | Go to the Custom Name option, and select Edit and Done. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | + | ||
- | ==== 5.4 How to disable and re-enable Bluetooth ==== | + | |
- | + | ||
- | All our products that have Bluetooth built-in, have a feature that allows disabling Bluetooth. Typically the reason for doing so is security, even though the Bluetooth connection is protected by a PIN code, there is nothing more secure than disabling it. | + | |
- | + | ||
- | In most cases, it's also possible to re-enable Bluetooth after disabling. For example by using a VE.Direct cable. | + | |
- | + | ||
- | There are, however, a few exceptions: | + | |
- | * The [[# | + | |
- | * The [[# | + | |
- | + | ||
- | === Finding the Bluetooth menu === | + | |
- | + | ||
- | First, complete your connection; then go to the **Product info** page by clicking the button on the upper right: | + | |
- | + | ||
- | * For some products, it will be the settings icon: {{: | + | |
- | * For other products you'll find the {{: | + | |
- | + | ||
- | If the product has the feature that Bluetooth can be disabled, you will see the field " | + | |
- | + | ||
- | For some products, a Disable button is shown instead of a toggle switch. | + | |
- | + | ||
- | === How to re-enable Bluetooth === | + | |
- | + | ||
- | // | + | |
- | + | ||
- | There are a few different ways to re-enable Bluetooth depending on your product, always check the manual of your product for more detailed instructions: | + | |
- | + | ||
- | == Re-enable Bluetooth using VE.Direct == | + | |
- | + | ||
- | Connect the product with a VE.Direct to USB cable to your phone and use VictronConnect to re-enable Bluetooth in the **Product Info** page (see [[# | + | |
- | + | ||
- | == Re-enable Bluetooth using the MODE button on the product == | + | |
- | + | ||
- | Press and hold the MODE button on the product for 10 seconds will perform a Bluetooth reset. This means that the following actions will be executed: | + | |
- | * Bluetooth will be re-enabled | + | |
- | * The connected Bluetooth product will be disconnected | + | |
- | * The PIN code is reset to its [[# | + | |
- | * The pairing information is cleared; this requires [[victronconnect: | + | |
- | + | ||
- | == Lithium Smart batteries == | + | |
- | The product page can be found [[https:// | + | |
- | Once Bluetooth is disabled, it is disabled **permanently** and is **irreversible**. This means that VictronConnect will ask for a confirmation code displayed in the dialogue; if you are sure that you want to permanently disable Bluetooth, enter the code displayed, and choose " | + | |
- | + | ||
- | == Phoenix Smart IP43 Chargers == | + | |
- | The product page can be found [[https:// | + | |
- | Once Bluetooth is disabled, there are multiple ways to re-enable it again: | + | |
- | - Using the [[# | + | |
- | - Using a [[# | + | |
- | + | ||
- | == Blue Smart IP22 Chargers == | + | |
- | The product page can be found [[https:// | + | |
- | Once Bluetooth is disabled, it can be re-enabled with the [[# | + | |
- | + | ||
- | == Blue Smart IP65 Chargers == | + | |
- | The product page can be found [[https:// | + | |
- | Once Bluetooth is disabled, it can be re-enabled with the [[# | + | |
- | + | ||
- | == Blue Smart IP67 Chargers == | + | |
- | The product page can be found [[https:// | + | |
- | For these chargers there are two options: | + | |
- | * Disable Bluetooth **permanently**. This option is **irreversible** and VictronConnect will ask for a confirmation code displayed in the dialogue; if you are sure that you want to permanently disable Bluetooth, enter the code displayed and choose " | + | |
- | * Enable Bluetooth for 30 seconds at power-up. This allows you to connect to the product and to perform a firmware update or re-enable Bluetooth. If you do not connect within the first 30 seconds Bluetooth will be disabled. | + | |
- | + | ||
- | == SmartSolar MPPTs == | + | |
- | The product page can be found [[https:// | + | |
- | Bluetooth can be re-enabled by connecting a VE.Direct to USB cable to your phone and following [[# | + | |
- | + | ||
- | **Smart Battery Protect**\\ | + | |
- | The product page can be found [[https:// | + | |
- | Bluetooth can be disabled/ | + | |
- | + | ||
- | **Smart BMV-712**\\ | + | |
- | The product page can be found [[https:// | + | |
- | The BMV-712' | + | |
- | + | ||
- | **Smart BMS**\\ | + | |
- | The product page can be found [[https:// | + | |
- | Bluetooth is temporarily enabled at power-up for 30 seconds. You can connect within these 30 seconds to perform a firmware update or re-enable Bluetooth. If you do not connect within the first 30 seconds Bluetooth will be disabled. | + | |
- | + | ||
- | **Smart Shunt**\\ | + | |
- | The product page can be found [[https:// | + | |
- | Bluetooth can be re-enabled by connecting a VE.Direct to USB cable to your phone and following [[# | + | |
- | ==== 5.5 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) 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:// | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | This feature is not available in the iOS and Android mobile versions of VictronConnect. | + | |
- | + | ||
- | + | ||
- | ===== 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.\\ | + | |
- | (Note that alarms and errors are only shown when the app is active.) | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | ===== 7. Settings files ===== | + | |
- | + | ||
- | ==== 7.1 Save, load, share and manage settings ==== | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | ** Save settings ** | + | |
- | + | ||
- | Connect your phone to the Victron product, go to the ' | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | ** Load settings ** | + | |
- | + | ||
- | Connect your phone to the Victron product, go to the ' | + | |
- | + | ||
- | When the file is loaded, the changes are not immediately applied to make it possible to review them first. The differences between the product' | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | Once you have reviewed them, click ' | + | |
- | + | ||
- | ** Share settings ** | + | |
- | + | ||
- | The 'Share settings' | + | |
- | Also, settings you have already saved using VictronConnect are stored in a settings file and can be shared with other products through the ' | + | |
- | + | ||
- | ** Settings file manager ** | + | |
- | + | ||
- | The Settings file manager is located in the main menu, and shows all stored settings: | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | From here files can be opened, shared or removed: | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | + | ||
- | ==== 7.2 Settings files and the demo library ==== | + | |
- | + | ||
- | The demo library can be a great tool for an installer to create a set of settings, and then share it to a customer whom can then apply it to their product. | + | |
- | + | ||
- | Note that whilst saving settings from the demo library is possible, loading settings from within the demo library is not possible. | + | |
- | + | ||
- | ==== 7.3 Limitation in opening older settings files ==== | + | |
- | + | ||
- | There are two methods to open a previously stored settings-file: | + | |
- | + | ||
- | - From the settings file manager, as in the above screenshot, to see the settings without having to be connected to the product. A snapshot of all data, including voltage readings, history data, and so forth, will be loaded and visible to inspect. | + | |
- | - From the product settings pages, only possible when connected to a product. | + | |
- | + | ||
- | Note that the first method only works when the settings file is created with the exact same VictronConnect version that was used to store the file. To open a file made with an older VictronConnect version, use the second method: connect the same product, and then load the settings. | + | |
- | + | ||
- | + | ||
- | ===== 8. Demo feature ===== | + | |
- | + | ||
- | VictronConnect contains a library with demonstration settings for all the supported products. | + | |
- | + | ||
- | The demo feature can be used to: | + | |
- | * Learn about the settings which are available on your Victron product. By exploring the library' | + | |
- | * Create a specific product setup, save it ...and then send it to a customer so that they have those settings on their phone, and can install them on their Victron product. | + | |
- | * Besides loading products from the standard library, it is also possible to load them from a saved file using the ' | + | |
- | * Review settings made to your installations, | + | |
- | + | ||
- | ** Loading demos ** | + | |
- | + | ||
- | The Demo library can be accessed through the main menu. | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | To load a saved settings file as a demo, go to the ' | + | |
- | + | ||
- | {{: | + | |
- | ===== 9. Firmware updates===== | + | |
- | ==== 9.1 Introduction & automatic updates ==== | + | |
- | + | ||
- | __What about updating Firmware on VE.Bus products such as MultiPlus and Quattro? | + | |
- | + | ||
- | Please follow this [[https:// | + | |
- | + | ||
- | __How can I see what firmware version is available? | + | |
- | + | ||
- | First, connect to the product, then go to the **Product info** page. Under the Firmware version if you will see a text informing you if you are using the latest available version or if there is an update available. If a new version is available you can start the update process by pressing the " | + | |
- | + | ||
- | Some firmware versions are mandatory, when you connect to the product VictronConnect will prompt to update immediately in case there is a mandatory version available. | + | |
- | + | ||
- | Or, when not close to the product, open the Demo library, and select the product. The Product info page will show the latest available version that is shipped with VictronConnect. | + | |
- | + | ||
- | __Do I need to be connected to the internet for updating firmware? | + | |
- | + | ||
- | No. Updating firmware does **not** require an internet connection, the latest Firmware files are already loaded inside VictronConnect, | + | |
- | + | ||
- | __How does it work?__ | + | |
- | + | ||
- | After connecting your product, VictronConnect will automatically check whether a mandatory update is available, and in that case, you will be guided through the update procedure before doing anything else. | + | |
- | + | ||
- | If an update is available but is not mandatory, you will be able to see your product' | + | |
- | + | ||
- | A firmware update - when available - will need to be completed in order to change settings on your Victron product using VictronConnect. | + | |
- | + | ||
- | __Will I need to reconfigure my MPPT or BMV after the update?__ | + | |
- | + | ||
- | No. The settings of your VE.direct and Bluetooth products will not be affected by the firmware update ...and so you will not need to reconfigure your product after the update. Also, the History data of BMVs and MPPTs will be preserved throughout a firmware update. | + | |
- | + | ||
- | ==== 9.2 Updating to a self-supplied firmware file ==== | + | |
- | + | ||
- | The previous chapter explained how VictronConnect will automatically update to the latest firmware version. Besides that, it is also possible to update a product with a file that you supply yourself. | + | |
- | + | ||
- | This is not needed very often. Some reasons to do so could be: | + | |
- | + | ||
- | * Update to a very recent version, that's already available on [[https:// | + | |
- | * Update a product to a special or unreleased version. | + | |
- | + | ||
- | + | ||
- | === Instructions for Windows and MacOS computers === | + | |
- | + | ||
- | With your phone and Victron product connected to VictronConnect, | + | |
- | + | ||
- | There is no need to worry about using a wrong file - VictronConnect will always first check if the file matches the product. And if wrong, it will show a "wrong firmware file error" | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | === Instructions for Android and iOS phones and tablets === | + | |
- | + | ||
- | The process is slightly different from the Windows/ | + | |
- | + | ||
- | 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. 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 it with VictronConnect. VictronConnect will be opened and show: "File added to the firmware library" | + | |
- | + | ||
- | If the message doesn' | + | |
- | + | ||
- | In case you are not sure which file to use, it is not a problem to add multiple files to the library. In the next step, VictronConnect will automatically only show the files that match with the connected product. | + | |
- | + | ||
- | * **Note for iOS**: The current version of Google Chrome for iOS fails to download " | + | |
- | * **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. | + | |
- | + | ||
- | Here are screenshot showing the detailed steps: | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | Now, after adding the firmware file to the library, go to the " | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | Select the desired file from the list, see next screenshot - it shows one entry in the list: | + | |
- | + | ||
- | Note that the update mechanism will detect-and-reject 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 be guided through the update process: | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | ==== 9.3 Troubleshooting firmware updates ==== | + | |
- | + | ||
- | A troubleshooting guide relevant to firmware updates can be found in [[# | + | |
- | + | ||
- | ==== 9.4 Error codes ==== | + | |
- | + | ||
- | 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/ | + | |
- | Sometimes you may need to [[# | + | |
- | + | ||
- | In the following list, you can check possible errors and descriptions. | + | |
- | + | ||
- | Check [[# | + | |
- | + | ||
- | **VE.Direct products** | + | |
- | ^Error | + | |
- | | D3 | No VE.Direct product(s) found. | | + | |
- | | D4 | Unknown error occurred. Try again and check the product settings once updated. | | + | |
- | | D10 | Error closing com port. | | + | |
- | | D20 | Could not start updating, no updatable product found. | | + | |
- | | D26 | Updating failed, communication lost. The product might be unusable. Check connection and power supply.\\ Try again and check the product settings once updated. | | + | |
- | | D29 | Could not start updating, the firmware file is corrupt. | | + | |
- | | D31 | Updating failed, the product is unusable. Try again and check the product settings once updated. | | + | |
- | | D32 | Could not start updating, entering boot mode failed. | | + | |
- | | D33 | Could not start updating, the firmware file is not found. | | + | |
- | | D90 | Could not start updating, the firmware is not for this product. | | + | |
- | | D91 | Could not start updating, an unknown product was found. | | + | |
- | | D92 | Updating failed, erasing firmware failed. The product might be unusable. Try 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. | | + | |
- | | D94 | Product updated successfully, | + | |
- | | D95 | Product updated successfully, | + | |
- | | 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. | | + | |
- | | D97 | Dup executable too old. | | + | |
- | | D98 | Firmware file is not a valid dup file. | | + | |
- | | D99 | Product updated successfully, | + | |
- | | D100 | Cannot migrate settings because the application is not active. Manual action required. | | + | |
- | + | ||
- | ** Blue Smart Charger, SmartLithium, | + | |
- | ^Error ^Description^ | + | |
- | | B1 | Error reading file. | | + | |
- | | B2 | Victron 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. | | + | |
- | | B4 | The product disconnected unexpectedly. Perhaps the bond information is no longer valid? Please remove\\ | + | |
- | | B5 | A write to the device failed. | | + | |
- | | B6 | The product did not activate its bootloader - although it should have. | | + | |
- | | B7 | The product did not disconnect - although it should. | | + | |
- | | B8 | Timeout waiting for access to the Victron BLE service. | | + | |
- | | B9 | Timeout waiting for access to the Dfu BLE service. | | + | |
- | | B10 | Timeout waiting for a response. | | + | |
- | | B11 | Timeout while writing to the product. Perhaps a pairing dialogue is shown? Please retry. | | + | |
- | | B12 | Device was no longer found. Perhaps out of range? Please retry. | | + | |
- | | B96 | An internal error occurred (Opcode 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 occurred (Data size exceeds limits). 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. | | + | |
- | | B100 | An internal error occurred (CRC error). 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. VictonConnect-Remote (VC-R) – Configuration and monitoring via VRM ===== | + | |
- | + | ||
- | ==== 10.1 Introduction ==== | + | |
- | + | ||
- | VictronConnect-Remote functionality enables Victron devices with a VE.Direct interface to be accessed remotely through a [[https:// | + | |
- | + | ||
- | This powerful new feature allows full device configuration and monitoring from practically anywhere in the world using the VictronConnect app. | + | |
- | + | ||
- | The user interface experience is just like the devices were connected locally using Bluetooth or a wired VE.Direct to USB interface. | + | |
- | + | ||
- | ==== 10.2 Compatibility ==== | + | |
- | + | ||
- | The VictronConnect-Remote feature is ONLY compatible with devices connected to a GX Device with a VE.Direct interface. | + | |
- | + | ||
- | This includes; | + | |
- | * MPPT solar chargers with a VE.Direct interface (SmartSolar and BlueSolar) | + | |
- | * Battery monitors with a VE.Direct interface (BMV and SmartShunt) | + | |
- | * Specific inverters with a VE.Direct interface (Phoenix Inverter VE.Direct and Phoenix Inverter Smart) | + | |
- | * Specific mains chargers with a VE.Direct interface (Phoenix Smart IP43) | + | |
- | + | ||
- | Devices connected with a VE.Bus interface, such as Multiplus/ | + | |
- | + | ||
- | Devices connected using a VE.Can interface, such as Lynx Shunt, Skylla chargers and MPPT solar chargers using a VE.Can interface are also NOT compatible and cannot be configured remotely. | + | |
- | + | ||
- | ==== 10.3 Setup ==== | + | |
- | + | ||
- | === 10.3.1 Minimum Requirements === | + | |
- | + | ||
- | * VictronConnect SW: v5.20 | + | |
- | * GX Device - Venus OS FW: v2.40 (However v2.53 recommended for full functionality) | + | |
- | + | ||
- | === 10.3.2 VictronConnect === | + | |
- | + | ||
- | - Confirm that the phone, tablet or PC has VictronConnect installed and that the software version meets or exceeds the minimum requirements - upgrade if necessary | + | |
- | - Authorize VictronConnect to access your VRM account; | + | |
- | * Open the VictronConnect app | + | |
- | * Swipe across to the VRM tab, then select ‘SIGN IN TO VRM’ | + | |
- | * Complete your email address and VRM password, then select ‘Authorize Victron Connect’ | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | * If using a tablet or PC your browser may also request permission to proceed, if prompted select ‘Open’ | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | === 10.3.3 GX Device === | + | |
- | + | ||
- | 1- Confirm that the GX Device is running Venus OS firmware version that meets or exceeds the minimum requirements - upgrade if necessary | + | |
- | 2- Enable ‘VRM two-way communication’ under Device List > Settings > VRM Online Portal | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | ==== 10.4 Local Tab ==== | + | |
- | + | ||
- | The local tab displays all devices that are within local Bluetooth and wireless LAN range or physically connected to the phone, tablet or PC with VictronConnect (such as with a VE.Direct to USB or MK3 to USB interface cable) | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | ==== 10.5 VRM Tab ==== | + | |
- | + | ||
- | The VRM tab displays all VRM installations associated with the VRM user profile. | + | |
- | + | ||
- | Any installation can be selected to access the VRM online portal or connected devices. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | When a VRM installation is selected it will take a few seconds for a connection to be made, once the connection is established two tabs will appear, an ‘OVERVIEW’ tab and a ‘DEVICES’ tab. | + | |
- | + | ||
- | === 10.5.1 Overview Tab === | + | |
- | + | ||
- | The ‘OVERVIEW’ tab has an image of the GX device, the name of the VRM installation and a direct link to the associated [[https:// | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | === 10.5.2 Devices Tab === | + | |
- | + | ||
- | The ‘DEVICES’ tab has a list of all compatible devices that are physically connected to the GX device. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | If using a tablet or PC, the ‘DEVICES’ tab is shown as a panel on the right side of the same screen. | + | |
- | + | ||
- | {{: | + | |
- | + | ||
- | ==== 10.6 Remote device access ==== | + | |
- | + | ||
- | When a device is selected it will take a few seconds for a connection to be made, once the connection is established live device information/ | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | Immediately after initial connection settings and historical data will be downloaded, during this time a cloud symbol will remain in the upper right corner (this typically takes less than 30 seconds). | + | |
- | + | ||
- | Settings cannot be accessed until the cloud symbol is replaced by the normal settings gear symbol. | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | ==== 10.7 Signing out ==== | + | |
- | + | ||
- | To disable the link between VictronConnect-Remote and your VRM account, expand the main menu and then select ‘Settings’. | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | In the settings page select ‘SIGN OUT’ and then select ‘OK’ in the prompt window to confirm. | + | |
- | + | ||
- | {{: | + | |
- | {{: | + | |
- | + | ||
- | After signing out VictronConnect-Remote will no longer have access to the VRM account or any of the associated VRM installations. To reinstate access the log in procedure needs to be repeated. | + | |
- | + | ||
- | ==== 10.8 Troubleshooting and FAQ ==== | + | |
- | + | ||
- | == Device not found == | + | |
- | + | ||
- | * VictronConnect-Remote is only compatible with devices that use a VE.Direct interface to the GX device – see the ‘compatibility’ section. | + | |
- | * Ensure that that the missing device is physically connected to the GX device, with the VE.Direct cable properly installed at both ends. | + | |
- | * Ensure that the device is running a recent firmware version. | + | |
- | + | ||
- | == Installation/ | + | |
- | + | ||
- | * Confirm that the installation is currently online and communicating with the VRM online portal. | + | |
- | * Ensure that the installation is linked to the VRM account used during initial VictronConnect-Remote sign in to VRM. | + | |
- | * Ensure that ‘VRM two-way communication’ is enabled – see the ‘settings’ section. | + | |
- | * Ensure that the GX device is running the minimum compatible Venus OS firmware version – see the ‘settings’ section. | + | |
- | + | ||
- | == VictronConnect has no VRM tab == | + | |
- | + | ||
- | * Ensure that the phone, tablet or PC is running the minimum compatible VictronConnect software version – see the ‘settings’ section. | + | |
- | + | ||
- | == VRM account == | + | |
- | + | ||
- | * It is necessary to have an active VRM account linked to your installation and any others that you intend to monitor or configure using VictronConnect-Remote - creating a new account is quick and easy. | + | |
- | * For further information in relation to VRM (Victron Remote Management) see [[https:// | + | |
- | + | ||
- | == Systems with no GX device == | + | |
- | + | ||
- | * VictronConnect-Remote functionality is not possible unless the system includes a GX device. A GX device can be easily added to any system and there are a [[https:// | + | |
- | + | ||
- | == Installations with no internet connection == | + | |
- | + | ||
- | * VictronConnect-Remote functionality is not possible unless GX device at the installation site has an active internet connection. | + | |
- | * For remote sites without an existing internet connection or with mobile installations, | + | |
- | + | ||
- | == Large systems == | + | |
- | + | ||
- | * The use of the VictronConnect-Remote feature will slightly increase the GX device CPU load. | + | |
- | * In some large/ | + | |
- | * It is important to select a GX device that has sufficient performance capability in relation to the system design, for example a Cerbo GX has significantly more processing power than a Color Control GX and is much better suited to large/ | + | |
- | + | ||
- | == VictronConnect Remote troubleshooting == | + | |
- | + | ||
- | VictronConnect will report errors encountered during communication attempts with VRM in a message box with an error code. The code can have one of the following value: | + | |
- | + | ||
- | ^Error ^Description^ | + | |
- | |-100 | Call to retrieve a list of child devices expired (60 seconds). The most common cause is a bad internet connection. | | + | |
- | | 1 | No link to VRM can be established. Check if the internet is present and try again. | | + | |
- | | 2 | VRM encountered temporary difficulties. Try again in a while. | | + | |
- | | 5 | The local system ran out of resources. Free some system resources and try again. | | + | |
- | | 8 | An error occurred with the network (e.g., the network cable was accidentally plugged out). | | + | |
- | | 13 | Proxy authentication error. VictronConnect does not support communication over proxy. | | + | |
- | | 14 | Failed to establish a secure connection to VRM. | | + | |
- | |65538| VRM MQTT broker is not responding. Please try again in a while. | | + | |
- | + | ||
- | There are also other error codes that could be reported. They are a result of internal errors in VictronConnect and/or VRM. In case these errors persist after a retry, please create a " | + | |
- | + | ||
- | VictronConnect Remote is establishing communication with a range of services on ' | + | |
- | + | ||
- | ===== 11. Troubleshooting ===== | + | |
- | + | ||
- | ==== 11.1 Common Bluetooth problems and how to solve them === | + | |
- | + | ||
- | The #1 first step before attempting any of the specific troubleshooting advice below is to power down and then restart all related devices. This includes closing the software, restarting the phone, tablet, computer and Victron equipment. This will solve most issues. | + | |
- | + | ||
- | For example with Victron MPPTs you must isolate the MPPT from both battery and solar voltage so that no lights appear, before reconnecting it again. | + | |
- | + | ||
- | == I cannot find my device listed == | + | |
- | * Make sure that you have a " | + | |
- | * Make sure your device is in range. | + | |
- | * 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# | + | |
- | * Only one device can be connected to a product at the same time. Make sure that no other device: phone/ | + | |
- | * Make sure you are attempting to connect from //within// VictronConnect - not from the system menu of your phone/ | + | |
- | + | ||
- | == I can see but not connect to my device == | + | |
- | - Make sure you are trying to connect to the right device. See [[start# | + | |
- | - 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. | + | |
- | - Make sure that Bluetooth is still enabled in your phone/ | + | |
- | - 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/ | + | |
- | - If you are using an Android phone/ | + | |
- | + | ||
- | === Connection fails around 20% === | + | |
- | + | ||
- | - Make sure you are up to date with the latest version of VictronConnect. | + | |
- | - [[https:// | + | |
- | - Then [[https:// | + | |
- | - Force close the VictronConnect app. Instructions: | + | |
- | - Reconnecting in VictronConnect using the default PIN 000000 | + | |
- | - Then [[https:// | + | |
- | + | ||
- | ==== 11.2 Bluetooth connection issues on Android devices ==== | + | |
- | + | ||
- | === Step 1: Check that your device is supported === | + | |
- | + | ||
- | See section [[# | + | |
- | + | ||
- | === Step 2: Check the Android version === | + | |
- | + | ||
- | * Android 4.2 or earlier: this Android version is not supported. The earliest Android version which can be used with Bluetooth is 4.3. | + | |
- | * Android 5: [[victronconnect:# | + | |
- | * Android 6 or later: no known issues. | + | |
- | + | ||
- | === Step 3: Check that VictronConnect has access to the Location services === | + | |
- | + | ||
- | On Android 5 and later VictronConnect needs access to the device location services to be able to scan nearby Bluetooth devices. Unless you checked " | + | |
- | + | ||
- | Permission to access location services is requested each time the app starts ...but if you checked the " | + | |
- | + | ||
- | === Step 4. Enable Location (or GPS) functionality in the system settings === | + | |
- | + | ||
- | For Bluetooth scanning to work, the Location (or GPS) functionality on the device needs to be enabled. | + | |
- | + | ||
- | === Step 5. Search & connect from within VictronConnect ...NOT from the system Bluetooth menu === | + | |
- | + | ||
- | === Step 6. Pin-code pop-up never shows === | + | |
- | + | ||
- | On some Android phones, the pin-code pop-up dialog doesn' | + | |
- | + | ||
- | Try to connect and when the connection is stuck at 80%, open the notifications bar and check if the PIN code/Pair request is there, if it the case open it and enter the PIN code. | + | |
- | + | ||
- | The default pin-code is 000000, six times zero. | + | |
- | + | ||
- | === Step 7. Try another phone at first === | + | |
- | + | ||
- | If you are still 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. | + | |
- | + | ||
- | ==== 11.3 Problems during firmware updating ==== | + | |
- | + | ||
- | First of all, it's 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. | + | |
- | + | ||
- | 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/ | + | |
- | Watch these instructional videos to learn how to remove the pairing on {{ : | + | |
- | + | ||
- | 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 === | + | |
- | When the firmware update fails at 4% or less, VictronConnect cannot make the device switch to the update mode. | + | |
- | + | ||
- | __ Solution for Blue Smart IP65 Chargers __ | + | |
- | * If you are in the firmware update screen, first force close VictronConnect. | + | |
- | * Unplug the mains cable from the charger and wait for 30 seconds. | + | |
- | * Press and hold the MODE button on the charger and plug in the mains cable again until the yellow and blue LEDs are blinking alternately to force the charger into update mode. | + | |
- | * Release the MODE button. You now have 30 seconds to connect to the product, after 30 seconds the charger will automatically leave the update mode. | + | |
- | * Start VictronConnect and click on the product in the device list. | + | |
- | * The firmware update screen will appear again. You should now be able to update your charger to the latest firmware version. | + | |
- | + | ||
- | __ Solution for VE.Direct Smart dongle __ | + | |
- | + | ||
- | * If you are in the firmware update screen, first force close VictronConnect. | + | |
- | * Unplug the dongle from the VE.Direct port. | + | |
- | * Press and hold the 'Clear PIN' button on the dongle and connect it to the VE.Direct port again, the red and blue LEDs will blink alternately; | + | |
- | * Release the 'Clear PIN' button. You now have 30 seconds to connect to the product, after 30 seconds the dongle will automatically leave the update mode. | + | |
- | * Start VictronConnect and click on the product in the device list. | + | |
- | * The firmware update screen will appear again. You should now be able to update the dongle to the latest firmware version. | + | |
- | + | ||
- | ==== 11.4 VE.Direct USB driver problem on macOS X 10.9 (Mavericks) ==== | + | |
- | + | ||
- | The driver included in macOS X 10.9 " | + | |
- | + | ||
- | If updating the operating system is not possible, there is a workaround which disables the Apple FTDI (Future Technology Devices International) driver and installs a compatible driver. Follow these steps: | + | |
- | + | ||
- | === Step 1. Open the terminal and run the following commands: === | + | |
- | < | + | |
- | cd / | + | |
- | sudo mv AppleUSBFTDI.kext AppleUSBFTDI.disabled | + | |
- | </ | + | |
- | + | ||
- | === Step 2. Restart the computer === | + | |
- | + | ||
- | === Step 3. Download and install the compatible FTDI driver === | + | |
- | + | ||
- | http:// | + | |
- | + | ||
- | === Step 4. Restart the computer === | + | |
- | VictronConnect should now show the connected products. | + | |
- | + | ||
- | ==== 11.5 VictronConnect on Windows doesn' | + | |
- | + | ||
- | VE.Direct USB cable requires a driver to be installed. | + | |
- | + | ||
- | The necessary drivers are available in the [[https:// | + | |
- | + | ||
- | ==== 11.6 VictronConnect on Android doesn' | + | |
- | + | ||
- | 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. | + | |
- | + | ||
- | + | ||
- | ==== 11.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 " | + | |
- | Please note that this service report is for Victron internal use and is not able to be read or used for any other purpose than developer troubleshooting. | + | |
- | + | ||
- | To do this, | + | |
- | + | ||
- | - Open VictronConnect | + | |
- | - Perform the action that leads to the bug or issue | + | |
- | - Return to the main menu | + | |
- | - Select the three lines menu | + | |
- | - Select Settings | + | |
- | - Click or tap CREATE SERVICE REPORT | + | |
- | - Save, email or copy the file to Victron, via email or the Victron Community. | + | |
- | + | ||
- | + | ||
- | {{: | + | |
- | + | ||
- | If you require more detailed power system diagnostic information, | + | |
- | ==== 11.8 VE.Bus firmware update fails at 5% on macOS ==== | + | |
- | + | ||
- | There is a known issue that makes VE.Bus firmware updates randomly fail on some macOS laptops. We are working on it; a new VictronConnect version fixing this issue is expected in the near future. Meanwhile this is the workaround for this: | + | |
- | + | ||
- | Proceed to update as usual and quickly minimise the VictronConnect window when progress bar is shown because the update starts. After ~20 seconds you can maximise VictronConnect to see the update status. (1) | + | |
- | + | ||
- | This issue was introduced in VictronConnect v5.9. | + | |
- | + | ||
- | (1) For those with a technical background and wondering how, why and what minimising has to do with this: yes this really works, and relates to a power saving mode that has a side effect on serial communication. | + | |
- | + | ||
- | ===== 12. Compatible Victron products ===== | + | |
- | + | ||
- | ==== Solar Chargers ==== | + | |
- | + | ||
- | === SmartSolar MPPT Charge controllers === | + | |
- | ^ ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ | + | |
- | | MPPT 75/10 | [[https:// | + | |
- | | MPPT 75/15 | [[https:// | + | |
- | | MPPT 100/ | + | |
- | | MPPT 100/ | + | |
- | | MPPT 100/ | + | |
- | | MPPT 100/ | + | |
- | | MPPT 150/ | + | |
- | | MPPT 150/45 Tr and MC4 | [[https:// | + | |
- | | MPPT 150/60 Tr and MC4 | [[https:// | + | |
- | | MPPT 150/70 Tr and MC4 | [[https:// | + | |
- | | MPPT 150/85 Tr and MC4 | [[https:// | + | |
- | | MPPT 150/100 Tr and MC4| [[https:// | + | |
- | | MPPT 250/60 Tr and MC4 | [[https:// | + | |
- | | MPPT 250/70 Tr and MC4 | [[https:// | + | |
- | | MPPT 250/85 Tr and MC4 | [[https:// | + | |
- | | MPPT 250/100 Tr and MC4| [[https:// | + | |
- | + | ||
- | (*) Note for early versions of SmartSolar MPPT 150/85 and 150/100: it is not possible to use both the VE.Direct port and the built-in Bluetooth Smart function at the same time. When connecting to VE.Direct, the built-in Bluetooth Smart function will not be available. These early versions can be recognized by their part number: | + | |
- | * SmartSolar MPPT 150/85 Tr. Early version: SCC010085210. | + | |
- | * SmartSolar MPPT 150/85 MC4. Early version: SCC010085310. | + | |
- | * SmartSolar MPPT 150/100 Tr. Early version: SCC010100210. | + | |
- | * SmartSolar MPPT 150/100 MC4. Early version: SCC010100310. | + | |
- | + | ||
- | The same models, but then with a different part number do support using both the VE.Direct port and the built-in Bluetooth Smart function at the same time. As do all other SmartSolar MPPT models. | + | |
- | + | ||
- | === BlueSolar MPPT Charge controllers === | + | |
- | ^ ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ | + | |
- | | MPPT 70/15 | Not compatible || | + | |
- | | MPPT 75/10 | [[https:// | + | |
- | | MPPT 75/15 | [[https:// | + | |
- | | MPPT 75/50 | [[https:// | + | |
- | | MPPT 100/ | + | |
- | | MPPT 100/ | + | |
- | | MPPT 100/ | + | |
- | | MPPT 150/ | + | |
- | | MPPT 150/45 Tr and MC4 | [[https:// | + | |
- | | MPPT 150/60 Tr and MC4 | [[https:// | + | |
- | | MPPT 150/70 Tr and MC4 VE.Direct (*) | [[https:// | + | |
- | | MPPT 150/85 Tr and MC4 VE.Direct | + | |
- | | MPPT 150/70 CAN-bus | Not compatible || | + | |
- | | MPPT 150/85 CAN-bus | Not compatible || | + | |
- | | MPPT 150/100 Tr and MC4 | [[https:// | + | |
- | + | ||
- | + | ||
- | ==== Battery Chargers ==== | + | |
- | + | ||
- | ^ Blue Smart IP22 ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ Bluetooth on/ | + | |
- | | All Blue Smart IP22 Chargers | + | |
- | ^ Blue Smart IP65 ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ Bluetooth on/ | + | |
- | | Blue Smart IP65 12/25 Charger | + | |
- | | Blue Smart IP65 24/13 Charger | + | |
- | | Other Blue Smart IP65 Chargers | + | |
- | ^ Blue Smart IP67 ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ Bluetooth on/ | + | |
- | | All Blue Smart IP67 Chargers | + | |
- | ^ Phoenix Smart IP43 ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ Bluetooth on/ | + | |
- | | All Phoenix Smart IP43 Chargers | Yes | Yes - Built in | Yes | No | No | | + | |
- | ^ IMPULSE-II Smart ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ Bluetooth on/ | + | |
- | | All IMPULSE-II Smart Chargers | + | |
- | + | ||
- | + | ||
- | ==== Orion-Tr Smart DC-DC Charger Isolated ==== | + | |
- | ^ ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ | + | |
- | | All Orion-Tr Smart DC-DC Isolated Chargers | + | |
- | + | ||
- | ==== Battery Monitors ==== | + | |
- | ^ ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ | + | |
- | | BMV-700 | + | |
- | | BMV-702 | + | |
- | | BMV-700H | [[https:// | + | |
- | | BMV-712 | + | |
- | + | ||
- | + | ||
- | ==== Phoenix Inverters VE.Direct ==== | + | |
- | ^ ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ | + | |
- | | Phoenix Inverter 12V 250VA | [[https:// | + | |
- | | Phoenix Inverter 12V 375VA | [[https:// | + | |
- | | Phoenix Inverter 12V 500VA | [[https:// | + | |
- | | Phoenix Inverter 12V 800VA | [[https:// | + | |
- | | Phoenix Inverter 12V 1200VA | [[https:// | + | |
- | | Phoenix Inverter 24V 250VA | [[https:// | + | |
- | | Phoenix Inverter 24V 375VA | [[https:// | + | |
- | | Phoenix Inverter 24V 500VA | [[https:// | + | |
- | | Phoenix Inverter 24V 800VA | [[https:// | + | |
- | | Phoenix Inverter 24V 1200VA | [[https:// | + | |
- | | Phoenix Inverter 48V 250VA | [[https:// | + | |
- | | Phoenix Inverter 48V 375VA | [[https:// | + | |
- | | Phoenix Inverter 48V 500VA | [[https:// | + | |
- | | Phoenix Inverter 48V 800VA | [[https:// | + | |
- | | Phoenix Inverter 48V 1200VA | [[https:// | + | |
- | + | ||
- | ==== Peak Power Pack ==== | + | |
- | ^ ^ USB via VE.Direct port ^ Wireless Via Bluetooth ^ | + | |
- | | Peak Power Pack 12.8 8Ah | [[https:// | + | |
- | | Peak Power Pack 12.8 20Ah | [[https:// | + | |
- | | Peak Power Pack 12.8 30Ah | [[https:// | + | |
- | | Peak Power Pack 12.8 10Ah | [[https:// | + | |
- | + | ||
- | ==== Smart LiFePO4 Lithium Batteries ==== | + | |
- | + | ||
- | ^ ^ USB via VE.Direct port^ Wireless Via Bluetooth^ | + | |
- | | LiFePO4 battery 12,8V/60Ah | No VE.Direct port| Yes - Built in| | + | |
- | | LiFePO4 battery 12,8V/90Ah | No VE.Direct port| Yes - Built in| | + | |
- | | LiFePO4 battery 12,8V/100Ah | No VE.Direct port| Yes - Built in| | + | |
- | | LiFePO4 battery 12,8V/150Ah | No VE.Direct port| Yes - Built in| | + | |
- | | LiFePO4 battery 12,8V/160Ah | No VE.Direct port| Yes - Built in| | + | |
- | | LiFePO4 Battery 12,8V/200Ah | No VE.Direct port| Yes - Built in| | + | |
- | | LiFePO4 Battery 12,8V/300Ah | No VE.Direct port| Yes - Built in| | + | |
- | | LiFePO4 Battery 25,6V/200Ah | No VE.Direct port| Yes - Built in| | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | ==== Smart Battery Sense ==== | + | |
- | + | ||
- | ^ ^ USB via VE.Direct port^ Wireless Via Bluetooth^ | + | |
- | | Smart Battery Sense| | + | |
- | + | ||
- | + | ||
- | ==== MultiPlus, EasySolar, Quattro, Phoenix Inverter with VE.Bus, and similar products ==== | + | |
- | + | ||
- | This section applies to MultiPlus, MultiPlus-II, | + | |
- | + | ||
- | In order to keep this section short, all these devices are referred to as VE.Bus products. | + | |
- | + | ||
- | The minimal required version of the VE.Bus devices is 19xx111 for European units and 20xx111 for 120V, which were released in 2007. Older models, 18xxxxx are not supported. | + | |
- | + | ||
- | The currently sold generation, VE.Bus firmware 26xxxxx and 27xxxxx is supported. | + | |
- | + | ||
- | Mixed systems (1954208 in parallel to 2654208) are not supported by vebus-interface, | + | |
- | + | ||
- | Inverter/ | + | |
- | + | ||
- | - Using USB, this requires the [[https:// | + | |
- | - Wirelessly, over Bluetooth. Requires the [[https:// | + | |
- | + | ||
- | Note that switching between on/ | + | |
- | + | ||
- | For systems with a [[venus-os: | + |
victronconnect/start.1593609856.txt.gz · Last modified: 2020-07-01 15:24 by evandromr