FANUC
Overview
Section titled “Overview”Couples a FANUC controller or a RoboGuide cell. Platform: Windows only.
Set up and parameters
Section titled “Set up and parameters”| Parameter | Example |
|---|---|
| Address / Port | 127.0.0.1 / 60008 |
| Axis count | 6 |
Addresses are FANUC signal names — a prefix plus a number, such as do4, di1, ui1, ao2. The prefix decides the direction: robot outputs (do, uo, ro, sdo, ao, wo) are read by realvirtual, robot inputs (di, ui, ri, sdi, ai, wi) are written by it.
With an axis count set, the robot’s joint positions are published additionally as <interface>.axis1 … axisN.
A RoboGuide cell with several robots uses one port per robot, incrementing from 60008.
Create or import signals
Section titled “Create or import signals”- Manually. Enter the FANUC signal name, a prefix plus a number:
do4,di1,ui1,ao2. The prefix gives the default direction and the dialog prefills it.axis<N>binds a joint position under a signal name of your own. - 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