system_integration:hub4_grid_parallel_external_control_loop
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| system_integration:hub4_grid_parallel_external_control_loop [2017-03-23 16:02] – [Hub-4 mode 2 and 3] mvader | system_integration:hub4_grid_parallel_external_control_loop [2019-01-22 10:16] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 197: | Line 197: | ||
| * As an alternative to running the control loop externally, using ModbusTCP, it is also possible to run code on the CCGX itself and update the AcPowerSetpoint via D-Bus. We have one customer that is running a MQTT client on the CCGX, written in Python, that gets the control-loop output as updates from a MQTT broker. And the Python script sends them to the Multi, using D-Bus service com.victronenergy.vebus.ttyO1, | * As an alternative to running the control loop externally, using ModbusTCP, it is also possible to run code on the CCGX itself and update the AcPowerSetpoint via D-Bus. We have one customer that is running a MQTT client on the CCGX, written in Python, that gets the control-loop output as updates from a MQTT broker. And the Python script sends them to the Multi, using D-Bus service com.victronenergy.vebus.ttyO1, | ||
| | | ||
| + | |||
| ===== DISQUS ===== | ===== DISQUS ===== | ||
| ~~DISQUS~~ | ~~DISQUS~~ | ||
| + | |||
system_integration/hub4_grid_parallel_external_control_loop.1490281344.txt.gz · Last modified: 2017-03-23 16:02 by mvader