FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important
information on the platform change.
01-21-2022 05:29 PM
Hi,
short facts / hypothesis:
- data mapping of process data from non-rexroth ethercat slaves can not be done byte-wise.
- This is maybe an issue of the ctrlx I/O Engineering software (which is an talored version of the codesys version)
Balluf IO-Link devices in Codesys V3.5 SP16.2 can use a feature to get the Process Data as type Bytes which creates Mapping nodes that would help ease the mapping process into PLC program variables.
See attached picture.
Note: Of course a so-called ESI device description file is installed in ctrlx I/O Engineering to get the fieldbus module and also the types of modules to be plugged into the bus, this file is available for download on Balluf website under the EtherCAT page https://www.balluff.com/en-de/products/BNI0077.
When Installed on Bosch Rexroth I/O Engineering tool software, The feature of BYTE type process data doesn’t show up (Grey IO logo) [Figure 2] and also no Mapping-Nodes available [Figure 3].
So the bit mapping has to be done BIT by BIT example [Figure 4].
So is this an issue of "there is no gray I/O icon" available when using ctrlx I/O Engineering vs. codesys? In the codesys installation every possible slave device config is offered two times: one time with "bit-wise-mapping" other time with "byte-wise-mapping"
Thanks for any hints.
BR
Andreas
Solved! Go to Solution.
02-28-2022 04:30 PM
Hello
sorry for the late answer, but this is a complex issue. Our development department goes in contact to Codesys directly.
If you install only the ESI-File of this device you see only a bit structure, in the native Codesys too. But if you install ESI-files of other Balluff devices with similar modules (e.g. BIS-V-6110 (https://www.balluff.com/en-de/products/BIS00U9)) the structure will be Byte like.
Statement of Codesys: It's a bug to mix up the different ESI definition. It could be possible that this will be fixed in the future by Codesys.
So in principial the situation is equal between Codesys and IO-Engineering.
If there are more questions/remarks you can contact me directly.
Best regards
Jochen
02-28-2022 04:38 PM - edited 02-28-2022 04:41 PM
Hi,
ok that is now clear. So we will check.
Thanks for the investigations. 👍
11-28-2023 08:18 PM
@drschiffler:, @Jochen_Mueller
Issue is fixed with 1.20 release.
best regards
Carsten