Sepam - HV/MV Protection and control units (ENG) - Trinet

Sepam 2000 internal eventsThe internal events are associated Sepam check-wordstatus at the Jbus address 0C8h.Presence of a major fault in Sepam 2000Whenever a major fault appears, Sepam 2000responds by an exception reply: “Sepam 2000not ready”. When the fault disappears, the masterreads the following in the event table:c appearance of “major fault”,c appearance of “data loss”,c disappearance of “major fault”,c disappearance of “data loss”,c appearance / disappearance of “non-synchronous”according to Sepam 2000’s synchronism status.Setting terminal: in parameter setting mode (1) /in reading mode (0)The appearance of “terminal in setting mode” eventis generated when a user connects locally to Sepam2000 using the setting terminal in parameter settingmode, i.e. after having pressed the “code” key on thesetting terminal and entered the password.The complementary event is generated when thesetting terminal is switched back to reading mode.Internal synchronization modeIn this mode, Sepam 2000 is in “correct time” and “synchronous”status after the receipt of the first “time message” frame.If Sepam 2000 is in correct time and synchronous status, it switchesto non-synchronous status if the synchronism error is greater than 50 milliseconds.Sepam 2000 declares itself “non-synchronous” when the difference betweenthe current Sepam 2000 time and the time frame received is greater than 50milliseconds for 3 consecutive time frames.When Sepam 2000 is in synchronous status, if no “time message” is receivedfor 200 seconds, the appearance of a “non-synchronous” event is generated.Sepam 2000 in data loss (1) / no data loss (0) statusSepam 2000 has an internal storage queue with a 64-message capacity.In the event of saturation of the queue, i.e. 63 events already present,the “data loss”, event is generated by Sepam 2000 in the 64th positionand detection of events is interrupted.Event detection is only started up again when the internal queue has beencompletely emptied by the master. The system event, disappearance of “data loss”is then generated.The appearance/disappearance of “non-synchronous” is generated accordingto Sepam 2000 synchronization status.Sepam 2000: incorrect time (1) / correct time (0)The appearance of the “incorrect time” event isgenerated by Sepam 2000 each time it is energizedand after re-initialization of the Sepam 2000communication system. Sepam 2000 initializes witha default time: 1 June 1993 0 hours 0 minutes 0milliseconds and the “incorrect time” status is set.The appearance of the “incorrect time” event indicatesthat time-setting by the master is required.When a time frame is received, Sepam 2000 switchesto “correct time” status and the “incorrect time” eventdisappears.Sepam 2000: non-synchronous (1) /synchronous (0)The date and time associated with the status changeswhich follow the appearance of a “non-synchronous”event prevent correct inter-Sepam 2000 chronologicalevent sorting. Once Sepam 2000 has becomesynchronous again, the disappearanceof “non-synchronous” event is generated.When the disappearance of the “incorrect time” and“non-synchronous” events takes place, Sepam 2000time tagging enables correct chronological sorting.Jbus/Modbus communication25