User Tools

Site Tools


vebus_smart_dongle_manual

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
vebus_smart_dongle_manual [2018-10-16 22:32]
guystewart [Installation]
vebus_smart_dongle_manual [2019-06-24 14:54]
jpasop Moved system requirements to the top of the manual
Line 1: Line 1:
 ====== VE.Bus Smart Dongle - manual ====== ====== VE.Bus Smart Dongle - manual ======
  
-Work in progress. This page contains input for the user manual 
 {{:​benh7ta_79897301-690x277.png?​400|}} {{:​benh7ta_79897301-690x277.png?​400|}}
 +
 +===== System requirements =====
 +**Multi firmware versions before 415 are not supported**
 +
 +^ Function ​                                           ^ Minimum Multi firmware version ^ Note ^
 +| Battery voltage and temperature sense               | 419                            |      |
 +| Input current limit and on/​off/​charger only control | 415                            | Not supported when a DMC and/or VeBus BMS is installed | 
 +
 ===== Introduction ===== ===== Introduction =====
  
Line 9: Line 16:
 {{:​img_4353.png?​200|}} {{:​img_4353.png?​200|}}
  
-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. ​ On MultiPlus-II models the dongle is, at present, the //only// way to add an "​on-battery"​ sensing capability.+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. 
 + 
 +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. 
 + 
 +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
  
-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 role the dongle will provide live-information via its VictronConnect interface; and it will provide no-internet firmware updates+In systems with a Multiplus-II,​ dongle and [[venus-os:​start|Venus-device]]but no other source of temperature and voltagethe data from the dongle will also be used
  
-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.+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. ​ 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. ​
Line 47: Line 58:
   - Plug the connector block into the dongle. ​   - Plug the connector block into the dongle. ​
   - Connect the dongle to the Multi'​s Ve.Bus interface, using a standard RJ45 UTP cable   - Connect the dongle to the Multi'​s Ve.Bus interface, using a standard RJ45 UTP cable
-===== System requirements ===== 
- 
-**Multi firmware versions before 415 are not supported** 
- 
-^ Function ​                                           ^ Minimum Multi firmware version ^ Note ^ 
-| Battery voltage and temperature sense               | 419                            |      | 
-| Input current limit and on/​off/​charger only control | 415                            | Not supported when a DMC and/or VeBus BMS is installed |  
  
 ===== LED Status codes ===== ===== LED Status codes =====
Line 77: Line 81:
  
 ===== Modes of operation ==== ===== Modes of operation ====
-The dongle can operate both as a //primary// and a //​background//​ information source. It will assume either role automatically depending on whether a Venus device (CCGX/​VenusGX/​OctoGX) is present in the system. ​+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. ​
  
 Due to restrictions in the VE.Bus communication protocol only one device can access data such as power readings. ​ Due to restrictions in the VE.Bus 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 //​background//​ mode. VE.Bus communication ports 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 a Venus device is detected it will switch itself to //​background// ​ mode.+[[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.
  
-Likewise, the dongle also monitors VE.Bus communication in order to discover if a 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. ​+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. ​
  
 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. ​ 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. ​
Line 104: Line 108:
  
 See both the [[victronconnect:​start|VictronConnect manual]] and the [[victronconnect:​ve-smart-networking|VE.Smart Network manual]]. See both the [[victronconnect:​start|VictronConnect manual]] and the [[victronconnect:​ve-smart-networking|VE.Smart Network manual]].
- 
  
vebus_smart_dongle_manual.txt · Last modified: 2019-08-15 11:50 by guy_stewart