LIN message not appearing in Receive/Transmit table
Posted: Thu 24. Jan 2019, 10:46
Hi,
I'm using PLIN-View Pro (version 2.1.1.92) to analyze LIN messages sent by our device. Our customer reported there is a problem with one message (0x0A), with no more details. I attached the PCAN-USB Pro FD (firmware version 3.2.0) to analyze the problem and found the message is not being sent at all. Or at least, this is how it looked like from the Receive/Transmit table, as the message was not present there.
I checked the signal by an oscilloscope, but didn't find any problem - the message 0x0A was being sent as expected. So I enabled the Trace in PLIN-View and, surprisingly, the analyzer also displayed the message, with no errors.
Anyway, the message was still missing in the Receive/Transmit table. So I tried to reset the analyzer using the
button with black arrow and suddenly the message appeared in the table.
So my question is, why the message did not appear in the Receive/Transmit table when the analyzer obviously detected it correctly in the Trace. Might there be something wrong with the message, or is this a problem with analyzer?
I'm using PLIN-View Pro (version 2.1.1.92) to analyze LIN messages sent by our device. Our customer reported there is a problem with one message (0x0A), with no more details. I attached the PCAN-USB Pro FD (firmware version 3.2.0) to analyze the problem and found the message is not being sent at all. Or at least, this is how it looked like from the Receive/Transmit table, as the message was not present there.
I checked the signal by an oscilloscope, but didn't find any problem - the message 0x0A was being sent as expected. So I enabled the Trace in PLIN-View and, surprisingly, the analyzer also displayed the message, with no errors.
Anyway, the message was still missing in the Receive/Transmit table. So I tried to reset the analyzer using the
button with black arrow and suddenly the message appeared in the table.
So my question is, why the message did not appear in the Receive/Transmit table when the analyzer obviously detected it correctly in the Trace. Might there be something wrong with the message, or is this a problem with analyzer?