<< Click to Display Table of Contents >> Navigation: »No topics above this level« Managing a PGN using a PV |
mapp Services V5.16
This section explains how to manage the information of a PGN using a PV.
Example
For example, the numeric value of PGN DTBI1 is 61710 (0xF10E). PGN DTBI1 can return or transmit the following signals:
These signals have a defined length. For example, signal "BodyRollAngle" has a length of 16 bits.
Input parameter "Data" of the function blocks must be used to provide a buffer that can receive and display the values of PGN DTBI1.
To receive PGN DTBI1, a structure must be created that contains the exact length of the signals. It must be known exactly how PGN DTBI1 is structured. Each signal has a start bit and a fixed bit length. This means it is exactly defined from which bit the signal starts and from which bit it ends. This looks as follows for PGN DTBI1:
Start bit |
Length |
|
BodyRollAngle |
0 |
16-bit |
BodyRaiseAngle |
16 |
16-bit |
BodyRaisePosRelToRecommendMax |
32 |
16-bit |
BodyEjectorBladePos |
48 |
8-bit |
In order to obtain the information for this PGN, a structure must be created that has exactly the same bit length.
It can look like this, for example:
Variable "My_DTBI1" was created that is of user-defined data type "My_DTBI1_Type". This data type contains variables that correspond to the same bit length of PGN DTBI1.
The alignment of the user-defined data type must be strictly observed. It must correspond exactly to the desired PGN.
The user-defined data type is not permitted to contain any stuff bytes!