Tes­ter shows non exis­tend error-frames

First of all plea­se update your soft­ware if this pro­blems hap­pens to you. The­re was an error in syn­chro­ni­za­ti­on befo­re ver­si­on 4.6.3.

Besi­de this it might be that your CAN-Bus Tes­ter 2 or your CAN­touch are sho­wing error-frames that are not exis­tent on your bus.Because the tes­ters are nor­mal­ly pas­si­ve devices which are non­re­ac­tive and the­re­fo­re can not send their error frames to other nodes, the­se “unre­al error-frames” are not visi­ble to the other nodes. At activ­i­ti­ing the pro­to­col moni­tor the devices beco­me active nodes and then send their active error-frames. In this case they react just like a node at the same posi­ti­on with iden­ti­cal bit-timing.

The tes­ters are con­fi­gu­red to a strin­gent bit timing that is given in the CiA stan­dards. They might show errors if your bus is not using the same strin­gent bit timing.

You find a reme­dy by con­fi­gu­ring the same bit timing in the tester.

Basi­cal­ly you could also use a very tole­rant bit timing. This is like clo­sing your eyes for the bit timing rela­ted pro­blems, the tes­ter will be fine with almost ever­y­thing. You have to balan­ce pros and cons on this.

CAN-Bus Tes­ter 2

Print Friendly, PDF & Email