Communication Problems

Symptom-first troubleshooting method for communication failures in CyberSun deployments.

Start with the physical layer

  • power
  • cable
  • link/activity
  • correct interface

Then verify protocol parameters

  • Modbus TCP host and port
  • RTU slave ID
  • baud rate
  • parity
  • stop bits

Then verify SEMS configuration

  • correct device profile
  • correct device type
  • correct channel / endpoint
  • polling enabled

Then verify live evidence

  • current device status
  • event history
  • whether the same device polls correctly from another known-good tool or procedure
CyberSun SEMS live values page for communication troubleshooting
Use live values and grouped telemetry to determine whether a communication problem affects the whole device path or only specific values.
CyberSun SEMS events page for communication troubleshooting
Check the Events page for repeated write failures, offline transitions and fault history before changing multiple parameters at once.

Was this helpful?

Did this article answer your question?