Profinet ABCC - mismatch between Real Identification and Expected Identification

Thomas Kuhnt

• October 08, 2024 12:56

Hi,

I have a running setup of a Master Controller with Anybus as Profinet Device. The device uses configurable WORD arrays for cyclic communication. I can generate a GSDML in which the names of the Application Data Object Instances are visible as expected. If the AR is established, cyclic data exchange works in principle, but the Anybus error LED's show an "Real Identification" mismatch. In the manual I see that the "assignment" of ADI's & names are done automatically. Can you give me any advice how to identify the reason for this?

Kind Regards,

Thomas

1

• 

  Thomas Kuhnt

  • October 09, 2024 06:04

  I have attached screenshots from my Profinet Master showing the Identification Data ("Expected" with my names provided by the Application Data Object Instances and "Real" with the ADI instance used as ModuleInfo)

  Thanks in advance,

  Thomas

  0
• 

  Thomas Kuhnt

  • October 23, 2024 05:30

  Hi,

  Does anyone have an idea what I could change in code? I have used the host application example code as template. It's not the first time I used it, and I didn't expect such a problem.

  Kind Regards,

  Thomas

  0
• 

  Deryck Beliveau

  • November 18, 2024 16:32

  Hello Thomas,
  
  Sorry for the late response here.  If you have not resolved typically this issue is suspect this has something to do with the ADI's being mapped.  Often this is the data being mapped incorrectly for how the hardware is setup.  In your case I am wondering if there could be an an issue with the GSDML file where the modules are not setup correctly. 

  0

Please sign in to leave a comment.