We recently had a problem on BN-3500 system installed at one of our machines.



TDI module OK relay actuated to generate an alarm on DCS which was automatically reset after 52 seconds (on DCS).



When the maintenance team checked the system all indications were OK, however, Events numbered 320, 340 and 341 were logged in System Events.

The events showed that the module had rebooted due to some reason.

Screenshot of event is attached for reference. This incident has repeated twice in the last 3 days.

I would like to know if anyone else has encountered similar incident and what can be done to resolve this issue.

 

We recently had a problem on BN-3500 system installed at one of our machines.



TDI module OK relay actuated to generate an alarm on DCS which was automatically reset after 52 seconds (on DCS).



When the maintenance team checked the system all indications were OK, however, Events numbered 320, 340 and 341 were logged in System Events.

The events showed that the module had rebooted due to some reason.

Screenshot of event is attached for reference. This incident has repeated twice in the last 3 days.

I would like to know if anyone else has encountered similar incident and what can be done to resolve this issue.

The same events here, the same day... (GTM-3)
Last one on 28/06/22

 

Dear colleagues

We have the same alarm in our BN 3500 rack.
Have you found out the reason ?

 

We recently had a problem on BN-3500 system installed at one of our machines.



TDI module OK relay actuated to generate an alarm on DCS which was automatically reset after 52 seconds (on DCS).



When the maintenance team checked the system all indications were OK, however, Events numbered 320, 340 and 341 were logged in System Events.

The events showed that the module had rebooted due to some reason.

Screenshot of event is attached for reference. This incident has repeated twice in the last 3 days.

I would like to know if anyone else has encountered similar incident and what can be done to resolve this issue.

It is a Power Supply unit problem. Replace it.

 

1. If the firmware version on the 3500/22 TDI is not the latest, the customer may experience Rebooting. Using the latest firmware version is always recommended.

2. High amounts of Ethernet network traffic can overwhelm the TDI and cause it to reboot. Adjust sampling rate, Alarms etc.

3. Having different sampling rates for a channel/orbit pair will cause the TDI to reboot constantly.

4. A TDI can reboot at extended temperatures. Temperature problems have occurred when racks are stacked on top of each other.

Replace the TDI card if above are not the cause of rebooting.