Festo AX / PLCnext
Overview
Section titled “Overview”Couples Festo AX and Phoenix Contact PLCnext controllers through their GDS variable service. Platform: Windows only.
Set up and parameters
Section titled “Set up and parameters”| Parameter | Example |
|---|---|
| Host / Port | 192.168.1.10 / 41100 |
| User / Password | controller credentials |
| Connection timeout | 10 s (default) |
| Validate certificate | on (default) |
Addresses are GDS variable paths, for example Arp.Plc.Eclr/MainInstance.bStart. Subscription is used when the controller accepts it, with polling as the fallback. Validate certificate only matters for an encrypted connection; switch it off only for a test PLCnext with a self-signed certificate.
Create or import signals
Section titled “Create or import signals”- Manually. Enter the GDS variable path, for example
Arp.Plc.Eclr/MainInstance.bStart. - Browse. Yes. Browse walks the PLCnext GDS variable tree on the live connection.
- File import. No protocol-specific file import. Use Addresses → Import address table… for a prepared list.
- From the model. When the model already has its PLC signals, Addresses → Fill from controller… in the signal-mapping section of the CONNECT panel previews matches by exact name against what Browse finds and then writes the addresses. Addresses → Import address table… takes a CSV or TSV with
name;address[;dataType[;topic]]rows. New signals take direction and type from the same-named model signal; signals that already exist keep their configured type. 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