How to Assess a TELEPERM Integrator Block for PCS 7 Migration

A TELEPERM “Integrierer” cannot be mapped safely to a PCS 7 block from the name alone. The available description gives no TELEPERM system, block type or number, complete terminal list, or function specification; it only mentions input YNF. Siemens' TELEPERM SIGRID TM V5 documentation identifies YNF as the Y-following mode input of a PID controller, where YN is passed through as the controller output and the integral component is aligned. That does not establish that the ticket's block is this controller, so the specific PCS 7 replacement remains unresolved.

What the documented `YNF` behavior means

In Siemens' SIGRID TM V5 general function description for a PID control algorithm, YNF = 1 activates Y-following. The value at input YN is routed as the controller output YABS, and the integral component YI is aligned with YN. The same manual explains the controller's P, I and D contributions and output limiting.

This is evidence for that documented SIGRID TM V5 controller behavior only. The short source description does not include a block number or enough signals to establish that its “Integrierer” is this PID controller or that YNF has the same meaning in the actual block.

Information required before selecting a PCS 7 replacement

Before engineering a migration, collect the original TELEPERM platform and software revision, exact block name and identifier, complete block interface, parameter values, connected signals, operating modes, and the intended behavior during startup, tracking, hold, reset, and controller/manual transitions. Obtain the matching TELEPERM function description and the PCS 7 library/version intended for the target project.

Then compare documented behavior and state handling, not just labels. Determine whether the function is a standalone integrator or a controller's integral component, what YNF selects, how its tracking input is used, how state is initialized and bounded, and what output is produced when tracking is active. The available evidence does not provide enough information to prescribe a block substitution or wiring.

Migration validation approach

Once the precise source function and target library are identified, document each input/output and its units, range, polarity, and operating-state behavior. Build a project-specific equivalence test plan covering normal integration, enable/disable, reset or initialization, output limits, tracking transitions, and power-up behavior where relevant. Compare the old and new function descriptions and validate behavior in an approved test environment before any production download.

These are engineering validation topics, not a verified conversion procedure for the unidentified block. No PCS 7 block name or parameter mapping can be established from the current information.

Verification

Verify the TELEPERM block's exact identity and semantics against the manual for the installed TELEPERM system. Confirm specifically whether YNF is a Y-following input, what signal is used as the tracking value, and how the integrator state responds. For the PCS 7 candidate, use the applicable official block documentation and test each required operating mode against that specification before accepting the migration.

Limitations and Operational Precautions

This article is under technical review because the reported block is not uniquely identified. The opened Siemens reference covers SIGRID TM V5 controller behavior; it does not establish a direct PCS 7 equivalent for a standalone TELEPERM integrator. Do not select or download a replacement based only on the YNF terminal name. An incorrect integrator/controller mapping can alter loop behavior; preserve the existing configuration and conduct a documented, reviewed migration test before production use.

Engineer FAQ

Does YNF prove this is a PID controller? No. It appears in the report, but the block identity is missing. Siemens documents Y-follow behavior for a SIGRID TM V5 PID controller, which is not enough to identify the reported block.

What does YNF do in the documented SIGRID TM V5 PID function? With YNF = 1, the documented function passes YN as YABS and aligns the integral component with YN.

Can an integrator be replaced by a PCS 7 PID block? The available information does not establish that equivalence. First determine whether the original function is a standalone integrator or part of a controller and compare state, tracking and limit behavior.

What source detail would unblock a mapping? The TELEPERM system/version, exact block identifier and full interface, together with its applicable function manual.

Is the outlined validation plan a tested conversion? No. It identifies behaviors that require project-specific comparison and testing; no conversion has been performed or laboratory-tested here.

Technical References

Siemens, TELEPERM SIGRID TM V5 Software Package with Procedure and Control Functions, C79000-G8000-C705-01, §4.10.1.4.3, “Y-Nachführen” (Y-following), pp. 4-141–4-142: https://cache.industry.siemens.com/dl/files/815/18317815/att_44997/v1/C79000-G8000-C705_01.pdf

How to Assess a TELEPERM Integrator Block for PCS 7 Migration