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.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
NI-XNET J1939 Receive Long Message to ECU
Cabman
Member
08-30-2018 04:21 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Labels:
I've wrote a VI to send receive J1939 messages on the USB-8502. For the most part it is working except for receiving long messages directed to a specific address. After failing to get this work on XNET 16, I upgraded to XNET 17.5.1 when I found that it had problem with the TP. It didn't fix it, but the CAN messages are different.
Sending a 8 byte J1939 message to a global or specific address my VI works. i.e.
TX | 00EF00 | 6 FA FF | 00 01 02 03 04 05 06 07
XNET RX | 18EFFFFA | x00 x01 x02 x03 x04 x05 x06 x07
TX | 00EF00 | 6 FA 09 | 00 01 02 03 04 05 06 07
XNET RX | 18EF09FA | x00 x01 x02 x03 x04 x05 x06 x07
If I send a J1939 long message to a global address it works. i.e.
TX | 00EF00 | 6 FA FF | 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
XNET RX | 00EF00FA | x00 x01 x02 x03 x04 x05 x06 x07 x08 x09 x0A x0B x0C x0D x0E x0F (XNET 17.5.1)
With XNET 16.1 the 4 8 byte CAN messages were displayed and correct:
RX | 3:59:12 PM | 8 | 18ECFFFA | x20 x10 x00 x03 xFF x00 xEF x00
RX | 3:59:12 PM | 8 | 18EBFFFA | x01 x00 x01 x02 x03 x04 x05 x06
RX | 3:59:12 PM | 8 | 18EBFFFA | x02 x07 x08 x09 x0A x0B x0C x0D
RX | 3:59:12 PM | 8 | 18EBFFFA | x03 x0E x0F xFF xFF xFF xFF xFF
If I send a J1939 long message to a specific address it does not work. i.e.
TX | 00EF00 | 6 FA 09 | 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
XNET RX | no response
With XNET 16.1 I would receive two CAN messages. The first 'BAM' is correct, don't know what the second is about. The three payload messages are missing:
RX | 3:58:35 PM | 8 | 18EC09FA | x10 x10 x00 x03 xFF x00 xEF x00
RX | 3:58:36 PM | 8 | 18EC09FA | xFF xFF xFF xFF xFF x00 xEF x00
I made sure that I have claimed the address 0x09 so I don't understand why I'm not receiving the message. Obviously the software is not resonding to the RTS command (0x10) in the first BAM message. I believe it should if the address is claimed. (I've actually confirmed this with different CAN hardware)
Any ideas what the problem is?
LabVIEW 2017 (Originally developed in LV2013)
NI XNET 17.5.1 (Originally developed with NI XNET 16.1)
Windows 10 (Originally developed in Win 7)
USB-8502
