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 [2019-03-03 08:10] – [Introduction] mvader | ccgx:modbustcp_faq [2019-12-11 10:02] – [Does Modbus TCP support Hub-4?] iburger | ||
---|---|---|---|
Line 2: | Line 2: | ||
==== Introduction ==== | ==== Introduction ==== | ||
- | ModbusTCP is a feature on our [[venus-os: | + | ModbusTCP is a feature on our [[venus-os: |
- | Through the ModbusTCP interface you can read and write date to the chargers, battery monitors, inverter/ | + | Through the ModbusTCP interface you can read and write date to the chargers, battery monitors, inverter/ |
Besides reading this FAQ, make sure to also read the ModbusTCP section in our [[https:// | Besides reading this FAQ, make sure to also read the ModbusTCP section in our [[https:// | ||
Line 20: | Line 20: | ||
==== Product categories and registers ==== | ==== Product categories and registers ==== | ||
- | In the ModbusTCP Registerlist xlsx file, there is a column | + | The ModbusTCP Registerlist xlsx file contains |
Note that besides device-specific registers, there is also a set of registers that represent the entire system: com.victronenergy.system. This service is also where the //System Overview// pages in the GUI, and the VRM Dashboard get their data. | Note that besides device-specific registers, there is also a set of registers that represent the entire system: com.victronenergy.system. This service is also where the //System Overview// pages in the GUI, and the VRM Dashboard get their data. | ||
Line 34: | Line 34: | ||
| com.victronenergy.grid | Energy meters configured to measure the grid | 2600 to 2609 | | | com.victronenergy.grid | Energy meters configured to measure the grid | 2600 to 2609 | | ||
| com.victronenergy.gps | GPS | 2800 to 2807 | | | com.victronenergy.gps | GPS | 2800 to 2807 | | ||
+ | | com.victronenergy.tank | Tank sensors | 3000 to 3007 | | ||
| com.victronenergy.genset | Generators | | com.victronenergy.genset | Generators | ||
| com.victronenergy.temperature | Temperature sensors < | | com.victronenergy.temperature | Temperature sensors < | ||
+ | | com.victronenery.meteo | IMT solar irradiation sensors | 3600 to 3603 | | ||
- | (1): Only the Venus GX is provided with temperature sensor inputs. The battery temperature as measured by a sensor connected to a VE.Bus device is not available. And the battery temperature as measured by a sensor connected to a BMV battery monitor is available under the com.victronenergy.battery register set. | + | (1): Check for compatible [[venus-os: |
General note: not all list registers are available for each device. For example a BMV Battery Monitor has lots of readings: historical data such as maximum/ | General note: not all list registers are available for each device. For example a BMV Battery Monitor has lots of readings: historical data such as maximum/ | ||
Line 60: | Line 62: | ||
==== What is a unit-id and what do I need to set it to? ==== | ==== What is a unit-id and what do I need to set it to? ==== | ||
- | The unit-id, sometimes called ‘slave address’, specifies how a product connected to the CCGX needs to be addressed. | + | The unit-id, sometimes called ‘slave address’, specifies how a product connected to the CCGX needs to be addressed. |
- | For the overal system data, look for com.victronenergy.system in the excelsheet, 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 clients and PLCs do not work with id 0. | + | Additionally this information is also documented on the ‘Unit ID mapping’ tab in the Modbus-TCP excel sheet. |
+ | 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 clients and PLCs do not work with id 0. | ||
==== Which products can be interfaced via Modbus TCP? ==== | ==== 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 91: | Line 96: | ||
==== Advanced debugging ==== | ==== Advanced debugging ==== | ||
- | If all unit-id' | + | If all unit-id' |
Follow these steps: | Follow these steps: | ||
Line 108: | Line 113: | ||
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 software or PLC. | 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 software or PLC. | ||
- | ==== Does Modbus TCP support | + | ==== Does Modbus TCP support |
- | Yes. See the [[https:// | + | Yes. See the [[https:// |
===== DISQUS ===== | ===== DISQUS ===== | ||
~~DISQUS~~ | ~~DISQUS~~ | ||
- |
ccgx/modbustcp_faq.txt · Last modified: 2023-10-31 10:32 by jpasop