User Tools

Site Tools


ccgx:start

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
ccgx:start [2019-10-10 16:35]
guy_stewart
ccgx:start [2020-08-05 19:49] (current)
pbu [1.10 Connecting IMT Solar Irradiance, Temperature and Wind Speed Sensors]
Line 34: Line 34:
 ==== 1.3 Power ==== ==== 1.3 Power ====
  
-Power the device using the //Power in V+// connector. It accepts 8 to 70 V DC. The device will not power itself from any of the network connections. Be sure to use a 1A slow blow fuse.+Power the device using the //Power in V+// connector. It accepts 8 to 70 V DC. The device will not power itself from any of the network connections. The supplied DC power cable includes an inline 3.15 A slow blow fuse.
  
 === Powering in systems with VE.Bus BMS === === Powering in systems with VE.Bus BMS ===
Line 43: Line 43:
  
 Or a modification can be done to the RJ45 cabling. See  Or a modification can be done to the RJ45 cabling. See 
-[[ccgx_faq##q20caution_when_powering_the_ccgx_from_the_ac-out_terminal_of_a_vebus_inverter_multi_or_quattro|FAQ Q21]] for more information about this.+[[ccgx_faq##q20caution_when_powering_the_ccgx_from_the_ac-out_terminal_of_a_vebus_inverter_multi_or_quattro|FAQ Q20]] for more information about this
 + 
 +Note that both with or without above modification, powering the monitoring equipment with the AC-out of an inverter/charger (ofcourse) has the disadvantage that all monitoring is shut down when there is a problem that causes the inverter/charger to shut down. Examples are Inverter overload, high temperature or low battery voltage. It is therefore recommended to power the GX device from the battery.
  
 === Isolation === === Isolation ===
Line 68: Line 70:
  
 __Single VE.Bus products__\\ __Single VE.Bus products__\\
-To connect a single VE.Bus product, connect it to one of the VE.Bus sockets on the back of the CCGX. Both sockets are identical, use either one. Use a standard RJ45 UTP cable, see our [[https://www.acceptance.victronenergy.com/information/pricelist|pricelist]].+To connect a single VE.Bus product, connect it to one of the VE.Bus sockets on the back of the CCGX. Both sockets are identical, use either one. Use a standard RJ45 UTP cable, see our [[https://www.victronenergy.com/information/pricelist|pricelist]].
  
 __Parallel, split- and three-phase VE.Bus systems__\\ __Parallel, split- and three-phase VE.Bus systems__\\
Line 77: Line 79:
 __VE.Bus systems with Lithium batteries and a VE.Bus BMS__\\ __VE.Bus systems with Lithium batteries and a VE.Bus BMS__\\
   * Connect the CCGX to the socket labelled ‘MultiPlus/Quattro’, or to one of the Multis/Quattros in the system. Do not connect it to the //Remote panel// socket on the VE.Bus BMS.   * Connect the CCGX to the socket labelled ‘MultiPlus/Quattro’, or to one of the Multis/Quattros in the system. Do not connect it to the //Remote panel// socket on the VE.Bus BMS.
-  * Note that it will not be possible to control the On/Off/Charger Only switch, nor to change the input current limit with the CCGX: these options are automatically disabled in the CCGX menu when a VE.Bus BMS is used. The only way to control a Multi or Quattro when used with a VE.Bus BMS is to add a Digital Multi Control to the system.+  * Note that it will not be possible to control the On/Off/Charger Only switch. This option is automatically disabled in the CCGX menu when a VE.Bus BMS is used. The only way to control a Multi or Quattro when used with a VE.Bus BMS is to add a Digital Multi Control to the system. Setting the input current limit is possible in systems with a VE.Bus BMS.
   * Combining MultiPlus/Quattro with a VE.Bus BMS and a Digital Multi Control is possible. Simply connect the Digital Multi Control to the RJ-45 socket on the VE.Bus BMS labelled //Remote panel//.   * Combining MultiPlus/Quattro with a VE.Bus BMS and a Digital Multi Control is possible. Simply connect the Digital Multi Control to the RJ-45 socket on the VE.Bus BMS labelled //Remote panel//.
   * To allow auto-power-down in the CCGX in case of a low battery, make sure the CCGX is powered via the VE.Bus BMS: connect //Power in V+// on the CCGX to //Load disconnect// on the VE.Bus BMS. And connect both negative leads to the negative stub of a common Battery.   * To allow auto-power-down in the CCGX in case of a low battery, make sure the CCGX is powered via the VE.Bus BMS: connect //Power in V+// on the CCGX to //Load disconnect// on the VE.Bus BMS. And connect both negative leads to the negative stub of a common Battery.
Line 109: Line 111:
 __Connecting more than two devices to your CCGX using VE.Direct__ __Connecting more than two devices to your CCGX using VE.Direct__
  
-First of all, note that the maximum of VE.Direct devices that can be connected is 5 for the CCGX. How they are connected, so direct, via USB or via CAN, does not change the maximum. See [[venus-os:start|here]] for the Venus GX, Octo GX, and other limits.+First of all, note that the maximum of VE.Direct devices that can be connected is 5 for the CCGX. How they are connected, so direct, via USB or via CAN, does not change the maximum. See [[venus-os:start|here]] for the maximum limit on Venus GX, Octo GX, and other GX Devices. 
 + 
 +Then, these are the options on how to connect more VE.Direct products than available VE.Direct ports:
  
   *Option 1: Use the [[https://www.victronenergy.com/accessories/ve-direct-to-usb-interface|VE.Direct to USB interface]]. The CCGX has two USB ports. Use a USB-hub when more than two USB ports are required.   *Option 1: Use the [[https://www.victronenergy.com/accessories/ve-direct-to-usb-interface|VE.Direct to USB interface]]. The CCGX has two USB ports. Use a USB-hub when more than two USB ports are required.
  
-  *Option 2: The BMV700 and BMV702  can also be connected using the [[https://www.victronenergy.com/accessories/ve-direct-to-ve-can-interface|VE.Direct to VE.Can interface]]. Note that the BMV712, MPPTs and VEDirect Inverters cannot be connected using this canbus interface as it does not translate the data into canbus messages. When using the VE.Direct to VE.Can interface, make sure that the VE.Can network is terminated, and also powered. For powering the VE.Can network, see Q17 in our [[https://www.victronenergy.com/upload/documents/Whitepaper-Data-communication-with-Victron-Energy-products_EN.pdf|data communication whitepaper]].+  *Option 2: (Only!) the BMV700 and BMV702 can also be connected using the [[https://www.victronenergy.com/accessories/ve-direct-to-ve-can-interface|VE.Direct to VE.Can interface]]. Note that the BMV712, MPPTs and VE.Direct Inverters __cannot__ be connected using this canbus interface as it does not translate their data into canbus messages. When using the VE.Direct to VE.Can interface, make sure that the VE.Can network is terminated, and also powered. For powering the VE.Can network, see Q17 in our [[https://www.victronenergy.com/upload/documents/Whitepaper-Data-communication-with-Victron-Energy-products_EN.pdf|data communication whitepaper]]. Lastly, note that this canbus interface is deprecated.
  
 __Notes about older VE.Direct MPPTs__\\ __Notes about older VE.Direct MPPTs__\\
Line 139: Line 143:
 Connect the [[https://www.victronenergy.com/dc-distribution-systems/dc-distribution-systems|DC Link box]], using the RJ-12 cable supplied. Then connect the BMV-700 to the CCGX - see **1.2.2** above for instructions. Connect the [[https://www.victronenergy.com/dc-distribution-systems/dc-distribution-systems|DC Link box]], using the RJ-12 cable supplied. Then connect the BMV-700 to the CCGX - see **1.2.2** above for instructions.
  
-=== 1.2.6 VE.Can Resistive Tank Sender Adapter ===+=== 1.4.6 VE.Can Resistive Tank Sender Adapter ===
 See [[https://www.victronenergy.com/accessories/ve-can-resistive-tank-sender-adapter|its page and manual on our website]] for details about the Adapter. See [[https://www.victronenergy.com/accessories/ve-can-resistive-tank-sender-adapter|its page and manual on our website]] for details about the Adapter.
  
Line 311: Line 315:
  
 See [[ccgx:fischer_panda|]]. See [[ccgx:fischer_panda|]].
 +
 +==== 1.9 Connecting NMEA-2000 tank senders ====
 +
 +A third party NMEA2000 tank sender must meet the following requirements to be visible on the GX Device:
 +  * Transmit the NMEA2000 Fluid Level PGN, 127505
 +  * The NMEA2000 device class needs to either General (80) in combination with function code Transducer (190), or Sensor (170). Or, the NMEA2000 device class needs to be Sensors (75), in combination with function Fluid Level (150).
 +
 +A single function reporting multiple Fluid Levels is currently not supported.
 +
 +For some tank senders it is also possible to configure the capacity and the fluid type on the GX Device - for example the Maretron TLA100. This facility may be available with other senders made by other manufacturers - it's well-worth trying.
 +
 +To connect an NMEA2000 network to the VE.Can port on the CCGX, use a [[https://www.victronenergy.com/cables/ve-can-to-nmea2000-cable|VE.Can to NMEA2000 cable]].
 +
 +Alternatively, instead of a VE.Can to NMEA2000, you can use a 3802 cable from Oceanic Systems: https://osukl.com/ve-can-adaptor/. The difference is that it lends itself well to connecting a single NMEA-2000 device into a VE.Can network. It's also able to power a lower voltage NMEA-2000 network directly from a 48V Victron system.
 +
 +Tested compatible NMEA2000 tank senders:
 +
 +  * Maretron TLA100
 +  * Maretron TLM100
 +  * Navico Fluid Level Sensor Fuel-0 PK, partno. 000-11518-001. Note that this sender requires a 12V powered NMEA2000 network; it breaks when connected to a 24V-powered NMEA2000 network. And note that you need a Navico display to configure the Capacity, Fluid type, and other parameters of the sensor.
 +  * Oceanic Systems (UK) Ltd (OSUKL) - 3271 Volumetric Tank Sender. In case it doesn’t work, it needs a firmware update. Contact OSUKL for that.
 +
 +Most likely others work as well. If you know of one working well, please edit this page -or- get in touch with us on [[https://community.victronenergy.com/spaces/31/index.html|Community -> Modifications]].
 +==== 1.10 Connecting IMT Solar Irradiance, Temperature and Wind Speed Sensors ====
 +
 +=== 1.10.1 Compatibility ===
 +Ingenieurbüro Mencke & Tegtmeyer GmbH (IMT) offer a range of digital silicon irradiance sensor models within the [[https://www.imt-solar.com/fileadmin/docs/en/products/Si-RS485-Selection.pdf|Si-RS485 series]] that are all compatible with a Victron GX device.
 +
 +The optional/additional external [[https://www.imt-solar.com/fileadmin/docs/en/products/Tmodul-Si_E.pdf|module temperature,]] [[https://www.imt-solar.com/fileadmin/docs/en/products/Tamb-Si_E.pdf|ambient temperature]] and [[https://www.imt-solar.com/fileadmin/docs/en/products/vwind-Si_E.pdf|wind speed]] sensors are also supported.
 +
 +Optional/additional external sensors are either connected to the solar irradiance sensor with pre-installed plugs or pre-wired to the solar irradiance sensor (external module and ambient temperature only).
 +When external sensors are connected via an appropriate solar irradiance sensor, all measurement data is transmitted to the Victron GX device with the single interface cable.
 +
 +Each model solar irradiance sensor within Si-RS485 series has a different capability with regards to external sensors (or comes with an external sensor pre-wired), so carefully consider any future desires/requirements before initial purchase.
 +
 +It is also possible to connect an independent [[https://www.imt-solar.com/fileadmin/docs/en/products/Tm-RS485_E.pdf|IMT Tm-RS485-MB module temperature sensor]] (visible as ‘cell temperature’) or [[https://www.imt-solar.com/fileadmin/docs/en/products/Ta-ext-RS485_E.pdf|IMT Ta-ext-RS485-MB ambient temperature sensor]] (visible as ‘external temperature’) directly to the Victron GX device, without a solar irradiance sensor or in addition to one. 
 +
 +=== 1.10.2 Operation ===
 +
 +The IMT Si-RS485 series solar irradiance sensors operate using RS485 electrical interface and [[https://www.imt-solar.com/fileadmin/docs/en/products/Specification_Si-RS485_MODBUS.pdf|Modbus RTU communication protocol.]]
 +
 +The required interface software is pre-installed within the Venus OS, however the Victron GX device must be running recent firmware - FW v2.40 is the minimum requirement.
 +
 +Physical connection to the Victron GX device is via USB port and requires a [[https://www.victronenergy.com/accessories/rs485%20to%20usb%20interface|Victron RS485 to USB interface cable.]]
 +
 +A suitable external DC power source (12 to 28 VDC) is also required - the sensor is NOT powered via USB.
 +
 +=== 1.10.3 Wiring Connections ===
 +
 +The schematic in the installation guide below depicts the wiring configuration in a typical installation.
 +
 +{{:ccgx:imt_si-rs485tc_series_solar_irradiance_sensor_-_victron_installation_guide_v6.png?direct|}}
 +
 +The table below describes the colour and function of each wire in the installation.
 +
 +^ IMT Si-RS485 Series Irradiance Sensor ^ Victron RS485 to USB Interface ^ Description ^
 +| Brown | Orange | RS485 Data + |
 +| Orange | Yellow | RS485 Data - |
 +| Red | - | Power Pos - 12 to 28 VDC |
 +| Black | - | Power Neg/Gnd - 0 VDC |
 +| Black Thick | - | Cable Shield - PE |
 +| - | Red | Power Pos - 5 VDC (not used) |
 +| - | Black | Power Neg/Gnd - 0 VDC (not used) |
 +| - | Brown | Terminator 1 - 120R (not used) |
 +| - | Green | Terminator 2 - 120R (not used) |
 +
 +=== 1.10.4 Installation Notes ===
 +
 +**1-** The maximum DC power supply voltage permitted for the IMT Si-RS485 series solar irradiance sensor range is 28.0 VDC - accordingly for 24 V and 48 V battery banks/systems an appropriate [[https://www.victronenergy.com/dc-dc-converters|Victron DC-DC converter]] (24/12, 24/24, 48/12 or 48/24) or AC-DC adaptor must be utilised in the installation.
 +
 +For 12 V battery banks/systems the IMT Si-RS485 series solar irradiance sensor range may be powered directly from the battery bank and will continue to operate down to minimum voltage of 10.5 V (as measured at the sensor, account for voltage drop in the cable).
 +
 +**2-** For detailed wiring/installation notes and specifications refer to the [[https://www.imt-solar.com/fileadmin/docs/en/products/Si_Instruction_digital_2017_E.pdf|IMT Si-RS485 series solar irradiance sensor 'Quick Reference Guide']] and [[https://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_USB_RS485_CABLES.pdf|Victron RS485 to USB interface cable ‘Datasheet’.]]
 +
 +To ensure signal integrity and robust operation, particularly ensure that;
 +  * Extension cabling complies with the minimum cross-sectional area specifications in the related table - dependent on DC supply voltage and cable length
 +
 +  * Extension cabling has appropriate shielding and twisted pair cores
 +
 +  * The original cable attached to the Victron RS485 to USB interface is reduced to a maximum length of 20cm in installations where the total cable length is over 10m or there are installation/site specific interference issues – in this case appropriate/high quality cabling should be used for the entire cable length, rather than only for the extension length
 +
 +  * Cabling is installed separated/away from the main DC or AC power cabling
 +
 +  * All wiring is properly terminated (including unused wires) and properly isolated from weather/water ingress
 +
 +  * The sensor housing is not opened or tampered with during installation - as sealing integrity will be compromised (and warranty void)
 +
 +**3-** The IMT Si-RS485TC series solar irradiance sensor includes internal Galvanic Isolation (up to 1000V) between power supply and RS485 Modbus circuits, accordingly the non-isolated Victron RS485 to USB interface is suitable for most installations.
 +
 +However, if an isolated RS485 to USB interface is preferred the only compatible device is [[https://hjelmslund.eu/Files/Product%20sheet%20-%20USB485-STIXL.pdf|Hjelmslund Electronics USB485-STIXL]] (any others type will not be recognised by the GX device).
 +
 +=== 1.10.5 Multiple Sensors ===
 +
 +It is possible to connect multiple IMT Si-RS485 series solar irradiance sensors to a common Victron GX device, however a dedicated Victron RS485 to USB interface is required for each individual unit.
 +
 +Multiple units cannot be combined on a single interface (as this is not supported by the related Venus OS software).
 +
 +=== 1.10.6 Configuration ===
 +
 +There is normally no need for any special/additional configuration – the default ‘as shipped’ configuration is compatible for communication with a Victron GX device.
 +
 +However, in cases where the IMT Si-RS485 series solar irradiance sensor has been previously used in another system and/or the settings changed for any reason, it is necessary to restore the default configuration before further use.
 +
 +To revise the configuration, download the [[https://www.imt-solar.com/fileadmin/docs/de/produkte/Si-MODBUS-Configurator_0.15.zip|IMT 'Si-MODBUS-Configuration software tool'.]]
 +Follow the instructions in the
 +[[https://www.imt-solar.com/fileadmin/docs/en/products/Si-Modbus-Configurator.pdf|IMT ‘Si Modbus Configurator Documentation’.]] and check/update the following settings:
 +  * MODBUS Address: 1
 +  * Baud Rate: 9600
 +  * Data Format: 8N1 (10 Bit)
 +
 +For further support related to configuration of the IMT Si-RS485 Series irradiance sensors please [[https://www.imt-solar.com/contact/|contact IMT Solar]] directly.
 +
 +=== 1.10.7 User Interface - GX Device ===
 +
 +Upon connection to the Victron GX device and power up the IMT Si-RS485 Series irradiance sensor will be automatically detected within a few minutes and appear in the 'Device List' menu.
 +
 +{{ :ccgx:imt_solar_-_device_list.png?direct&400 |}}
 +
 +Within the ‘IMT Si-RS485 Series Solar Irradiance Sensor’ menu all available parameters will be automatically displayed (dependent on the sensors connected) and update in real time.
 +
 +{{ :ccgx:imt_solar_-_main_menu.png?direct&400 |}}
 +
 +Within the ‘Settings’ sub-menu it is possible to manually enable and disable any optional/additional external sensors that are connected to the IMT Si-RS485 Series irradiance sensor.
 +
 +{{ :ccgx:imt_solar_-_settings_menu.png?direct&400 |}}
 +{{ :ccgx:imt_solar_-_manual_enable_disable_menu.png?direct&400 |}}
 +
 +=== 1.10.8 Data Visualisation - VRM ===
 +
 +To review logged historical data on the VRM portal, expand the ‘Meteorological Sensor’ widget list and select the ‘Meteorological Sensor’ widget.
 +
 +{{ :ccgx:imt_solar_-_widget_selection.png?direct&600 |}}
 +
 +Data from all available sensor types will be automatically displayed in the graph. Individual sensors/parameters can also be disabled/enabled by clicking on the sensor name/legend.
 +
 +{{ :ccgx:imt_solar_-_vrm_graph.png?direct|}}
 +
 ===== 2 Configuration ===== ===== 2 Configuration =====
  
Line 351: Line 492:
 |Language |English |Choose between English, Dutch, Chinese, German, Spanish, French, Italian, Swedish, Turkish and Arabic. | |Language |English |Choose between English, Dutch, Chinese, German, Spanish, French, Italian, Swedish, Turkish and Arabic. |
 |**VRM online portal** ||| |**VRM online portal** |||
-|Log to |Internet |Choose between //no logging//, //logging via the internet// directly to the VRM Portal, and //logging to a microSD card or USB flash drive//. See chapter 2.2 below for more information. | 
 |Log interval |15 minutes |Set to anything between 1 minute and 1 day. Choose longer times on systems with an unreliable connection. Note that this setting does not affect reporting problems and state changes (bulk → absorption) to the VRM Portal. These events initiate an immediate transmission of all parameters. | |Log interval |15 minutes |Set to anything between 1 minute and 1 day. Choose longer times on systems with an unreliable connection. Note that this setting does not affect reporting problems and state changes (bulk → absorption) to the VRM Portal. These events initiate an immediate transmission of all parameters. |
 +|Rest of parameters |See section 5.3, Datalogging to VRM, for more details ||
 |**Wireless AC Sensors** ||| |**Wireless AC Sensors** |||
 |Select the position for each AC sensor (PV Inverter on AC-input 1, 2 or on AC-output). [[:ccgx:ccgx_wireless_ac_sensor|More information about the Wireless AC sensors.]]||| |Select the position for each AC sensor (PV Inverter on AC-input 1, 2 or on AC-output). [[:ccgx:ccgx_wireless_ac_sensor|More information about the Wireless AC sensors.]]|||
Line 388: Line 529:
 When all done, don't forget to change the access level to user when required. When all done, don't forget to change the access level to user when required.
  
-Click the thumbnail below to see the complete menu-tree:+==== 2.2 Battery State of Charge (SOC) ====
  
-{{:ccgx:menustructure_ccgx.jpeg?direct&200  }} +=== 2.2.1 Which device should I use for SOC calculation? ===
-==== 2.4 Battery State of Charge (SOC) ==== +
- +
-=== 2.4.1 Which device should I use for SOC calculation? ===+
 There are three products types that calculate State Of Charge (SOC). The CCGX itself does not calculate SOC, it only retrieves it from the connected devices. There are three products types that calculate State Of Charge (SOC). The CCGX itself does not calculate SOC, it only retrieves it from the connected devices.
  
Line 415: Line 553:
    
  
-=== 2.4.2 The different solutions explained in detail ===+=== 2.2.2 The different solutions explained in detail ===
  
 __(A) Battery and Multi or Quattro (a typical backup system)__ __(A) Battery and Multi or Quattro (a typical backup system)__
Line 474: Line 612:
 Note that the //Battery Monitor// setting in VEConfigure3 is irrelevant. For systems like this, changing this setting will have no effect on the charge - or any other parameters - in this type of system. Note that the //Battery Monitor// setting in VEConfigure3 is irrelevant. For systems like this, changing this setting will have no effect on the charge - or any other parameters - in this type of system.
  
-=== 2.4.3 Notes ===+=== 2.2.3 Notes ===
   * Note that this is all about showing an accurate state of charge to the user, rather than being required for an efficient system. The SOC percentage is not used for battery charging. It is, however, required when a generator needs to be started and stopped automatically based on battery SOC.   * Note that this is all about showing an accurate state of charge to the user, rather than being required for an efficient system. The SOC percentage is not used for battery charging. It is, however, required when a generator needs to be started and stopped automatically based on battery SOC.
   * For hub-2 installations we recommend you do **not** add a BMV to the system as it will only confuse the user when there are two SOCs with different readings being displayed.   * For hub-2 installations we recommend you do **not** add a BMV to the system as it will only confuse the user when there are two SOCs with different readings being displayed.
Line 482: Line 620:
   * [[ccgx:start#configurable_parameters|CCGX Manual - configurable parameters]]. See Battery Monitor selection and Has DC System.   * [[ccgx:start#configurable_parameters|CCGX Manual - configurable parameters]]. See Battery Monitor selection and Has DC System.
  
-=== 2.4.4 Selecting SOC source ===+=== 2.2.4 Selecting SOC source ===
  
 (Settings -> System Setup -> Battery monitor) (Settings -> System Setup -> Battery monitor)
Line 511: Line 649:
 A short explanation: the VE.Bus SOC as determined by the Multi or Quattro will be incorrect in above situation. As it will not take the discharge and charge currents by those other DC Loads, and also unmonitored chargers, into account. A short explanation: the VE.Bus SOC as determined by the Multi or Quattro will be incorrect in above situation. As it will not take the discharge and charge currents by those other DC Loads, and also unmonitored chargers, into account.
  
-=== 2.4.5 Details on VE.Bus SOC ===+=== 2.2.5 Details on VE.Bus SOC ===
  
   * While the Inverter/Charger is in bulk, the SOC will not rise above the value as set in VEConfigure3 for the “State of charge when Bulk finished" parameter on the General tab; default 85%. In a system with Solar chargers, make sure that the Absorption voltage as configured in the MPPT is slightly above the same setting in the inverter/charger. The latter needs to recognize that the battery voltage has reached the absorption level. If it doesn’t, the SOC will be stuck at the earlier mentioned End-of-bulk percentage, default 85%.   * While the Inverter/Charger is in bulk, the SOC will not rise above the value as set in VEConfigure3 for the “State of charge when Bulk finished" parameter on the General tab; default 85%. In a system with Solar chargers, make sure that the Absorption voltage as configured in the MPPT is slightly above the same setting in the inverter/charger. The latter needs to recognize that the battery voltage has reached the absorption level. If it doesn’t, the SOC will be stuck at the earlier mentioned End-of-bulk percentage, default 85%.
  
-==== 2.Customize the logo on the Boat & Motorhome page ====+==== 2.Customize the logo on the Boat & Motorhome page ====
  
 It is possible to use a custom logo onto the Boat & Motorhome page. It is possible to use a custom logo onto the Boat & Motorhome page.
Line 544: Line 682:
 Two more examples: (In both cases if you //disable// 'Overrule by remote', setting a current limit in the CCGX will have no effect. And if you //enable// 'Overrule by remote' for both inputs, the current limit set in the CCGX will be applied to both inputs.) Two more examples: (In both cases if you //disable// 'Overrule by remote', setting a current limit in the CCGX will have no effect. And if you //enable// 'Overrule by remote' for both inputs, the current limit set in the CCGX will be applied to both inputs.)
  
-=== Systems where it is not possible to control the input current limit === 
-It is not possible to control the input current limit in certain installations. In these cases, the CCGX menu will not allow changing the setting: 
-  - Installations with a VE.Bus BMS 
-  - Installations with a Digital Multi Control (or its predecessors) 
-{{:ccgx:ccgx_inverter_switch_disabled.png?nolink|}} 
-{{:ccgx:ccgx_inverter_currentlimit_disabled.png?nolink|}} 
- 
-Also the //on/off/charger only// switch in the CCGX will be disabled in the case. 
- 
-In installation with a VE.Bus BMS, use the rocker switch instead - or add a Digital Multi Control to the installation. 
  
 === Minimum input current limit values === === Minimum input current limit values ===
Line 569: Line 697:
 The AC supply, either Generator or Grid, to a three phase inverter/charger system needs to be in the correct rotation, also known as sequence. If not, then the Inverter/chargers will not accept the AC supply and remain in Inverter mode. The AC supply, either Generator or Grid, to a three phase inverter/charger system needs to be in the correct rotation, also known as sequence. If not, then the Inverter/chargers will not accept the AC supply and remain in Inverter mode.
  
-The ''Phase rotation warning'' will be raised in such case. To resolve the issue, change the wiring on the AC input: swap either one of the phases, effectively changing the rotation from ''L3 -> L2 -> L1'' to ''L1 -> L2 -> L3''.+The ''Phase rotation warning'' will be raised in such case. To resolve the issue, change the wiring on the AC input: swap either one of the phases, effectively changing the rotation from ''L3 -> L2 -> L1'' to ''L1 -> L2 -> L3''. Or reprogram the Multis and modify the phase assigned to match the wiring
  
 On the GX device itself, the warning will be popup as a notification on the GUI: On the GX device itself, the warning will be popup as a notification on the GUI:
Line 585: Line 713:
 And also it will be listed in the Alarm Log on VRM, and an email will be sent; using [[:vrm_portal:alarms#automatic_alarm_monitoring|the VRM Alarm Monitoring system]]. And also it will be listed in the Alarm Log on VRM, and an email will be sent; using [[:vrm_portal:alarms#automatic_alarm_monitoring|the VRM Alarm Monitoring system]].
  
 +==== 3.3 Grid failure monitoring ====
  
 +When this feature is enabled, an alarm is raised when the system hasn't been connected to the AC input configured to be Grid or Shore for more than 5 seconds.
  
 +{{ :ccgx:grid_failure_monitoring.png?nolink&500 |}}
 +
 +The alarm shows as a Notification in the GUI, and as an alarm on the VRM Portal, and is available on ModbusTCP / MQTT.
 +
 +Recommend to use for backup systems. But also for yachts or vehicles on shore power.
 +
 +Note that this settings monitors that the system is connected to grid/shore. Generator monitoring is already available as part of the Generator start/stop function and not part of this.
 +
 +Do not use this feature in systems that use the Ignore AC Input settings in our inverter/chargers: when the system ignores the AC input, ie runs in island mode, as intended, even though grid is available, it will report a grid failure.
 +
 +==== 3.4 Advanced menu ====
 +
 +{{:ccgx:vebus_advanced_page.png?nolink&500 |}}
 +
 +=== Equalisation ===
 +
 +Starts equalisation. See Multi or Quattro documentation for details.
 +
 +=== Redetect system ===
 +
 +Redetects the type of inverter/charger and its features & configuration. Use this feature when, for example, a VE.Bus BMS used to be part of a system, and is no longer.
 +
 +=== System reset ===
 +
 +Restarts the inverter/charger when it has stopped retrying. For example after a (very) heavy overload; or three overloads in a row.
 +
 +=== ESS Relay test ===
 +
 +Shows the status of the ESS Relay test. Only relevant when its an ESS system. See Q9 in the [[https://www.victronenergy.com/live/ess:design-installation-manual#faq|ESS Manual FAQ]] for details
 ===== 4 DVCC - Distributed Voltage and Current Control ===== ===== 4 DVCC - Distributed Voltage and Current Control =====
  
 ==== 4.1 Introduction and features ==== ==== 4.1 Introduction and features ====
  
-Enabling DVCC changes a GX device from a passive monitor into an active controller.+{{ :ccgx:dvcc.png?nolink&480 |}} 
 + 
 +Enabling DVCC changes a GX device from a passive monitor into an active controller. The available features and effects of enabling DVCC depend on the type of battery used. The effect also depends on the installed Victron components and their configuration.
  
-For example, in systems with an intelligent CAN-bus BMS battery connected, the GX receives a Charge Voltage Limit (CVL), Charge Current Limit (CCL), Discharge Current Limit (DCL) from that battery and relays that to the connected inverter/chargers and solar chargers. These then disable their internal charge algorithms and simply do what they're told by the battery. There is no need to set-up charge voltages or choose the charge algorithm type.+**Example 1 - Managed CAN-bus batteries** 
 +For example, in systems with an Managed CAN-bus BMS battery connected, the GX receives a Charge Voltage Limit (CVL), Charge Current Limit (CCL), Discharge Current Limit (DCL) from that battery and relays that to the connected inverter/chargers and solar chargers. These then disable their internal charge algorithms and simply do what they're told by the battery. There is no need to set-up charge voltages or choose the charge algorithm type.
  
-For systems with lead batteries, DVCC offers features such as a configurable system wide charge current limit and shared temperature sense.+**Example 2 - Lead batteries** 
 +For systems with lead batteries, DVCC offers features such as a configurable system wide charge current limit, where the GX device actively limits the inverter/charger in case the solar chargers are already charging at full power. As well as shared temperature sense (STS) and shared current sense (SCS).
  
-As also in above example, the available features and effects of enabling DVCC depend on the type of battery used. The effect also depends on the installed Victron components and their configuration.+This table shows the recommend settings for different battery types:
  
 {{ :ccgx:dvcc_table2.png?nolink&800 |}} {{ :ccgx:dvcc_table2.png?nolink&800 |}}
  
-For the details, carefully study below chapters to fully understand DVCC for a particular system.+Carefully study below chapters to fully understand DVCC for a particular system. 
 + 
 +To enable or disable DVCC, see Settings -> DVCC in the menus: 
 + 
 +{{:ccgx:dvcc-menu.png?400|}}
  
-To enable or disable DVCC, see Settings -> System Setup in the menus. 
 ==== 4.2 DVCC Requirements ==== ==== 4.2 DVCC Requirements ====
  
Line 620: Line 786:
   * MultiGrid: 424   * MultiGrid: 424
   * CCGX / Venus GX: v2.12   * CCGX / Venus GX: v2.12
-  * VE.Direct MPPTs: v1.29 +  * VE.Direct MPPTs: v1.46 
-  * VE.Can MPPT Solar Chargers cannot be used: they do not yet support the new control mechanisms.+  * VE.Can MPPTs with VE.Direct: v1.04 
 +  * Older style VE.Can MPPT Solar Chargers (with the screen) cannot be used: they do not support the new control mechanisms.
   * Lynx Ion + Shunt: v2.04   * Lynx Ion + Shunt: v2.04
   * Lynx BMS: v1.09   * Lynx BMS: v1.09
 +
 +From Venus firmware v2.40, there will be a warning message 'Error #48 - DVCC with incompatible firmware' when one of the devices has an incompatible firmware while using DVCC.
  
 In case of an ESS System, the ESS Assistant needs to be version 164 or later (Released in November 2017). In case of an ESS System, the ESS Assistant needs to be version 164 or later (Released in November 2017).
  
-{{ :ccgx:dvcc_page2.png?nolink |}}+{{:ccgx:dvcc_menu.jpg?direct&500|}}
  
 ==== 4.3 DVCC effects on the charge algorithm ==== ==== 4.3 DVCC effects on the charge algorithm ====
Line 665: Line 834:
 These features apply to all types of systems when DVCC is enabled: with or without ESS Assistant, and with lead or other normal batteries as well as when an intelligent CAN-bus BMS connected battery is installed: These features apply to all types of systems when DVCC is enabled: with or without ESS Assistant, and with lead or other normal batteries as well as when an intelligent CAN-bus BMS connected battery is installed:
  
-=== Limit charge current ===+=== 4.4.1 Limit charge current ===
  
 This is a user-configurable maximum charge current setting. It works across the whole system. MPPT Solar Chargers are automatically prioritized over the mains/generator. This is a user-configurable maximum charge current setting. It works across the whole system. MPPT Solar Chargers are automatically prioritized over the mains/generator.
Line 685: Line 854:
 5) In all situations, the maximum charge limit configured in a device itself, ie. the Charge current limit set with VictronConnect or VEConfigure for the Solar chargers or Inverter/chargers will still be in effect. An example to illustrate this: in case there is only an Inverter/charger in the system, and in VEConfigure is charge current is configured to 50 Amps. And on the GX Device, a limit of 100A is configured, then the working limit will be 50 Amps. 5) In all situations, the maximum charge limit configured in a device itself, ie. the Charge current limit set with VictronConnect or VEConfigure for the Solar chargers or Inverter/chargers will still be in effect. An example to illustrate this: in case there is only an Inverter/charger in the system, and in VEConfigure is charge current is configured to 50 Amps. And on the GX Device, a limit of 100A is configured, then the working limit will be 50 Amps.
  
-=== Shared Voltage Sense (SVS) ===+=== 4.4.2 Shared Voltage Sense (SVS) ===
  
 Works with VE.Bus devices and VE.Direct Solar Chargers. Works with VE.Bus devices and VE.Direct Solar Chargers.
Line 695: Line 864:
 Shared Voltage Sense (SVS) is by default enabled when DVCC is enabled. It can be disabled with a switch in the Settings -> System Setup menu. Shared Voltage Sense (SVS) is by default enabled when DVCC is enabled. It can be disabled with a switch in the Settings -> System Setup menu.
  
-=== Shared Temperature Sense (STS) ===+=== 4.4.3 Shared Temperature Sense (STS) === 
 + 
 +Select the temperature sensor to use; and the GX device will send the measured battery temperature to the Inverter/charger system as well as all connected Solar Chargers. 
 + 
 +Selectable sources for the battery temperature are: 
 + 
 +  * BMV-702 battery monitor 
 +  * BMV-712 battery monitor 
 +  * Lynx Shunt VE.Can battery monitors 
 +  * Temperature inputs on a Venus GX (and same for other GX devices that have a temperature input) 
 +  * Multi/Quattro inverter/charger 
 +  * Solar Chargers (if fitted with a temperature sensor) 
 + 
 +=== 4.4.4 Shared Current Sense (SCS) === 
 + 
 +This feature forwards the battery current, as measured by a battery monitor connected to the GX device, to all connected solar chargers.  
 + 
 +The solar chargers can be configured to use the battery current for its tail current mechanism that ends absorption when the current is below the configured threshold. For more information about that, refer to Solar charger documentation. 
 + 
 +This feature only applies to systems that are not ESS, and/or don’t have a managed battery, since in both of those cases the MPPT is already externally controlled.
  
-tbd+Requires MPPT solar charger firmware v1.47 or newer.
 ==== 4.5 DVCC Features when using CAN-bus BMS Battery ==== ==== 4.5 DVCC Features when using CAN-bus BMS Battery ====
  
Line 745: Line 933:
   * Remote Console on VRM: access and configure your system as if you were standing besides it   * Remote Console on VRM: access and configure your system as if you were standing besides it
   * Remote Firmware updates of connected Solar Chargers and other Victron products.   * Remote Firmware updates of connected Solar Chargers and other Victron products.
 +  * Use of the [[https://www.victronenergy.com/support-and-downloads/software|VRM App for iOS and Android]].
  
 See chapter 1 for how to connect the device to the internet. See chapter 1 for how to connect the device to the internet.
Line 799: Line 988:
  
 This feature, disabled by default, makes the GX device automatically reboot itself in case it has not been able to connect to the VRM Portal. This feature, disabled by default, makes the GX device automatically reboot itself in case it has not been able to connect to the VRM Portal.
 +
 +Please be careful with enabling this feature on ESS systems: when grid connection is lost, and the GX device reboots, the system can loose power when rebooting takes too long (when grid is present, the Multi's or Quattro's will enter passthru)
 ==== 5.4 Trouble shooting data logging ==== ==== 5.4 Trouble shooting data logging ====
  
Line 850: Line 1041:
  
 If a Connection error is shown, the CCGX is not able to contact the VRM database. The connection error will show an error code that indicates the nature of the connectivity problem. Also, details of the error message are shown, to facilitate on site IT experts to diagnose the problem. If a Connection error is shown, the CCGX is not able to contact the VRM database. The connection error will show an error code that indicates the nature of the connectivity problem. Also, details of the error message are shown, to facilitate on site IT experts to diagnose the problem.
-  * Error #150 Unexpected response text: A connection succeeded, but the result was incorrect. This might indicate that a transparent proxy is hijacking the connection. Examples include a WiFi login page or a cellular providers payment page.+  * Error #150 Unexpected response text: The http/https call succeeded, but the response was incorrect. This indicates that there is a WiFi or network login page. Such as seen in Airports, Hotels, Marinas or RV campgrounds some times. There is no solution to make the CCGX work with WiFi network that requires such login page and/or accepting of terms of use.
   * Error #151 Unexpected HTTP Response: A connection succeeded, but the response did not indicate a successful HTTP result code (normally 200). This might indicate that a transparent proxy is hijacking the connection. See #150 above for examples.   * Error #151 Unexpected HTTP Response: A connection succeeded, but the response did not indicate a successful HTTP result code (normally 200). This might indicate that a transparent proxy is hijacking the connection. See #150 above for examples.
   * Error #152 Connection time-out: this could indicate a poor quality internet connection, or a restrictive firewall.   * Error #152 Connection time-out: this could indicate a poor quality internet connection, or a restrictive firewall.
   * Error #153 Connection error: this could indicate a routing problem. For details, check the shown error message: {{ :ccgx:vrm-connection-error.png?nolink |}}   * Error #153 Connection error: this could indicate a routing problem. For details, check the shown error message: {{ :ccgx:vrm-connection-error.png?nolink |}}
 +  * Error #153 Connection problem, and then specifically an SSL related issue, such as in below screenshot: check the date and time setting of the Gx Device, and also the time zone. And check that your router router is not showing a special disclaimer, login or acceptance page, like often seen in airports, hotels and other public wifi. {{ :ccgx:b0942edf-b59c-4054-b503-a42b629ed103.jpeg?400 |}}
   * Error #154 DNS Failure: Make sure that a valid DNS server is configured in the Ethernet or WiFi menu. Typically this is assigned automatically by a DHCP server in a network.   * Error #154 DNS Failure: Make sure that a valid DNS server is configured in the Ethernet or WiFi menu. Typically this is assigned automatically by a DHCP server in a network.
   * Error #155 Routing error: VRM is unreachable. This error occurs if an ICMP error is received indicating that no route exists to the VRM server. Make sure your DHCP server assigns a working default route, or that the gateway is correctly configured for static configurations.   * Error #155 Routing error: VRM is unreachable. This error occurs if an ICMP error is received indicating that no route exists to the VRM server. Make sure your DHCP server assigns a working default route, or that the gateway is correctly configured for static configurations.
Line 870: Line 1062:
   - In VictronConnect, use the GX Log Converter feature to convert them to Excel sheets.   - In VictronConnect, use the GX Log Converter feature to convert them to Excel sheets.
  
-==== 5.6 Remote Console on VRM ====+==== 5.6 Remote Console on VRM - Setup ====
  
 This feature allows full remote control of a GX Device, over the internet: This feature allows full remote control of a GX Device, over the internet:
Line 884: Line 1076:
 {{ :vrm_portal:vrm_remote_console.jpg?direct }} {{ :vrm_portal:vrm_remote_console.jpg?direct }}
  
-Trouble shooting tips:+==== 5.7 Remote Console on VRM - Trouble shooting ====
  
-  - Make sure that basic communication with VRM works, see chapter 5.4. +Follow these steps to trouble shoot Remote Console on VRM 
-  - After enabling the feature, make sure to set (or disable) the password. + 
-  - Also make sure to restart the CCGX.+  - Make sure that Logging to the VRM portal works, see chapter 5.4. Without this; Remote Console on VRM will not work. 
 +  - Note that when logging to the VRM Portal is configured for HTTP (rather than the default HTTPS), extra care is needed: Remote Console on VRM requires outbound access on the HTTPS port 443. Even when VRM Portal logging is configured to use HTTP port 80
 +  - After enabling the Remote Console feature, make sure to have set (or disabled) the password. 
 +  - Also make sure to restart the CCGX after setting (or disabling) the password.
   - Make sure to update the CCGX to the latest firmware version. The last stability improvement for Remote Console was made in version v2.30.   - Make sure to update the CCGX to the latest firmware version. The last stability improvement for Remote Console was made in version v2.30.
   - After the restart, check the Remote Console on VRM status shows online or a port number. In case it says offline, or port number 0, the CCGX was unable to connect to the Remote Console server. This is normally caused by a (company) firewall, blocking the connection. The solution is then to configure an exception rules in the firewall.   - After the restart, check the Remote Console on VRM status shows online or a port number. In case it says offline, or port number 0, the CCGX was unable to connect to the Remote Console server. This is normally caused by a (company) firewall, blocking the connection. The solution is then to configure an exception rules in the firewall.
-  - Verify that your local web browser can access the [[https://vncrelay.victronenergy.com/|websocket port (443 on vncrelay.victronenergy.com]]). If you click that link and get 'Error response, method not allowed', it means the connection between your PC and the VNC relay is workingIf you get a timeout or another (browsererrorthere may be firewall blocking the connection.+  - Verify that your web browser, on which you're using VRM, can access both of below URLs. Click both of the links, to check them. __Note that seeing an Error means that all is OK__. The good error is 'Error response, Error code 405, Method Not Allowed'. If you get a timeout or another (browser) error, there may be a firewall blocking the connection. 
 +    - [[https://vncrelay.victronenergy.com/|websocket port (443 on vncrelay.victronenergy.com)]].  
 +    - [[https://vncrelay2.victronenergy.com/|websocket port (443 on vncrelay2.victronenergy.com)]]. 
 + 
 +=== Technical background === 
 +To have Remote Console on VRM working, your web browser and the GX Device need to have a connection between them. This connection is designed such that it doesn't need any special configuration or opening up of firewalls in almost all situations. The 0.1% of situations where it doesn't work out of the box are, for example, large corporate networks with special security, or long range expensive satellite or radio supported networks, such as seen in rural areas of Africa and other remote areas. 
 + 
 +When Remote Console on VRM is enabled, the GX Device will open and maintain a connection to any of the servers pointed to by supporthosts.victronenergy.com. Which currently resolves to two IP addresses (84.22.107.120 and 84.22.108.49), and likely more in the future. The technology used is ssh, and it will try to connect using port 22, 80 and 443, only one of them needs to work. The reason for it to try all three is that on most networks one of them will be allowed by the local firewall
 + 
 +Once connected to one of the supporthost servers, that reverse ssh tunnel is waiting to be connected from someone needing the connection. Which can be your browser, or a Victron engineer since this same technology is used for the Remote Support functionality; for more information see above.
  
-Remote Console on VRM uses the same reverse SSH tunnel as is used for Remote Support: outbound connection to supporthost.victronenergy.com on port 2280 or 443. It is not necessary to set up port forwarding in routers to use Remote Console on VRM. It is necessary for the firewall/router to which the CCGX is connected, to allow outbound connections to supporthost.victronenergy.com on at least one of the three mentioned port numbers. Most routers will allow this by default.+When using Remote Console on VRMthe browser will connect to either vncrelay.victronenergy.com, or vncrelay2.victronenergy.com, using websockets on port 443.
  
-===== 6. Marine MFD Glass bridge integration =====+For more details of used connections by the GX Device, see [[https://www.victronenergy.com/live/ccgx:ccgx_faq#q15what_type_of_networking_is_used_by_the_color_control_gx_tcp_and_udp_ports|Q15 of the FAQ]]. 
 +===== 6. Marine MFD integration by App =====
  
 ==== 6.1 Introduction & requirements ==== ==== 6.1 Introduction & requirements ====
Line 912: Line 1117:
   * Monitor battery status for one or more batteries. By using the voltage of for example battery chargers, it can also visualise secondary batteries such as Generator starter batteries.   * Monitor battery status for one or more batteries. By using the voltage of for example battery chargers, it can also visualise secondary batteries such as Generator starter batteries.
   * Monitor the power conversion equipment: chargers, inverters, inverter/chargers.   * Monitor the power conversion equipment: chargers, inverters, inverter/chargers.
-  * Monitor solar production from an MPPT.+  * Monitor solar production from an MPPT Solar Charger.
   * Monitor AC loads, and DC loads.   * Monitor AC loads, and DC loads.
   * Control shore power input current limit.   * Control shore power input current limit.
Line 918: Line 1123:
   * Optionally open the Victron Remote Console panel; allowing access to further parameters.   * Optionally open the Victron Remote Console panel; allowing access to further parameters.
  
-Power equipment compatibility:+Victron equipment compatibility:
   * All Victron inverter/chargers: From a 500VA single phase device up to a large 180kVA three phase-system, including Multis, Quattros, 230VAC and 120VAC models.   * All Victron inverter/chargers: From a 500VA single phase device up to a large 180kVA three phase-system, including Multis, Quattros, 230VAC and 120VAC models.
   * Battery Monitors: BMV-700, BMV-702, BMV-712 and newer, Lynx Shunt VE.Can, Lynx Ion BMS.   * Battery Monitors: BMV-700, BMV-702, BMV-712 and newer, Lynx Shunt VE.Can, Lynx Ion BMS.
   * All Victron MPPT Solar Charge Controllers   * All Victron MPPT Solar Charge Controllers
  
-Requirements+Required components: 
-  * Battery system. +  * Victron GX Device (all models are compatible: CCGX, Cerbo GX, Venus GX, and so forth) 
-  * Victron inverter/charger. +  * Battery system 
-  * Victron Battery monitor. +  * Victron Inverter/charger 
-  * Network cable connection between MFD and GX device such as a Color Control GX, Venus GX or an Octo GX. +  * Victron Battery monitor 
-  * UTP network cable.+  * Ethernet network cable connected between MFD and the GX device 
 +  * MFD specific ethernet adapter cable (only for some brands, see detailed information in below links)
  
 ==== 6.2 Compatible MFDs and instructions ==== ==== 6.2 Compatible MFDs and instructions ====
  
-  * [[https://docs.victronenergy.com/gx/mfd-garmin.html|Instructions for Garmin MFDs]] +  * [[https://www.victronenergy.com/live/venus-os:mfd-garmin|Instructions for Garmin MFDs]] 
-  * [[venus-os:mfd-navico|Instructions for Navico MFDs]] (Simrad, B&D, Lowrance) +  * [[venus-os:mfd-navico|Instructions for Navico MFDs]] (Simrad, B&G, Lowrance) 
-  * [[venus-os:mfd-raymarine|Instructions for Raymarine]] - Note support on Raymarine MFDs is pending a Raymarine firmware update. [[https://www.victronenergy.com/blog/|Subscribe to our blog (link at the bottom)]], or for direct customers, monitor our weekly e-mail, to be informed about that release.+  * [[venus-os:mfd-raymarine|Instructions for Raymarine]] 
 +  * [[venus-os:mfd-furuno|Instructions for Furuno]] 
 +==== 6.3 Using the App for other purposes ====
  
 +The App as visible on the MFDs, is a HTML5 App, hosted on the GX Device. It can also be accessed from a normal PC (or a tablet), by navigating to with a browser to: http://venus.local/app/. Or replace venus.local with the GX ip address.
  
-Furuno: support on Furuno MFDs is in the pipeline. There is no expected date of availability. 
  
-===== 7 More information resources ===== +===== 7. Marine MFD integration by NMEA 2000 ===== 
-  * [[:ccgx:generator_start_stop|CCGX Genset start/stop]]+ 
 +==== 7.1 Introduction ===== 
 + 
 +Our GX Devices feature an NMEA 2000-out function: when enabled, the GX Device acts as a bridge: it makes all Battery monitors, Inverter/chargers and other products connected to the GX device available on the NMEA2000 network. 
 + 
 +Using that feature, and having the GX Device connected a NMEA2000 network, Marine MFDs can read this data and visualise it to the user. Often in a highly configurable manner. 
 + 
 +Use our [[https://www.victronenergy.com/cables/ve-can-to-nmea2000-micro-c-male|VE.Can to NMEA2000 micro-C male cable]] to connect the GX Device to the NMEA 2000 network. 
 + 
 +{{:ccgx:ccgx_nmea_mfd2.png?nolink|}} 
 + 
 + 
 +__Comparison to the App integration__ 
 + 
 +Compared to MFD integration using the App, as explained in the previous chapter, integration via N2K offers a more customisable configuration. The downside of integration via N2K is that there is more work in making such configuration, as well as making sure all PGNs and fields therein are supported and compatible between the Victron system and the MFD. 
 + 
 +__More information__ 
 + 
 +Besides this chapter, make sure to also read (1) [[https://www.victronenergy.com/blog/2019/12/11/venus-os-v2-40-nmea2000-out-solar-irradiance-and-more/|the introduction blogpost]], (2) our [[ve.can:nmea-2000:start|main Marine MFD Integration document]] and (3) the NMEA2000 chapter in the Victron manual for the MFD you are using ([[venus-os:mfd-navico|Navico/Simrad/Lowrance/B&G]], or [[venus-os:mfd-raymarine|Raymarine]], or [[venus-os:mfd-garmin|Garmin]], or [[venus-os:mfd-furuno|Furuno]]) 
 + 
 +Yes that is a lot of reading, but that is basically inherent to NMEA2000: for example some of those MFDs support displaying AC data received over the NMEA2000 wiring, others do not. Some require changing Data instances, others do not, and so forth. 
 +==== 7.2 Supported devices / PGNs ==== 
 + 
 +NMEA 2000 defines several messages. Messages are identified by their parameter group number (PGN). A 
 +textual description of the message is publicly available on the NMEA 2000 website (http://www.nmea.org/). 
 + 
 +Detailed specification of the protocol and message definition or part thereof can be ordered online on the NMEA 
 +2000 website. 
 + 
 +NMEA 2000 is based on and compatible with SAE J1939. All AC information messages are in the AC 
 +status message format as defined in J1939-75. The specification of these messages can be bought on the SAE website (http://www.sae.org/). 
 + 
 +For a detailed list of PGNs, please refer to our data communication whitepaper. 
 + 
 +=== Inverter/chargers ==
 + 
 +All inverter/chargers that connect using a VE.Bus port are supported. This includes Multis, Quattros, MultiPlus-IIs, and other (similar) Victron inverter/chargers. 
 + 
 +Data is transmitted out; and its possible to set shore current as well as switch the inverter charger on, off, inverter only and charger only. 
 + 
 +The interface has two functions: 
 + 
 +  - The function, “153 Inverter”, represents the AC-output 
 +  - The function “154 AC Input” monitor represents the AC-input 
 + 
 +Charger Status messages will be sent by the Inverter function. Both functions have their own network address. 
 + 
 +Since both functions transmit the same PGNs, for example an AC Status PGN containing voltage, current and more information, NMEA 2000 data consumers like generic displays will need to be able to make a distinction 
 +based on the network address. Depending on the function belonging to that network address the need to interpret it as either Inverter Input or Inverter Output. Displays not being capable of doing so will regard the data as belonging to the mains (utility). The Inverter Output is then interpreted as utility #0 and Inverter Input as utility #1. These default instance numbers can be changed by a network configuration tool if necessary. 
 + 
 +=== Inverters === 
 + 
 +Only VE.Bus type inverters are supported: any Inverter connected using VE.Direct is not (yet) made available on the N2K bus. 
 + 
 +=== Battery monitors === 
 + 
 +Supported. This includes any battery monitor as supported by the GX Device. 
 + 
 +=== Solar chargers === 
 + 
 +Not yet supported by the NMEA2000-out function but in the works and expected after in a firmware update after the summer of 2020. 
 + 
 +=== Tank level data ===  
 + 
 +Not yet supported by the NMEA2000-out function but in the works and expected after in a firmware update after the summer of 2020. 
 + 
 +=== Other data and product types === 
 + 
 +Not supported. Above explicitly mentioned types are the only ones now supported. For example data from a charger (such as the Phoenix Smart Charger connected via VE.Direct) is not supported and not expected to be supported soon. 
 +==== 7.3 Related menu settings ==== 
 + 
 +{{ :ccgx:can-bus_configuration.png?nolink&600 |}} 
 + 
 +^ Setting ^ Default ^ Description ^ 
 +| CAN-bus Profile |  VE.Can  | Defines the type & baudrate of the CAN-bus network. To use in combination with NMEA2000, make sure to choose one of the profiles that include VE.Can and is at 250kbit/s | 
 +| Send data to VE.Can |  Off  | Enables and disabled the NMEA2000-out function | 
 +| Unique device number |  1  | Selects the block of numbers to use for the NAME Unique Identity Numbers in the PGN 60928 NAME field. For the GX Device itself, and when NMEA2000-out is enabled, also for the virtual-devices. Change it only when installing multiple GX Devices in the same VE.Can network. There are no other reasons to change this number. | 
 +| Check unique numbers |   | Searches for other devices that use the same unique number. When the search is completed it will respond with either an OK, or the text \\ ''There is another device connected with this unique number, please select another one.''. Note that there is normally no reason to use this function: the GX Device automatically and continuously checks uniqueness of the numbers in use, and will warn when in case there is a conflict. This setting is made available to quickly confirm that everything is OK after changing the setting. | 
 + 
 +==== 7.4 NMEA2000-out technical details ==== 
 + 
 +=== 7.4.1 Glossary === 
 + 
 +To make this text good to interpret, here is a glossary of used terms: 
 + 
 +  * Virtual-device: a Battery Monitor, Inverter, or other Victron device that does not have a CAN-bus port by itself, made available "virtually" on the CAN-bus by the NMEA2000-out function of the GX Device. 
 +  * CAN-bus: the VE.Can port on the GX Device, that, in the context of this chapter, is most likely connected to a NMEA2000 network. 
 +  * NMEA2000-out function: the software feature in the GX Device, which is described in this chapter. 
 +  * NMEA2000: Marine CAN-bus protocol, based on J1939. 
 +  * Instance: there are many types of instances, and explained in detail below. 
 +  * J1939: A set of standards defining a CAN-bus protocol, defined by the SAE organisation. 
 +  * Address Claim procedure (ACL): a mechanism, specified by J1939 and used in NMEA2000, which used by devices on the network to negotiate and assign each device on the network a unique network addresses. Its is a number from 0 to 252. There are three special network addresses defined: 
 +    - 0xFD (253) - Reserved 
 +    - 0xFE (254) - Unable to claim address - for example when all others are in use 
 +    - 0xFF (255) - The broadcast address 
 + 
 + 
 +=== 7.4.2 Virtual-devices === 
 + 
 +When the NMEA2000-out feature is enabled, the GX Device acts as a bridge: it will make each Battery monitor, Inverter/charger or other device that is connected, available __individually__ on the CAN-bus. 
 + 
 +Individually, as in each with its own network address, its own device instance, function codes, and so forth. 
 + 
 +For example, a GX Device with two BMVs connected on a VE.Direct port and an inverter/charger connected using VE.Bus, will make the following data available on the CAN-bus: 
 + 
 +^ Address ^ Class ^ Function ^ Description ^ 
 +| 0xE1 | 130 (Display) | 120 (Display) | The GX Device itself | 
 +| 0x03 | 35 (Electrical generation) | 170 (Battery) | The 1st BMV | 
 +| 0xE4 | 35 (Electrical generation) | 170 (Battery) | The 2nd BMV | 
 +| 0xD3 | 35 (Electrical generation) | 153 | The inverter/charger (AC-output) |  
 +| 0xD6 | 35 (Electrical generation) | 154 | The inverter/charger (AC-input) |  
 + 
 +The used network addresses are random examples. Network addresses can change due to the J1939/NMEA2000 Address Claim Procedure (ACL), and they are not and cannot be configured to a permanent value. Even though they might seem fixed, when checking with a NMEA2000 monitoring tool, adding or replacing devices from the system might lead to changes in the network addresses. 
 + 
 +=== 7.4.3 Classes and functions === 
 + 
 +As per NMEA2000 specification, these define the types of senders and devices connected to the CAN-bus. Classes are  the main categories, and functions specify it to a further detail. 
 + 
 +=== 7.4.4 Instances === 
 + 
 +NMEA2000 defines three different instances: 
 + 
 +  - Data instance 
 +  - Device instance 
 +  - System instance 
 + 
 +For all Battery monitors and other devices that the GX Device makes available on the CAN-bus, each of above types of instance is available, and can be individually configured. Per virtual-device, there is one Device instance and one System instance. And depending on the type of the virtual-device, there are one or multiple Data instances. For example, for a BMV-712 there are two data instances, one "DC Instance" for the main battery, and another one for the Starter battery voltage. 
 + 
 +How to configure the instances depends on the equipment and software that is used to read them from the CAN-bus. Examples of equipment and software meant here are MFDs such as from Garmin, Raymarine or Navico; as well as more software oriented solutions from for example Actisense and Maretron. Most, or hopefully all, of those solutions identify parameters and products by requiring unique Device instances, or using the PGN 60928 NAME Unique Identity Numbers. They do not rely on the data instances to be globally unique. 
 + 
 +The NMEA2000 specification specifies the following: "Data instances shall be unique in the same PGNs transmitted by a device. Data instances shall not be globally unique on the network. Field programmability shall be implemented through the use of PGN 126208, Write Fields Group Function.". In other words, data instances need to be unique only within a single device. There is no requirement for them to be globally unique – the only exception is “Engine Instance” that at least for now, to cope with legacy devices, needs to be globally unique (e.g. Port = 0, Starboard  = 1). For example, some of our BMV Battery monitors can measure two voltages, one for the main battery, and one for the starter battery, and thats where data instancing is used. Similar for multiple-output battery chargers. Note that there is no need for the installer to change those data instances, as those products are pre-configured to transmit the relevant PGNs with unique data instances (Battery instance & DC Detailed instance, in this case). 
 + 
 +**WARNING**: whilst it is possible to change the data instances, changing them on a Victron devices will render that device impossible to read correctly by other Victron devices. 
 + 
 +A note about the Device instances: it is not necessary to assign a unique device instance to each device on the CAN-bus. Its no problem for a battery monitor and a solar charger to both be configured with (their default) Device instance 0. Also when having multiple battery monitors or solar chargers, it is not always necessary to assign each of them a unique device instance. If at all necessary, they only need to be unique between the devices that use the same Function. 
 + 
 +And note that changing the Device instance on a Victron device can change its operation, see below. 
 + 
 + 
 + 
 +__System instances__ 
 + 
 +As per NMEA2000 specification, this instance is a 4-bit field with a valid range from 0 to 15 that indicates the occurrence of devices in additional network segments, redundant or parallel networks, or sub networks. The System 
 +Instance Field can be utilized to facilitate multiple NMEA 2000 networks on these larger marine platforms. NMEA 2000 Devices behind a bridge, router, gateway, or as part of some network segment could all indicate this by use and application of the System Instance Field. 
 + 
 +__The ECU instance and Function instance__ 
 + 
 +In some documentation and software tools, yet other terminology is used: 
 + 
 +  * ECU Instance 
 +  * Function Instance 
 +  * Device Instance Lower 
 +  * Device Instance Upper 
 + 
 +Here is how they all relate: the ''ECU Instance'' and ''Function Instance'' terminology originates from the SAE J1939 and ISO 11783-5 specification. And they do not exist in the NMEA2000 definition. However, they all do define the same fields in the same CAN-bus messages which NMEA2000 defines as ''Device instance''
 + 
 +In more detail: the field that J1939 defines as ECU Instance is in the NMEA2000 specification renamed to ''Device Instance lower''. The Function Instance is renamed to ''Device Instance Upper''. And together they form the ''Device Instance'', an NMEA2000 definition. 
 + 
 +While using different terms, those fields **are** the same fields in both standards. Device Instance Lower being 3 bits in length, and Device Instance Upper 5, together 8 bits. Which is the one byte being the NMEA2000 Device Instance. 
 + 
 +__The Unique Instance__ 
 + 
 +The ''Unique Instance'' is one more word used to describe almost the same information. Its used by Maretron, and can be made visible in their software by enabling the column. The Maretron software itself chooses (?) between Device Instance and Data Instance. 
 + 
 +=== 7.4.5 Changing Instances  === 
 + 
 +__Data instance__ 
 + 
 +Even though we recommend to not change data instances (see explanation and WARNING above), it is possible to change them. 
 + 
 +There is no option within Venus OS to change them - a third party tool is required and the only tool that we know can do that is Actisense NMEA2000 reader. 
 + 
 +To change the Data instances, see [[ve.can:changing_nmea2000_instances|this document]]. 
 + 
 +__Device instance__ 
 + 
 +To change the Device instances, see [[ve.can:changing_nmea2000_instances|this document]]. 
 + 
 +WARNING: these (Victron-)features depend on the Device Instance: 
 + 
 +  - For an [[ess:start|ESS system]] with Solar chargers connected on a VE.Can network, those Solar chargers must remain to be configured to their default Device instance (0) for proper operation. This does not apply to VE.Direct-connected Solar Chargers made available on the CAN-Bus as a Virtual-device, using the NMEA2000-out function. Unless the Device instance of the GX Device is re-configured to another Device Instance. Which is technically possible but not advised and also never required. But in that situation the chargers must be configured to the same instance as the GX Device. 
 +  - For systems with managed batteries & DVCC the as above: VE.Can-connected solar chargers will only be included in the DVCC control mechanism when their Device Instance is set to 0. 
 +  - For both Solar chargers, as well as AC-Connected battery chargers, when connected in a VE.Can network, they will synchronise their operation. Charge state and such. For that function to work, all chargers must be configured to the same device instance. 
 + 
 +In summary, for the majority of systems we recommend to leave the Device instance to its default, 0. 
 + 
 +=== 7.4.5 PGN 60928 NAME Unique Identity Numbers === 
 + 
 +The GX Device will assign an individual Unique Identity Number to each virtual-device. The number assigned is a function of the ''PGN 60928 NAME Unique Identity Number block'' aka ''Unique device number for VE.Can'' as in above screenshot, as configured in the settings of the GX Device. 
 + 
 +This table shows how changing that setting translates into the virtual-devices as made available on the CAN-bus: 
 + 
 +^ configured Unique Identity block: ^ 1 ^ 2 ^ 3 ^ 4 |  
 +| GX Device   | 500 | 1000 | 1500 | 2000 | 
 +| 1st virtual-device (for example a BMV) | 501 | 1001 | 1501 | 2001 | 
 +| 2st virtual-device (for example another BMV) | 502 | 1002 | 1502 | 2002 | 
 +| 3st virtual-device (for example a third BMV) | 503 | 1003 | 1503 | 2003 | 
 + 
 + 
 + 
 +===== 8 Error Codes ===== 
 + 
 +==== Different origins of errors ==== 
 + 
 +On your GX device, some error codes shown will be from the GX device itself, in that case see below list. But since its the system control panel, it also shows error codes from the connected devices. 
 + 
 +  * Multi and Quattro inverter/chargers: [[ve.bus:ve.bus_error_codes|]] 
 +  * MPPT Solar Chargers: [[:mppt-error-codes|]] 
 + 
 +==== GX Error #42 - Storage corrupt ==== 
 + 
 +This error means that the flash memory inside the GX Device is corrupt. 
 + 
 +The device must be sent in for repair/replacement. Its not possible to correct this issue in the field or with a firmware update. 
 + 
 +The affected flash memory is the partition that holds all user settings and factory data,  such as serial numbers and wifi codes. 
 +==== GX Error #47 - Data partition issue ==== 
 + 
 +The internal storage in the GX Device is most likely broken: causing it to loose its configuration. 
 + 
 +Contact your dealer or installer; see www.victronenergy.com/support 
 + 
 +==== GX Error #48 - DVCC with incompatible firmware ==== 
 + 
 +This error is raised when the DVCC feature is enabled whilst not all devices in the system are updated to recent enough firmware. More information about DVCC and minimal required firmware versions in chapter 4 of this manual. 
 + 
 +__Note for systems with BYD, MG Energy Systems, and Victron Lynx Ion BMS 
 + batteries:__ 
 + 
 +Since Venus OS v2.40, released in December 2019, the DVCC feature is automatically switched on in case the systems detects one of mentioned battery/BMS types connected. And it is not possible to switch DVCC off in that case. 
 + 
 +This creates an issue for systems installed and commissioned a long time ago, from before DVCC was available and later due to mandatory work for such systems. 
 + 
 +The solution is to: 
 + 
 +  - Disable automatic updates; Settings -> Firmware -> Online updates. 
 +  - Roll back to v2.33; See Settings, Firmware and then Stored backup firmware. 
 +  - Make sure that DVCC is disabled again. 
 + 
 +Please do consult your installer, to check if the battery system is managed with two wire control (no DVCC needed) or not: 
 + 
 +In case there is no charge- and discharge- wiring between BMS, inverter/chargers and charge controllers, then DVCC is required for the above mentioned battery brands, and this also has certain minimum firmware requirements for connected Inverter/Chargers and Solar Charge Controllers. 
 + 
 +Whats new since Venus OS v2.40 is (a) that it automatically enables DVCC when it sees the above mentioned battery types, and (b) that when DVCC is enabled, it checks the connected devices for the minimum firmware, and raises Error #48 in case the firmware of one or more connected devices is too old. 
 + 
 +===== 9 More information resources ===== 
 +[[https://www.easy-lms.com/course-34261|{{:ccgx:training_video.jpg|}}]] 
 +  * [[https://www.easy-lms.com/course-34261|CCGX Basic Training Video and Exam]]
   * [[:ccgx:ccgx_faq|CCGX Frequently asked questions]]   * [[:ccgx:ccgx_faq|CCGX Frequently asked questions]]
   * [[ccgx:firmware_upgrade_to_v2|CCGX Firmware upgrade to v2.00 or later]]   * [[ccgx:firmware_upgrade_to_v2|CCGX Firmware upgrade to v2.00 or later]]
   * [[:ccgx:firmware_updating|CCGX Manually updating firmware]]   * [[:ccgx:firmware_updating|CCGX Manually updating firmware]]
-  * [[:ccgx:ccgx_ve_power_setup|CCGX Remote VEConfigure and remote firmware updates]] 
   * [[https://www.victronenergy.com/upload/documents/Datasheet-Color-Control-GX-EN.pdf|CCGX Datasheet]]   * [[https://www.victronenergy.com/upload/documents/Datasheet-Color-Control-GX-EN.pdf|CCGX Datasheet]]
-  * [[:ccgx:fischer_panda|CCGX & Fischer Panda generators]] +  * [[:ccgx:generator_start_stop|GX - Generator start/stop]] 
-  * [[:vrm_portal:start|VRM Portal]] +  * [[:ccgx:fischer_panda|GX - Fischer Panda generators]] 
-  * [[:vrm_portal:troubleshooting_ccgx_vrm_connectivity#trouble_shooting_remote_console_on_vrm|VRM Portal - trouble shooting Remote Console]]+  * [[:venus-os:gx-gsm|GX GSM]] 
 +  * [[:vrm_portal:start|VRM Portal - manual]] 
 +  * [[:ccgx:ccgx_ve_power_setup|VRM Portal - Remote VEConfigure and remote firmware updates]]
   * [[:ccgx:beta-testing]]   * [[:ccgx:beta-testing]]
   * [[open_source:start]]   * [[open_source:start]]
- 
- 
 ===== DISQUS ===== ===== DISQUS =====
 ~~DISQUS~~ ~~DISQUS~~
ccgx/start.1570718159.txt.gz · Last modified: 2019-10-10 16:35 by guy_stewart