Skip to content

In a real cabinet you find a signal fault with the LEDs on the IO cards. The IO modules window brings that tool into realvirtual. It shows the cards of your controller as a flat 2D picture, sorted by slot, with one LED per channel. The window opens next to the 3D model, like the operator panel.

An IO card is a component, WebIOModule, on a node of the model. Nothing is drawn in 3D. The component stores which signal each channel shows, and the window reads the live values.

The IO modules window with a DI card and two DO cards: one LED per channel, labelled with the signal name and the channel number; the LEDs of StartLamp, StackGreen and ArmDown are lit, ArmIsDown is dark

The LED always shows the value on the controller side of the card. That is what makes a fault findable: the simulated fault sits between the card and the field.

Card kindSignal typeLED and display
DI (digital input)PLC input, boolThe value the PLC reads, including a fault on the line
DO (digital output)PLC output, boolThe value the PLC program wrote, even if a fault keeps it from reaching the machine
AI (analog input)PLC input, float or intA bar and the number the PLC reads
AO (analog output)PLC output, float or intA bar and the number the PLC wrote

Example: a training scenario holds the output ArmDown at false. The PLC program sets it, so the LED of the DO card lights up, and the arm still does not move. Students conclude that the fault is behind the card, not in the program.

Where the LED sits relative to the fault The PLC program writes ArmDown. The LED of the DO card shows that value. A signal fault between the card and the field holds the line at false, so the model never receives it and the arm does not move. PLC program writes ArmDown = 1 DO card LED is on: it shows the PLC value Fault StuckFalse holds the line at false Model sees false: the arm does not move What the LED shows: the controller side What the machine gets: the field side
The LED sits before the fault. If the LED is on and the machine stays still, look behind the card.
  1. Select the node that should carry the card, or create an empty node.
  2. In the Inspector choose Add component and pick WebIOModule.
  3. Set Kind, Slot and Style and give the card a Label, for example -A2.
  4. Under Channels add one row per channel and pick the signal with the reference picker. The picker only offers signals that fit the Kind; a wrong type is shown as an error at the field.
PropertyDescription
LabelName printed on the card, for example -A2
KindDI, DO, AI or AO
SlotPosition in the window, counted from 0. Cards are sorted by slot
StyleLook of the card: ET200SP, BeckhoffEL or Neutral
ChannelsOne row per channel with Source (signal), ChannelLabel, LedColor and, for AI and AO, RangeMin and RangeMax in the unit of the signal

The card does not store an address. If a CONNECT gateway maps the signal to a controller address, the window shows that address live. Without CONNECT it shows the channel number.

Instead of adding each card by hand, use Generate from signals in the Inspector of a WebIOModule. It reads all signals of the document, groups them by direction and type, and creates the cards with 8 channels each (16 on request). The whole run is one undo step.

AI and macro users call the same function as the command ioModule.generateFromSignals with the argument channelsPerModule set to 8 or 16.

In the normal (teacher) view you can click an LED of a DI or DO channel to force the signal, and click again to release it. This uses the same force as the signal list, including its confirmation. In the student view the LEDs are display only.