MODICON M580 : NOP0300 parameter value from Easergy P5F30 relay don't update /change

[Maitree_ri]

Dear Commmunity

        I have the project that use PLC Modicon M580 connected to  Easergy P5F30 relay via Iec61850 protocol thought NOP0300 I/O card. we met 2 from 30 pcs of the relay don't updated value when real measurement or BI at relay has changed. Could you please advised procedure to investigation or fixing them.

        Activity we done below.

                1. Use IED scout monitor, the value as changed as real value at P5F30

                2. Down load new CID file to P5F30

                3. Disconnecetd and connected UTP cable to P5F30, the value that monitor at PLC has changed but then they still this value 

Thank you

Maitree R.

[Siddiqui]

Hi @Maitree_ri,

Check my comments below:

My understanding is that you have 30s P5 relays communicating with the BMENOP0300 module, and you are facing issues with two of them. Is that correct?

I would advise you to start the investigation with the following:

1. Open the device DDT of the Easergy P5F30 relay inside the ECE and verify the freshness status while connective live to the M580 controller. You can use the animation table to check the status. Check the status of the relay from where you are facing the issue. The below snapshot is just for reference. You verify the P5F30 status from your application, and the value should be 1, which indicates that IED is communicating with the BMENOP0300 module.

2. You mentioned that you downloaded the updated/New CID file into the relay. Please make sure that you are using the same updated CID to configure the IEC 61850 client inside the Modicon IEC 61850 configuration tool for the BMENOP0300 module. The CID files should be the same inside the IED and in the BMENOP0300 module.
3. You did not mention which way the values are updated in the BMENOP0300 module: via polling or reporting.
4. Whichever method is used, you have to trigger it using the DDT of the relay inside the ECE and ensure that you get positive status feedback from the DDT.

The below snapshot is just for your reference for polling and reporting control blocks "CMD" and "status" inside the DDT.

5. Which method was used to get the updated values when you used IED Scout?
6. Check the DDT status using the ECE and share it with me so I can take a look and advise further.

I hope the above comments provide help at least to initiate the investigation.

Best Regards,

MWS

[Maitree_ri]

Hi @Siddiqui

         Thank for your advised please find my reply as  below.

         Yes I mean we have P5F30 30+ pcs   connected to BMENOP0300 modules . And I attached system architecture as attached. (As attached have P5M30  10+ pcs)

          1. As  we are checked, the freshness status value is 1.

          2. Yes, I confirmed they are same CID files at P5 relay and BMENOP0300 module.

          3. I'm not sure that's the meaning of the polling method. As the attached picture shows, the polling status shows failed after being sent.cmd, but the others are normal.

          4. Is it same as 3.? Or do you mean check error at P5 relay, please advised.

          5. How to checked which way in IED scout? polling or report?

          6. I attached logic file for review.

If you need more information, do not hesitate to request from me.

Thank you.

Maitree R.

[Siddiqui]

Hi@Maitree_ri,

Thank you for sharing more details.

I checked your application. You have configured five P5 relays inside the NOP module and are reading the data from IEDs using the polling method. As you mentioned, the freshness status value of all five IEDs is 1. Please confirm this.

For the IED SW05_IR1_P5F, you are facing an error on the polling command status. Have you been facing this error since the start of the polling command? OR does it work fine for a few polling commands, and then it starts giving this error status?

I suggest the following: In your polling trigger logic, please verify the polling command status feedback for the given polling command and make sure you get the successful feedback status before initiating the following polling command.

Maybe you are polling too fast at every 200ms? But you can verify this while doing the test with IEDSCOUT, as explained later on in this comment.

You can convert the Polling command status into binary and then segregate the low and high bytes to understand the status clearly, as shown in the snapshot below.

The snapshot below explains the polling command status register. For example, the CMD is triggered with the value 1. Bit 0 of the low byte of the command status register is also equal to 1. The High bytes of the command status registers show that the command is successfully executed with bits 7 and 6 equal to 01.

Please refer to the BMENOP0300 module user guide for a detailed explanation of status registers.

You can access the TVDA document from the following link. It might help you better understand the BMENOP0300 module and the basics of the IEC 61850 data exchange mechanism.

Connect Modicon M580 to an IEC61850 Network

From the IEDSCOUT, if you drag and drop the Data Object (DO) into the "Activity Monitor" Windows screen, you can also configure the polling interval, which is set to 1 second in the snapshot below.

The following DOs from the IR1_P5F relay you are reading through the polling method inside the BMENOP0300 module, you can use IEDSCOUT and drag all those DOs and perform the test to make sure you are able to poll all the information from this P5 without getting any errors. From here, you can start the investigation.

I am on vacation, so I did not go through the shared architecture, but it would be great if you could provide a simple explanation of the connection between the NOP module and the IEDs.

I hope the above comments help start the investigation. Please share the outcome of the IEDSCOUT test, and we'll see where it leads.

Best Regards,

MWS