GGPTechnical enquiryRequest support ↗
Menu
Technical notes / Field questions

Engineering notes built for diagnosis and planning.

Diagnostic guidance for recurring control-system questions, organized around evidence, isolation and verification.

NOTE / 01Mark VIe diagnostics

Ground fault: what to check before replacing hardware

A ground-fault alarm does not automatically identify a failed controller or I/O pack. The diagnostic task is to separate the cabinet ground, field circuit, channel and communication symptoms.

Online checks
  1. Capture the exact alarm tag, timestamp, controller, I/O pack or terminal-board reference and operating condition
  2. Review alarm and trend history to determine whether the condition is persistent, intermittent or linked to a specific event
  3. Correlate simultaneous alarms, recent maintenance, moisture, wash-down, weather or switching activity
Isolated checks
  1. Apply the approved shutdown, isolation and lockout–tagout (LOTO) procedure before cabinet entry or circuit disconnection
  2. Inspect terminals, junction boxes and field devices for moisture, corrosion, loose strands, damaged insulation or conductive debris
  3. Disconnect sensitive electronics before insulation testing, then isolate field segments one at a time under the approved test procedure
  4. Repair the located cause and verify alarm, channel and network health before return to service
Evidence to retain

Retain alarm and trend exports, affected-channel references, inspection findings, circuit-isolation points, test records and the post-repair verification result.

NOTE / 02HMI & historian

Plan an upgrade without losing operating context

A workstation or historian upgrade is not only a hardware replacement. Software versions, project files, network addressing, time sources, alarm behavior and recovery media must remain aligned.

Before migration
  1. Create and verify the WorkstationST project backup
  2. Record operating system, application version, patch level, drivers and license status
  3. Capture IP addressing, naming, Ethernet Global Data (EGD) exchanges, users, permissions and time-source dependencies
  4. Baseline alarm, event, trend, historian and report behavior before any change
Acceptance & recovery
  1. Validate EGD data flow, alarm and event processing, trends, historian retention and display navigation
  2. Confirm user access controls and post-upgrade time synchronization
  3. Keep the original hardware or a verified image, baseline project, network reconnection steps and recovery test script
  4. Define rollback triggers and decision authority before the outage window begins
Evidence to retain

The handover pack should connect each baseline item to its SAT result and include a usable rollback procedure, not only backup files.

Apply the note to your system

Send the operating evidence for a focused review.

Request technical support ↗