Victron Energy

User Tools

Site Tools

You are here: Documentation » Color Control GX manual
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
Last revision Both sides next revision
ccgx:start [2020-05-06 04:02]
guy_stewart [7.1 Introduction] 		ccgx:start [2020-09-29 17:08]
mvader [7.2 Supported devices / PGNs]
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 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 ====
  
-A thrid party NMEA2000 tank sender must meet the following requirements to be visible on the GX Device:+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   * 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]].
 +
 +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 Connecting IMT Solar Irradiance, Temperature and Wind Speed Sensors ====
  
Line 352: Line 346:
 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. 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 Vicron GX device is via USB port and requires a [[https://www.victronenergy.com/accessories/rs485%20to%20usb%20interface|Victron RS485 to USB interface cable.]]+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. A suitable external DC power source (12 to 28 VDC) is also required - the sensor is NOT powered via USB.
Line 676: 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 1045: 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 a 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 1085: 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 1098: Line 1083:
 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 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 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 1142: Line 1127:
  
   * [[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]]
-Furuno: support on Furuno MFDs is in the pipeline. There is no expected date of availability. +
 ==== 6.3 Using the App for other purposes ==== ==== 6.3 Using the App for other purposes ====
  
Line 1171: Line 1154:
 __More information__ __More information__
  
-Besides this chapter, make sure to also read [[https://www.victronenergy.com/blog/2019/12/11/venus-os-v2-40-nmea2000-out-solar-irradiance-and-more/|the introduction blogpost]], as well as our [[ve.can:nmea-2000:start|main Marine MFD Integration document]]. +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 ==== ==== 7.2 Supported devices / PGNs ====
  
Line 1202: Line 1185:
 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 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. 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 === === Inverters ===
Line 1211: Line 1198:
 Supported. This includes any battery monitor as supported by the GX Device. Supported. This includes any battery monitor as supported by the GX Device.
  
-=== Other data and product types ===+=== Solar chargers ===
  
-Not supported. Above are the only now supported types. For example tank levels are not yet transmitted out on N2K, nor is any data from a charger (such as the Phoenix Smart Charger connected via VE.Direct), and neither is data from solar chargers.+Supported. Battery related values as well as the PV Array Voltage & Current is made available on the NMEA2000 network.
  
-==== 7.3 Related menu settings ====+=== 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 |}} {{ :ccgx:can-bus_configuration.png?nolink&600 |}}
  
 ^ Setting ^ Default ^ Description ^ ^ 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 | +| 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 | +| NMEA2000-out |  Off  | Enables and disables 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. |+| 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. | | 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 NMEA2000-out technical details ====
Line 1274: Line 1284:
 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. 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 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.+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). 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).
Line 1314: Line 1324:
 __Data instance__ __Data instance__
  
-Data instances cannot be changed -at least- at Victron we do not provide a means to do so and also we don't know of any other available tool that allows changing Data instances. Note that as explained above under the WARNING, we also recommend to not change a data instance; since then the information cannot be properly read any more by other Victron devices.+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.
  
-On a more technical note, our products do support to have their data instances changed, by using the CAN-bus messages specified to do so as per NMEA2000 documentation (so called "complex write commands").+To change the Data instances, see [[ve.can:changing_nmea2000_instances|this document]].
  
 __Device instance__ __Device instance__
Line 1325: Line 1337:
  
   - 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 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, the same.+  - 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.   - 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.
  
Line 1389: Line 1401:
 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|}}]]
ccgx/start.txt · Last modified: 2020-10-15 10:37 by ictbeheer

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki