| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
| vebus_smart_dongle_manual [2021-02-14 13:02] – [System requirements] guystewart | vebus_smart_dongle_manual [2021-03-20 03:25] – guystewart |
|---|
| 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|GX device]] and CANbus battery. | 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|GX device]] and CANbus battery. |
| |
| The dongle can be used in systems with or without a [[venus-os:start|GX device]] - such as the CCGX. In systems //with// a [[venus-os:start|GX 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 dongle can be used in systems with or without a [[venus-os:start|GX device]] - such as the Cerbo GX. In systems //with// a [[venus-os:start|GX device]], and another source of temperature and voltage data (eg from a CANbus battery), the GX device 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|GX 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. | When the dongle is used in systems which //do not// have a [[venus-os:start|GX 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. |
| |
| ===== 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-os:start|GX 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|GX device]] (Cerbo GX) 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. |
