Specifications

OPERATIONS
Page 107 MRC-565 Packet Data Radio Operations & Maintenance
a carriage return and line feed. The response text, up to 1024 bytes, will be captured and
returned to the originating modem as a remote command response message.
Example Script:
generic,1,type,auto
generic,1,group,auto
generic,2,type,line
generic,2,group,fixed,2
generic,2,sensor,line,2,22,32
generic,2,date,line,1,12,19,YY/MM/DD
generic,2,time,line,1,20,29,HH:MM:SS
generic,2,poll,off
generic,2,report,Date/Time:
generic,3,type,off
generic,0,type,off
assign,dta,off
assign,alt,off
assign,dta,2,generic,5
setbaud,2,9600
assign,alt,1,generic,2
setbaud,1,9600
generic
save
5.11 Event Programming
The MRC-565 supports customer-programmed event logic. Discrete and analog inputs can be
monitored by the event program to detect "events" which then perform a defined "action".
Actions may include the controlling of discrete output signals, incrementing counters, setting
timers, transmission of canned messages and issuance of various reports. This means that
customers are somewhat independent of factory reprogramming from MRC and that MRC-565
behavior can be readily modified in the field. It also means that operators now have limited
power to make the MRC-565 react to various field-programmable conditions.
The operator sets up the event program when installing the MRC-565 or during maintenance and
operation. Because the event program is implemented via operator commands, it can be entered
not only at a local maintenance console, but also via the remote command capability. The event
programs are stored within a non-volatile table in the MRC-565 battery-backed-up RAM. They
are not lost due to external power failure. When the external power is restored, they will be
enabled to respond to events again.
Programming is usually done by creating a "script file" of the required event commands, and
loading these into the MRC-565 using XTERM or any other terminal emulator software.