> For the complete documentation index, see [llms.txt](https://support.powerio.com/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.powerio.com/hub/codesys-hvac/en/hvac-modbus-library/functionblocks/eastron/eastron_sdm630mct_tcp.md). # EASTRON\_SDM630MCT\_TCP ## `EASTRON_SDM630MCT_TCP` (FB) `FUNCTION_BLOCK` EASTRON\_SDM630MCT\_TCP ### Display
### Short description > Display of the measured values of an energy meter from Eastron SDM630MCT in the TCP variant. ### General Function: 1-3-phase, LCD display, with / without current transformer\ Current: transformers with 1A / 5A output\ Frequency: 50/60 Hz AC\ Rated voltage: 173V - 500V\ Option: MID directive\ Version: 1-tariff meter ### Guidelines - software development Allowed function codes: 03, 04, 08, 16\ Possible exception codes: 01,02,03,05\ Possible Modbus addresses: 1 - 247\ Possible baud rates: 2400 - 38400 baud\ Possible parameters: 1-8-N/E/O-1/2\ A maximum of 40 consecutive registers may be read at once.\ FC16: Only one register may be written at a time.\ All configuration registers are not affected here; the required settings are made via the display independently of the Modbus connection. InOut: | Scope | Name | Type | Initial | Comment | | ----------- | ------------------- | ------------------ | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Input | `xEn` | `BOOL` | TRUE | Enable / disable communication (TRUE = enable) | | Input | `byUnitId` | `BYTE` | 0 | Address of the device | | Input | `xUpdateActual` | `BOOL` | FALSE |

Update of actual values (on every rising edge
)

| | Input | `xResDevice` | `BOOL` | FALSE |

Triggering the reinitialization of meter-internal measured variables
(on every rising edge). The parameter rResDevice
contains the measured value(s).

| | Input | `xResError` | `BOOL` | FALSE |

Reinitialization of the outputs eErrorCodeCom to the
error-free state (on every rising edge)

| | InOut | `ModbusClient` | `ModbusClientBase` | | Client of the device | | Output | `rU1N` | `REAL` | | Phase voltage L1 - N in V | | Output | `rU2N` | `REAL` | | Phase voltage L2 - N in V | | Output | `rU3N` | `REAL` | | Phase voltage L3 - N in V | | Output | `rU12` | `REAL` | | Line voltage L1 - L2 in V | | Output | `rU23` | `REAL` | | Line voltage L2 - L3 in V | | Output | `rU31` | `REAL` | | Line voltage L3 - L1 in V | | Output | `rIL1` | `REAL` | | Line current L1 in A | | Output | `rIL2` | `REAL` | | Line current L2 in A | | Output | `rIL3` | `REAL` | | Line current L3 in A | | Output | `rNeutralCurrent` | `REAL` | | Current in the neutral conductor in A | | Output | `rPowerFactorL1` | `REAL` | | Power factor L1 | | Output | `rPowerFactorL2` | `REAL` | | Power factor L2 | | Output | `rPowerFactorL3` | `REAL` | | Power factor L3 | | Output | `rActivePowerL1` | `REAL` | | Active power L1 in W | | Output | `rActivePowerL2` | `REAL` | | Active power L2 in W | | Output | `rActivePowerL3` | `REAL` | | Active power L3 in W | | Output | `rApparentPowerL1` | `REAL` | | Apparent power L1 in VA | | Output | `rApparentPowerL2` | `REAL` | | Apparent power L2 in VA | | Output | `rApparentPowerL3` | `REAL` | | Apparent power L3 in VA | | Output | `rReactivePowerL1` | `REAL` | | Reactive power L1 in var | | Output | `rReactivePowerL2` | `REAL` | | Reactive power L2 in var | | Output | `rReactivePowerL3` | `REAL` | | Reactive power L3 in var | | Output | rTotalActivePower | REAL | | Total active power of the system in W | | Output | rTotalApparentPower | REAL | | Total apparent power of the system in VA | | Output | rTotalReactivePower | REAL | | Total reactive power of the system in VAr | | Output | rTotalPowerFactor | REAL | | Total power factor of the system | | Output | `rFrequency` | `REAL` | | Frequency in Hz | | Output | `rActEneImpTotal` | `REAL` | | Consumed active energy - total - in kWh | | Output | `rActEneExpTotal` | `REAL` | | Delivered active energy - total - in kWh | | Output | `rReaEneImpTotal` | `REAL` | | Consumed reactive energy - total - in kVarh | | Output | `rReaEneExpTotal` | `REAL` | | Delivered reactive energy - total - in kVarh | | Output | `xAlarm` | `BOOL` | FALSE | Collective fault (TRUE = fault) | | Output | `xAlarmCom` | `BOOL` | FALSE | Collective fault - communication (TRUE = fault) | | Output | `eErrorCodeCom` | ModbusErrorCode | | Error code - communication (0 = no error) | | Output | `xBusy` | `BOOL` | | Communication indicator (TRUE = communication) | | Input Const | `wResDevice` | `WORD` | 1 | Register content during a reset process (register 61456), 0 = reset of the peak load phase ('maximum demand'), 3 = reset of the resettable energy counters (holding register 384 - 395) | | Input Const | `tTimeUpdateActual` | `TIME` | TIME#10s0ms |

Update interval for the processes affected by the input
xUpdateActual are influenced

| --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://support.powerio.com/hub/codesys-hvac/en/hvac-modbus-library/functionblocks/eastron/eastron_sdm630mct_tcp.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.