/
Diagnostic Tools & Logs
Interlingo

The SmartGrid™ Control Suite provides a range of diagnostic features that allow operators and engineers to collect evidence, isolate causes, and validate corrective actions. These tools are essential in ensuring that issues are properly documented and resolved.

System Logs

Logs are the first resource when diagnosing problems. They capture both real-time events and historical information.

Log Categories:

  • Event Logs: Record alarms, warnings, and state changes.

  • Optimization Logs: Track algorithm decisions, such as peak shaving or load shedding.

  • Communication Logs: Record packet transmission, failures, and SCADA link status.

  • Safety Logs: Document E-stop activations, relay trips, and overcurrent events.

/var/log/smartgrid/
   event.log
   optimization.log
   comm.log
   safety.log

Retention Policy:

  • Default: 7 days, rolling archive.

  • Configurable via sg_config logrotate.

[2025-09-14 18:02:14] INFO: Controller 02 initialized successfully
[2025-09-14 18:02:20] WARN: SCADA link delay exceeded 150ms
[2025-09-14 18:02:22] ERROR: SAF-350 Overcurrent on Bus 1
[2025-09-14 18:02:23] ACTION: Load shedding initiated, Priority Load = HVAC

Always correlate logs with SCADA timestamps. This helps identify whether issues are internal to SmartGrid™ or external in the supervisory system.

Diagnostic Console

SmartGrid™ includes a built-in command-line interface (CLI) for on-site diagnostics.

Command

Function

Example Output

sg_status

Displays system health

Controllers online: 4/4; SCADA link: Active

sg_diag

Runs hardware diagnostics

PCU3: Relay test failed; PCU4: OK

sg_netcheck

Tests connectivity to SCADA servers

Ping SCADA_IP: OK, Latency: 22ms

sg_fwcheck

Checks firmware consistency

PCU1–PCU4 running v2.4.1

sg_diag
[PCU1] Relay test: OK
[PCU2] Relay test: OK
[PCU3] Relay test: FAILED
[PCU4] Relay test: OK
Summary: 1 module requires service

Run sg_diag before and after major maintenance. This creates a baseline to compare against future issues.

Network & SCADA Diagnostics

Communication issues are often network-related. Use sg_netcheck to verify paths.

sg_netcheck --scada 192.168.20.10
PING SCADA Server: Success
Latency: 22 ms
Packet Loss: 0%

If packet loss >2%, check:

  • Ethernet cabling integrity.

  • Switch port configuration.

  • Firewall rules.

Log Analysis Best Practices

  • Correlate Events: Align multiple logs to reconstruct event sequences.

  • Look for Patterns: Repeated errors often indicate systemic faults (e.g., firmware bugs).

  • Distinguish Cause vs. Effect: A SCADA timeout may be an effect of a relay failure, not the root cause.

  • Automate Parsing: Use log parsing tools (grep, awk, or vendor-provided analyzers).

When escalating to support, compress and send the entire /var/log/smartgrid/ directory rather than selective entries. Context matters.