Using the DrewTech J2534-I engineering interface
Hello folks, Scott has encouraged me to get active on the forum, and I thank him for his support, and for creating Diag.net
I have purchased a Drewtech Cardaq-M, and downloaded the DrewTech J2534-I engineering interface.
I would like to: measure, record and assess how a generic scan tool accesses and interacts with any particular vehicle.
Any support or feedback would be appreciated.
(I am aware that this is a very general question, logically it seems a good place to start the conversation.)
That's not only general, it's extremely difficult to explain via a forum like this. I'll give it a shot but first, I don't use their engineering interface though I have looked at it. I do use the CARDQ-M.
My day job consists of a lot of tech support to repair community but in addition, I QA OBD software for the IM program so I am looking at generic communication all the time. To look at the vehicle, I prefer RA Consulting software which is the Silver Scan Tool. It lines up everything with j1979 so allows better accuracy than other scan tools. It allows you to monitor the communication on the bus in 2 ways and provides this in a hex format so you have to know how scan tools communicate and how vehicles respond in order to read that file. If you so choose, you can create your own CAN commands and send them via the bus to monitor vehicle response in the same way the engineering interface does. Another feature is it performs the J1699-3 function which is a verification process for the vehicle, See J1 of the 1968.2 regulation.
When I need the IM lane software debugged, I have a log file program running there and I retrieve that to see what it is doing and it to is in hex format.
The next question is what are you specifically trying to do?
Hello Randy, thank you for your response.
Similar to what you are describing with your IM lane software debugging, I would like to create a hex format logfile.
The first level of this would be how any generic scan tool will connect and interrogate the ECM to obtain a VIN.
I need to firstly create a baseline, to reference my testing data to. In my region, Im thinking that this will likely be more logical to create a base line for each OEM. (Or ECM model?)
My initial task will be to obtain raw data on why so many ECM's will NOT return a VIN, on request.
Hopefully, analysis of this raw data may show the path forward, or at least a possible path per OEM
From your response, are you running the Cardaq - M with the Silver Scan Tool software?
How do I obtain the Silver Scan Tool?
The request for OBD VIN is straght forward. We just got done with our latest fix on that issue and it seems to be working. The basics are it’s a mode $09 info type 2 request but is only required on 2005 and later us built vehicles With CARB OBD. It can be stored on any OBD module. You will want to make multiple requests. After that, I would need to know what vehicles and protocols you are having issues.
one of the issues we see is technicians replacing modules and not entering the vin. For instance, there was a recall on 2006 Toyota Corrollas for module replacement and they do not have mobilizer so we see a lot of them with blank obd vin.
RAConsulting is a German company but sells around the world, mostly to OEs for OBD verification which is why it is rock solid engineering level scan tool. They are also very open to special software requests. I have asked for several and they have obliged.
yes to how I am running it. The downside is all the data you will end up with and then how to manage it. I wrote a very large macro that would grab the data from the xml files and order it in a usable format for excel. I can put hundreds of files from the same or different vehicles and find trends, issues, anomalies etc.
If I have time this week and that’s a big if, I will share a file on a 2006 Saturn that has a data PID anaomoly that has a reflash fix but the SST was able to identify the issue. It’s a well known issue but gives you an idea how to use it. Scott will have to tell me how to load an excel file to this site than can be readable though.
I’m still not sure what you are trying to do and on what vehicles so my suggestions may or may not help.
Randy, this seems to be on point.
RE: What am I trying to do, and on what vehicle: I am working on debugging a scan tool on Australian vehicles. We have close to 76 OEM's selling vehicles here in Australia. When I first started this project I noticed that many OBD functions are not available in Australia. For example on a lot of vehicles when OBD is accessed from a scan tool there will an error message "selected system not available" Sometimes, in other cases there is limited data available under obd protocols. For example, under live data it may have engine rpm and coolant temp.
It seems that a good place for me to start would be to observe any correlation with all the test vehicles, and test data to observe any patterns. In this way, a method could be developed to approach each group in the pattern, be they model, OEM and/or ECU model.
Update* I have spoken with Mario @ RA consulting, he cant guarantee that his software will function in the Australian environment. He is arranging for a demo version of the software, for a fortnight. Also, the tool only functions on OBD protocols. This brings up the question, will the DrewTech software read non-OBD, like the pin 9 GM: 8192 bit/s ALDL?
Are there only DrewTech folks here that can answer this question?
The Cardaq+2, Cardaq+3, GM Mongoose Pro II and Cardaq M all support GM UART, which is a -2 protocol addition. I try not to use the acromym ALDL (Assembly Line Data Link) in discussions on OBDII because that term technically refers to a GM OBD1 12 pin connector.
Connectivity to UART would be dependent on the software you are utilizing.
Hello Bob, thank you.
I hear you describe the ALDL as the early GM 12 Pin connector.
I have a GM Mongoose Pro II, and a Cardaq - M unit. I also have a Mongoose FORD unit, but I haven't found a use for it?
I have a copy of the DrewTech J2534-I software, but this isn't the software that you are referring to? Are you referring to the software that I am using to interrogate the vehicle?
Also, do you have any training, support or educational resources for your DrewTech J2524-I software?
The DT J2534-1 software is for primarily -1 protocols. It appears that the common -2 ones were added to the supported list (like SW CAN) and since GM is no longer installing UART (and hasn't for 10+ years) my guess is that was not included in the software connectivity.
I was referring specifically to the software you are using to communicate with the vehicle. Your hardware supports UART, you will need an application that also does to complete the loop.
I am unaware of any support materials, but our J2534-1 software is basic. Select your device in the top right and the Protocol in the bottom right to connect. It will not connect to UART. I'm also sure Tech2WIN will not connect to UART either. UART and K-Line are the big offenders with Tech2WIN; never implemented. I know the UART ECUs on my 2006 Pontiac GTO (a Holden) do not work with Tech2WIN and requires a real Tech2. Here is a link to a Tech2Win document that describes the challenges.
Hopefully this helps.
Hello Bob, I have not used Tech2WIN, however I have a Tech 2 here. I hear you say that this J2534-i program is basic. Is it possible that you might be able to walk me through it? In context, an overview, introduction to menus, functions and usage.?
Hi Jaxon, Bob had me share a document covering the Tech2Win challenges within his response above.
Hi Scott, and Bob, thank you. Ill look into that after classes this week.
About a year ago it seems emissions testing was a hot issue:
I don't know what happened since then but what is the current state of vehicle emissions legislation, testing, compliance, enforcement, etc in Australia?
If you are interested in troubleshooting the functions of Vehicle Onboard Diagnostics I would try to engage with local authorities.
Hi Andrew, thank you for your input.
To answer your question, we have very little in the way of vehicle emissions legislation, testing, compliance, enforcement.
I have held an examiners licence in Queensland for car, motorcycle and trailers. This is an except from the official Code of Practice - Vehicle Inspection Guidelines: June 2018 (Queensland, Australia)
So, that is all the law has to say about emissions testing, in my state. It is a visual assessment only.
I dont think it will serve anyone here to bring politics into this forum, however, please note that a number of organisations and independent workshops and people have been campaigning for years for laws similar to your country.