• Not Answered

Alarm Assignment of Remote IO Units(RIU)

Hi All,

I currently see that all Delta V controllers have 'alarms and events' section in properties, where I can assign the area for alarms coming out of the controllers, Whereas the Remote IO Units does not have 'alarms and events' in their properties. By default, all the alarms of the Remote IO units goes into the default area 'AREA_A'. Are there any workaround to move RIU alarms to the parent controller assigned areas?

Regards,

Akash

6 Replies

  • I don't have RIU but if I remember correctly hardware alarms for the RIU unit itself would be reported by the first controller that have the IO assignment.

    Conditions from the channels would be reported to the controller where it was assigned.

    Is this not what you are observing? What version of DeltaV are you using?
  • In reply to Lun.Raznik:

    Thanks Raznik, We are using Delta V 13.3.1. Yeah, all the hardware alarms of RIUs(example-ACN connection of Operator station to RIU) gets recorded in AREA_A(Default). But, it should be reporting to the controller assigned area.
  • In reply to Akash KA:

    I would consult GSC how to do this in a supported fashion.

    If you have a "development" system, you can export RIU and change area assignment of the corresponding FHX and do an import. Please let us know if this is working.
  • In reply to Akash KA:

    All the hardware connection events to be precise.
  • In reply to Akash KA:

    Yeah, would consult with GSC and will update. Currently we dont have a development environment to test.
  • In reply to Akash KA:

    I have exported the .fhx of all Remote IO units and had a look at the area. All hardware alarms were assigned to default area 'AREA_A'. Seems changing the area directly on the .fhx and importing back is the only option. Are there any workaround to assign RIO hardware alarms to other areas from delta V explorer itself?