Vxlapi- VN1610 - Unable to read Data from ECU

[Vamsi_Venkata_Sai_Kumar]

Hi all,

Good Day,

I have vn1610 and trying to read data from ECU that runs on J1939 protocol and it gives no Identifier or DLC information. Then I tried CAN received example program from Vector XL LV2011  and it read only one data "000000F0" and DLC is "0". But I have checked the hardware information and serial number and those details was matching with the hardware that connected. Can anyone point out what went wrong.

Details used: Hw: VN1610, Hw index:0, Hw channel: 0, EXT for extended identifiers and last baud rate as 500K.

Could anyone can point out what when wrong?

Thank you,

Vamsi.

[GerdW]

Hi Vamsi,

did you verify there are any other messages on this CAN bus?

Which ArbIDs (messages) do you expect?

[Vamsi_Venkata_Sai_Kumar]

Hi GerdW,

No, they were no other message in the CAN Bus.

I was expecting 29 bit CAN identifier related to engine.

Thanks for replying.

Vamsi.

[GerdW]

Hi Vamsi,

---

@Vamsi_Venkata_Sai_Kumar wrote:

No, they were no other message in the CAN Bus.

---

You verified this with some other CAN interface software, like CANalyzer?

---

@Vamsi_Venkata_Sai_Kumar wrote:

I was expecting 29 bit CAN identifier related to engine.

---

Why? Why do you expect just an ArbID?

Which kind of engine (passenger car, HD truck, …)?

Do you have a DBC file for that ECU with all message and signal descriptions?

[TroyK]

Has the device gone to sleep? Do you need to send something to wake it up?  Perhaps some sort of regular network management frame?

Is the 0 length CAN frame that you are seeing just a power-up message that is only sent once on powering up the device or is it sent regularly?

Edit: I've had another look at the front panel image you included in your first post.  Looks like you're getting over heaps of messages every second.

The example VI included on the wrapper library page DOES NOT HANDLE ERROR FRAMES.

I'd say you are seeing error frames, they just aren't being interpreted properly by that example VI.

Check that you have terminated the CAN bus properly and have selected the correct bit-rate for your application.

[Vamsi_Venkata_Sai_Kumar]

Good day,

The ECU is auto wakeup when we gave power supply to both battery and ignition. 

I have check the same connection in USB Link 2 VCI and CANOE tool and it read information from ECU and I got the data, But I was unable to send the request in those VCI's due to some personal reasons. I had only VN1610 and I had the LabVIEW license and I'm trying to receive and transmit request using the Vector LabVIEW interface. I have check the connection twice and I even check with raw data from the program and it was also not matching the data I received with USB Link 2 or CANOE. 

please go through the raw data I received using you first program.

Thanks for supporting. 

[TroyK]

I can't interpret that raw data image you attached.  It doesn't look like any VI that I posted.

[Vamsi_Venkata_Sai_Kumar]

Good day,

It was in Vector XL LV2018 v3, Please look into the screenshot.

I think it actually taking raw data, please correct me if I was wrong.

Thanks,

Vamsi. 

[TroyK · Accepted solution]

"xl Get Driver Config.vi" does not read CAN messages.  It just gets a list of the connected Vector hardware connected to the system.  You don't even have to use it if you know what hardware is connected.

The v3 "Vector XL Library.lvlib" was a new version of the library made by the user @Hooovahh.

Maybe he can offer better help than I can.

In any case it will be easier to help you debug your code if you actually attach your code.  Pictures of the front panel are close to useless.

[Vamsi_Venkata_Sai_Kumar]

Good Day,

Issue solved, The actual problem was in the vector hardware configuration the channel has default baud rate that not matching with the program. that why its shows no data while reading.

thanks for the support,

Vamsi.