KUKA OfficeLite
Overview
Section titled “Overview”Couples KUKA OfficeLite through the OC_Assistant_OfficeLite Y200 server.
Set up and parameters
Section titled “Set up and parameters”| Parameter | Example |
|---|---|
| Host / Port | 127.0.0.1 / 54600 |
| Max digital signals | 10 (up to 8192) |
| Axis count | 6 |
Couples to KUKA OfficeLite through the OC_Assistant_OfficeLite Y200 server. Addresses follow KUKA’s numbering: in1 is $IN[1] (written by realvirtual), out1 is $OUT[1] (read), axis1 … axis6 are the joints in degrees. Joint positions are also published as <interface>.axis1 … axisN. Bits above Max digital signals are not exchanged and show as a signal issue.
Not to be confused with WINMOD Y200, which is a shared memory on the same PC.
Create or import signals
Section titled “Create or import signals”- Manually. Enter
in1($IN[1], written by realvirtual),out1($OUT[1], read) oraxis1…axis6(joints in degrees). - 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.
See also
Section titled “See also”- Common concepts — text signals, direction, write access, tracking signals
- Configuring interfaces — adding signals, direction and write access
- All supported interfaces
- Troubleshooting — connection and signal problems