Modbus TCP
The Teleport can be configured to have a local Modbus TCP server running. By default it is disabled.
Conventions
- Values are in big-endian word order.
- The highest allowed value of the type is used to signal
null, eg.2^16 - 1for UInt16 and2^31 - 1for SInt32. - Unlisted addresses for listed Unit IDs will return
2^16 - 1. - In case the unit includes a number, e.g.
0.001 °C, it means that the value is scaled. E.g. with the unit being0.001 °C, a register with value1000represents1.000 °C, i.e. the register should be multiplied by0.001to get the actual value.
Register
Teleport Device
On Unit ID 0 a Modbus TCP client can interact with the Teleport device.
| Item | Start address | Size | Type | Unit | R/W | Notes |
|---|---|---|---|---|---|---|
| Heartbeat | 0 | 1 | UInt16 | R/W | Value does not matter. Modbus server power limits are removed if there is no heartbeat for 60 seconds. Any other write is also counted as a heartbeat | |
| Unix timestamp | 1 | 4 | UInt64 | ms | R |
Aggregated solar and wind assets
At Unit ID 1 a Modbus TCP client can control and readout all connected solar and wind assets together. Aggregated statistics are provided for connected assets. Be aware that these statistics are partial aggregates if (and only if) registers 0 and 1 are not equal. To avoid drawing incorrect conclusions by reading out registers 0 and 1 at a different time than the aggregate statistics, it is advisable to read out all required registers of this Unit ID in a single request.
| Item | Start address | Size | Type | Unit | R/W | Notes |
|---|---|---|---|---|---|---|
| Number of assets configured | 0 | 1 | UInt16 | R | The number of assets the Teleport should be connected to. | |
| Number of connected assets | 1 | 1 | UInt16 | R | The number of assets the Teleport is connected to. | |
| Nominal active power of configured assets | 2 | 2 | UInt32 | W | R | The sum of the values from the assets the Teleport should be connected to. |
| Nominal active power of connected assets | 21 | 2 | UInt32 | W | R | The sum of the values from the assets the Teleport is connected to. |
| Combined target active power limit of connected assets | 31 | 1 | UInt16 | 0.01% | R | The minimum of setpoints from the various sources listed here, corrected for static limits. Is null if it differs between connected assets. |
| Target active power limit from modbus server of connected assets | 32 | 1 | UInt16 | 0.01% | R/W | As set through the local modbus interface of the Teleport. Writing null (2^16 - 1) means that there is no limit. Overwrites the individual limits set using Unit ID >= 100. Is null if it differs between connected assets. |
| Target active power limit from cloud of connected assets | 33 | 1 | UInt16 | 0.01% | R | As set through the Teleport Cloud API using limitProductionPower commands. Is null if it differs between connected assets. |
| Target active power limit from realtime interface of connected assets | 34 | 1 | UInt16 | 0.01% | R | As set through the Realtime Interface by the grid operator. Is null if it differs between connected assets. |
| Target active power limit from local active control of connected assets | 35 | 1 | UInt16 | 0.01% | R | As set by the Teleport as the result of a control strategy. Is null if it differs between connected assets. |
| Target active power limit aFRR-delta of connected assets | 36 | 2 | SInt32 | W | R | As set through the Teleport Cloud API using applyAfrrDeltaSetpoint commands. Is the sum of connected assets. |
| Target active power limit aFRR-delta of connected assets | 38 | 1 | SInt16 | 0.01% | R | As set through the Teleport Cloud API using applyAfrrDeltaSetpoint commands. Is null if it differs between connected assets. |
| Effective active power limit of connected assets | 50 | 1 | UInt16 | 0.01% | R | Is null if it differs between connected assets. |
| Active power of connected assets | 51 | 2 | SInt32 | W | R | The sum of the values read out from the connected assets. |
| Available active power of connected assets | 53 | 2 | SInt32 | W | R | The sum of the values read out from the connected asset or calculated using an asset like a pyranometer. |
Individual wind or solar asset
Starting at Unit ID 100 a Modbus TCP client can control and readout an individual asset. The second asset is available at Unit ID 101 and so on. The number of assets can be retrieved from register 1 of Unit ID 0 (see above).
| Item | Start address | Size | Type | Unit | R/W | Notes |
|---|---|---|---|---|---|---|
| Asset type | 0 | 1 | UInt16 | R | 1 = solar, 2 = wind. | |
| Asset identifier | 1 | 20 | ascii string | R | Uniquely identifies the asset within the assets connected to this Teleport device. | |
| Nominal active power | 21 | 2 | UInt32 | W | R | |
| Combined target active power limit | 31 | 1 | UInt16 | 0.01% | R | The minimum of setpoints from the various sources listed here, corrected for static limits. |
| Target active power limit from modbus server | 32 | 1 | UInt16 | 0.01% | R/W | As set through the local modbus interface of the Teleport. Writing null (2^16 - 1) means that there is no limit. Overwrites the limit set on Unit ID 1 for this asset. |
| Target active power limit from cloud | 33 | 1 | UInt16 | 0.01% | R | As set through the Teleport Cloud API using limitProductionPower commands. |
| Target active power limit from realtime interface | 34 | 1 | UInt16 | 0.01% | R | As set through the Realtime Interface by the grid operator. |
| Target active power limit from local active control | 35 | 1 | UInt16 | 0.01% | R | As set by the Teleport as the result of a control strategy. |
| Target active power limit aFRR-delta | 36 | 2 | SInt32 | W | R | As set through the Teleport Cloud API using applyAfrrDeltaSetpoint commands. |
| Target active power limit aFRR-delta | 38 | 1 | SInt16 | 0.01% | R | As set through the Teleport Cloud API using applyAfrrDeltaSetpoint commands. |
| Effective active power limit | 50 | 1 | UInt16 | 0.01% | R | As read out from the solar or wind asset. |
| Active power | 51 | 2 | SInt32 | W | R | As read out from the solar or wind asset. |
| Available active power | 53 | 2 | SInt32 | W | R | As read out from the solar or wind asset or calculated using an asset like a pyranometer. |
| Number of environmental sensors | 100 | 1 | Uint16 | R | Between 0 and 20 environmental sensors. | |
| Environmental sensor data | 1000 | 4000 | R | Environmental sensor data, as described in Environmental Sensors. |
Environmental sensors
The following table describes the data of an environmental sensor. The starting address is offset by the index of the environmental sensor multiplied by 200, plus the offset of the environmental sensor data in the table that refers to this section. For example, with a starting register of 1000, the starting address of the first sensor is 1000 and the starting address of the second sensor is 1200.
| Item | Start address | Size | Type | Unit | R/W | Notes |
|---|---|---|---|---|---|---|
| Environmental sensor type | 0 | 1 | UInt16 | R | 1 = irradiance, 2 = temperature, 3 = wind | |
| Sensor identifier | 1 | 30 | ascii string | R | ||
| Irradiance factor | 31 | 2 | UInt32 | R | ||
| Irradiance | 33 | 2 | UInt32 | 0.001 W/m² | R | |
| Wind speed | 40 | 2 | UInt32 | 0.001 m/s | R | |
| Number of temperature measurements | 90 | 1 | Uint16 | R | Between 0 and 10 temperature measurements. | |
| Temperature measurement 1 | 91 | 2 | Int32 | 0.001 °C | R | |
| Temperature measurement 2 | 93 | 2 | Int32 | 0.001 °C | R | |
| Temperature measurement 3 | 95 | 2 | Int32 | 0.001 °C | R | |
| Temperature measurement 4 | 97 | 2 | Int32 | 0.001 °C | R | |
| Temperature measurement 5 | 99 | 2 | Int32 | 0.001 °C | R | |
| Temperature measurement 6 | 101 | 2 | Int32 | 0.001 °C | R | |
| Temperature measurement 7 | 103 | 2 | Int32 | 0.001 °C | R | |
| Temperature measurement 8 | 105 | 2 | Int32 | 0.001 °C | R | |
| Temperature measurement 9 | 107 | 2 | Int32 | 0.001 °C | R | |
| Temperature measurement 10 | 109 | 2 | Int32 | 0.001 °C | R |