Jordan BurgessSoftware design · Connected systems · Embedded hardwareView in archive

Remote Diagnostics for Fielded Power Systems

Establishing remote diagnostic paths that make fielded power systems understandable from a distance, not just visible online.

Minimum useful evidence

  • Device identity and topology
  • Time-correlated events
  • Commanded and reported state
  • Configuration and software context
  • Source of each observation

I set up and use remote diagnostic access to mobile and off-grid power systems through device telemetry, network connectivity, status reporting, configuration inspection, and structured testing in the field.

The work includes troubleshooting diagnostic paths, interpreting telemetry, investigating missing devices, and comparing reported behavior with the state of the system. An important part of that process is separating a problem with remote access from a problem involving control, configuration, firmware, power, or the application itself.

Being online is useful, but it is not enough to make a system diagnosable. A useful investigation requires knowing which device produced an observation, when it happened, what configuration and software were present, what commands had been sent, and what state the system reported afterward. Without that context, remote data can show that something happened without explaining why.

  • Remote diagnostics
  • Telemetry
  • Observability
  • Field support
Format
Remote diagnostics
Threads
Fieldwork

Ongoing