IMDHMIControls LibraryShop main store

Troubleshooting

Why ctrlX I/O Engineering shows bits instead of byte mapping nodes

Industrial networks Published 5 min read

Short answer

The mapping tree follows the installed ESI descriptions. With only the Balluff BNI ECT-508-105-Z015's own ESI present, ctrlX I/O Engineering and native CODESYS both show bits; the byte nodes came from mixing other Balluff ESI files, a defect reported fixed in release 1.20. Map the bits now and update the tool.

On this page
  1. Why does ctrlX I/O Engineering show only bit mapping nodes?
  2. Is a missing byte mapping node a network fault?
  3. Is byte mapping unsupported for third-party EtherCAT slaves?
  4. Why did CODESYS offer bit and byte versions of the same slave?
  5. Which ESI file do I install for the Balluff IO-Link slave?
  6. How do I map bits into PLC variables until the tool is corrected?
  7. How do I apply the release 1.20 correction safely?
  8. Questions asked

ctrlX I/O Engineering shows only bit-level mapping nodes for the Balluff BNI ECT-508-105-Z015 because the mapping tree is built from the ESI device descriptions installed in the tool, and the byte-wise presentation came from a defect that mixes definitions across different ESI files. The tool vendor's support reproduced it both ways: with only this device's ESI installed, native CODESYS also shows a bit structure, and the defect was reported fixed in release 1.20. Map the bits the correct description offers today, update the engineering tool, and do not install other Balluff ESI files to force byte nodes.

Why does ctrlX I/O Engineering show only bit mapping nodes? #

The tree shows bits because it is generated from the ESI device descriptions installed in that copy of the tool, and with only this slave's own description present, native CODESYS shows exactly the same bit structure.

An ESI file is the EtherCAT Slave Information description, an XML file the EtherCAT ESI specification defines as the device description that ships with every subdevice. It carries the device identity, the object dictionary and the process-data layout, and the engineering tool reads it to generate the configuration tree and every mapping node you see. Which entries appear is a property of the installed description set, not of the cable, the master or the slave's firmware.

Is a missing byte mapping node a network fault? #

No — the missing node is a configuration-presentation problem that says nothing about cyclic data transport, so verify link status and slave diagnostics first and treat the mapping tree as a separate question.

A slave that drops off the bus, a wrongly identified device and a missing byte assignment node are three different faults. Link trouble can even hide from diagnostics, as in the case where CODESYS EtherCAT master xError stays false on cable pull. Walk the checkpoints in order:

  • Physical link: port LEDs, cabling and the master's slave diagnostics.
  • Configured slave: the identity the tool shows versus the module's nameplate.
  • Process-data layout: input and output lengths for the plugged modules.
  • PLC assignment: mapped variables and their online values.

If data moves and only the tree looks wrong, you have a description problem, and changing IP addressing or port settings will not alter the mapping presentation.

Is byte mapping unsupported for third-party EtherCAT slaves? #

No, third-party slaves are not excluded — the EtherCAT ESI specification ships an XML description with every subdevice, and the tool builds whatever bit or byte layout that description declares for the selected modules.

The BNI ECT-508-105-Z015 is a third-party IO-Link master on EtherCAT, and nothing in the ESI mechanism reserves byte-wise presentation for the controller vendor's own I/O. For third-party devices the description simply comes from the device maker's download pages instead of the tool's packaged set. What looked like a capability difference between the two engineering systems was a difference in which descriptions each repository contained.

Why did CODESYS offer bit and byte versions of the same slave? #

Because that CODESYS V3.5 SP16.2 installation also held ESI files for other Balluff devices with similar modules, among them the BIS-V-6110, and the tool mixed definitions across those files, exposing a byte tree the device's own description never declared.

In that installation every slave configuration was offered twice, once bit-wise and once byte-wise with the gray I/O icon, and the byte variant appeared only while the other descriptions were present. The vendor's support escalated it to the description handling, and the answer came back plainly: mixing definitions from different ESI files is a defect, reported corrected in release 1.20 of the engineering tool. The decision follows directly: treat the extra byte option as a diagnostic clue about the repository, never as a configuration technique, and keep unrelated descriptions out of any project that must be reproducible.

Install exactly one file: the ESI for the Balluff BNI ECT-508-105-Z015 from Balluff's official EtherCAT product pages, and record the description revision alongside the project so the configuration can be reproduced later.

Load it through the device-description repository management the engineering software provides — in ctrlX I/O Engineering, EtherCAT configuration is reached through the EtherCAT Master window in the ctrlX CORE side navigation. Description mismatches surface in other tools as identification failures, which is why fixing PROFINET device ID read errors in CODESYS scans starts at the same place: what the tool believes the device is.

How do I map bits into PLC variables until the tool is corrected? #

Map the bits the tree offers — an eight-channel block costs eight assignments — and if the program wants bytes, assemble them in code, where one byte variable replaces those eight mappings.

  1. Map each bit the tree offers to a BOOL variable, one assignment per channel.
  2. Assemble a byte in code where the program wants byte-wide access.
  3. Test the assembly with a known bit pattern before wiring it to outputs.

Structured text, every variable illustrative:

VAR
    byOut : BYTE := 0;    // assembled output byte
    xCh0  : BOOL := TRUE;
    xCh1  : BOOL := FALSE;
    xCh2  : BOOL := TRUE;
    xCh3  : BOOL := TRUE;
END_VAR

byOut := 0;
IF xCh0 THEN byOut := byOut + 1; END_IF;  (* bit 0 = 2#0000_0001 *)
IF xCh2 THEN byOut := byOut + 4; END_IF;  (* bit 2 = 2#0000_0100 *)
IF xCh3 THEN byOut := byOut + 8; END_IF;  (* bit 3 = 2#0000_1000 *)

The arithmetic: 1 + 4 + 8 = 13, so byOut holds 13 (16#0D), binary 2#0000_1101. Decoding 13 back sets channels 0, 2 and 3 and clears channel 1 — that decode is the test that proves the mapping. A corrected tool's byte node reduces the eight assignments to one, and this code can then be deleted.

How do I apply the release 1.20 correction safely? #

Update the engineering component carrying the release 1.20 correction in a test installation first, after backing up the project and noting the installed description revisions, then compare module arrangement and process-data lengths against the saved baseline.

  1. Identify from the release notes which component the correction ships in, and its compatibility with the installed automation software.
  2. Back up the project and the description files needed to reproduce it.
  3. Install the corrected package in a test installation, not on the station that configures the running machine.
  4. Reopen the project, refresh the device description if the tool asks, and reselect the slave only if the documented procedure requires it.
  5. Compare module arrangement, input and output lengths and PLC assignments against the baseline before the project goes back online.

A changed process-data layout reroutes I/O with no visible wiring change, so make description and tool changes on a bench project first. If byte nodes appear with only the exact device's ESI installed, the correction is in effect; if they still depend on other descriptions, the mixing persists and bit mapping remains the valid representation.

Questions asked

Does the gray I/O icon in CODESYS mark the byte-wise configuration?

In the compared CODESYS installation, yes: each slave appeared twice, once bit-wise and once byte-wise, and the gray I/O icon marked the byte variant. ctrlX I/O Engineering lacked that second variant because its description repository did not contain the extra definitions, not because the icon or the byte format was unavailable as a feature.

Will installing another Balluff ESI file give me the byte nodes?

It can, and that is exactly why you should not do it. The byte tree appeared only while ESI files for other devices with similar modules were installed, and the tool vendor's support confirmed that mixing definitions from different files is a defect. The resulting tree may not match the slave you actually configured, so the mappings become unverifiable.

What does an ESI file actually contain?

It is an XML device description, defined by the EtherCAT ESI specification as the file that ships with any subdevice. It carries the device identity, the object dictionary, the pluggable module types and the process-data layout the master exchanges. The engineering tool reads it to build both the configuration tree and the mapping nodes you assign to PLC variables.

How do I prove the fix worked after updating the tool?

Reopen the project with only the exact device's ESI installed and check three things: the slave identity the tool displays, the module arrangement, and the input and output lengths in the process-data image. If those match your saved baseline and the byte nodes no longer depend on other descriptions being present, the correction is in effect.

Keep reading

  • Comparison

    PROFINET versus DeviceNet for machine and panel I/O

    Choose by controller ecosystem first: PROFINET is industrial Ethernet at 100 Mbps with line, star and ring topologies, while DeviceNet is a CAN-based trunk running 125 to 500 kbps. Speed only decides when the panel needs dense or fast I/O. PROFINET for new high-speed machines, DeviceNet where the Rockwell-era devices and wiring already exist.

    Industrial networks

  • Troubleshooting

    Fix an S7-300 PROFIBUS gateway: module address above the image

    The PROFIBUS side is fine: the S7-300 accepted the GSD file and the telegram carries your values. The assigned module addresses sit above the CPU's process image, so ordinary I and Q access reads zeros. Move them into bytes 0 to 127, or read and write them with peripheral access.

    Industrial networks

  • How-to

    How to map a 1747-SDN scanner for DeviceNet drive control

    Seeing the drive in an RSNetWorx browse is not an I/O connection. Put the drive in the 1747-SDN scanlist, read the M-file words the scanner mapping assigns, and reference those mapped words in the SLC 5/04 ladder. A node address is not an integer-file offset: the mapping view, not node 10, decides where each command and status word lives.

    Industrial networks