Skip to main content

Logical I/O of a Standard Field Device

These logical I/Os serve the exchange of standard I/Os between the standard and safety controllers.

If standard I/Os are used in the safety application, then this data is not safe!

First the desired standard field device is inserted under the standard controller, depending on the device. The procedure corresponds to standard CODESYS.

Subsequently, the appropriate logical I/O ("generated logical device") must be inserted manually under the safety application object:

Adding the "generated logical device"

Procedure. Adding the "generated logical device"
  1. Select the Logical I/Os node point of the safety application object in the project tree.

  2. Click the Add Object context menu command with the Logical Device selection.

  3. In the Add Logical Device dialog in the Logical devices category, select the corresponding logical I/O in the Generated Logical Devices subcategory

  4. Click the Add button.

Connection of a field device to the logical I/O

After successful insertion of the standard field device under the standard controller and the corresponding logical I/Os under the safety controller, they must be "linked" to one another in order to be able to exchange I/O data.

Assignment of a field device to the logical I/O

  1. Select standard field device in the project tree

  2. Click "Edit object" in the context menu.

  3. Open the (...) I/O Mapping tab (in the case of PROFIBUS).

  4. Click the Logical I/O mapping combo box.

  5. Select the corresponding logical I/O from the list that opens.

Among the logical I/Os, only those that have not already been mapped to other devices or Logical Exchange GVLs can be selected. The system accepts only the selection of a logical I/O that has the same device description as the physical device.

A function block of the type NonSafeIO is generated as a stack instance.

Tip

The editor of the logical I/Os of standard devices has no Safe Configuration tab or Safe device parameterization tab. The configuration and the device parameterization take place under the default application as in CODESYS standard.

Type consistency of the I/O channels

Important

. The type consistency of the I/O channels is only ensured
  • if the application revision levels on the safety controller and on the standard controller correspond to the revision level of the same translatable project

    and

  • if the field devices in the project correspond to the field devices in the machine. – Depending on the bus system, a mismatch is recognized automatically here (e.g. with PROFIBUS).