Inet alarms management

[redrider]

I am working with a building that has inet software installed. It has 3 NPR's installed. I keep getting an alarm indicating comm loss to one of the routers. This has been an issue for this building for quite some time. It has a dedicated power supply.
I guess I have 2 questions:
1. How do I change the alarm profile from critical to priority or routine? They are sick of having the audible alarm go off 3-4 times per day.
2. Short of replacing the 527 NPR, are there any fixes to this issue? I suspect a intermitant Ethernet connection may be the culprit.

[crab master]

Been too long away from INET, but doing a few quick searches.

- "You can make I/NET more tolerant of communication delays over the IP network by makeing the following change:

1. Open regedit.
2. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\CSI - Control Systems International\I/Net 2000\Configurations.
3. Select your active profile.
4. On the right side, right click and modify the DWORD value "EthernetTimeout" and click "Decimal".
5. The default value is 500mS or half of one second. Increasing this value will determine how long I/NET waits for a response over the ethernet before it gives up. Raise it to 1000, 2000, 2500, etc. and see if it helps."

- "There is a windows registry setting that allows you to increase the communication response time.

To do this go into the Start>run>regedit mode, then select the following registry location:

HKEY_LOCAL_MACHINE > SOFTWARE > CSI-Control Systems International > I/Net 2000 > Configurations > YOUR_ACTIVE CONFIGURATION
where YOUR_ACTIVE_CONFIGURATION is the name of the configuration in use at the site.

In the right pane of this window there will be listed an entry of " Ethernet Timeout". Double Click the "Ethernet Timeout", in the next popup window change the "Base Function" to the "Decimal" Mode.

In the "Value data" box put in value from 1000 to no more than 1500. After making this change, return the "Base Function" back to the "Hex" mode. Then close out of the registry and reboot the PC to make this change active."

- "Changes to bin file revisons sometimes include updates to communication
This can be caused by a mis-match in .bin file revisions on all downloadable controllers. Verify all the .bin files in each downloadable controller are from the current I/NET revision at the customer's site.
The mis-match can come from a tech loading a .bin file from his laptop (with a different rev than the customer). It can also occur when I/NET is upgraded, but the controllers aren't."