The TMR1P is able to receive alphanumeric messages and send via the RS232 serial output to
any industrial standard display device. The RS232 port speed of 1200/2400/4800/9600/19200
baud rate with even/odd/none parity option can be set through the TPS. TMR1P supports both
numeric and alphanumeric vector. However, there are some constraints in using numeric vector to
send the control codes for both control and display data, which will be specified in the relevant
sections.
1.2 Receiver Frequency
The TMR1P’s receive frequency is normally set during the production of the units in accordance
to customers’ specifications. The receive frequency can be changed by using the TMR
Programming Software (TPS) by programming the frequency synthesizer.
1.3 Multiple Addressing
The TMR1P can support up to 7 POCSAG capcode addresses.
1.4 LED Indication
The following table describes the different indications of the LED for different conditions:
S/No LED Indication Status Condition
01 Continuously on Reset is successful After Power on
02 Blinking every half a second EEPROM failure After Power on
03 Blinking every 2 seconds until
synchronization is restored
04 Blinking every 0.3 second for
up to 3 seconds
1.5 Output Control Codes
The TMR1P is able to control different industrial applications such as motor, relay,
lighting and electronic-lock by sending the right control codes through its 8 output ports
(1/0/k/s/r).
When a port control code sent is “1”, the corresponding output port is set to high state or source
state.
When a port control code sent is “0”, the corresponding port is set to low state or sink state.
When a port control code sent is “k”, the corresponding port’s state remains unchanged from its
previous state (“k” means “keep”).
When a port control code sent is “s”, the corresponding port is set to a state which is the opposite
of the previous state (“s” means “toggle”).
When a port control code sent is “r”, the corresponding port is reset to high impedance state (“r”
means “reset”). All 8 ports can also be reset to high impedance if the reset control code “r” is sent
(refer to MESSAGE PROTOCOL section), or if the device is programmed with the TPS.
When the TMR1P is switched off and on again, the states of all the 8 output ports will
remain unchanged.
For numeric vector, the control code supported is either “0” or “1”, control code “k”, “s”
and “r” are not supported.
1.6 Output Display Message
The TMR1P is able to receive numeric and alphanumeric messages and send via the RS232 serial
output to any industrial standard display device. The message buffer size is 10,240 bytes and the
maximum message length is 4096 bytes. For continuous receiving, it can receive messages of
1000 characters. The RS232 port speed of 1200/2400/4800/9600/19200 baud rate with
even/odd/none parity option can be set through the TPS.
1.7 Error Message
When the TMR1P detects any errors in a received message, it will discard the message, truncate
the error message, or send the error message as it is without any truncation, depending on the TPS
setting (error message handling option) programmed in the unit.
TPS Option:
Error Message
: Send/Truncate/Discard
1.8 Configuring an Output as Source or Sink
Two (2) of the 8 output ports can support up to a maximum of 1A source current at High
state or to sink a maximum of 1A drain current at Low state. The other 6 ports have a
maximum current rating of 100mA for both source and sink (High and Low state).
If Out Of Range (OOR) Indication is enabled in the TPS, the TMR1P can indicate an OOR
condition. The LED on the device will blink every 2 seconds until the OOR condition disappears
or the device is back to synchronization with the network.
TPS Option:
Out of Range
: enable/disable
1.10 Serial Interface (RS232 Port)
The serial interface used by the TMR is a half-duplex type. Both data and command information
are sent over this interface. The serial interface can be reconfigured to match to the host
equipment by means of some special paging codes. The TPS allows settings of the baud rate and
parity bit to be changed.
TPS Options:
Parity
: Even/Odd/None
Baud rate
: 1200/2400/4800/9600/19200 bps
1.11 Flow Control
Communications between the TMR1P and the host is done asynchronously through the RS232 or
TTL serial ports (TXD output). A signal is generated to alert the host equipment that a message is
available. This is done by asserting the RTS line. There is also a clear-to-send (CTS) line from
the host to the TMR1P that signals the host is ready to accept commands. The TMR1P is able to
buffer 10,240 bytes of data before it overflows.
TPS Option:
Flow Control
: enable/disable
1.12 Serial Data
To automatically send data out the serial port, the Flow Control programming option in the TPS
must be disabled. If the Flow Control is enabled, the user can have more control over the
message. These features are further described in the following sections.
1.13 RTS Control
This option allows the use of the RTS line to indicate to the external host device that there is a
new page data ready to be sent out of the serial port. This line will turn to logic low when the
TMR1P is ready to send data out of the serial port.
If flow control is enabled, the CTS line is used to determine if the host is ready to receive data
from the TMR1P. When the host has received an RTS and is ready to receive the data, a logic
high is asserted. If the host disables the CTS line while the complete message is not fully
received, TMR1P will perform timeout for 10 seconds. If the host re-asserts the CTS line before
timeout, the TMR1P will continue to send out the remaining message to the host. If the CTS line
is asserted after timeout, the TMR1P will resend the entire message provided the message has not
been overwritten by the incoming paging messages.
When CTS is asserted, TMR will delay for a programmable interval before sending out data.
This programmable delay is a TPS option.
TPS Option:
CTS Response Delay
: (0 – 10000ms)
1.15 Over-the-Air (OTA) Programming
Over-the-air (OTA) programming is a method of changing TMR1P settings without requiring the
TMR1P to be physically connected to a PC. OTA programming commands are transmitted over
the paging system as alphanumeric messages.
You can use the TMR1P TPS (Telemetry Programming Software) to generate the OTA strings
that are to be sent to TMR1P. The TPS itself does not send the OTA strings; separate paging
software is required for that. OTA reprogramming can only be used with TMR1P that had the
OTA password field set when they were last programmed through a connection to PC.
Each TMR1P will only process OTA messages received on Capcode 1. The TMR1P will not
process OTA messages received on other capcodes. Additionally, the TMR1P cannot process
OTA messages where there was an error in transmission, or if the TMR1P is off.
For more information on OTA programming, please refer to the on-line help file in the TMR1P
TPS.
Cautions: When an OTA string of incorrect password is received 8
times by a TMR, it will set
the RF Disable Bit in the EEPROM and disable the receiver
permanently. The only way out is to
erase the EEPROM and start afresh. If OTA is attempted with a
correct password prior to the 8
th
incorrect password, the TMR will reset the OTA password count to
0, thus allowing 8 more tries.
A page is considered as a candidate for a valid OTA string as
long as the OTA header matches
“)&)NP1”. The purpose of such design is to prevent unauthorised
users from hacking the TMR
via OTA.
The TMR1P processes the received data only when the sub-address received is correct. The subaddress (4-characters: 0~9, a~z, A~Z) can be programmed via the TPS.
For numeric vector, the
sub-address is supported only from character “0” to “9”.
TPS Option:
Sub-address Control
Sub-address
: (4 characters, char type: 0~9, a~z, A~Z)
: enable/disable
1.17 Message Header Control (used for display data through the serial port)
For the convenience to display messages in different display devices, the TMR1P can
send up to 40 pairs of Hex codes or 80 characters (“0”~”F”) in total through its serial port
There are two kinds of message headers. Header1 (up to 20 pairs of Hex codes) can be
pre-programmed or disabled by the user in the TPS. Header2 (up to 20 pairs of Hex
codes) can be sent out together with the message sent by the user or operator. For
numeric vector, the 20 pairs of hex codes for header 2 is supported only from character
“0” to “9”. (Refer to Section 3 Message Protocol)
The header will be treated as displayed data under the following conditions: invalid hex
code, hex codes not in pair, no “[[ ]]” pair, or more than 20 pairs of hex codes in either
header 1 or header 2.
TPS Option:
Msg-Header Control
Msg-Header
: 1~20 pairs, ‘0’~’F’ characters (2~40 characters, must be even or in pairs)
: enable/disable
1.18 Message Trailer Control (used for display data through the serial port)
For the same reason above, the TMR1P can also send two kinds of message trailers
through its serial port to different display devices. Trailer2 (up to 20 pairs of Hex codes)
can be pre-programmed or disabled by the user in the TPS. Trailer1 (up to 20 pairs hex
codes) can be sent out together with the message sent by the user. For numeric vector, the
20 pairs of hex codes for trailer 1 is supported only from character “0” to “9”. (Refer to
Section 3 Message Protocol)
The trailer will be treated as displayed data under the following conditions: invalid hex
code or hex codes not in pair. If there are more than 20 pairs of hex codes in either trailer
1 or trailer 2, the excess characters will be truncated and the remaining 40 characters will
be processed to determine whether it is a valid trailer.
TPS Option:
Msg-Trailer Control: user/default/disable
Msg-Trailer (when “user” is selected)
: 1~20 pairs ‘0’~’F’ charactersr (2~40 characters, must be
DAVISCOMMS (S) PTE LTD
DAVISCOMMS (S) PTE LTD
1.19 Message Source ID Control
The TMR1P can send any index number of the 7 capcode addresses at the start of a message and
this function can be enabled or disabled by the user in the TPS.