Choosing a PROFIBUS DP slave for CODESYS Control Win

How does CODESYS Control Win V3 reach a PROFIBUS DP slave?

Through a master interface you add to the PC: a PROFIBUS card of the cifX family in a free slot, or an EtherCAT link into a station holding a PROFIBUS master gateway terminal of the EL6731 class. The runtime is software; it speaks PROFIBUS through that hardware, and Control Win supports these two paths.

Both paths are licensed add-ons; the gateway path runs on a licensed PROFIBUS master SL product sold for that terminal.

Follow the chain from the sensor inward. Sensors land on the slave's input terminals. The slave packs their states into its cyclic input image and hands that image to the master across the PROFIBUS cable. Your application task reads the image from the master. No sensor is ever addressed from the PC, and no card choice buys input terminals: terminals come from the slave.

Before you order either path, read the card's supported operating systems and runtime versions. On the gateway path, confirm the EtherCAT interface the runtime supports, then the coupler, the terminal station's supply, and its assembly needs.

Does 32 input words equal 512 digital inputs?

Yes on the arithmetic, and only then on the hardware: 32 words times 16 bits per word gives 512 bits, or 64 bytes of cyclic input data, and that is 512 sensors when every bit sits on its own input terminal. The arithmetic is fixed: 32 words × 16 bits = 512 bits, and 512 bits ÷ 8 = 64 bytes.

The arithmetic sizes the container. The module list sizes the contents, because a slave's input image can also carry status and diagnostic bytes that the configured modules declare. So you buy in two moves: count input modules until the terminals reach 512, then read the GSD entry for that module list and confirm 64 input bytes.

Match the module electronics to your sensors while you are in that list. 24 V DC digital inputs sharing a common are the standard case. Check signal type, how channels share a common, isolation between groups, and the input filter when sensors pulse quickly.

Which slave device should you pick for 512 inputs?

A modular remote-I/O station configured as one DP slave: 16 input modules of 32 channels each, 16 × 32 = 512 terminals, and 16 × 4 bytes = 64 bytes of input image. A remote-I/O station is a bus coupler with module slots, a power supply, and one PROFIBUS address. The coupler is the DP slave the master sees; the modules behind it supply the terminals. Order coupler, modules, supply and terminal blocks as one line, and confirm the coupler's limits cover 16 modules and at least 64 input bytes.

When to pick something else

• Up to about 32 inputs: a fixed block slave with built-in terminals, one GSD entry, less assembly.
• Analog or counter channels mixed in: add their bytes first. A 16-bit analog value takes one word per channel, and fast counters take more.
• No slot and no EtherCAT interface on the PC: let a machine PLC own the I/O and serve the values to the PC; an OPC UA server in the CODESYS runtime is the standard read path.

How does an example 512-input station size out?

Sixteen modules of 32 channels in one remote-I/O coupler: 16 × 32 = 512 terminals, 512 bits = 64 bytes = 32 words on the wire, one station address, and a trunk that fits the cable table at the chosen rate. Scenario: a packaging line needs 512 digital inputs, every sensor is 24 V DC, the farthest sensor sits 18 m from the cabinet, and the PC has one free slot.

• Terminals: 16 modules × 32 channels = 512 sensor points.
• Image: 512 bits ÷ 8 = 64 bytes = 32 words of input data.
• Master path: a cifX-family card in the free slot.
• Bus: address 3 on the coupler, 1.5 Mbit/s everywhere, trunk measured at 60 m. Type A cable allows 200 m at 1.5 Mbit/s, so 60 m fits with margin.
• Termination: switched on at the card connector and the station connector, off everywhere between.

If the module list you choose appends one status word per module, the image grows: 16 × 2 bytes = 32 extra bytes, 96 bytes total, 48 words. Your application mapping shifts with it, and the coupler must carry the larger image. That is why the GSD is read before purchase, with the module order fixed.

Result: one DP slave at address 3, 512 sensors landed, 64 bytes crossing the bus each cycle.

What bus settings must match before data flows?

Set every device on the segment to the same rate between 9.6 kbit/s and 12 Mbit/s, give each station one unique address from 0 to 125, and switch termination on at both physical ends of the trunk. PROFIBUS DP sits in IEC 61158, and its Type A cable table sets the length per rate:

Pick the fastest rate your trunk allows, since a 64-byte image taxes the cycle more than a small one. One segment carries up to 32 stations, masters included; repeaters join segments into a longer network. Set the coupler address on its rotary or DIP switch and enter the same number in the master configuration.

On wiring, buy PROFIBUS-specified cable and connectors. On the standard 9-pin D-sub, the green wire lands on pin 3 and the red on pin 8. Termination lives inside the connectors and is switched on only at the two physical ends of the trunk.

When the slave stays dark, read in this order: supply voltage at the station, the station's power and bus LEDs, the master's diagnostic status in the engineering tool, then cable, address, rate and termination. Confirm the control program is executing first: check whether the CODESYS runtime is running or stopped. Bus checks put your hands in live cabinets: read LEDs and the tool while the panel is powered, and lock out the supply before you touch any terminal.

How do you import the GSD file and line up the I/O layout?

Take the GSD file from the slave's manufacturer, import it into the device repository of your master project, then pick the exact slave and its module list so both sides carry the same 64 input bytes. The GSD is the device description: identity, the modules the slave accepts, and the cyclic bytes each module adds. Every DP slave ships with one from its manufacturer, and the master needs it before the slave can be parameterized. The file name appears in the device properties next to the slave type, and the same import procedure is documented in the help of every major master engineering tool.

When the slave side is engineered in a second tool that exports a GSD, export there and import here. The two I/O configurations must agree completely: same identity, same module order, same input and output byte counts.

When the bus runs but a value reads wrong, compare the online device state and the configured image against the installed station before you touch the logic.

What should you ask for on the quote?

Ask for four groups as separate line items: the station with its GSD file, the master path with its license, bus cable with two terminated connectors, and the spares you want on the shelf.

Station

• Coupler with a DP slave interface rated for 16 modules and 64 input bytes
• 16 digital input modules, 32 channels each, 24 V DC, plus one spare on the shelf
• Station power supply and terminal blocks, labeled
• GSD file matched to the ordered firmware

Master path

• The card and its driver, or the EtherCAT coupler plus the PROFIBUS master terminal
• The master license for the runtime

Bus

• PROFIBUS cable cut to the measured trunk, plus slack at each end
• Two connectors with switchable termination

If operators also need a screen on the floor showing counts and states, treat it as its own job: specify a read-only process display for a plant.

Recommendation: For 512 digital inputs on Control Win V3, order a modular remote-I/O station with 16 modules of 32 channels, drive it through a cifX-family card when the PC has a free slot, and take the EtherCAT gateway path when it has none. Read the GSD before purchase, confirm 64 input bytes on both sides, and write address, rate and termination into the commissioning sheet.

Questions