From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
I don't work with LIN too often, but I suspect this is a timeout waiting for the slave's data. A master will send the ID for the data it wants, and then it is the responsibility of the slave to send the data for that ID. Each ID you send should have a corresponding single device that will send that. Some times it is the master itself, which is how the master can send data. But most of the time the ID needs corresponds to another device on the bus, which will act as a read.
If the master sends the ID, and then no slave populates the data, then I'd expect a timeout error. This might happen if the slave isn't powered, isn't connected, or the ID doesn't correspond to any slave. Also if you want to know more about LIN I just made a blog post on it that compares it to CAN and covers some of this.
ID 0d60 (0x3C) and 0d61(0x3D) are reserved for diagnostics. Please refer to shipping example LIN Diagnostic Frame Master.vi and LIN Diagnostic Frame Slave.vi from NI Example Finder >> Hardware Input and Output >> LIN >> NI-XNET >> Advanced.
Senior Technical Support Engineer | CLD CTA | NI
DISCLAIMER: The attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system, or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense