![FLIR identiFINDER R300 User Manual Download Page 245](http://html1.mh-extra.com/html/flir/identifinder-r300/identifinder-r300_user-manual_2306030245.webp)
FLIR Detection
A. Info Pool
A.6
Bluetooth Serial Port Pro le (SPP) Communication Overview
While the FLIR identiFINDER R300 has Bluetooth Serial Port Pro ile (SPP) enabled (see
6.23.1
,
p.
141
) and is connected to a compatible device it will respond to properly formatted queries and
can also stream data. This allows integrators to design custom interfaces and for operators to use
such interfaces to either listen for or inquire about current instrument status. The following is a
description of the FLIR identiFINDER R300 SPP data format.
The following does not apply to Bluetooth Periphery mode and only applies to Bluetooth SPP
mode.
A.6.1 Bluetooth Device Name and PIN
A unique Bluetooth device name for each FLIR identiFINDER R300 is set during manufacture and
can be provided upon request. Each FLIR identiFINDER R300 will also have a unique PIN (see
6.23.1
, p.
141
) made up of 16 characters selected from lower-case English alphabet characters (a-z)
and numerals (0-9).
A.6.2 Data Format
The FLIR identiFINDER R300 is capable of responding to commands from a device connected via
a Bluetooth SPP connection. In addition, the FLIR identiFINDER R300 can be con igured to stream
data in response to an environmental or user trigger. The commands and triggers are explained in
the following sections.
A.6.3 Conventions and Usage Notes
The format of the commands and responses make up a complete and well-formatted XML docu-
ment, including the XML declaration. The character encoding of these messages shall be UTF-8 and
shall not include a byte order marker (BOM).
The
NUL
character is represented in this document’s example listings in C-style notation as
\0
. It is a single standard byte with the character value of zero.
For the purposes of this speci ication, any number of
NUL
(
\0
) bytes contained
within
the XML mes-
sage is illegal, since
NUL
is used as the message delimiter
after
the completed XML. Every message
shall be terminated with the
NUL
character.
XML tags are case sensitive.
identiFINDER
®
R300/en/2014.4(13623)/Feb2015
245