12-16-2009 07:13 PM
I am attempting to connect to a OBD ECU using a usb8473 and CAN. I think I have the physical connection correct but I get the a timeout error when calling the ADCS toolkit OBD Open. What I dont know is how to determine the baud rate and Tx/Rx IDs. Where is this information. How can I determine the cause of the problem.
12-17-2009 09:25 AM
Hi Pual,
That information will be contained in the A2L file that corresponds to your ECU. Do you have this file?
12-17-2009 01:03 PM
12-18-2009 04:59 PM
Hi Paul,
Sorry I was mistaken with your setup you won’t have an A2L file. One thing you can do I open up Bus Monitor and see what baud rate allows you to receive transmissions. Do you have any more information regarding the ECU to obtain these parameters?
12-20-2009 07:57 PM
12-21-2009 03:51 PM
Hi Paul,
If you can read from the CAN network using Bus monitor you will be able to see any messages being transmitted and received. Unfortunately, I don’t have any more information regarding your particular ECU’s baud rate or arbitration IDs. That information is specific to your vehicles CAN system.
05-18-2010 03:48 PM
Hey Paul,
Did you ever get any more info about connecting with the F250?
I am trying to find a way to get engine oil temps (EOT) off my truck, but it is not a standard can message and was thinking about messing around with LabVIEW.
I tried looking for an option to PM you, but it is not possible on this forum.
05-19-2010 05:15 PM
Hey Bryan,
If the EOT is not a standard CAN message, how exactly do you plan on getting this data using LabVIEW? If the message is passed through the CAN bus, you would need to find the arbitration ID of the specific message, so that you can get that data off the bus.
05-19-2010 05:18 PM
05-20-2010
11:24 AM
- last edited on
05-23-2024
10:25 AM
by
Content Cleaner
Bryan,
one other thing to consider is using the Automotive Diagnostic Command Set. The product page can be found at the link below.
https://www.ni.com/en-us/shop/product/automotive-diagnostic-command-set-toolkit.html
If your F250 is newer than 2006, it most likely has an ODB2 interface for you to be able to use the command set. This might be easier to use as it abstracts the arb id's and might help you get what you are looking for. I would also look into getting in touch with the manufacturer to find out exactly what you need to communicate to get the specific data you are looking for.