I would like to add IO-Link sensors to the hardware, I have imported sensors via the IODD DTM Configurator.
When opening the Automation Studio 3rd-Party Device Manager, a warning is displayed in the Output Result: Duplicate DTM device found, it will be skipped (ProgID: IOLink.GenericDeviceDTM.DTMCore, Name: UF200.P IODD1.1, Version: V1.1)
However, it is not the same type of sensor, the reason is probably that the identification is only made via the device name, which is identical in this case.
No, I haven’t conducted any further research on this. Since we have replaced one of the sensors with an optical sensor from another manufacturer, the issue is no longer relevant.
We have also opened a ticket with B&R regarding this issue, here is the summary:
Problem description:
We have the two BAUMER ultrasonic sensors with the corresponding IODD XML files:
Type UF200.P25-GP1J.72N – Article No.: 11708359 // DTM ID3073
Type UF200.PA0-GP2J.72N – Article No.: 11708345 // DTM ID3083
BAUMER uses the IO-Link Device ID as identification.
B&R, however, uses the content of T_DeviceName_Global in Automation Studio / DTM Tool.
This leads to problems when using XML files with the same T_DeviceName_Global.
Solution:
BAUMER now uses different T_DeviceName_Global values for the sensors, as well as different Device IDs.
This ensures compatibility with B&R and other platforms.
B&R statement on this:
Essentially, there are two pieces of information that can be used to distinguish between two devices:
“T_DeviceName_Global”
“DeviceID”
The DTM from B&R (created by Hilscher) only considers T_DeviceName_Global.
Therefore, our DTM treats the devices as a single device, even if the DeviceID is different.
The B&R development department is aware of this; however, no changes will be made to this approach.
