ccgx:modbustcp_faq
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
ccgx:modbustcp_faq [2020-02-06 21:16] – [6. Error codes and trouble shooting] mvader | ccgx:modbustcp_faq [2020-05-29 14:48] – [1. Introduction] bwillacker | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== GX ModbusTCP | + | ====== GX Modbus-TCP |
==== 1. Introduction ==== | ==== 1. Introduction ==== | ||
- | ModbusTCP | + | Modbus-TCP |
- | ModbusTCP | + | Modbus-TCP |
- | Besides reading this GX ModbusTCP | + | Besides reading this GX Modbus-TCP |
- | By default, | + | By default, |
==== 2. Addressing, Unit-ID and Registers ==== | ==== 2. Addressing, Unit-ID and Registers ==== | ||
=== 2.1 Definitions === | === 2.1 Definitions === | ||
- | The ModbusTCP | + | The Modbus-TCP |
- | * The **Unit-ID** is the device-selector: | + | * The **Unit-ID** is the device-selector: |
* The **Register Address** then determines the parameter to read or write: ie. voltage, or current, and so forth. | * The **Register Address** then determines the parameter to read or write: ie. voltage, or current, and so forth. | ||
Line 28: | Line 28: | ||
For the overall system data, look for com.victronenergy.system in the excel sheet, and use Unit-ID 100. | For the overall system data, look for com.victronenergy.system in the excel sheet, and use Unit-ID 100. | ||
- | Note that both Unit-ID 0 and Unit-ID 100 map to the same internal address. We recommend to use ID 100, since many ModbusTCP | + | Note that both Unit-ID 0 and Unit-ID 100 map to the same internal address. We recommend to use ID 100, since many Modbus-TCP |
=== 2.3 Register addresses === | === 2.3 Register addresses === | ||
Line 57: | Line 57: | ||
(1): These are the auxiliary temperature sensors built-in to our GX devices, such as the Venus GX. For details, see [[venus-os: | (1): These are the auxiliary temperature sensors built-in to our GX devices, such as the Venus GX. For details, see [[venus-os: | ||
- | ==== 3. Supported | + | ==== 3. Supported |
The supported function codes are: | The supported function codes are: | ||
Line 69: | Line 69: | ||
==== 5. Mapping example ==== | ==== 5. Mapping example ==== | ||
The purpose of this example is to show how to interpret the information in the worksheets of the | The purpose of this example is to show how to interpret the information in the worksheets of the | ||
- | excel sheet containing the modbustcp | + | excel sheet containing the Modbus-TCP |
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 CCGX, use the following settings: Unit-ID 246, and set the data address of the first request register to 3. | ||
- | The ModbusTCP | + | The Modbus-TCP |
==== 6. Error codes and trouble shooting ==== | ==== 6. Error codes and trouble shooting ==== | ||
Line 83: | Line 83: | ||
Besides double checking the mapping, there are two ways to see where the error lies. One is to check the last error as shown in the GX Device menus. And secondly you can look at the error code as is visible on (most but not all) PLCs. See the two sections below for details. | Besides double checking the mapping, there are two ways to see where the error lies. One is to check the last error as shown in the GX Device menus. And secondly you can look at the error code as is visible on (most but not all) PLCs. See the two sections below for details. | ||
- | === 6.2 Looking up the last ModbusTCP | + | === 6.2 Looking up the last Modbus-TCP |
- | To see why a certain register is not available, use the Settings -> Services -> ModbusTCP | + | To see why a certain register is not available, use the Settings -> Services -> Modbus-TCP |
{{ : | {{ : | ||
Line 103: | Line 103: | ||
==== 7. Support ==== | ==== 7. Support ==== | ||
- | The recommended method for report on ModbusTCP | + | The recommended method for report on Modbus-TCP |
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 109: | Line 109: | ||
==== 8. FAQ ==== | ==== 8. FAQ ==== | ||
- | === Q1: Which products can be interfaced via Modbus TCP? === | + | === Q1: Which products can be interfaced via Modbus-TCP? === |
All products that can be connected to the [[https:// | All products that can be connected to the [[https:// | ||
Line 124: | Line 124: | ||
=== Q5: In a parallel or three-phase system, how can I address a single unit? === | === Q5: In a parallel or three-phase system, how can I address a single unit? === | ||
- | You cannot interface with them individually if they are configured for parallel-working; | + | You cannot interface with them individually if they are configured for parallel-working; |
=== Q6: Will unit-id' | === Q6: Will unit-id' | ||
Line 133: | Line 133: | ||
- | If all unit-id' | + | If all unit-id' |
Follow these steps: | Follow these steps: | ||
Line 148: | Line 148: | ||
2016-01-08 16: | 2016-01-08 16: | ||
- | In most cases the problem will be found in either the unit's id address; or the register addresses. Double check the numbers shown in the output with the numbers as used in your modbustcp | + | In most cases the problem will be found in either the unit's id address; or the register addresses. Double check the numbers shown in the output with the numbers as used in your Modbus-TCP |
- | === Q8: Does Modbus TCP support ESS? === | + | === Q8: Does Modbus-TCP support ESS? === |
Yes. See the [[https:// | Yes. See the [[https:// | ||
ccgx/modbustcp_faq.txt · Last modified: 2023-10-31 10:32 by jpasop