1.570 Remote-Alarm

The Remote-Alarm logical device is part of the remote alarm client feature of the software which reports failures of a M&C system to a remote site through a ('on demand') dial up connection.

If you launch a client (user interface program) to a M&C computer from a remote site through a 'dial on demand' connection, the watchdog mechanism built in the software keeps this connection open, even if there is no other data exchange. May be you simply want to be informed at the remote site if the M&C system shows a fault. In this case the Remote-Alarm facility of the software helps you to keep the communication costs as low as possible.

To make this feature work, configure a Remote-Alarm logical device at the M&C server and run the alarm client program at the remote site. Normally there will be no active network connection between the sites. If, however, the summary fault flag of the M&C system or another one of the configured flags changes, the Remote-Alarm logical device will connect to the remote client program on order to update the signalling there.

Beside signalling the M&C system's summary alarm with a OK/FAULT display on the screen and the keyboard bell, the remote alarm client program is able to switch some relay circuits due to alarm conditions in the M&C system. The Remote-Alarm device in the M&C server maps alarm flags to relay circuits. Controlling the relay circuits is optional, if there is no appropriate hardware at the client machine installed, nothing happens, no error messages appear. The first relay circuit (number 0) always is mapped to the M&C system summary fault. The remaining 5 circuits are user configurable, these assignments are part of the configuration parameters described below.

Device window pages

The following table shows which device window pages are available with this individual device type. Tool-bar functions not mentioned here are described at the general description of device windows .

Configuration parameters

At the maintenance page of the device window there are a couple of configuration parameters which must be set to integrate the Remote-Alarm device into the M&C setup.

parameter description
clientIP Enter the IP address of the machine running the remote alarm client. If the remote machine's name is known by DNS or listed in the computer's /etc/host file, you may enter the remote machine's name, too.
clientPort Enter the IP port number where the remote alarm client accepts connections from this machine. The standard value is 2010, you should not change this unless you know exactly which IP ports on the client machine are free. If another port number than 2010 is used, is also must be set as a command line parameter when the remote alarm client is invoked.
faultId1 Enter the message identifier of the fault flag which shall set the relay circuit 1 at the remote client. Leave it empty if the remote client has no relay circuits installed or if you don't want to control this particular relay circuit.
faultId2 Enter the message identifier of the fault flag which shall set the relay circuit 2 at the remote client. Leave it empty if the remote client has no relay circuits installed or if you don't want to control this particular relay circuit.
faultId3 Enter the message identifier of the fault flag which shall set the relay circuit 3 at the remote client. Leave it empty if the remote client has no relay circuits installed or if you don't want to control this particular relay circuit.
faultId4 Enter the message identifier of the fault flag which shall set the relay circuit 4 at the remote client. Leave it empty if the remote client has no relay circuits installed or if you don't want to control this particular relay circuit.
faultId5 Enter the message identifier of the fault flag which shall set the relay circuit 5 at the remote client. Leave it empty if the remote client has no relay circuits installed or if you don't want to control this particular relay circuit.

Running the alarm client program

To run the alarm client on a PC with an installed sat-nms client use the same command line but change the parameters after 'satnms.jar': [jre] -cp satnms.jar satnms.gui.FaultFrame <IP address of M&C system> [Options]

Possible options are:

Example command line for Windows: jrew.exe -cp satnms.jar satnms.gui.FaultFrame 192.168.10.10

Chosing port numbers

For standard applications you should use the default port number 2010 whenever possible. However, there may be situations where it is necessary to use an alternate port number. For example, if you are running two instances of the alarm client on one machine showing the fault state of two particular M&C systems. In this case, the alarm clients must use different port numbers.

You should ensure, that the chosen port number isn't used by another application and you must set the same port number with the -l port-number switch at the alarm client and at the Remote-Alarm device's setup window as well.

Variables defined by this device driver

name type flags range
info.driver TEXT R/O StringRange R/O
info.type TEXT R/O StringRange R/O
info.frame TEXT R/O StringRange R/O
info.state TEXT R/O StringRange R/O
config.clientIP TEXT SAVE SETUP StringRange
config.clientPort INTEGER SAVE SETUP IntegerRange (0 .. 0)
config.faultId1 TEXT SAVE SETUP StringRange
config.faultId2 TEXT SAVE SETUP StringRange
config.faultId3 TEXT SAVE SETUP StringRange
config.faultId4 TEXT SAVE SETUP StringRange
config.faultId5 TEXT SAVE SETUP StringRange
reset TEXT StringRange