Literature .................................................................................................. 67
Glossary of Terms 69
Index 71
XML SDK V8.7.0 Remote Control Interface Contents vii
Version
Date
Changes
Beta
20-Jul-2005
Initial draft
Release
25-Jan-2006
1.1
15-Jul-2006
Added:
BinaryFFT element
fft-data-format
frame-length
frame-format
1.2
7-May-2007
Minor bug fixes
Added:
passband-center
passband-bandwidth
MilStanagMessageType element
1.3
25-Mar-2008
New codes in table
New diversity parameter
New threshold-level parameter
New layout
Added:
ClassifierSetup element
Get element - item
classifiersetup settings
1.4
13-Aug-2008
W-CODE added
1.5
15-Nov-2008
Added:
AlphabetList Element
Get element - item
New codes in table
1.6
20-May-2009
CustomInputList Element
Get element - item (CustomInputList)
Set element - item (CustomInput)
New codes in table
Welcome
Congratulations on your purchase of a WAVECOM decoder product. The product that you bought incorporates the latest technology in data decoding together with the latest software release available at the time
of shipment.
Please check our website http://www.wavecom.ch for software updates.
Always check the latest documentation on the installation DVD or on our website.
We thank you for choosing WAVECOM decoder and look forward to working with you in the future.
Options
Various options to the decoder series are available from WAVECOM.
In the manual, options are marked with “(Option)”.
Training
WAVECOM provides training on the WAVECOM XML interface. Training can take place at a customer selected location or at our offices in Switzerland.
Revisions
XML SDK V8.7.0 Remote Control Interface Welcome 1
MilStanagMessageType:
Parity changed
Display format changed
robust-packet-radio replaced with robust-packet
1.7
11-Nov-2009
IP-CONF: correction of wrong spelling
Additional range information for the port number, sampling rate and number-
of-channels attributes
6.8.1
10-Feb-2010
Release version system changed. In the future the XMLRCI manual and a software release will have identical release versions
MilStanagMessageType element: display-format “ascii” removed and documen-
tation changed
CustomInput element: sr-finetuning=““ removed
Documentation improved and errors corrected
7.0
22-Nov-2010
Timeslot parameter removed
SAT-A and METEOSAT removed
CODAN renamed to CODAN-SELCAL
Shift and center changed from short to integer.
MilStanagMessageType “auto-detect” added.
BR-6028 changed from demodulator type to mode
dPMR added
TETRA added
X.25 added
New parameters and commands added for Classsifier-Code-Check (CCC)
7.1
16-Mar-2011
ClassifierSetup documentation completed
“CC-timeout”, “CC-table” etc. changed to lower case
APCO-25 added
7.2
27-Jul-2011
Manual revised
GW-OFDM added
LINK-11 added
cc-table-vhfdir and cc-table-vhfind added
CC and CCC restart command added
Removed: AGC on, off, low-noise
Changed: low pass
7.4
16-Sept-2011
Just increase the version number to match that of the W-PCI/e and W-CODE.
8.0
05-Dec-2011
Increase the version number to match that of the W-PCI/e and W-CODE.
8.1.00
01-Feb-2012
A new parameter “output-demod-symbol” for demodulated symbol output with
the value “on” and “off”.
Parameter “translation” renamed to “offset”.
Add “display-mode” to Pactor
8.2.00
30-Nov-2012
Add on several new mode strings.
8.3.00
01-Jun-2013
Change mode string “chinese-4-4” to “chn-4-4”.
Add on WCloudSources message.
8.3.01
06-Jun-2013
Add commands to retrieve CCC tables (Get CC Table HF, Get CC Table VHFDIR and Get CC Table VHF-SUB).
8.4.00
25-Nov-2013
Classifier results streamed in a structured way, by their tags.
API improved.
DMR has a “bit-transparent” output. Choose via “subcode” in “Parameter
name”.
8.5.0
20-March-2014
New mode: MIL-188-110A-MOD.
New mode: THROB and THROBX.
dPMR has a “bit-transparent” output. Choose via “subcode” in “Parameter
2 Welcome XML SDK V8.7.0 Remote Control Interface
name”.
Small correction in “alphabet” parameter.
8.6.0
20-Oct-2014
Add the message “Confidence”.
Add following strings of new decoders to the parameter “code”: clover-2500,
sat-b-c-hsd and sat-mini-m-c-hsd.
8.7.0
05-March-2015
Add new modes: SAT-AERO-P, SAT-AERO-C, SAT-AERO-R and SAT-AERO-T.
Add new parameters: “acars-reassemble” and “acars-enable-ads-c”.
Add new parameters: “live-sound-mute” to turn on/off sound output to the
speaker.
New “CustomInput” element supporting the VITA-49 format.
Version
Date
Issue
All
7-Feb-2011
Incomplete un-installation of XML RCI SDK
Cause:
A windows background application is started if you start the RCI test
software. This software continues running even if the RCI test software
is stopped. Because of this the directory is still in use if you start a uninstallation of the XML RCI SDK and installation is incomplete.
Solution:
Restart your computer.
Run un-installation of the XML RCI SDK.
Category
Direction
Data type
Data
Server to client
Text, images, binary data, analysis data
Metadata
Server to client
Parameter information
Command
Client to server
Settings
Information
Server to client
Settings
Error
Server to client
Error messages
Issues
XML Messages
Scope
This section describes all XML messages used to interact with the WAVECOM Remote Control Interface
(RCI) and contains information from the DTD (Document Type Definition). The DTD file is available in the
XMLRCI installation folder.
Constraints
The values used in the description of the XML messages are only valid in the XML Remote Control Interface context. In the context of the business logic of the WAVECOM decoders the values may be invalid.
Message categories
Messages are divided into five categories:
Data messages contain data derived from the captured signal, i.e., text, images, binary or analysis data.
Metadata messages return parameter values.
Command messages allow the client to control the behavior of the server and the decoder(s) it controls.
XML SDK V8.7.0 Remote Control Interface XML Messages 3
Information messages provide information about the hardware, the software or hardware versions, the
state of the decoders, and the state and configuration of the server.
Error messages provide information about server system errors (not errors in the decoded data).
Encoding
The XML files are encoded in UTF-8, UTF-16 or Unicode.
Message template
XML header
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Message SYSTEM "RCI/1.0/DTD/WAVECOM.dtd">
The XML header is not interpreted by the server and may be included or omitted. For server messages the
header is empty.
Message elements
The implied attributes instance/subinstance, serial-nr, date and time only contain a value if the extended message header is set on the server. This can be done by sending a set configuration message.
Attribute List
version
The message version is formatted as major.minor version. A server will handle all messages from a client
as long as the major versions of the server and the client are equal and the minor version of the server is
equal to or greater than the minor version of the client. This attribute is locked to the version of the DTD
in the current Wavecom DTD.
instance
subinstance
In future decoder releases multiple codes may be instantiated on a single card. This feature requires that
the server knows the destination of the message or the client knows the source of the message. These attributes are implied and are not used in this release.
serial-nr
The serial number of the decoder assigned to this client. This attribute is implied and represents a string.
date
Date of message creation. This attribute is implied and represents a string. The format of date is
YYYYMMDD.
time
Time of message creation. This attribute is implied and represents a string. The format of time is
hh:mm:ss:milliseconds.
Content
The content is a choice between the Data, Metadata, Command, Information and Error elements.
4 XML Messages XML SDK V8.7.0 Remote Control Interface
Indicates how the content is encoded. This attribute is required and may assume the values “base2”,
“base16”, “base64” or “base64-mime”. The difference between “base64” and “base64-mime” is the way
the encoded string is terminated. Both encodings use the same character set, but “base64-mime” follows
the specification for SMTP messages and aligns the string to four characters and fills unused positions with
the padding character “=”, whereas “base64” reduces the number of characters to just the ones required,
depending on the bit count.
bit-count
Indicates the number of bits transferred excluding trailing zeros which are appended to achieve byte
boundary alignment. This attribute is required and is a string representing a positive integer.
Content
The content is a string of data decoded by the decoder and encoded as described by the encoding attribute.
The IAS (ISO-ASYNCHRONOUS and SYNCHRONOUS modes) Bit Stream Output sends a raw, synchronized
bit stream (FSK, some PSK only) to an external application. Before data can be transferred, the parameters of the decoder software (e.g. demodulator, shift frequency, center frequency etc.) must be set to correct values.
In case of “base2” encoding, a “FALSE” bit is encoded as character ‘0’, “TRUE” as character ‘1’.
In case of “base16” encoding, 4 bits are encoded by their respective hexadecimal character, i.e., ‘0’ to ‘F’.
In case of “base64(-mime)” encoding, 6 bits are represented by a single character of the base64-code.
XML SDK V8.7.0 Remote Control Interface Data messages 5
Specifies the channel from which decoded data originates. In case of single channel systems, the value is
always channel “A”. This attribute is required and may assume the values “A”, “B”, “C” and “D”.
error-indication
Indicates an error in the decoded data. This attribute is required and is a choice between “no” or “yes”.
Note: The channel information and the error indication are valid for all content of a single text element.
Content
The content is either a Translated element, a Raw element, or both.
Translated element
Text
</Translated>
Content
</Text>
</Data>
</Message>
Attribute List
alphabet
Indicates which alphabet is used to translate the decoded data. This attribute is required and represents a
string (for values, see section “Parameter names and values”).
Indicates the number of pixels (points) returned. This attribute is required and represents an integer.
Count is 1 in case of type “Fax” and 2 in case of “FFT”and “SSTV”.
Content
The content is a sequence of one or more Point elements or a single BinaryFFT element.
The coordinates of the returned pixel. These attributes are implied and represents integers or floating
point values depending on the type of graphic.
rgb
RGB color information values. This attribute is implied and is a string. It is sent in a hex format
0xRRGGBB, where each of the colors red, green and blue has a weight between 0 and 255.
Content
This element has no content.
8 Data messages XML SDK V8.7.0 Remote Control Interface
Encoding type
Bits per character
Character set
base2
1
0, 1
base16
4
0-9, A-F
base64
6
0-9, A-Z, a-z ,+, /
base64-mime
6
0-9, A-Z, a-z, +, / (“=” padding character for byte alignment)
The content is the binary encoded FFT data. The encoding type (base2, base16, base64 or base64-mime)
is set by the Set Configuration Message.
Characters are converted into bits according to the selected encoding type.
Each FFT value is represented by a signed 16 bit word, where 12 bits are used for the integer part and 4
bits are used for the real part of the value. The following example shows how to extract the FFT value
from a bit stream:
Indicates the type of metadata returned. This attribute is required and is a choice between “code” and
“code-list”. “code” is synonymous with the term “mode” used when referring to the decoder.
Content
The content is a sequence of one or more MDCode elements.
MDCode message
MDCode element
10 Metadata messages XML SDK V8.7.0 Remote Control Interface
Returns the name of the mode being decoded. This attribute is required and is a choice between all possible modes (for values see section “Parameter names and values”).
Content
The content is a sequence of zero or more MDParameter elements, zero or more MDModulation elements and zero or more MDInput elements.
Indicates the modulation type used. This attribute is required and is a choice between all possible modul ation types (for values see section “Parameter names and values”).
Content
The content is a sequence of zero or more MDParameter elements.
The content is a choice between the elements Speed, ParameterList, Configuration, Key, MilStanagMessageType, ClassifierSetup, CustomInput and WCloudSources.
Speed element
14 Command messages XML SDK V8.7.0 Remote Control Interface
The Message element has a few implied attributes (see message template) which are only filled by the
server if recommended by the client, and the message-header attribute sets the filling preferences. This
attribute is implied and is a choice between “short” and “extended”.
text-data-format
Specifies how the content is displayed in a text data message. This attribute is implied and is a choice be-
tween “translated”, “raw” and “all”. “translated” indicates that the decoded text is translated with the se-
lected alphabet. “raw” indicates the decoded text is raw and unformatted. “all” indicates that all formats of
displaying the text are transferred.
binary-data-format
Indicates how the content is encoded. This attribute is required and may assume the value of “base2”,
“base16”, “base64” or “base64-mime”. The difference between “base64” and “base64-mime” is the way of
the encoded string is terminated. The difference between “base64” and “base64-mime” is the way the
encoded string is terminated. Both encodings use the same character set, but “base64-mime” follows the
specification for SMTP messages and aligns the string to four characters and fills unused positions with the
padding character “=”, whereas “base64” reduces the number of characters to just the ones required, depending on the bit count.
information-indicators-interval-per-minute
Determines the maximum number of information indicator messages per minute sent to the client. If configured to 60 messages per minute the client will receive between 0 and 60 messages per minute. A value
of 0 indicates that no messages are sent and a value greater than 6000 indicates that all messages are
sent. This attribute is implied and represents an integer.
fft-interval-per-second
Determines the maximum number of FFT graphic messages per second sent to the client. If configured to
20 messages per second the client will receive between 0 – 20 messages per second. A value of 0 indicates that no messages are sent and a value greater than 100 indicates that that all messages are sent.
This attribute is implied and represents an integer.
fft-data-format
Determines the FFT data format. This attribute may assume the values “text” or “binary”. The default set-
ting is “text”.
The sync mode is a choice between "async" and "sync".
data-bits
The number of data bits. The valid range is 5 to 8.
parity-bits
The parity bit is a choice among "none", “even”, “odd”, “mark” and "space".
stop-bits
The number of stop bits. The valid range is 0 to 2.
Valid attribute combinations:
bit-sequence
The bit sequence order is a choice between "lsb" and "msb".
data-polarity
The data polarity is a choice between "nor" and "inv".
auto-detect
The auto-detect command is a choice between “start”, and “stop”.
The auto-detect information is a choice between “idle”, “active”, and “success”.
display-format
The display format is a choice among "ita5", "ita2", "hex" and "binary".
The Stanag-4285 mode includes an additional display format, "s5066".
Valid combinations:
Note: Depending attributes are forced to valid values if their current values are not compatible with the
updated reference attribute. For example, if display-formatis changed from “ita2” to “ita5”, then data-bits is set to 7 bits.
XML SDK V8.7.0 Remote Control Interface Command messages 17
Loading...
+ 56 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.