CANopen LSS Node ID Joystick: Assign Without Bus Guesswork

Integrators commissioning a CANopen LSS node ID joystick use CiA 305 Layer Setting Services — not random DIP guesses — to select a device by its 1018h identity and write a valid node-ID (and optionally bit rate) over reserved CAN IDs 7E5h/7E4h [Source: CiA 305 LSS knowledge base; CiA CNLM node-ID assignment using LSS (Pfeiffer); MicroControl AN1204 LSS application note]. Trunsin ZS40 supports CANopen RFQs once EDS, PDO, and node-ID policy are documented.

Pair with CANopen joystick EDS file, CANopen PDO mapping joystick, CANopen EDS PDO deadband, and CANopen safety joystick SRDO.

CANopen LSS node ID joystick — selective vs Fastscan

Method When to use Risk if skipped
Switch selective (1018h known) Vendor/product/rev/serial known Wrong node selected
LSS Fastscan Unconfigured node-ID Endless bus guessing
Store + NMT reset After set node-ID ID not applied
Bit-rate switch Whole network change Partial baud mismatch

Writing a CANopen LSS node ID joystick address while another node still owns that ID causes silent SDO failures that look like “bad EDS” [Source: CiA 305 LSS manager/server rules].

Commission checklist

  • Read 1018h identity — Vendor ID + product + revision + serial.
  • Enter LSS configuration state — Selective switch for one server.
  • Set node-ID and store — Then reset communication / power cycle.
  • Import EDS and map PDOs — See EDS and PDO posts before Operational.

Termination still matters — CANbus wiring termination before blaming LSS tools.

Frequently asked questions

Is LSS the same as SDO?

No — LSS configures node-ID/bit rate at a lower layer than normal OD access.

What if node-ID is already 0xFF?

Unconfigured — use Fastscan or selective if identity known.

Does ZS40 require LSS?

Some builds ship fixed IDs; RFQ documents the policy.

PDO next?

Yes — PDO mapping.

Related articles

Specify aftermarket paths on ZS40 via the Trunsin configurator after OEM labels and harness photos are confirmed.

Request a Quote