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 [2020-01-15 14:56]
wiebe [5.7 Remote Console on VRM - Trouble shooting]
ccgx:start [2020-10-15 10:37] (current)
ictbeheer Added more vncrelays; load balancing
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 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 148: Line 152:
 Make sure that the canbus is powered, see the [[https://www.victronenergy.com/live/ve.can:ve.can_resistive_tank_sender_adapter#power|Power chapter in the Tank Sender Adapter manual]] for details. Make sure that the canbus is powered, see the [[https://www.victronenergy.com/live/ve.can:ve.can_resistive_tank_sender_adapter#power|Power chapter in the Tank Sender Adapter manual]] for details.
  
-=== 1.4.7 NMEA Tank senders from other manufacturers === 
- 
-A tank sender must meet the following requirements to be visible on the CCGX: 
-  * Transmit the NMEA2000 Fluid Level PGN, 127505 
-  * The NMEA2000 device class needs to be 'General', 80 
-  * The NMEA2000 function needs to be 'Transducer', 190 
- 
-Since v2.17 the following functions are accepted as well: 
-  * The NMEA2000 device class 'General', 80 and function 'Sensor', 170 
-  * The NMEA2000 device class 'Sensors', 75 and 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 from the CCGX - 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 NMEA200, 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. 
  
 ==== 1.5 Connecting a PV Inverter ==== ==== 1.5 Connecting a PV Inverter ====
Line 218: Line 204:
 === 1.6.2 Wi-Fi USB dongle === === 1.6.2 Wi-Fi USB dongle ===
  
-Using a Wi-Fi dongle it is possible to connect to WEP, WPA and WPA2 secured networks. There are four supported USB Wi-Fi dongles. Two of them are also available from stock at Victron Energy:+Using a Wi-Fi dongle it is possible to connect to WEP, WPA and WPA2 secured networks. There are five supported USB Wi-Fi dongles. Two of them are also available from stock at Victron Energy:
  
   * Partno. BPP900100200 - CCGX WiFi module simple (Nano USB), small, low cost.   * Partno. BPP900100200 - CCGX WiFi module simple (Nano USB), small, low cost.
Line 312: Line 298:
 See [[ccgx:fischer_panda|]]. See [[ccgx:fischer_panda|]].
  
-==== 1.9 Connecting NMEA-2000 tank senders ====+==== 1.9 Connecting third-party NMEA-2000 tank senders ====
  
-thrid party NMEA2000 tank sender must meet the following requirements to be visible on the GX Device:+third party NMEA2000 tank sender must meet the following requirements to be visible on the GX Device:
   * Transmit the NMEA2000 Fluid Level PGN, 127505   * 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).   * 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).
Line 320: Line 306:
 A single function reporting multiple Fluid Levels is currently not supported. 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.+For some tank senders it is also possible to configure the capacity and the fluid type on the GX Device menus - 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]]. +Tested compatible NMEA2000 tank senders:
- +
-Alternatively, instead of a VE.Can to NMEA200, 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 NMEA2000 tank senders:+
  
   * Maretron TLA100   * Maretron TLA100
-  * 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.+  * Maretron TLM100 
 +  * Navico Fluid Level Sensor Fuel-0 PK, partno. 000-11518-001. Note that you need a Navico display to configure the Capacity, Fluid type, and other parameters of the sensor. **See voltage warning below** 
 +  * Oceanic Systems (UK) Ltd (OSUKL) - 3271 Volumetric Tank Sender. In case it doesn’t work, it needs a firmware update. Contact OSUKL for that. **See voltage warning below** 
 +  * Oceanic Systems UK Ltd (OSUKL) - 3281 Water Level Sender. **See voltage warning below**
  
 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]]. 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 sensors ====+To connect an NMEA2000 network to the VE.Can port on the CCGX, which both have different type connectors, there are two solutions: 
 + 
 +  - The [[https://www.victronenergy.com/cables/ve-can-to-nmea2000-cable|VE.Can to NMEA2000 cable]]. Which by either inserting or leaving out  the fuse allows to either power the NMEA2000 network with Victron equipment, or not. Take note of below warning. 
 +  - The [[https://osukl.com/ve-can-adaptor/|3802 VE.Can Adapter by OSUKL]]. Its advantage is that it lends itself well to connecting a single NMEA-2000 device such as a tank sender into a VE.Can network. It's also able to power a lower voltage NMEA-2000 network directly from a 48V Victron system. 
 + 
 +**Warning and solution for 24V and 48V systems** 
 + 
 +Whilst all Victron components can work up to 70V input on their CAN-bus connections, Oceanic and Navico senders cannot. They require a 12V powered NMEA2000 connection, as that is what they use to power their sensor circuitry. See above 3802 VE.Can Adapter by OSUKL for a solution. 
 +==== 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
  
-__Compatibility and wiring__+  * Extension cabling has appropriate shielding and twisted pair cores
  
-The compatible types are the [[https://www.imt-solar.com/fileadmin/docs/en/products/Si_Instruction_digital_2017_E.pdf|Si-RS485TC Series]]. The optional wind and temperature sensor are also supported.+  * 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
  
-The sensor is connected using RS485 wiring, and requires our [[https://www.victronenergy.com/accessories/rs485%20to%20usb%20interface|USB to RS485 accessory cable]].+  * Cabling is installed separated/away from the main DC or AC power cabling
  
-Follow this diagram for the connection of the Sensor to the GX device's USB port, via the RS-485 to USB interface.+  * All wiring is properly terminated (including unused wires) and properly isolated from weather/water ingress
  
-{{:ccgx:sensordiagram.jpg?direct|}}+  * 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).
  
-The Si-Sensor needs to be powered with 12 to 28V DC supplyIf the system voltage will exceed this (eg 24V or 48V systems) then use a [[https://www.victronenergy.com/dc-dc-converters/orion-24-12-5-10|nonisolated 24V to 24V DCDC Converter]], or [[https://www.victronenergy.com/dc-dc-converters/orion-tr-dc-dc-converters-isolated|isolated 48V to 24V DCDC Converter]], with its input in parallel to the GX Device, and output connected to Si-Sensor. +=== 1.10.5 Multiple Sensors ===
  
-BEWARE! The maximum input voltage is 28Vwhich is too low for 24V battery system (normally up to 28.8V or more), so it is recommended to use an Orion DCDC Converter.+It is possible to connect multiple IMT Si-RS485 series solar irradiance sensors to a common Victron GX devicehowever 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).
  
-__Wire connections__+=== 1.10.6 Configuration ===
  
-^ Si-Sensor ^ RS 485 interface ^ Signal ^ Note ^ +There is normally no need for any special/additional configuration – the default ‘as shipped’ configuration is compatible for communication with a Victron GX device.
-|Black | Black | Minus | Connect to GX Device minus as well.+
-|Brown | Orange | RS485 Data A + | |  +
-|Orange | Yellow | RS485 Data B - | |  +
-|Black (thick) | | Ground | Ground| +
-|Red | | Power positive (12/24V)| Connect to either battery or output of DCDC Converter|+
  
-Make sure all unused wires of the RS485 USB interface are terminated in an isolated manner. The data sheet for the [[http://www.farnell.com/datasheets/652302.pdf?_ga=2.109087045.1341578072.1576877093-346170190.1576877093&_gac=1.114585333.1576877093.CjwKCAiA__HvBRACEiwAbViuU6u5HSgNPlrACh3Qrw5A5ugDJSgYqGM6xd03nfJ0i6vuY-wIwTncoRoComkQAvD_BwE|RS485 to USB adapter is here]]+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.
  
-__Isolated RS485 to USB Adapters__ +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)
  
-In some applications it may be necessary to use an isolated RS485 interface (eg positive ground systems). +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.
-You must use the USB485-STIXL : Isolated USB to RS485 converter from [[https://hjelmslund.eu/default.asp|Hjelmslund Electronics]]. Don't use any others, they will not be recognised by the GX Device.+
  
-__Configuration of the sensor__+=== 1.10.7 User Interface - GX Device ===
  
-Normally, the Sensor should work out of the box. In case it does not, for example when the sensor has previously been used in another system, then:+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.
  
-  - Download the Si-MODBUS-Configuration software tool from the IMT website. +{{ :ccgx:imt_solar_-_device_list.png?direct&400 |}}
-  - Configure the following settingsModbus Address 3, Baud Rate: 9600, Data Format: 8N1 (10 Bit).+
  
-For more support on configuring the IMT sensor, [[https://imtsolar.com/contact/|please contact IMT]].+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.
  
-__Connecting multiple IMT sensors__+{{ :ccgx:imt_solar_-_main_menu.png?direct&400 |}}
  
-It'possible to connect multiple IMT sensors. A separate USB to RS485 converter cable is required for each sensor.+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.
  
-You can't combine multiple Si-Sensor RS485 sensors on one bus, our software supports only one. To use multiple sensors, you will also need to add multiple USB to RS485 converters+{{ :ccgx:imt_solar_-_settings_menu.png?direct&400 |}} 
-   +{{ :ccgx:imt_solar_-_manual_enable_disable_menu.png?direct&400 |}}
-__Usage__+
  
 +=== 1.10.8 Data Visualisation - VRM ===
  
-{{ :ccgx:imt-main-menu.png?400 |}}+To review logged historical data on the VRM portal, expand the ‘Meteorological Sensor’ widget list and select the ‘Meteorological Sensor’ widget.
  
-{{ :ccgx:imt-settings.png?400 |}}+{{ :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.
  
-This picture shows how its visualised on VRM:+{{ :ccgx:imt_solar_-_vrm_graph.png?direct|}}
  
-{{ :ccgx:imt_visualisation_on_vrm_portal.png?600 |}} 
 ===== 2 Configuration ===== ===== 2 Configuration =====
  
Line 624: Line 670:
 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 738: Line 774:
   * 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
Line 747: Line 784:
 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 939: Line 976:
  
 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 990: Line 1029:
  
 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.
Line 1030: Line 1069:
  
   - Make sure that Logging to the VRM portal works, see chapter 5.4. Without this; Remote Console on VRM will not work.   - 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.   - 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.   - Also make sure to restart the CCGX after setting (or disabling) the password.
Line 1037: Line 1077:
     - [[https://vncrelay.victronenergy.com/|websocket port (443 on vncrelay.victronenergy.com)]].      - [[https://vncrelay.victronenergy.com/|websocket port (443 on vncrelay.victronenergy.com)]]. 
     - [[https://vncrelay2.victronenergy.com/|websocket port (443 on vncrelay2.victronenergy.com)]].     - [[https://vncrelay2.victronenergy.com/|websocket port (443 on vncrelay2.victronenergy.com)]].
 +    - [[https://vncrelay3.victronenergy.com/|websocket port (443 on vncrelay3.victronenergy.com)]].
 +    - [[https://vncrelay4.victronenergy.com/|websocket port (443 on vncrelay4.victronenergy.com)]].
 +    - [[https://vncrelay5.victronenergy.com/|websocket port (443 on vncrelay5.victronenergy.com)]].
  
 === Technical background === === 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. 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.+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 multiple IP addresses (84.22.108.49, 84.22.107.120, 3.25.10.245, 13.244.154.199 or 35.165.124.40, depending on where you are), 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 the 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.+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.
  
 When using Remote Console on VRM, the browser will connect to either vncrelay.victronenergy.com, or vncrelay2.victronenergy.com, using websockets on port 443. When using Remote Console on VRM, the browser will connect to either vncrelay.victronenergy.com, or vncrelay2.victronenergy.com, using websockets on port 443.
Line 1077: Line 1120:
  
 Required components: 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://www.victronenergy.com/live/venus-os:mfd-garmin|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]]   * [[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. Marine MFD integration by NMEA 2000 ===== ===== 7. Marine MFD integration by NMEA 2000 =====
  
-Since Venus OS v2.40, our GX Devices feature an NMEA 2000-out function. This section will be expanded laterfor now read [[https://www.victronenergy.com/blog/2019/12/11/venus-os-v2-40-nmea2000-out-solar-irradiance-and-more/|the v2.40 blogpost]].+==== 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 featureand 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. 
 + 
 +Battery temperature as measured by the inverter(/charger) is transmitted as well. 
 + 
 +All VREG communications need to be sent to be sent to the address representing the Inverter function. The other one, AC input, does not support VREG requests: that address only transmits AC information related to the AC input. 
 + 
 +=== 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 === 
 + 
 +Supported. Battery related values as well as the PV Array Voltage & Current is made available on the NMEA2000 network. 
 + 
 +=== Tank level data ===  
 + 
 +Supported. Tank levels measured by the GX Device are transmitted on PGN xyz (todo) 
 + 
 +=== 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 Configuration ==== 
 + 
 +{{ :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 | 
 +| NMEA2000-out |  Off  | Enables and disables the NMEA2000-out function | 
 +| Unique identity number selector |  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. For more details regarding the Unique identity number, read the last section in this chapter. | 
 +| 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 Configuring device instances ==== 
 + 
 +The Devices submenu gives access to a list showing all detected Devices on the VE.Can / NMEA-2000 network: 
 + 
 +{{ :ccgx:devices_submenu.png?nolink |}} 
 + 
 +Each entry first shows the name - either the product name as in our database, or when configured, the custom name as configured during installation. 
 + 
 +Then, between the square brackets, the Unique Identity Number is shown. 
 + 
 +On the right, you can see the VE.Can Device Instance which is the same as the NMEA-2000 Device Instance. 
 + 
 +Press enter to Edit that Device Instance. Or, press the right-key to go one step deeper in the menu structure, to a page that shows all generic data available for that device: 
 + 
 +{{ :ccgx:mppt_can_page.png?nolink |}} 
 + 
 +==== 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 |
  
-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, hereafter referred to as N2K for brevity. 
  
-Compared to the integration using the App, as explained in the previous chapter, integration via N2K offers a more customisable configuration. This being at the cost of more hassle in doing such configuration, as well as making sure all PGNs and fields therein are supported and compatible between the Victron system and the MFD. 
  
 ===== 8 Error Codes ===== ===== 8 Error Codes =====
Line 1108: Line 1368:
   * MPPT Solar Chargers: [[:mppt-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 ==== ==== GX Error #47 - Data partition issue ====
  
Line 1137: Line 1404:
 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. 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.
  
 +==== GX Error #49 - Grid meter not found ====
 +This warning is raised in an ESS system when Grid metering is configured to use an External meter, but no meter is present. This alerts installers and end-users that the system is not correctly configured, or cannot operate correctly because it cannot communicate with the grid meter.
 ===== 9 More information resources ===== ===== 9 More information resources =====
 [[https://www.easy-lms.com/course-34261|{{:ccgx:training_video.jpg|}}]] [[https://www.easy-lms.com/course-34261|{{:ccgx:training_video.jpg|}}]]
   * [[https://www.easy-lms.com/course-34261|CCGX Basic Training Video and Exam]]   * [[https://www.easy-lms.com/course-34261|CCGX Basic Training Video and Exam]]
-  * [[:ccgx:generator_start_stop|CCGX Genset start/stop]] 
   * [[: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.1579096590.txt.gz · Last modified: 2020-01-15 14:56 by wiebe