> 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/imi/imi_ta_slider_160.md). # IMI\_TA\_SLIDER\_160 ## `IMI_TA_SLIDER_160` (FB) `FUNCTION_BLOCK` IMI\_TA\_SLIDER\_160 ### Representation
InOut: | Scope | Name | Type | Initial | Comment | | ----------- | ----------------------- | ---------------------------------- | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Input | `xEn` | `BOOL` | TRUE | Enable / disable communication (TRUE = enable) | | Input | `byUnitId` | `BYTE` | 1 |

Device address (1… 247, default =
factory setting)

| | Input | `xUpdateActual` | `BOOL` | FALSE |

Update of actual values (on every rising edge
)

| | Input | `xUpdateSetp` | `BOOL` | FALSE |

Update of setpoints (on every rising edge
)

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

Reinitialization of the outputs eErrorCodeCom or
xErrorCodeDev to the fault-free state (at each
rising edge)

| | Input | `rSetpPosition` | `REAL` | 0.0 |

Setpoint - position in % (0.0 - 100.0 %) (Default: 0.0%
= spindle extended, configuration via app)

| | Input | `xForceCalib` | `BOOL` | FALSE |

Triggering a calibration process (with every rising
edge)

| | Input | `xRelayState_Mod` | `BOOL` | FALSE |

Definition of the relay state via Modbus (TRUE =
activation) (configuration via app)

| | Input | `xInputState_Mod` | `BOOL` | FALSE |

Definition of the state of the digital input via Modbus (
TRUE = active) (configuration via app)

| | Inout | `ModbusClient` | `ModbusClientBase` | | Client of the device | | Output | `rSetpPositionFb` | `REAL` | |

Feedback - setpoint - position in % (0.0 - 100.0 %) (
Default: 0.0% = spindle extended, configuration via app
)

| | Output | `rVolumeFlow` | `REAL` | |

Current flow rate in the selected unit (parameter
eFlowUnit) (available depending on device type)

| | Output | `stSerialNumber` | `STRING` | | Device serial number | | Output | `rPosition` | `REAL` | |

Current position in % (0.0 - 100.0 %) (Default: 0.0% =
spindle extended)

| | Output | `rCalibStroke` | `REAL` | |

Measured total stroke during the calibration process (in
micrometers, 1000 micrometers = 1 mm, maximum 6300 micrometers
)

| | Output | `eMotorStatus` | TA\_SLIDER\_160\_MOTOR\_STATUS | | Current status of the actuator | | Output | `dwSecSinceReset` | `DWORD` | |

Number of seconds since the last restart (=
power return 24VAC/DC)

| | Output | `xInputState` | `BOOL` | | Current state of the external binary input | | Output | `xRelayState` | `BOOL` | | Current state of the relay | | Output | `eCharacteristic` | TA\_SLIDER\_160\_CHARACTERISTIC | |

Current characteristic of the control signal (stroke =
f(rSetpPosition), configuration via app)

| | Output | `eSetpSource` | TA\_SLIDER\_160\_SETP\_SOURCE | |

Current source for the setpoint - position (configuration
via app)

| | Output | `stValveName` | `STRING` | ‘’ |

Valve name (configuration via app, only via
xUpdateActual read-only, setting function in the app is still missing - status 30/09/2021)

| | Output | `stObjectName` | `STRING` | ‘’ |

Object name (configuration via app, only via
xUpdateActual read-only)

| | Output | `stLocalName` | `STRING` | ‘’ |

Location of the valve (configuration via app, only via
xUpdateActual read-only, setting function in the app is still missing - status 30/09/2021)

| | Output | `rTemperature1` | `REAL` | |

Current temperature from sensor 1 in the selected unit (
parameter eTemperatureUnit) (PT1000)

| | Output | `rTemperature2` | `REAL` | |

Current temperature from sensor 2 in the selected unit (
parameter eTemperatureUnit) (PT1000)

| | Output | `xSensorOffsetInDevice` | `BOOL` | |

Indication whether the sensors must be calibrated in the device
(TRUE = calibration in the device required, FALSE = calibration in
the FB required)

| | 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 | `stErrorCodeDev` | `STRING` | |

String with the numbers of the active device errors (Bit 0 =
number 1, Bit 1 = number 2, etc.)

| | Output | `xBusy` | `BOOL` | | Communication indicator (TRUE = communication) | | Input Const | `rTemperatur2Offset` | `REAL` | 0.0 |

Constant measurement offset for the transmitted temperature
actual value 2

| | Input Const | `rTemperatur1Offset` | `REAL` | 0.0 |

Constant measurement offset for the transmitted temperature
actual value 1

| | Input Const | `eFlowUnit` | TA\_SLIDER\_160\_FLOW\_UNIT | TA\_SLIDER\_160\_FLOW\_UNIT.LITER\_PER\_HOUR |

Influence: Outputs: rTemperature1
Unit for the flow-rate measured values

| | Input Const | `eTemperatureUnit` | TA\_SLIDER\_160\_TEMPERATURE\_UNIT | TA\_SLIDER\_160\_TEMPERATURE\_UNIT.DEGREE\_CELSIUS | Unit for the temperature measured values | | Input Const | `tTimeUpdateSetp` | `TIME` | TIME#45s0ms |

Update interval for the operations that are influenced by the input
xUpdateSetp influenced

| | Input Const | `tTimeUpdateActual` | `TIME` | TIME#3s0ms |

Update interval for the operations that are influenced by the input
xUpdateActual 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://support.powerio.com/hub/codesys-hvac/en/hvac-modbus-library/functionblocks/imi/imi_ta_slider_160.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.