PAS600L and IFM monitoring

[BrianW]

Hi all,

I was wondering if anyone could assist with an issue I am having connecting a stack of four or five IFM devices to a Panel Server PAS600L. While the 600L sees the IFMs and shows they are in a connected state, but when I try to use the monitoring function to see what status the IFM is reporting from an NSX breaker (with a BSCM module and NSX cord SD cable), I am not seeing anything as seen in the attached screenshot. 

The firmware on the PAS600L is up to date. 

Also, IFM status works just fine using Modbus Poll through the PAS600L, so perhaps there is a setting that I have overlooked using the webpage?

Any suggestions would be wonderful...

regards,

Brian

[Guillaume_Evrard · Accepted solution]

hello,

You are using serial modbus to the IFM ?

Have you tried to detect the devices using the PAS ? Normally you should detect the micrologic, not the IFM.

If detection does not work you can add the NSX manually bu selecting modbus ID and the model for your device. What we can see in your screenshot is a device without any datamodel (ie without any modbus table).

When using the embeded model PAS will detect the SN of the micrologic unit.

[Romain_Polette · Accepted solution]

Hi @BrianW , 

What Modbus registers are you reading to have information from your IFMs ?

Please check that your NSX breakers have a communicating Micrologic and follow the procedure described by Guillaume.

If you do not have communicating Micrologic and need only information from the BSCM, you will need to create a Custom Model because BSCM is not a device native to the Panel Server.

Regards, 

[BrianW]

Thank you both, @Guillaume_Evrard & @Romain_Polette , this is very useful information to have. I'm just basically retrieving the breaker status from a BSCM & SD switch on the NSX cord via the IFM back to the PAS600L. As you mention Romain, I cannot detect the BSCM, which now makes sense if its not yet supported, so until I get some time, I am using the method suggested by Guillaume and manually selecting the MB address and model. This works very well. 

It would be nice and a bit faster in set up if the auto detection worked for BSCM, but for now, this is good!

Thank you both for your wisdom!! Also, I have noticed that, as seen with the digital inputs, that there seems to be a significant lag or delay until the software reports a change in status, sometimes up to 20~25 seconds. I have been informed that this is normal? 

Regards,

Brian

[Romain_Polette]

Hi @BrianW , 

Regarding the DI status change delay, I suppose you are talking about the embedded Web services.

Can you check if you have the same delay when reading the DI status through Modbus TCP ?

Regards, 

[BrianW]

Hi @Romain_Polette 

I have just checked and see that the delay is down to about 6 or 7 seconds using Modbus TCP for changes in status from OPEN to CLOSED and vice versa. Using the Web service pages, this delay can be up to 20~25 seconds for each status change. 

I notice using the EPC, the status change is a lot quicker than the Web Service pages also, with delay times of about the same as Modbus TCP tests.

Hope this is of some help?

Regards,

Brian

[Romain_Polette]

Hi @Eric_HAVAS , 

Can you help us with the following questions ?

1. Why delay on the PAS Web Page is about 20-25 sec when any change on the DI ?
2. Is a delay of 7 sec expected when you check any DI status change through a Modbus TCP tool ?

Thanks.