Event structure: native BOP
|
Event Structure |
What is a BOP event ?... |
 |
|
native BOP display |
by using Clarinet Event-Editor without
any filter ... |
|
|
BOP decoding |
by using Clarinet Event-Editor with a
filter ... |
 |
|
Standards |
|
|
The BOP (Bit Oriented Protocol) events are generated by the analysis process
from the SL or DL link when the data structure is based on HDLC frame envelope.
More details about BOP in Clarinet Slides.(see Native events/BOP envelope)
The binary event structure is defined in the Clarinet-API.
Clarinet Event-Editor: native BOP display
The edition of the BOP events without any decoding/formatting allows to
display the contents of the differents fields:
|
Event information |
Date |
Date of the event (end of BOP frame) in
the format: hh:mm:ss/xxx.y |
|
| N |
The interface number which identifies the
Clarinet-interface connected to the host. |
| Link type |
- TS: Signalling Link Transmit
direction
- RS: Signalling Link Receive
direction
- TD: Data Link Transmit
direction
- RD: Data Link Receive
direction
|
| Dx |
The decoding level as specified in the
filter (protocol stack). |
|
Protocol fields |
BOP |
<BOP type> <flag
counter> [nnnn] |
|
|
Data field |
Field of the conveyed data,
displayed in hexadecimal. |
|
|
<BOP type> |
- Frame: Valid frame with correct CRC calculation result.
- Beginning of Idle state (1 permanent).
- End of Idle state (1 permanent).
- Abort frame.
- Crc error: Frame with false CRC calculation result.
|
|
<flag_counter> |
If normal frame, the numbers of flags
from the previous BOP event on the same direction. |
|
[nnnn] |
If normal frame, the numbers of octets of
the information field. The length does not include the
2-octet CRC. |
| 