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-08-05 19:49]
pbu [1.10 Connecting IMT Solar Irradiance, Temperature and Wind Speed Sensors]
ccgx:start [2020-10-15 10:37] (current)
ictbeheer Added more vncrelays; load balancing
Line 152: 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 222: 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 316: 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 third 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:
Line 324: 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]]. +
- +
-Alternatively, instead of a VE.Can to NMEA2000, you can use a 3802 cable from Oceanic Systems: https://osukl.com/ve-can-adaptor/. The difference is that it lends itself well to connecting a single NMEA-2000 device into a VE.Can network. It's also able to power a lower voltage NMEA-2000 network directly from a 48V Victron system.+
  
 Tested compatible NMEA2000 tank senders: Tested compatible NMEA2000 tank senders:
Line 334: Line 312:
   * Maretron TLA100   * Maretron TLA100
   * Maretron TLM100   * Maretron TLM100
-  * Navico Fluid Level Sensor Fuel-0 PK, partno. 000-11518-001. Note that this sender requires a 12V powered NMEA2000 network; it breaks when connected to a 24V-powered NMEA2000 network. And note that you need a Navico display to configure the Capacity, Fluid type, and other parameters of the sensor. +  * 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.+  * 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 1089: 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 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. 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.
Line 1197: Line 1188:
 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 1208: Line 1203:
 === Solar chargers === === Solar chargers ===
  
-Not yet supported by the NMEA2000-out function but in the works and expected after in a firmware update after the summer of 2020.+Supported. Battery related values as well as the PV Array Voltage & Current is made available on the NMEA2000 network.
  
 === Tank level data ===  === Tank level data === 
  
-Not yet supported by the NMEA2000-out function but in the works and expected after in a firmware update after the summer of 2020.+Supported. Tank levels measured by the GX Device are transmitted on PGN xyz (todo)
  
 === Other data and product types === === 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. Not supported. Above explicitly mentioned types are the only ones now supported. For example data from a charger (such as the Phoenix Smart Charger connected via VE.Direct) is not supported and not expected to be supported soon.
-==== 7.3 Related menu settings ====+==== 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 1393: 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|}}]]
ccgx/start.1596649749.txt.gz · Last modified: 2020-08-05 19:49 by pbu