cliu/ci-server-engineer
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ci-server-engineer/knowledge/manuals/IM36K10L55-01EN.md
cliu 7be194d6a3 Add phase 7 manual summaries (L30, L45, E20, L55) 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-01 10:46:28 +10:00

2.9 KiB
Raw Blame History

manual title edition version status
IM 36K10L55-01EN Exchange Tool Engineering 3rd Edition, Sep. 2023 R1.03 from docs only (needs CENTUM VP / an RGS node or CCC Prodigy data; not available on the test system)

Exchange Tool Engineering (R1.03)

Two tools convert another system's engineering data into CI Server engineering data (a "publication" = generated quick load files plus load.cmd). Section numbers refer to the manual; Appendix 1 lists the supported CENTUM VP function blocks.

1. CI Exchange for CENTUM VP (§2)

  • Runs on an RGS (Remote Gateway Station: CI Server PC with a Vnet/IP card and driver from the medium, VirtualProduct_CIServer_packageRxxx.zip, option installVirtProd) that talks to CENTUM VP. Single server: the RGS is also the CI Core. Non-single: an upper CI Core gets the data from the RGS (MDUR).
  • Solutions: RGS (manual or automatic mode; automatic = the tool is embedded in the RGS, ENG HIS equalisation enabled, the RGS registered in the CENTUM VP project; publications generated after each CENTUM VP download) and RGS with EAL (external alarms; manual mode only).
  • Manual workflow: start the tool → create a project (Single Server ticked or not) → import CENTUM VP engineering data from the ENG HIS (and MTL file) → Publish (name pattern, folder, optional SQL tag filter such as %PVI%) → copy the publication folder to C:\Program Files (x86)\Yokogawa\CIServer\Utility → run its load.cmd on the RGS and/or CI Core (in an IT-security environment run cmd.exe as different user first). Automatic publications land in %TLS_ALLUSERS_PATH%\lst\rgs\pub\.
  • Output: items <section>.<TAG>.<PARAM> (e.g. <Section>.FIC001.PV), points <STATION>:[<item>], plus lines/stations, displays and symbols (displays only on the CI Core in non-single configurations).
  • Precautions (§2.15): refresh open LIST displays after a CENTUM VP online download; CI Server does not allow alarm limits on the wrong side of SV; short data gaps after Vnet scan changes or RDC switch-over; trends may lag after large downloads — reload displays, roll over the history group, tune scan types.
  • Installed: launcher %TLS_ROOT_PATH%\tls\com\jwuiutl_ciexchange.cmd (no RGS on the test system).

2. CI Exchange for Prodigy (§3)

  • For CCC Prodigy turbo-machinery controllers (antisurge, performance, speed). Input: the Modbus register list (.csv, from MakerPro) per controller; the station name and IP are entered in the tool.
  • Install: copy Windows\EngineeringTools\CIExchange_Prodigy.zip from the medium, extract to C:\Program Files (x86)\Yokogawa\CIServer\Utility (create the folder), run CIExchange_Prodigy.cmd.
  • Workflow: create project → import source configuration → generate publication → load it. Output: items <section>.<Prodigy variable path>, Modbus points <STATION>:[<item>], and faceplates (title and engineering unit can be customised, §3.12.1).