Skip to content

Yaskawa Motoman

Beta

Couples a Yaskawa Motoman controller through the High Speed Ethernet Server (HSES) over UDP. Beta.

ParameterDefaultMeaning
Address / Port127.0.0.1 / 10040Controller IP and HSES UDP port
AxisCount60–8 joints published as axis1 … axisN
PulsesPerDegreeEmptyOne positive value per axis, from the controller’s pulse parameters
TimeoutMs1500 msTimeout for connect, read and write calls

Couples to a Yaskawa Motoman controller through the High Speed Ethernet Server (HSES) over UDP. The poll interval is the interface’s update cycle.

The controller reports joint positions in encoder pulses. CONNECT converts them to degrees with PulsesPerDegree, one value per axis. Without a complete list (exactly AxisCount positive values) no axis signal is registered, and the interface status names the reason.

AddressDirectionMeaning
axis<N>ReadJoint N in degrees
io:<byte>.<bit>Read for bytes 1–512 (user inputs) and 1001–1512 (user outputs); written for 2701–2956 (network inputs)One bit (0–7) of an IO byte
status:servo, status:running, status:alarm, status:hold, status:teach, status:playReadController status
var:B<n>, var:I<n>, var:D<n>, var:R<n>Read as PLCOutput, written as PLCInputByte, integer, double-integer and real variables

Writes need the interface’s write access. Only the network input range 2701–2956 can be written; other bits of the same bytes keep their values. The interface sends no motion, servo or job commands. Writing to the controller needs remote mode on the pendant; reading always works.

HSES is a UDP protocol that is usually not routed between networks. Run CONNECT in the same subnet as the controller.

  • Manually. Enter axis<N>, io:<byte>.<bit>, status:servo and similar, or var:B<n>, var:I<n>, var:D<n>, var:R<n>.
  • Browse. No browse: enter addresses by hand.
  • File import. No protocol-specific file import.
  • From the model. Use Addresses → Import address table… in the signal-mapping section of the CONNECT panel: a CSV or TSV with name;address[;dataType[;topic]] rows, where the name is the model’s signal name. New signals take direction and type from the same-named model signal; signals that already exist keep their configured type. Fill from controller… has nothing to match, because this protocol cannot be browsed. See Configuring interfaces.

How direction, data types and write access are decided is explained in Common concepts and Configuring interfaces.