Skip to content

SOP · Networking · Moxa

Certificates & authentication

How device identity works — and how an invalid certificate can leave a powered robot unable to communicate.

Purpose

Understand certificate-based authentication states.

Prerequisites

  • Device time is correct (validity depends on time)

Safety considerations

  • Follow your site's lockout / isolation and robot-zone entry rules before approaching equipment.
  • Only trained, authorized personnel perform service actions. This page is concept training.

Normal behavior

Certificates are valid, trusted and not near expiry; authentication succeeds.

Conceptual operation

  • Certificate → device identity → authentication → secure communication.

Inspection points

  • Expiry dates (via authorized tools)
  • Device clock / NTP

Diagnostics

  • Authentication errors in logs
  • Time drift

Common symptoms

  • Associated or reachable, yet secure session fails
  • Failures after a date passes

Recovery decision tree

  1. 1. Is the device clock correct?

    YES → Check certificate validity and trust chain.

    NO → Fix time sync first (per authorized SOP).

Authorized procedure

INTERNAL / AUTHORIZED ONLY

Certificate files, keys, enrollment and renewal procedures — available only in the model-specific, authorized SOP for your site. Not published on this website.

Verification

  • Secure session established and stable

Escalation

Security/network owner. Never paste certificates or keys into tickets.

References