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.
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.
09-29-2015 09:59 AM - edited 09-29-2015 10:02 AM
Is it possible to change the default length (13 bits) of the LIN Break with a NI USB-8476 and the NI-CAN Frame API ?
Solved! Go to Solution.
09-30-2015 05:00 AM - edited 09-30-2015 05:06 AM
There is a property in NI-XNET to configure the length of the break.
Unfortunately I haven't found a similar property in the NI-CAN Frame API.
09-30-2015 07:29 AM
I am pretty sure it is supported, but it may not be documented. Try attribute 0x80020047. It should accept a similar range as the NI-XNET version.
09-30-2015 10:54 AM
Many thanks for your answer ! I will try this tomorrow.
There is indeed no documentation about this attribute, neither in the NI-CAN Hardware and Software Manual nor in the help of LabVIEW.
10-19-2015 04:42 AM
Sorry for my late reply due to holidays.
According to a test conducted by a colleague, this attribute has no effect on the length of the break. Could you please verify its number and if it is really supported by the NI-CAN Frame API ? Many thanks in advance.
10-19-2015 07:11 AM
From what I can tell, that is indeed the number and it should work.
10-20-2015 05:03 AM
Thank you very much.
I will make a new test myself. This is how the bus is configured.
10-27-2015 09:52 AM
The "secret" 0x80020047 attribute is indeed supported by the NI-CAN Frame API and allows to change the length of the break.
Many thanks once again.
10-27-2015 09:56 AM
I don't think it was intended to be a secret (more likely the documentation was just forgotten). I was a bit nervous when the preliminary results indicated that it didn't work, so I do appreciate the update to let me know that it did.
10-27-2015 10:12 AM
I labelled this ID "secret" because it is neither documented nor listed in the selector of the IDs.
Would it be possible to add it to the next release of the driver ?