What Does YNF Mean When Migrating a TELEPERM Integrator to PCS 7?
The YNF input alone is not enough to identify a TELEPERM integrator or choose its PCS 7 replacement. In Siemens' SIGRID TM V5 PID documentation, YNF = 1 selects Y-following: input YN is passed to output YABS, and the integral component is aligned to YN. The report does not provide the TELEPERM system revision or block identifier, so that documented behavior cannot safely be assumed to describe the controller in question.
Table of Contents
- Interpret
YNFonly in the documented block context - Identify the legacy block before conversion
- Validate the project-specific mapping
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Interpret YNF only in the documented block context
The Siemens SIGRID TM V5 function description documents YNF in its PID control algorithm. During Y-following, the controller passes the value at YN as YABS; its integral component follows the YN value. This explains a documented controller mode, not a generic integrator interface.
Because the report calls the source a TELEPERM “integrator” but also mentions a controller input named YNF, the exact function remains ambiguous. No PCS 7 block or direct parameter mapping is established by the available source.
Identify the legacy block before conversion
Collect the TELEPERM model and software revision, exact block name or number, complete I/O list, parameter values, and applicable function description. Determine whether the block is a standalone integrator or a PID controller with an integral term and Y-follow mode. Establish the role and polarity of YNF, what value is tracked, and how state behaves on startup, reset, limit conditions, and return to automatic control.
Use the matching PCS 7 library documentation to identify a candidate only after the source semantics are known. Compare input scaling, integral state, output limiting and operating-mode transitions. Similar signal names do not establish equivalent behavior.
Validate the project-specific mapping
For a confirmed source and target, prepare a reviewable mapping table and test plan covering normal integration, tracking active and inactive, transitions, initialization/reset, and output limits. Compare expected responses from the applicable manuals and observe the target implementation under an approved test configuration. The source does not include enough detail for reproducible conversion steps or a target-block recommendation.
Verification
Verify the full source interface and block behavior from the correct TELEPERM documentation. Then verify the target behavior from the exact PCS 7 block manual and project version. The mapping is ready for engineering review only when YNF and all related state transitions have documented counterparts or an explicitly approved project-specific implementation.
Limitations and Operational Precautions
This case is unresolved because the exact legacy block is unidentified. The SIGRID TM V5 reference is authoritative for its documented PID behavior but does not prove the reported block is that PID function, and it does not document a PCS 7 conversion. Do not migrate control behavior based solely on the label YNF; preserve existing logic and complete design review and controlled testing before any production download.
Engineer FAQ
Does YNF always identify a PID controller? No. Its meaning must be confirmed in the applicable block documentation. The cited manual only establishes its behavior for the SIGRID TM V5 PID function.
What is Y-following in that SIGRID TM V5 function? When YNF = 1, YN is passed as YABS and the integral component is aligned with YN.
Can this be replaced by a PCS 7 integrator? The evidence does not establish equivalence or identify a suitable target block. Determine whether the source is standalone integration or part of a controller first.
What details are needed to proceed? TELEPERM version, exact block identity, full I/O and parameterization, and the matching function manual.
Can the described test plan be treated as a completed conversion? No. It identifies behaviors for project-specific validation; no conversion procedure or test result is established.
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