Mantracourt Electronics Limited
T24-PR1 User Manual
2
Introduction / Overview
The T24-PR1 is a thermal printer module that can print a 57mm wide ticket which can include data from up to
8 devices and optionally sum them. The printout can be triggered from the arrival of data from a specific
device or alternatively by a handheld device which can also optionally supply the data value to print.
NOTE: Print triggering from an external button/switch option will be made available on future releases of the T24-PR1.
The actual printed output can be designed by the user using multiple lines which can include free text or
tokens which can represent real data. i.e.
<V1>
would be decoded as the value from input 1 when the print is
triggered or
<TV>
would reference the Trigger Value from an external handheld for example.
Communications Overview
The T24 range of telemetry devices each have a factory set unique
ID
.
Data is shared between devices using
Data Provider
messages. A device generates these messages which can
then be used by many other devices simultaneously.
These messages ( or packets ) of information contain a single value of data and each is identified by a
Data
Tag
.
The
Data Tag
should
be unique for each message.
ID
Identifies each device
Each device has a unique
ID
that is factory set. This is represented as a 6 character hexadecimal
number consisting of the digits 0 to 9 and the letters A to F.
I.e.
FFD3BE
Data Tag
Identifies each Data Provider message
A
Data Tag
consists of a 4 character hexadecimal number consisting of the digits 0 to 9 and the
letters A to F. The
Data Tag
can be changed by the user but the factory default is to match the
last 4 characters of the device
ID
.
I.e. An acquisition device of
ID
FFC12B
would have a default
Data Tag
of
C12B
.
When a device consumes data (i.e. a handheld displaying data from an acquisition device) all it is doing is
listening to all of the
Data Provider
messages and selecting the one it wants to use. It then extracts the data
and displays it.
Some devices that use
Data Provider
messages also need to know the
ID
of the device providing the data. This
is necessary if that device needs to specifically wake the data providing device as opposed to using a broadcast
wake that will wake all devices on the same channel and using the same encryption key.
Pairing offers an automated method of hooking a provider and consumer of data together. However, some
devices may require you to manually enter
Data Tag
and
ID
information so it would be beneficial to the user to
understand the above mechanism.
Configuration Overview
Once it has been determined how many devices are feeding data to this device you need to record the Data Tag
that each of these devices are attaching to their Data Provider packets.
These Data Tags are then entered into the
ValueDataTagx
parameters. Once the rate at which this data arrives
is known you can enter the
Timeoutx
values.
Leave unused
ValueDataTagx
parameters with a value of zero to ensure that they are not checked for timeouts
and do not contribute to gross or net sums.
When a data provider packet arrives whose Data Tag matches one of those in the
ValueDataTagx
parameters
the value it contains will be placed in the
Valuex
parameter.
If data does not arrive from a device within the
Timeoutx
period then any reference to either the individual
Vx
tokens or one of the summing tokens will result in
------
rather than a numeric value.
The actual serial output can now be constructed using
Line1
to
Line25
(In the toolkit these are hidden and the
user simply creates the ticket on screen). These parameters take text into which you can insert tokens. When a
