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 revision Previous revision
Next revision Both sides next revision
ccgx:modbustcp_faq [2019-03-03 08:10]
mvader [Introduction]
ccgx:modbustcp_faq [2019-08-15 12:27]
guy_stewart replace venus-device with GX device
Line 2: Line 2:
  
 ==== Introduction ==== ==== Introduction ====
-ModbusTCP is a feature on our [[venus-os:​start|Venus-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]]. ModbusTCP is an industry standard protocol, that can be used to interface PLCs or other equipment with Victron products. For example to enable a heat pump when there is excess solar power, or create a fully integrated glass bridge on a yacht.+ModbusTCP 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]]. ModbusTCP is an industry standard protocol, that can be used to interface PLCs or other equipment with Victron products. For example to enable a heat pump when there is excess solar power, or create a fully integrated glass bridge on a yacht.
  
-Through the ModbusTCP interface you can read and write date to the chargers, battery monitors, inverter/​chargers and other products connected to the Venus-device. The unit-id combined with the register address is used as a device-selector:​ selecting for example from which device you want to read its battery voltage measurement.+Through the ModbusTCP interface you can read and write date to the chargers, battery monitors, inverter/​chargers and other products connected to the GX device. The unit-id combined with the register address is used as a device-selector:​ selecting for example from which device you want to read its battery voltage measurement.
  
 Besides reading this FAQ, make sure to also read the ModbusTCP section in our  [[https://​www.victronenergy.com/​upload/​documents/​Whitepaper-Data-communication-with-Victron-Energy-products_EN.pdf|Data communication whitepaper]]. Besides reading this FAQ, make sure to also read the ModbusTCP section in our  [[https://​www.victronenergy.com/​upload/​documents/​Whitepaper-Data-communication-with-Victron-Energy-products_EN.pdf|Data communication whitepaper]].
Line 37: Line 37:
 | com.victronenergy.temperature | Temperature sensors <​sup>​(1)</​sup>​ | 3300 to 3305 | | com.victronenergy.temperature | Temperature sensors <​sup>​(1)</​sup>​ | 3300 to 3305 |
  
-(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:​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.
  
 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/​minimum,​ for example. A canbus-connected lithium battery might not have those parameters available. 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/​minimum,​ for example. A canbus-connected lithium battery might not have those parameters available.
Line 91: Line 91:
 ==== Advanced debugging ==== ==== Advanced debugging ====
  
-If all unit-id'​s and register-addresses have been checked and re-checked, and still the connection doesn'​t work, you could try looking at the modbustcp log file on the [[venus-os:​start|Venus-device]]. ​+If all unit-id'​s and register-addresses have been checked and re-checked, and still the connection doesn'​t work, you could try looking at the modbustcp log file on the [[venus-os:​start|GX device]]. ​
  
 Follow these steps: Follow these steps:
Line 114: Line 114:
 ===== DISQUS ===== ===== DISQUS =====
 ~~DISQUS~~ ~~DISQUS~~
- 
ccgx/modbustcp_faq.txt · Last modified: 2020-05-26 14:42 by mvader