DNA Configuration Error on POWERLINK (X20IF1082)

Ask Questions Controls & Vision
1

Hi everyone,

I am trying to set up a POWERLINK network using an X20CP3684 CPU (master) and an X20IF1082 interface module. My topology consists of an X20BC0083 bus controller and two generic POWERLINK stations named “plctest30” and “plctest35” that are X20CP1684 CPU (slaves).

{411474FF-997C-400F-9E9E-E21B82BA3228}
{411474FF-997C-400F-9E9E-E21B82BA3228}1211×454 99.8 KB

I am encountering two specific issues depending on the configuration mode:

  1. Automatic Configuration (DNA): When I set the DNA Configuration to “automatic” in the IF1 parameters of the X20IF1082, Automation Studio returns the following build error: “The hardware module ‘plctest35’ does not support DNA and therefore can not be used in this DNA-Strand.”

{C54BAB8B-6C88-459E-AEAE-24EE49E62FA5}

{4F9997FE-75FD-4D2C-AD1D-EF7E4A99E9B3}

  1. Manual Configuration: If I switch the configuration to manual, the build error disappears and I can transfer the project. However, the network fails to initialize properly, and the plState remains stuck at 1.image

{32858074-A563-4D9C-8A8D-600C60B06ACA}
{32858074-A563-4D9C-8A8D-600C60B06ACA}1279×547 45.8 KB

I have configured the DNA settings in X20BC0083 as shown in the photo

{83E60571-2B85-49DC-8630-22125F49BD55}
{83E60571-2B85-49DC-8630-22125F49BD55}972×203 9.52 KB

Is it possible to create this configuration with the hardware I am currently using, or do I need to replace an element that is incompatible with the network I want to build? If the hardware is correct, am I missing a configuration step that is preventing a successful connection between the remote, plctest35 and my master?

Thanks in advance,

Estela

2

Hello Estela Rodriguez i Milan;

Firstly welcome to B&R community,

The first thing I’d try to see is:

1- if the hardware in SDM is properly detected, or see which is not,

2- Check the node number of the real hardware

3-Since Dna is not compatible with the generic powerlink, I don’t think there is reason to set in the bus controller, try deactivating it.

4- Check on logger to see if more error is present.