User Tools

Site Tools


ccgx:modbustcp_faq

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
ccgx:modbustcp_faq [2020-05-29 14:48] – [1. Introduction] bwillackerccgx:modbustcp_faq [2023-10-31 10:32] (current) jpasop
Line 2: Line 2:
  
 ==== 1. Introduction ==== ==== 1. Introduction ====
-Modbus-TCP is a feature on our [[venus-os:start|GX devices]] eg [[https://www.victronenergy.com/panel-systems-remote-monitoring/colorcontrol|Color Control GX]], and also the [[https://www.victronenergy.com/panel-systems-remote-monitoring/venus-gx|Venus GX]].+Modbus-TCP is a feature on all our [[venus-os:start|GX devices]] eg [[https://www.victronenergy.com/panel-systems-remote-monitoring/cerbo-gx|Cerbo GX]], and [[https://www.victronenergy.com/panel-systems-remote-monitoring/venus-gx|Venus GX]].
  
 Modbus-TCP is an industry standard protocol, that can be used to interface PLCs or other third party equipment with Victron products. Through the Modbus-TCP interface you can read and write data to the chargers, battery monitors, inverter/chargers and other products connected to the GX device. Modbus-TCP is an industry standard protocol, that can be used to interface PLCs or other third party equipment with Victron products. Through the Modbus-TCP interface you can read and write data to the chargers, battery monitors, inverter/chargers and other products connected to the GX device.
Line 71: Line 71:
 excel sheet containing the Modbus-TCP mapping. This excel sheet is available for download from our website on the [[https://www.victronenergy.com/panel-systems-remote-monitoring/color-control#whitepapers|Color Control page]]. excel sheet containing the Modbus-TCP mapping. This excel sheet is available for download from our website on the [[https://www.victronenergy.com/panel-systems-remote-monitoring/color-control#whitepapers|Color Control page]].
  
-To request the input voltage of a Multi or Quattro, connected to the VE.Bus sockets on the CCGX, use the following settings: Unit-ID 246, and set the data address of the first request register to 3. +To request the input voltage of a Multi or Quattro, connected to the VE.Bus sockets on the GX device, use the following settings: Unit-ID 246, and set the data address of the first request register to 3. 
  
 The Modbus-TCP reply will contain 2302. Divide it by 10, as specified in cell E3, and then you have the voltage: 230.2 Volts AC. The Modbus-TCP reply will contain 2302. Divide it by 10, as specified in cell E3, and then you have the voltage: 230.2 Volts AC.
Line 97: Line 97:
 |0x02|IllegalDataAddress|The requested Unit-ID is available, but one or more of the requested register(s) does not exist.| |0x02|IllegalDataAddress|The requested Unit-ID is available, but one or more of the requested register(s) does not exist.|
 |0x03|IllegalDataValue|The requested quantity of registers is invalid. See the modbus specs, http://www.modbus.org/specs.php, for the limits per function code.| |0x03|IllegalDataValue|The requested quantity of registers is invalid. See the modbus specs, http://www.modbus.org/specs.php, for the limits per function code.|
-|0x0A|GatewayPathUnavailable|The requested Unit-ID is defined in the mapping list, but there is no device found on the mapped port. Double check the Unit-ID mapping list in the excel sheet, and make sure that the device is properly connected to the CCGX, switched on, and that its data is available on the CCGX display.|+|0x0A|GatewayPathUnavailable|The requested Unit-ID is defined in the mapping list, but there is no device found on the mapped port. Double check the Unit-ID mapping list in the excel sheet, and make sure that the device is properly connected to the GX device, switched on, and that its data is available on the GX device display.|
 |0x0B|GatewayTargetDeviceFailedToRespond|Requested Unit-ID not found in the mapping list. Double check the Unit-ID mapping list in the excel sheet.| |0x0B|GatewayTargetDeviceFailedToRespond|Requested Unit-ID not found in the mapping list. Double check the Unit-ID mapping list in the excel sheet.|
  
Line 103: Line 103:
 ==== 7. Support ==== ==== 7. Support ====
  
-The recommended method for report on Modbus-TCP questions is to use the [[https://community.victronenergy.com/spaces/31/index.html|Modifications section on Victron Community]]. Its frequently visited by many people using Modbus-TCP and other methods of integrating with Victron products.+The recommended method for support on Modbus-TCP questions is to use the [[https://community.victronenergy.com/spaces/31/index.html|Modifications section on Victron Community]]. Its frequently visited by many people using Modbus-TCP and other methods of integrating with Victron products.
  
 Direct company support is only offered on a limited basis. For such support, contact our Victron representative. Direct company support is only offered on a limited basis. For such support, contact our Victron representative.
Line 139: Line 139:
   - Login with SSH (use for example Putty in Windows - or simply type //ssh root@[ip address here]// on a Linux or Mac terminal console.   - Login with SSH (use for example Putty in Windows - or simply type //ssh root@[ip address here]// on a Linux or Mac terminal console.
   - List the latest log file:<code>   - List the latest log file:<code>
-cat /log/dbus-modbustcp/current | tai64nlocal+cat /var/log/dbus-modbustcp/current | tai64nlocal
 </code> </code>
  
ccgx/modbustcp_faq.1590756508.txt.gz · Last modified: 2020-05-29 14:48 by bwillacker

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki