Why can't HOPC read backup BRC410 modstatus information on an Infi 90 network

Hi, If possible, I was hoping for some insight regarding obtaining MODSTATUS information on a backup MFP11/12 controller on an INFI 90 network via an IET800 as OPC data. To clarify, I am successfully receiving the Primary Controller status information eg. Address in HOPC configuration -> Loop 1, PCU 1, Module 3 Block 0 (1,1,3,0) through to HOPC 6 but I am failing to get the MODSTATUS information from any backup controller (eg 1,1,4,0).

When I run a report on Composer, I see the module status information for both controllers – in this instance the PC running composer is retrieving the information via a serial link to the INfi 90 network, not through the IET800s. It seems the IET800 is not passing the OPC data from the Controllers in slot 4 but slot 3 works fine. This is the same for the few redundant pair BRC410s we have in place as well. All other OPC tags read just fine through to HOPC.

Would anyone have any idea why this might be the case.


Cheers, Glenn


Add New Comment


glumsden   

asked 5 months ago
Closed



Best Answer

3

Hi Glenn,
As far as I know, the creation of a N90STA/MODSTAT tag for a redundant Harmony controller is still invalid in the Harmony enviroment and can ultimately cause module redlight and communications issues. There are several bulletins discussing this issue (WE-DOC-3BUA001225R0001 is the most recent, 2011) but basically N90STA/MODSTAT tags should only be configured for

-Both the primary and backup NPM (address 0 and 1)
-IET/ICI modules (always module address 2)
-Only the primary module address for redundant pairs of controllers
-Both the primary and backup bridge/gateway nodes, but only for the ‘local’ side of any bridge/gateway nodes (always module address 2).

The bulletins also include the procedure for removing incorrectly defined N90STA/MODSTAT tags from the system.

If you want to explicitly alarm the backup module status you can use the FC95(MODST) to extract the backup status from the PRIMARY controller status bytes.


Regarding the difference in behaviour between HOPC and Composer. Composer is polling and communicating with each module directly to retrieve the module status data, so will behave differently to a MODSTAT tag.

Regards,

Alan

Source: WE-DOC-3BUA001225R0001

Alan   

answered 5 months ago


 


By glumsden on 4/4/2017 | Like (0) | Report

Hi Alan,
Thank you very much for this great response. Answers my question precisely. Cheers, Glenn.


Add New Comment


Answers

3

Hi Glenn,
As far as I know, the creation of a N90STA/MODSTAT tag for a redundant Harmony controller is still invalid in the Harmony enviroment and can ultimately cause module redlight and communications issues. There are several bulletins discussing this issue (WE-DOC-3BUA001225R0001 is the most recent, 2011) but basically N90STA/MODSTAT tags should only be configured for

-Both the primary and backup NPM (address 0 and 1)
-IET/ICI modules (always module address 2)
-Only the primary module address for redundant pairs of controllers
-Both the primary and backup bridge/gateway nodes, but only for the ‘local’ side of any bridge/gateway nodes (always module address 2).

The bulletins also include the procedure for removing incorrectly defined N90STA/MODSTAT tags from the system.

If you want to explicitly alarm the backup module status you can use the FC95(MODST) to extract the backup status from the PRIMARY controller status bytes.


Regarding the difference in behaviour between HOPC and Composer. Composer is polling and communicating with each module directly to retrieve the module status data, so will behave differently to a MODSTAT tag.

Regards,

Alan

Source: WE-DOC-3BUA001225R0001

Alan   

answered 5 months ago


 


By glumsden on 4/4/2017 | Like (0) | Report

Hi Alan,
Thank you very much for this great response. Answers my question precisely. Cheers, Glenn.


Add New Comment



Get weekly AKS updates


Partner Exclusive Webinars

 

> – Login to the partner portal to register



Points Redemption Program - Redeem your points for ABB training, Bluetooth speakers and mugs. Terms and conditions >


Earn points when you refer a friend
AKS Referral Program is "Live" - Learn more



AKS Experts


avatar
Ask Harsha.D   

Rank: 6

Tech.Support,software and commisioning engineer with Proficient knowledge in 800xA and its products, RNRP,Networking in general.


avatar
Ask Govindaraj   

Rank: 10

Working in ABB India Operation Center. Have Project engineering and commissioning experience in ABB 800xA, Freelance, AC500.


avatar
Ask Flavio Mussolin   

Rank: 5

ABB AVP, Senior Electronic and Automation Engineer with over 30 years of experience in the field of process automation automotive, pharmaceutical, hollow glass, steel and rolling.


avatar
Ask Stefan Stromqvist   

Rank: 1

I joined ABB in the year of 1994 and has since 1999 been working as a Service & Support Engineer at BU Control Technologies in Västerås, Sweden. My areas of expertise are: 800xA Base, 800xA for Advant Master, Information Management, operating systems, RNRP and Ethernet comms/networking in general.


avatar
Ask Dieter Henkel   

Rank: 24


avatar
Ask Sumit Gargav   

Rank: 2

I have worked with Freelance in majority, with 800xA FD and Melody system partly. Also had opportunity to work with Protocols - HART,Profibus,FF & Modbus.


avatar
Ask Rob Lyon   

Rank: 3

info@lymac.co.nz I'm an independent DCS software and commissioning engineer with extensive experience in 800xA and other ABB products. I've worked in almost every corner of the world and still haven't seen it all.


avatar
Ask nikismith   

Rank: 260

I have been a part of the Recording & Control Factory team for 17 years in total, having spent a number of years as a repairs technician withi the manufacturing department, but being in my current role for 9 years now.


avatar
Ask kstoilov   

Rank: 21

Control System Engineer: 800xA, Compact 800, AC500, AC31-50, Advant Master, Simatic, AC&DC Drives 11 years worked for ABB - Control Systems


avatar
Ask MMM   

Rank: 4

ABB PA CT Technical Support