What is the software being used by dmaxben for parsing the data and only seeing responses, I was able to do some things with my truck last night, I was able to map the steering wheel buttons, as well as window lock and door locks, I can see a ton of messages on the key in switch on position. Once I start the truck messages are far too fast for me to manually see anything… I have an STI tuner for the truck and I can see standard parameters, speed, RPM, temp, etc. With the tuner I have, I can manipulate the transmission shift points and such so I am guessing that I might be able to see that info as well. Is there any way to use SavvyCAN to filter the J1850 messages using your M2 Library?
There CURRENTLY is no utility to map out J1850 responses.
SavvyCAN is only for canbus stuff and won’t work with J1850 or anything other than CAN.
You need to either build your own program to strip out the responses, do it manually or plug into a spread sheet and do comparisons. You CAN do a sort of rows based on what is in them so you can sort a log into like commands and go that route. With no real software to do this for you this is the best route. Your logging software should be able to group stuff together and go that route.
I may be able to get something together that will make this easier after my finals this and next week. Something to at least make the library useful. Shouldn’t be too hard to make an M2 logger that can make a spread sheet importable data file (.CSV). Then you just drop the CSV into your favorite spreadsheet program and sort them.
I have to reference my materials to decode the data structure then create the lines with that structure in place and go from there.
MAY be able to write to the SDcard as well but haven’t played with that yet.
Rodney
I will have a busy week this week as I prepare for my last final exam which is a group presentation. Once I am done with that I will try to build a logger that writes to the SDcard which should allow for VPW stuff to be loaded into a spread sheet. This should help with figuring out commands since you can then import into a spread sheet and sort through the data. That will be as far as I go with this for now until I complete some other stuff I will be working on. Want to get the ELM327 stuff working on the current setup and possibly get BT and WIFi working. Once that is completed then I will try to integrate J1850VPW into it and so on.
Rodney
Is anybody here working on the j1850 PWM implementation?
I don’t believe anyone currently is. I plan to but have a bunch of other stuff to accomplish first.
Hey all. I tried the M2 sketch for J1850 VPW, but had no luck communicating with a PCM. The PCM is otherwise accessible via ELM, etc.
Can anyone please confirm if they were able to get the library working (the one posted at https://github.com/redheadedrod/j1850 - if so, were any changes necessary to get it working? Thx.
Works fine as is. What PCM are you using? I have a lab right now using a 12200411 PCM which it connects to quite easily. Depending on what your using you MAY need a wake up code to be sent which software for the ELM generally does.
If you look in the examples there is basically a serial terminal that sends a code out and receives it printing what it receives.
In examples you want to run “J1850_M2_v1.ino”
I did this just now and I get this from my “411”
TX: 48 69 2D 4D 32 21 CC
RX: 88 83 10 0A 00 00 EB
TX: 48 69 2D 4D 32 21 CC
RX: 88 83 10 0A 00 00 EB
TX: 48 69 2D 4D 32 21 CC
RX: 88 83 10 0A 00 00 EB
TX: 48 69 2D 4D 32 21 CC
RX: E8 FF 10 03 B3
TX: 48 69 2D 4D 32 21 CC
RX: 88 83 10 0A 00 00 EB
TX: 48 69 2D 4D 32 21 CC
RX: E8 FF 40 03 ED
TX: 48 69 2D 4D 32 21 CC
RX: 88 83 10 0A 00 00 EB
TX: 48 69 2D 4D 32 21 CC
RX: 88 83 10 0A 00 00 EB
TX: 48 69 2D 4D 32 21 CC
RX: 88 83 10 0A 00 00 EB
TX: 48 69 2D 4D 32 21 CC
RX: E8 FF 10 03 B3
TX: 48 69 2D 4D 32 21 CC
RX: 88 83 10 0A 00 00 EB
TX: 48 69 2D 4D 32 21 CC
RX: E8 FF 40 03 ED
TX: 48 69 2D 4D 32 21 CC
RX: 88 83 10 0A 00 00 EB
TX: 48 69 2D 4D 32 21 CC
RX: 88 83 10 0A 00 00 EB
TX: 48 69 2D 4D 32 21 CC
RX: 88 83 10 0A 00 00 EB
TX: 48 69 2D 4D 32 21 CC
RX: E8 FF 10 03 B3
Please note that this library will be re-written in the coming months with the intent of being integrated with M2RET and total ELM/STN compatibility. Also intend to be compatible with the new PCM flash software being worked on. I hope to embed the PCM flashing configuration within the M2 for those desiring that capability. It will be an optional add on over the top of J1850VPW
1 Like
Thanks for the quick reply. I’m bench testing it with an ebay PCM from a 2004 Chevy Astro 12586243. As mentioned before, no problems communicating with it using other adapters (ELM, OBDLink LX) via J1850 VPW on torque, etc.
I was excited to play with J1850_M2_v1.ino but unfortunately I only see a “TX: …” message, but never an “RX” reply in the serial monitor.
I was just making sure there were no missing steps, whether hardware on the M2, or software tweaks to get the sketch to run. Not sure about the wakeup you mention and whether it is required for J1850 VPW. I’ll go back and check my work…
All I can tell you is that it has worked with anything I have tested it with so far. Make sure both of your grounds on the port are connected together to a ground on the PCM. Make sure you have 12 volts going to the PCM and DLC port and make sure you have one of the data lines connected between the two. I wouldn’t hook up both of the PCM lines as it might confuse the PCM since generally it appears one is to connect directly to the BCM and the other connects directly to whatever else is in the driveline assuming your PCM has 2 datalines.
I haven’t taken it out to my truck to test which would be more in line with your PCM but should work fine. Others have tested it and it works well so I am not sure what to tell you?
If you have an ODBII Y cable try using that to connect both your ELM and your M2 and see what you see. You may find it chats just fine. The ELM with software may be giving the proper wake up command to get a response.
Got it! Thanks for sticking with me on this. I made a noob mistake where I only had OBD pin 4 (chassis) grounded, but needed to ground pin 5 (signal) as well, and then it started working. I’m guessing a lot of adapters tie 4+5 together (for better or worse), which masked the issue I was having. It’s getting good responses back, about 25ms “round trip” for a mode 01 PID request/response.
Glad to have helped. Yes for benchtop work the DLC should have both grounds connected together. Some adapters only use one ground and ignore the other and other configurations. But you can’t go wrong if you tie them together for a benchtop setup.
Pin 4 would be considered a “Chassie” type of ground. Pin 5 would be considered a “Signal or Data” ground directly from the Pcm. In a lot of cases pin 4 alone will work but some vehicles use a discrete grounding method on the data port connector where pin 4 and 16 are designed to feed the device power and pin 5 is intended to be used as the ground for data communication.
There is also nothing wrong with connecting pin 4 and 5 together. Glad you got it working.
Hello dmaxben,
I am messing around with the HUD and DIC in my '08 Vette - got some things to work, others not.
I do not have onstar to reverse engineer and Us-Chevys are hard to come by in this part of the world ^^
Could you share some of the details of the DIC communication? PM me if you want!
Regards,
Funky Luke
Hi Funky Luke! I am just starting to investigate hacking the HUD in my '08 Cadillac XLR which is based on the 'Vette. Any (an all) information you could share with me would be SO appreciated. What I eventually want to do is send messages like the ones displayed when you change XM stations. My hope is to bridge between the iDataLink Maestro interface on an aftermarket radio and my existing HUD. I’m planning to get a HUD to play with on the bench rather than risk bricking the car. Since you have some things working, I’d really like to get a head start with your progress.
Bob
Hello MPRCTCL,
Nice to hear that somebody else is on this.
What I got is all the codes needed to display the audio screens on the HUD - FM, AM, XM, CD, DAB etc. including the frequencies.
What I haven’t figured out as of now is the nav screens. I got an original NAV unit on the bench and a bus trace of some nav turn instructions on the hud. But i’m not yet able to reproduce them. I used a ELM327 unit for my original research but switched to the macchina since the GM J1850 implementation does use non-standard (too long) frames that can not be sent with standard interfaces.
I will try to put something together on gdocs to share the details.
Outstanding! Looking forward to hearing more.
Does anyone have an update with regards to the J1850 PWM protocol. I have 2 ford ranger electric vehicles from 1998 and 1999 and they communicate on this bus. It would be nice to be able to use the macchina to decode and read the bus communciations. And one day simulate the modules that are no longer available.
I was actually working on my own J1850 VPW implementation with my '99 Suburban, but am in the process of finding a PWM vehicle to use to consolidate the two into one library. I haven’t done any PWM work yet but I do have a lot of the SAE documents for the implementation, including the full 4 page writeup on the protocols. If I get any work done on the PWM side, I’ll let you know.
Edit: side note; I was considering using my Tech2 to possibly add some support for the extended PIDs I can access. That said, as far as I know the PIDs are/can be different for each different vehicle or model year. I’ll see once I get to that point. As of now I’ve been having trouble communicating with my trucks’ PCM due to some ground issues that I’m still hunting down. (darn project vehicles!)
I would be willing to do any testing. I can test with a macchina, but I also have an ELM327 and lists of commands and responces on the bus, and a ford star NGS tester for the ranger EV, which communicates to the modules.