Wago PFC I/O Configuration Manual
Introduction
This document describes how to set up an application to use the WagoPFCIOServer component and how to configure the WagoPFCIOServer instance to communicate with the I/O modules directly connected to the Wago PFC 100/200.
About
The WagoPFCIOServer component implements native KBUS access on the Wago PFC 100/200 using the Device Access Layer and Application Data interface (DAL & ADI).
Note: 'Complex' Wago modules such as the 750-658 and 750-652 are not supported yet.
Terms and Definitions
| Wago PFC 200 | An Industrial arm-based controller with built-in I/O and external interfaces. See also Wago PFC 200 |
| Wago Module | A physical module as supplied from Wago. The 750-431 digital input module is an example of such a module. |
| SD Card | A physical storage medium. See also the SD Association page on SD Card capacity. |
WagoPFC 100/200 First-Time Setup
- Install and set up the correct image for the WAGO PFC 100/200 as explained in the toolkit for the WAGO PFC:
- For the Wago PFC 100/200 Gen.1, please see Toolkit 1.3 - WAGO PFC ARMv7 32-bit (Gen.1) for how to install and setup an image that works with CDP Studio.
- For newer versions of the Wago PFC 100/200, see Toolkit 1.3 - WAGO ARMv7 32-bit for how to install and setup an image that works with CDP Studio.
- Remember to select the correct toolkit for the device that runs the WagoPFCIOServer
WagoPFCIOServer component configuration
Configuration elements
| Name | Description |
|---|---|
| WagoPFCIOServer | The IOServer that converts CDP Signals into data understanable by the Wago KBUS, and from Wago KBUS to CDP Signals. This IOServer must run at least 20Hz, or outputs will be set to 0 by the hardware. |
| IOModule | A generic configuration element that can be dragged into the WagoPFCIOServer component. |
The IOModule has the following settings:
| Name | Description |
|---|---|
| Name | The unique name of the I/O module |
| Model | The model name, currently only WagoIOModules.IOModule is a supported model name. |
Configuration procedure
To start configuring the IOServer it must be added to your application in configure mode. See Wago PFC Setup Guide for tutorial.
Note: The WagoPFCIOServer will validate the physical configuration of the modules as reported by the ADI and compare it with the one made in CDP Studio. If there is a mismatch between the physical configuration and the configuration made by CDP Studio, the WagoPFCIOServer will be suspended. The problem must then be fixed either in config or physically, and the application should be restarted. The same applies if the physical bus is changed during runtime.
The following typically must be done to the added WagoPFCIOServer component to configure the i/o server:
- Add in one or more 750-xxxx elements, in the same order as they are physically stacked on the buscoupler.
- Optional: Give the module a unique name
Get started with CDP Studio today
Let us help you take your great ideas and turn them into the products your customer will love.