FLIR identiFINDER R300, Руководство пользователя

Страница: 249 / 304

FLIR Detection A. Info Pool
2
< E r r o r n a m e = ” (CommandName) ” t y p e = ”nanoRaider” id = ” (SerialNumber) ”
d e s c r i p t i o n = ” (ErrorDescription) ” / > \0
*
Line 1: XML Declaration
The XML declaration is the same for all messages.
Line 2: Error element
The message will will contain one
Error
element as the root element.
name
An error message will contain the same (CommandName) present in the command
message it is in response to. This is true even if the (CommandName) was invalid.
This may also be
”(unknown)”
if the FLIR identiFINDER R300 was unable to parse a
command element from the XML message.
type
The
type
attribute indicates the device class sending the message. For the FLIR
identiFINDER R300 this will be
”nanoRaider”
.
description
The
description
attribute, shown in the example with the (ErrorDescription) place-
holder, will contain a brief textual description of the error condition and/or cause. The
following are examples of some actual error descriptions:
”Unknown command.”
”Malformed XML message received.”
”Spectra id 416 does not exist.”
A.7 SPP Commands and Updates
A.7.1 Ping
The Ping command will generate a Ping update from the FLIR identiFINDER R300. This can be used
to verify SPP communication is functional and to determine the device serial number.
Listing A.4.
Ping Command
1
< ? xml v e r s i o n = ” 1.0 ” e n c o d i n g = ” utf -8 ” ? >
2
< C o m m a n d n a m e = ” P i n g ” / > \0
The Ping command should be verbatim as shown in the listing.
Listing A.5.
Ping Update
1
< ? xml v e r s i o n = ” 1.0 ” e n c o d i n g = ” utf -8 ” ? >
2
< U p d a t e n a m e = ” P i n g ” t y p e = ”nanoRaider” id = ” (SerialNumber) ” / > \0
*
Test footnote.
identiFINDER
®
R300/en/2014.4(13623)/Feb2015 249