AXC-2152 Redundant and FPNO-21
I'm integrating 2 AXC-2152 (ASR) with some ABB inverters. I want to communicate them using Profinet S2, but those drivers don't communicate with the redundant control system.
I already checked if the GSDML of the FPNO-21 contain “RT_InputOnBackupAR_Supported” and i'm using the last version of the available GSDML.
I also increased the time of the system redundancy data hold time to 2400ms and increased the monitor time to something around 1s.
Besides the inverters, we have 1 BK PN TPS and this module work correctly on PROFINET S2.
Jeferson Carvalho.
Comments
Hi Jeferson.
Here is the answer from the developers of the ASR app (you can also contact them directly using the "Contact Developer" button in the PLCnext Store):
What happens if you operate your system with just one PLC. Does the Profinet IO device of the ABB inverters then connects to this PLC?
Did you follow up all the necessary steps for the integration of a Profinet IO device into the ASR system as stated in the documentation of the library?
Especially that the “Start AR on startup” parameter has to be set to “No” and that the “Name of Station” of all Profinet IO devices has to be stored at the “arrAR_DevList” InOut parameter.
Which status is shown for the Profinet IO devices at the PROFINET Diagnostics in the web pages of the PLCs?
Hi, good afternoon.
Here the answers:
What happens if you operate your system with just one PLC. Does the Profinet IO device of the ABB inverters then connects to this PLC?
Did you follow up all the necessary steps for the integration of a Profinet IO device into the ASR system as stated in the documentation of the library?
Especially that the “Start AR on startup” parameter has to be set to “No” and that the “Name of Station” of all Profinet IO devices has to be stored at the “arrAR_DevList” InOut parameter.
Which status is shown for the Profinet IO devices at the PROFINET Diagnostics in the web pages of the PLCs?
I've made some actions trying to solve this problem:
But none of this actions solved the problem, i also found another issue, the PLC NEXT ENGINEER 2023.0.1 LTS crashes and close when we try to open the LOGIC ANALYSER.
The picture of wbm diagnostic:
About the previous discuss, any updates?
Hi Jeferson,
In the case of the Profinet connection is not functioning, which error code is shown at the PROFINET Diagnostics in the web pages of the PLCs?
Please also get in contact with the vendor of the Profinet IO devices and check them, whether the GSDML device description file and the firmware you are using is the proper one.
If this doesn’t help, we would need a Wireshark record of the Ethernet data traffic between the PLCs and the ABB Profinet IO devices for further analysis.
The web pages of PLCs shows me exactly this error code (0x0023), on both PLCs.
The vendor of the Profinet IO devices told me if the ABB Driver is shown on the profinet scan, the connection must work. But in the following image the scan shows me that the device online isn't the same of the offline project.
The Vendor also said that the firmware version of FPNO-21 and GSDML used are correct.
They (ABB) are investigating this issue internally.
About Wireshark record, i'll provide this data traffic log as soon as possible.
Good morning,
After several weeks, i finally recorded the wireshark ethernet data traffic between the devices.
Besides the data traffic, i printed some informations that may be useful to understand the scenario.
Both files are attached on this comment.
Let me know if those informations are enough to solve this problem.
Best Regards.
Jeferson Carvalho
Hi Jeferson,
I looked at your Wireshark records. Unfortunately, they do not contain the whole data traffic of the communication between the PLC and the ABB Profinet IO device.
To create a complete, meaningful Wireshark record, you need to mirror the port of the PLC on the switch. You can set this mirroring on the switch's WBM. In my example, the PC with which I perform the recording is connected to port 8 and the controller is located on port 5:
As an example, I attached a typical Wireshark record which contains the complete Profinet communication.
What makes me a little suspicious at your case is that the PLCnext Engineer displays a warning in the "Online Devices" view (as it is shown at your image “21”). The warning indicates that the device type "FPNO-21 S2" is integrated in the Profinet configuration, but actually the device type "FPNO-21" is connected.
That's why I'm wondering if you're using the right hardware and firmware version of the ABB device? Does the device you are using actually supports Profinet S2 redundancy?
I have carried out an experiment in which I have integrated a non-S2 capable device into the Profinet configuration. The same behavior occurred as with your ABB Profinet IO device. If there is only one controller in the network, the Profinet communication works fine. But as soon as I connect the second controller in the network, both controllers no longer have a Profinet connection to this device and the same error as yours (0x0023) is displayed. That's why I suspect that the device you're using doesn't support the Profinet S2 redundancy protocol.
Good evening,
I'll provide the correct wireshark data record until next week. Just to clarify a doubt, i'll have to mirror the port connected to the controllers (primary and backup) or the device PROFINET, which is the ABB driver?
About the ABB module, FPNO-21, their support checked with me the firmware and hardware version, and assured that is correct and supports PROFINET S2 redundancy. I'll attached the GSDML i used on the network configuration, the version 2.4 supports Profinet S2 redundancy.
The behavior of the ABB module was exactly as you said, once i have just one controller on the network, the connection is stablished just fine, the moment i add the second one, neither controller could connect to the driver.
You indicated you were using the latest version of the GSDML file for the FPNO. Just to confirm...it is GSDML-V2.4-ABB-FPNO-20201118?
Yes, i'm using GSDML-V2.4-ABB-FPNO-20201118.
Tomorrow i'm going to record wireshark data traffic, just to confirm and provide the correct data traffic, i'll have to mirror the port connected to the controllers (primary and backup) or the device PROFINET, which is the ABB driver?
You would to mirror the port at which the controller (PLC) is connected.
In this way we could then see all the Ethernet telegrams which are send and received by the PLC.
Hi Friedrich,
I just recorded the wireshark data traffic on startup for both PLCs (Primary and Backup). I mirroed both PLC ports and rebooted both PLCs to record the traffic on startup.
I removed the other devices from my PROFINET network.
The "unmanaged switch_1" appeared after the configuration of port mirroring.
Let me know if this is enough to understand this problem, cause i'm gonna be at the client Site until tomorrow.
Good afternoon Friedrich,
I'd like to know if there is any updates about this issue?
Best Regards,
Jeferson.
Hi Jeferson,
the analyses for this case unfortunately took a long time.
Since I do not have the Profinet IO device from ABB, the error analysis was theoretically carried out on the basis of the Wireshark records provided by you:
In the device description file of the Profinet IO device, the attribute “DataInvalidOnBackupAR_Supported” is set to True.
According to the Profinet specification, this attribute is an option that the IO controller either may use or not.
The controllers of our ASR system do not need this option, and therefore this option is not activated when the Profinet connection is established.
Apparently, however, the IO device does not accept the Profinet Connect Request without this option activated and rejects the Connect Request from the PLC.
In order to confirm whether the behaviour described above is actually the reason for the problem, the Profinet connection establishment should not work when redundancy is switched on, even when the system is operated with only one PLC.
Can you confirm that if S2 redundancy is activated in the PLCnext Engineer project, even if only one PLC is switched on, the Profinet connection to the ABB device does not work?
Best Regards,
Friedrich
I tried this before.
Even with only one PLC on the network but using S2 Redundancy, the connection is not established.
When i deactivate the S2 Redundacy, i'm able to connect with the ABB Driver with no issues.
Best Regards,
Jeferson Carvalho.
Hi Friedrich,
I'd would like to know if these modules won't be compatible working on S2 redundancy.
Hi Jeferson,
Thanks for this information, this confirms our assumption:
Because the ASR system do not need the option “DataInvalidOnBackupAR_Supported”, our PLCnext controllers do not activate this option at the Profinet connection establishment.
Since this is an option that can either be used or not, the manufacturer of the Profinet IO device would have to ensure that in such a case the Profinet Connection Request is accepted by his device.
So, i assume that i'll have to contact the manufacturer to check this condition.
Yes, that would be the best thing if you also get in contact with the Profinet IO-device manufacturer.
I had already spoken to people who are working on the Profinet specifications. Their opinion is that the IO-device should allow the Profinet connection to be established, even if the controller does not need this particular "DataInvalidOnBackupAR_Supported" option.