topic J1939 Transport Protocol in Components

J1939 Transport Protocol

Christian_L — Mon, 16 Dec 2024 16:28:58 GMT

Please post your comments, questions, and feedback on the J1939 Transport Protocol Reference Example in this thread.

回复： J1939 Transport Protocol

hyl175 — Fri, 09 Oct 2009 06:12:12 GMT

hi,

maybe there is a bug in the vi named Convert CAN Arb ID to J1939 ID.vi

its path in the package is……CAN_Message_Online\J1939 Multi Packet Frame\Code\J1939 Utilities\_SubVIs\Convert CAN Arb ID to J1939 ID.vi

when the PF is smaller than 240(10), the PS in the PGN should be 0.

回复： J1939 Transport Protocol

hyl175 — Fri, 09 Oct 2009 06:13:51 GMT

hi,

maybe there is a bug in the vi named Convert CAN Arb ID to J1939 ID.vi

its path in the package is……CAN_Message_Online\J1939 Multi Packet Frame\Code\J1939 Utilities\_SubVIs\Convert CAN Arb ID to J1939 ID.vi

when the PF is smaller than 240(10), the PS in the PGN should be 0.

Re: J1939 Transport Protocol

bfeddeck — Fri, 11 Dec 2009 04:17:53 GMT

Can I get these examples in version 8.5?

Re: J1939 Transport Protocol

brent2004 — Thu, 28 Oct 2010 18:26:28 GMT

It would be nice if NI had a J1939 driver or add-on that would work with both the frame API and/or the channel API. The only examples provided for J1939 here are based on the frame API, which precludes you from using the channel API with a CAN database on the same port. The channel API is a very time saving feature for most applications.

DMC recently developed a set of J1939 protocol drivers for LabVIEW which are based on the NI-CAN channel API. The drivers are written in LabVIEW just like the example, but provide functions at a layer above the base CAN channel API layer. This allows the simultaneous capture of data from both J1939 packets which are simple broadcast CAN frames, or more complex transport using BAM, including extended data frames.

Although it would be nice to have an option like the Automotive Diagnostic toolkit, which worked withouot forcing a user to pick an API and stick with it for J1939 and whatever else they have going on with that CAN port.

Re: J1939 Transport Protocol

brent2004 — Thu, 28 Oct 2010 19:09:36 GMT

Correct link for J1939 protocol drivers for LabVIEW which are based on the NI-CAN channel API.

Re: J1939 Transport Protocol

Julianne_K — Mon, 16 Dec 2024 16:29:54 GMT

Customers have recently requested that a J1939 Reference Example be provided for the new sbRIO-9606, which uses the RIO Embedded CAN driver.

Re: J1939 Transport Protocol

Djalex86 — Mon, 12 Mar 2012 11:05:29 GMT

Hello , i am using the NI 9853 to communicate with a charger that use J1939.

With the project J1939 cRIO Example Project.lvproj when i send the message appears the message code -63001-Invoke Method: FIFO.Write in J1939 cRIO Example.vi .

How can i solve this error??

Thank you

Re: J1939 Transport Protocol

Djalex86 — Mon, 12 Mar 2012 13:57:40 GMT

Hello , i have this error -63001 .

How can i solve this??

Thank you

Re: J1939 Transport Protocol

Mark_Gillespie — Tue, 09 Jul 2013 21:23:00 GMT

I am trying to use the xnet frame example in conjunction with a PXI-8513 card. I am physically connected to an ECU that is transmitting a single PGN. I have both pxi ports connected to the network with port 2 running the can bus monitor. I can see the pgn message coming from the ECU on the bus monitor. When I send data from the frame example, I can see it on the bus monitor.

However, I am not seeing anything on the input display of the example. It seems like I should see the same info as the bus monitor. Am I incorrect? The pgn being transmitted is a proprietary one. Is there some kind of filtering going on that keeps this message from showing up? The PGN is 65298. The full ID on the bus monitor is 4ff1200.

Thanks for any help.

Re: J1939 Transport Protocol

AmitSaste — Mon, 16 Dec 2024 16:30:27 GMT

Hello,

I am trying to use J1939 NI CAN Frame Example.vi available at: https://forums.ni.com/t5/Example-Code/J1939-Transport-Protocol-Reference-Example/ta-p/3984291

My requirement is to read various messages and two of them may have size greater than 8 bytes. The message which may have size > 8 bytes is received at 1s while other messages which are of 8 bytes are received at 10ms.

When this VI is executed, I am able to see only one message which is transmitted at 1s. Other messages which are transmitted at 10ms are not seen as output in "Read Processed Incoming Message" loop.

Any idea on this?

Re: J1939 Transport Protocol

Daniel_E — Thu, 29 May 2014 14:25:03 GMT

Hey,

I apologize but I need a little more information. What are the messages you are trying to monitor (IDs)? What driver are you using (NI XNET or NI CAN)? Have you tried probing the NI XNET or CAN read VI to see if the messages some in at all? What device address are you using for the code?

Ultimately, the code does some level of filtering out of messages based on who the message was intended for, etc. Once I know the IDs and device address, I could tell you which ones should pass through.

More specifically, J1939 has the idea of peer to peer messages (PDU1 and Connection Mode) and global messages (PDU2 and BAM). The code respects those rules so it will filter out messages that are peer to peer and not addressed to it. If you open the Process Incoming Messages VI you can see the filter subVI and see that I don't pass through messages that aren't intended for the device. You are welcome to modify that. That said, it is outside of the intended use case so I am not sure how everything will work with that change.

I hope that helps!

Re: J1939 Transport Protocol

vdvfvd — Mon, 16 Dec 2024 16:30:54 GMT

Hi,

I have the J1939 Transport Protocol VI that can read or write CAN signals with the SAE J1939 protocol.

I would like te control the PVED-CC module, it is a Sauer Danfoss CAN Communication Interface Module (actuator)

This module is used to control a hydraulic PVG 32 (proportional valve group)

I know that the actuator send short SAE J1939 signals, because I measured it with a digital oscilloscope, the signals are not log because they are fault messages. Because I didn't connect the valve group yet.

I have used two resistors of 220 Ohm, to make the bus terminations. I assume that the RIO Evaluation board (sb-9636) doesn't have a jumper where you can change the resistor onboard of the connector (on the CAN0 connector). So I took my own resistors to make the termination.

I can't get communication with the CC module in Labview, when the VI runs there is nothing that happens

I am not sure that with the VI, I can control the CC-module I used 254 as the current device adress and a baud rate 250000kbps and a Receive queue size of 5.

I made two concersions in the Process Incoming Messages and the Output Processed Outgoing Messages loops. Because the clusters where not the same as the NI CAN , NI XNET or cRIO drivers uses. I uses bundle and unbundle function for clusters, to make the VI excecutable.

I attached the VI, as some information of the fault mode of the actuator

I can send messages from the VI to the bus, I measured them with my scope. But I can't confirm that they are SAE J1939 compatible

I am dutch student, and I need some help for my thesis. I would like to know if it is possible to control the CAN module by using controllers of National instrument

If the test suceed, we will buy the cRIO-9030 controller with the NI 9853 CAN module. Because it is almost the same hardware as the evaluation kit, I would like to use it as a test to proove that the hardware is compatile.

Links

NI J1939 transport protocol:

https://forums.ni.com/t5/Example-Code/J1939-Transport-Protocol-Reference-Example/ta-p/3984291

Sauer Danfoss PVED-CC module:

http://files.danfoss.com/documents/520l0665.pdf

Thanks!,

Best Regards,

Gautier

Re: J1939 Transport Protocol

vdvfvd — Wed, 18 Mar 2015 14:14:13 GMT

Hi,

This is a bettec picture of the VI

Thanks,

Gautier

Re: J1939 Transport Protocol

BLowery — Wed, 22 Apr 2015 12:57:58 GMT

Is there a version of this example for LabWindows/CVI? If not, could we please get one?

Re: J1939 Transport Protocol

prithvibasak — Fri, 04 Nov 2016 18:22:22 GMT

I'm looking to extend the example code here to talk to multiple device addresses.However, I faced difficulties trying to extend it to multiple devices as I went into the sub-VI's such as J1939 Process Incoming Messages.vi. I am using NI-XNET communication.

Re: J1939 Transport Protocol

CoastalMaineBird — Mon, 16 Dec 2024 16:31:23 GMT

The ref document <https://forums.ni.com/t5/Example-Code/J1939-Transport-Protocol-Reference-Example/ta-p/3984291> has an error:

In the description of the PDU S field, the value of PDU F is divided into two categories:

... If PDU F is greater than or equal to 240

... "If PDU F is intended for a specific device (less than 239)"

which of course does not include the value 239 itself.