Differences

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

--- vebus_smart_dongle_manual [2018-09-21 13:07] – [Introduction] justin_tyers_live_a_c
+++ vebus_smart_dongle_manual [2019-06-21 16:13] – [VE.Bus Smart Dongle - manual] mvader
@@ Line 1: / Line 1: @@
 ====== VE.Bus Smart Dongle - manual ======
-Work in progress. This page contains input for the user manual
 {{:benh7ta_79897301-690x277.png?400|}}
 ===== Introduction =====
-The VE.Bus Smart dongle is a Bluetooth Smart enabled VE.Bus interface, with battery temperature-and-voltage sensor. It communicates system information straight to your smart phone - using the free-to-use //VictronConnect// app.
+The VE.Bus Smart dongle is a Bluetooth Smart enabled VE.Bus interface, with battery temperature-and-voltage sensing. It communicates system information straight to your smart phone - using the free-to-use [[https://www.victronenergy.com/support-and-downloads/software#victronconnect-app|VictronConnect app]].
-When used with Multi- inverter/chargers the dongle provides //on-battery// temperature and voltage sensing capabilities - allowing compensation for possible cable losses which can occur during charging and discharging; and it allows temperature-compensation.  On MultiPlus-II models the dongle is, at present, the //only// way to add an "on-battery" sensing capability.
+{{:img_4353.png?200|}}
-The dongle can be used in systems with or without a Venus device - such as the CCGX. In systems //with// a Venus device, the dongle will not override temperature and voltage information already being supplied by the Venus device - in this rôle the dongle will provide live-information via its VictronConnect interface; and it will provide no-internet firmware updates.
+When used with Multi- inverter/chargers the dongle provides //on-battery// temperature and voltage sensing capabilities - allowing compensation for possible cable losses which can occur during charging and discharging. Temperature sensing allows accurate temperature-compensation during battery charge cycles. The dongle is, at present, the //only// way to add an "on-battery" sensing capability to the MultiPlus-II models, if they are not also connected to a [[venus-os:start|Venus-device]] and CANbus battery.
-When the dongle is used in systems which //do not// have a Venus device, the dongle's voltage and temperature data becomes the primary source of that information, and can be used by other connected devices for voltage compensation. Thus, the VE.Bus Smart dongle can be part of a VE.Smart network ...sending voltage and temperature data to other Smart network devices.
+The dongle can be used in systems with or without a [[venus-os:start|Venus-device]] - such as the CCGX. In systems //with// a [[venus-os:start|Venus-device]], and another source of temperature and voltage data (eg from a CANbus battery), the CCGX data will override temperature and voltage information from the dongle. In this role the dongle will still provide live-information via its VictronConnect interface; and it will provide firmware updates without requiring an internet connection.
-The VE.Bus Smart dongle is able to receive its temperature data in two ways: The default source of information is the dongle's on-board temperature sensor: when the dongle is mounted directly onto the battery case (using its adhesive attachment) it will sense the battery temperature from the battery casing. However,improved battery temperature sensing is available by using an optional //battery-terminal// mounted sensor. If connected, the dongle will automatically detect this sensor, and use its temperature readings instead.
+When the dongle is used in systems which //do not// have a [[venus-os:start|Venus-device]], the dongle's voltage and temperature data becomes the primary source of that information, and can be used by other connected devices for voltage compensation.
+In systems with a Multiplus-II, dongle and [[venus-os:start|Venus-device]], but no other source of temperature and voltage, the data from the dongle will also be used.
+At this time, the VE.Bus Smart dongle cannot send its temperature and voltage data as part of a [[https://www.victronenergy.com/live/victronconnect:ve-smart-networking|VE.Smart network]].
+The VE.Bus Smart dongle is able to sense battery temperature in two ways: The default method is the dongle's on-board temperature sensor. When the dongle is mounted directly onto the battery case (using its adhesive attachment) it will sense the battery temperature directly from the battery casing. The second method - which provides improved battery temperature sensing - is available by using an optional //battery-terminal// mounted sensor. When this sensor is connected, the default sensor is overridden and the dongle will use this method instead.
 ===== What's in the box =====
   - VE.Bus Smart Dongle
@@ Line 26: / Line 30: @@
 ===== Installation =====
-Installation without battery sensor:
+**Installation without battery sensor**:
   - Connect the red connection wire to the B+ input on the connection block
   - Connect the black connection wire to the B- input on the connection block
-  - Connect the two eyelets to your battery terminal. Red wire eyelet on bat+ , black wire eyelet on bat-
+  - Connect the two eyelets to your battery terminals. Red wire eyelet on bat+ , black wire eyelet on bat-
-  - Mount the dongle on or near the battery using the dongle's adhesive mounting. If mounted near the battery, screws can be used.
+  - For battery temperature sensing, mount the dongle on or near the battery using the dongle's adhesive mounting. If mounted near the battery, screws can be used.
   - Plug the connector block into the dongle.
   - Connect the dongle to the Multi's Ve.Bus interface, using a standard RJ45 UTP cable
-Installation with battery terminal temperature sensor:\\
+{{:ve.bus:smart_vebus_dongle_-_2018-10-17.png?direct&600|}}
+**Installation with battery terminal temperature sensor**:\\
 The battery temperature sensor replaces the included red battery(+) connection wire.
   - Connect the temperature sensor's red  connection wire to the B+ input on the connection block
@@ Line 43: / Line 50: @@
   - Plug the connector block into the dongle.
   - Connect the dongle to the Multi's Ve.Bus interface, using a standard RJ45 UTP cable
 ===== System requirements =====
@@ Line 62: / Line 68: @@
 When the LEDs are alternating quickly for more than 30 seconds, the //Ve.Bus Smart// is in firmware update mode and will need to complete the update before it can be used. Firmware updates are performed (where necessary) after connecting to VictronConnect.
+{{:img_4337.png?200|}}
 ^ Blue LED       ^ Red LED          ^ Ve.Bus Smart dongle state ^ Connection State ^ Remark  ^
@@ Line 73: / Line 80: @@
 ===== Modes of operation ====
-As indicated in the introduction the dongle can operate in "primary" or "secondary" mode. The mode depends on the availability of a Venus device. Due to restrictions in the VeBus communication protocol only one device can access data such as power readings.A Venus device has priority over the dongle and should always be able to access all data. When power is applied to the dongle - or after a firmware update - the dongle will startup in "secondary" mode. VE.Bus communication will be monitored for 30 seconds. If during this time no Venus device is detected the dongle will switch to "primary" mode and all supported data will be available. While switching modes VictronConnect will temporarily indicate an "unknown" VE.Bus state. The dongle continuously monitors Venus device activity on the VE.Bus. As soon as Venus device is detected it will switch back to "secondary" mode.
+The dongle can operate both as a //primary// and a //background// information source. It will assume either role automatically depending on whether a [[venus-os:start|Venus-device]] (CCGX/VenusGX/OctoGX) is present in the system.
-Likewise the dongle also monitors VE.Bus communication in order to discover if a Venus device supplies the Multi with battery voltage and temperature data. It takes around 4 minutes after power on, or reset, before the dongle decides whether or not to transmit the battery voltage and temperature.
+Due to restrictions in the VE.Bus communication protocol only one device can access data such as power readings.
-When no Multi is connected the dongle will be shown as VeBus Smart dongle only. In this case the dongle can be used as a Voltage/Temperature sensor. VictronConnect will display the dongle in the device list.
+A [[venus-os:start|Venus-device]] has priority over the dongle and should always be able to access all data. When power is applied to the dongle - or after a firmware update - the dongle will startup in //background// mode. VE.Bus communication ports will be monitored for 30 seconds. If during this time no [[venus-os:start|Venus-device]] is detected the dongle will switch to //primary// mode, and all supported data will be available. While switching modes //VictronConnect// will temporarily indicate an "unknown" VE.Bus state. The dongle continuously monitors [[venus-os:start|Venus-device]] activity on the VE.Bus. As soon as a [[venus-os:start|Venus-device]] is detected it will switch itself to //background//  mode.
-It takes a bit of time before a Multi is detected. When the dongle detects a Multi, it will show the Multi product ID. VictonConnect will than display the Multi in the Device list.
-Shortly after updating the firmware in VictronConnect only the dongle will show up in the device list. If connected, a re-scan will reveal the Multi.
+Likewise, the dongle also monitors VE.Bus communication in order to discover if a [[venus-os:start|Venus-device]] is supplying the //Multi// with battery voltage and temperature data. It takes around 4 minutes after power on, or reset, before the dongle decides whether or not to transmit the battery voltage and temperature.
-===== Troubleshooting =====
+When no //Multi// is connected //VictronConnect// will list the 'VE.Bus Smart Dongle' in the device list. In this case the dongle can be used as a Voltage/Temperature sensor.
-See both the [[victronconnect:start|VictronConnect manual]] and the [[victronconnect:ve-smart-networking|VE.Smart Network manual]].
+{{:victronconnect:vc_vebus_dongle_3.jpeg?direct&200|}}
+It takes a bit of time before a Multi is detected. When the dongle detects a Multi, //VictonConnect// will identify the Multi in the Device list.
+Shortly after updating the firmware in //VictronConnect// only the dongle will show up in the device list. If connected, a re-scan will reveal the //Multi//.
+===== Victron Connect Screenshots =====
+{{:victronconnect:vc_vebus_dongle_6.jpeg?direct&200|}}
+{{:victronconnect:vc_vebus_dongle_5.jpeg?direct&200|}}
+{{:victronconnect:vc_vebus_dongle_4.jpeg?direct&200|}}
+{{:victronconnect:vc_vebus_dongle_2.jpg?direct&200|}}
+{{:victronconnect:vc_vebus_dongle_1.jpeg?direct&200|}}
+===== Troubleshooting =====
+See both the [[victronconnect:start|VictronConnect manual]] and the [[victronconnect:ve-smart-networking|VE.Smart Network manual]].