I'm seeking some advice about eye diagrams for analysing node behaviour on CAN for a prototype system.
I've been given this eye diagram, which is generated using Vector's .scope Canalyser tool and trying to understand what is going on here.
The eye diagram is generated using the tools "Window sweep" setting which, from what I understand, shows the timing of bit transitions relative to the expected speed of the CANBUS. So, in the eye diagram shown, the bus baud rate was 500k meaning that bit cells should be 2us.The pinky area is the bit mask, in which no bit transitions should encroach, especially the points at <= 75%, since this is where some CAN nodes will often sample the dominant or recessive state.
From the diagram, I could conclude that this particular node is running "up to 20% fast" relative to the expected baud rate which means that some of the trailing edges of bit transitions encroach upon the 75% sample point but I'm not 100% sure that this is a correct interpretation. The diagram relates to a particular node on the CANBUS; other nodes have transitions around the 0% and 100% points, which is what is expected.
It is also possible to view a frame in "VN" mode, where the bit cells are shown relative to the actual bus speed. Notionally, this seems more applicable, because it is my understanding that bit transitions are used to synchronise "clocks" on receiving nodes and this is why we have a stuff bit every so often to maintain clock synchronisation (or maybe it is just so that we can see that the bus is actually operational still?). In other words, it doesn't matter if a node has a slightly fast or slow clock just as long as it isn't wrong enough by more than 25% of a bit cell. Is this the correct interpretation?
If anyone has used this tool and has seen something like what is in the diagram, it'd be great if you could share what the root cause was.
Thanks in advance for any help.