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
ccgx:start [2020-08-19 12:10]
mvader [1.9 Connecting third-party NMEA-2000 tank senders] 		ccgx:start [2020-10-15 10:37]
ictbeheer Added more vncrelays; load balancing
Line 1077: 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 1185: 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 1196: 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 1381: 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.txt · Last modified: 2020-10-15 10:37 by ictbeheer

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki