DTM (eds) import error - AS4.12

Ask Questions B&R Software & Runtime
1

Hi,

I get the following error while trying to inport eds files. This is happenig to all eds files.

Does any one knows this error?

I’m using AS4.12.9 and DTM v2.11.2.

Thank you

image

2

Hi @Pedro_Antonio ,
I asked help to AI about your issue:
This error usually means your CANopen configuration file (like an EDS or DCF file) is missing a required parameter that tells the system how many Receive Process Data Objects (RPDOs) the device supports.

How to Fix the Error

You can fix this by manually editing the configuration file using a standard text editor like Notepad.

  1. Open the file: Locate your device’s .eds or .dcf file and open it in a text editor.

  2. Find the section: Search for the text [Device Info].

  3. Add the missing line: Underneath that header, type NrOfRXPDO= followed by the number of RPDOs your device uses.

  4. Save and reload: Save the file and reload it into your PLC or master configuration software.

Example Configuration

ini

[Device Info]
VendorName=ExampleCorp
DeviceName=MotorDrive
NrOfRXPDO=4
NrOfTXPDO=4

=============
I think you should ask their Support team to review their EDS file and add missing entries.

Ciao
Valerio

3

Hello Valerio,

Thank you for your answer.

Unfortunatly the file has no problem.

The .eds file is for an EthernetIP master and it is beeing used without any errors in other PCs.

The error came with a new installation of the AutomationStudio 4.12 but I don’t find a reason for that. The applications like B&R DTM/B&R Generic Hart DTM have the same versions on all PCs.

Best Regards

Pedro.

4

Hello,

I suppose you use a IF10D-1 and used “import fieldbus device” instead of “import DTM device”

image
image272×427 11.8 KB

Please use Import DTM device and then select EthernetIP device

image
image418×217 7.05 KB

The reason for your problem is if you use “import filedbus device” then AS thinks you use the “old” native fieldbus options where EthernetI Pwas not available. Due to this AS thinks your EDS file is aCanOpen device and inside the EthernetIP EDS files keywords for CanOpen are missing

5

Hello,

Thank you!

I’ll try this.

6

Thanks so much Oliver for the clarification!

Ciao
Valerio