3.3.2       Example

 

The following example illustrates the single steps using a decoder profile.

 

Assumed a log-file contains following log-entries with several message and we want decode these messages by means of a decoder profile.

 

…

09:07:49,680 DEBUG id=23 msg_7 out 0,F,0,19,0,0,2,6,27,0,0,2,7,AD,92,

09:07:49,727 DEBUG msg_8 inp 0,E,0,44,0,0,2,A2,A8,1,0,0,70,BE,

09:07:54,446 DEBUG msg_0 inp 0,15,0,0,0,0,0,0,A0,31,30,36,33,31,0,58,7C,50,5,96,B9,

09:07:53,961 DEBUG id=54 out >> 0,11,DB,2E,0,0,0,0,A5,0,0,0,0,0,80,C9,A8,

…

 

 

1.    Data Pre-Processing

 

Internal Pre-Processing

 

·         data pre-processing is necessary because the decoder which will be used needs a well formed hexadecimal string as input, e.g. 000F0019 …

·         in a first step of pre-processing the message data has to be separated from the log-entry

·         we can use the text-pattern 'inp'  and 'out' for it to get the begin of the message data

 

09:07:49,680 DEBUG id=23 msg_7 out 0,F,0,19,0,0,2,6,27,0,0,2,7,AD,92,

 

 â first pre-processing

 

0,F,0,19,0,0,2,6,27,0,0,2,7,AD,92,

 

 

Pre-Processor Library

 

·         in a second pre-processing we use a data-processor library which converts the comma separated message data into a well-formed hexadecimal data string

 

 

0,F,0,19,0,0,2,6,27,0,0,2,7,AD,92,

 

 âsecond pre-processing

 

000F0019000002062700000207AD92

 

 

Note: for more information about data-processor libraries see chapter Decoders and Data-Processors

 

 

 

 

2.    Data Decoding

 

·         the data input for our decoder is the hexadecimal string from the second pre-processing

·         the used decoder is a library which provides a result as XML

 

 

000F0019000002062700000207AD92

 

 â data decoding

 

<TSA_Request>

<IP_Radio_Msg_1_3_10>

<Data_Packet>

<packetLen pos="0.0" datlen="16" dr="15&#32;bytes">000F</packetLen>

<communicationID pos="2.0" datlen="16" dr="25">0019</communicationID>

:

</TSA_Request>

 

Note: for more information about decoder libraries see chapter Decoders and Data-Processors

 

 

3.    Data Post-Processing

·         data post-processing can be used to process a decoder output, e.g.
- to separate any data from the result in order to use these in further applications
- to convert or format the result data for special display

 

example for data post-processing - assumed a log-file contains a lot of messages containing geo-data - after decoding the result strings provides these geo-data e.g. as XML <lat dr="11&#44;73803"> 00B31BAE</lat> <lon dr="53&#44;02411"> 0329156B</lon> - for a further application you need these geo-data, e.g. as NMEA data - a post-processor library reads the decoder result and can do then the job
 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


4.    Result Viewing

·         setup a viewer application which shows the decoder output, e.g. a simple viewer application could be the 'notepad'


image

Figure 53: Result-Viewer