LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Replacing USB-8476 (LIN) with USB-8506 (XNET)

We have built several testers that function test an automotive component via LIN, i.e. detect when a switch is pressed, illuminate items on the part's front panel, etc. For all these testers we used the USB-8476. For the new tester we are using the XNET USB-8506.

Luckily I have a known working component from the last tester that I have hooked up to the XNET device. The JPEG below shows how I was initializing the LIN bus using  the NI-CAN Frame API instructions. The read/write instructions use the same items, CWrite, CWait, CAttr (Read Entries Pending) switching the IsRemote value from 18 (write) to 17 (read). This all worked fine.

Needless to say, I'm having difficulty communicating with the XNET device. I noticed that the only attribute available is Termination...the other ones that I used to set are not there: Self Reception, Log Bus Errors, LIN Checksum Type, and LIN Enable DLC Check. I don't know if they were all necessary.

Can anyone recommend documentation that may help? I'm going through all the example programs provided in LabVIEW (vers 2015 sp1, using Windows 10) and have also tried communicating through MAX.

Thanks for any assistance!

0 Kudos
Message 1 of 10
(5,917 Views)

Hi teritask,

 

the functions/subVIs in your image look like those from the "old" NICAN driver - they look completely different than those XNet functions.

 

Have you tried to use your XNet device using XNet functions?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 10
(5,863 Views)

Yes, I know they're different, I was asking about some of the old functions that are not available in the XNET instructions.

I hooked up a part that I know worked with the old instructions so I can transfer to the XNET instructions. No luck yet but I just started.

0 Kudos
Message 3 of 10
(5,843 Views)

Let us know what happens

0 Kudos
Message 4 of 10
(5,834 Views)

Due to time constraints, I ended up purchasing 2 of the older USB-8476 modules. I will keep working with the XNET module since I have a part that I can communicate with with the older module. When I do so I will definitely update this thread.

0 Kudos
Message 5 of 10
(5,827 Views)

Hello teritask,

 

Any news regarding USB-8476 to USB-8506 migration? How did it go?

 

regards, Bogomir

0 Kudos
Message 6 of 10
(4,709 Views)

Sorry, I never saw this message! Since then I just kept using the older USB-8476 modules for the customer but now I have to switch to the USB-8506 XNET device.

I'm back at square one, still not getting anywhere, just waiting for the "AH HA" moment.

 

I used XNET many, many years ago for CAN comms on several test benches we produced but the LIN interface seems much different. I will post my results when I figure it out.

0 Kudos
Message 7 of 10
(4,303 Views)

Can you share your program for USB-8476(LIN)?

0 Kudos
Message 8 of 10
(3,902 Views)

This a simplified version of my comms VI that I've used in several programs for around 10 years with no problems. This one is saved with LV 2017.

0 Kudos
Message 9 of 10
(3,893 Views)

Your program give me huge help, I have solved my problem today, I'm appreciated with your kindly support! Thank you very much!

0 Kudos
Message 10 of 10
(3,877 Views)