Differences

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

--- ccgx:modbustcp_faq [2019-08-15 12:27] – replace venus-device with GX device guy_stewart
+++ ccgx:modbustcp_faq [2019-12-11 10:02] – [Does Modbus TCP support Hub-4?] iburger
@@ Line 20: / Line 20: @@
 ==== Product categories and registers ====
-In the ModbusTCP Registerlist xlsx file, there is a column called 'dbus-service-name'. And it must be consulted to find out which set of registers are available for a product.
+The ModbusTCP Registerlist xlsx file contains a column named 'dbus-service-name'. Consult this document to find out which set of registers are available for a product.
 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.gps | GPS | 2800 to 2807 |
+| com.victronenergy.tank | Tank sensors | 3000 to 3007 |
 | com.victronenergy.genset | Generators  | 3200 to 3223 |
 | com.victronenergy.temperature | Temperature sensors <sup>(1)</sup> | 3300 to 3305 |
+| com.victronenery.meteo | IMT solar irradiation sensors | 3600 to 3603 |
 (1): Check for compatible [[venus-os:start|GX devices]] (eg Venus GX) that provide 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.
@@ Line 60: / Line 62: @@
 ==== 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. See the tab ‘Unit ID mapping’ tab in the Modbus-TCP excel sheet.
+The unit-id, sometimes called ‘slave address’, specifies how a product connected to the CCGX needs to be addressed. Since Venus 2.40, this information is available on the CCGX under Settings -> Services -> Modbus/TCP -> Available services.
-For the overal system data, look for com.victronenergy.system in the excelsheet, and use unit-id 100.
+{{ :ccgx:modbus-tcp-services.png?nolink&600 |}}
-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? ====
 All products that can be connected to the [[https://www.victronenergy.com/panel-systems-remote-monitoring/color-control|Color Control GX]].
@@ 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.
-==== Does Modbus TCP support Hub-4? ====
+==== Does Modbus TCP support ESS? ====
-Yes. See the [[https://www.victronenergy.com/live/system_integration:hub4_grid_parallel_external_control_loop|Hub-4 advanced control manual]] for more details.
+Yes. See the [[https://www.victronenergy.com/live/ess:ess_mode_2_and_3|ESS mode 2 and 3 manual]] for more details.
 ===== DISQUS =====
 ~~DISQUS~~