BinTerm - Help
Prior Next

1.2.2 Operating protocol - receive from CAN- data:
 
On operating mode CAN with the USB- Dataspy with CAN- extension you can receive and send telegrams from CAN bus of version 2.0A and 2.0B .
With CAN 2.0A are telegrams with 11- bit identifier, on CAN 2.0B are telegrams with 29- bit identifier protocoling. BinTerm can protocoling both variants at the same time.

Receive from data:
In the protocol from BinTerm is the ID from telegram, the state from RTR- bit, the data length DLC and the data:


Receive from errors from bussystem:
All received errors are red protocoling.
- You can see the direction from the error (RX / TX)
- How you can interpret the error (bit- error, form- error, stuff- error, other error)
- In witch segment was the error .

Further BinTerm protocoling in witch bit the error occur.

The count for the errors for RX- and TX- error count.

At last you can see the state from bus and a overflow from CAN- controller.

Altogether can BinTerm more then 60 errors protocoling.

As long as a error is pending, the red LED from USB-Dataspy is on. In the CAN- controller is a error- count for RX- and TX- errors included. Are there more then 125 error detect, so the red led goes on. Are both counters less then 125, the red led goes off. On every telegram with error, the error- counter increment. On every good telegram, the error counter decrement. It is possible, the red LED goes off, after receiving some good telegrams.


Prior
www.MmVisual.de

Mail: mm@MmVisual.de

Next