Hello,
I have set my PCAN - LIN as a LIN Master with the CAN-LIN Gateway configuration (scheduler inactive).
I am sending an RTR CAN message with identifier 0x16 from a Peak CAN router to the PCAN-LIN device, expecting it to send then a request for LIN ID 0x16 at our slave.
I set the length of the message to 0 or 4 bytes but it doesn't work as expected.
I get a 0x0Ah warning on the LIN bus -> "Slave Id not available".
Our slave node (LIN) has two parity bits which are included in the identifier byte. I added these such that our RTR CAN message had an identifier of 0xD6. This time we get no warning but also no response.
Our PCAN-LIN was purchased last year with software SLAVE SIM.
Please help!
Catherine
Request of a data frame on the LIN bus by transmitting a CAN RTR
Re: Request of a data frame on the LIN bus by transmitting a CAN RTR
Hi,
can you please post the config file (*.pclin) with which you have configured the PCAN-LIN? Did you set the frame configuration to the correct length, direction=subscriber and checksum type of your LIN system? You have to send the CAN ID depending on the used CAN-ID offset and also with the same length code defined in the frame configuration. Having the ldf of your system as reference will be helpful. You can also contact us by email to echange those data.
regards
Michael
can you please post the config file (*.pclin) with which you have configured the PCAN-LIN? Did you set the frame configuration to the correct length, direction=subscriber and checksum type of your LIN system? You have to send the CAN ID depending on the used CAN-ID offset and also with the same length code defined in the frame configuration. Having the ldf of your system as reference will be helpful. You can also contact us by email to echange those data.
regards
Michael
Re: Request of a data frame on the LIN bus by transmitting a CAN RTR
Hello,
Thank you for your response. We had a hardware problem on our side (relay malfunctioning) which was inhibiting the communication between the PCAN-LIN and our slave node.
To resume for others:
Sending an RTR CAN frame ID 0x16 (with length 4 Bytes) to the PCAN-LIN device (set to the LIN master with scheduler disabled, see Master Gateway CAN-LIN setting), enabled us to then correctly request via LIN the 0x16 LIN ID (with length 4 Bytes) at the slave.
Catherine
Thank you for your response. We had a hardware problem on our side (relay malfunctioning) which was inhibiting the communication between the PCAN-LIN and our slave node.
To resume for others:
Sending an RTR CAN frame ID 0x16 (with length 4 Bytes) to the PCAN-LIN device (set to the LIN master with scheduler disabled, see Master Gateway CAN-LIN setting), enabled us to then correctly request via LIN the 0x16 LIN ID (with length 4 Bytes) at the slave.
Catherine