pcmhacking.net

NSFW wrote:

kur4o wrote:Here is some logs and a file with some commands to control pcm. It can give you a better understanding about how to set ip up.

Setting up is the channels is the trickiest part. You need a list of all the pids the pcm supports, if you request non-supported pid the pcm gives an error.
And than there is some priority byte that is not fully understood. Mimic the commands set from the logs can prove it works reliable.

Thanks, that looks very helpful! The logs show a mode $10 message at the start of the logging session, which might be the key thing I've been missing. I'm going to try that plus some different DPID IDs and see if streaming will work.

Mode 10 is disable faults or something along those lines off the top of my head?

Going through the logs we have multiple dynamic requests, first one being:
6C 10 F1 2C F6 4A 11 42 11 52
2C - Mode
FE - DPID Table that PIDs are loaded into
4A - 01001010, therefore 01 is used PID, 001 is start at byte 1, 010 is get 2 bytes
1142 - PID 1142
1152 - PID 1152

Each byte will be 1 byte response.

Once all the DPIDs have been filled with all data if interest:

6C 10 F1 2A 14 F6 F7 F9 FA
6C F1 10 7F 2A 14 F6 F7 F9 FA 23
6C 10 F1 2A 24 FB FC FD FE

First frame requests to begin live data (0x2A), the timer priority is 0x14 and to run DPIDs F6,F7,F9 and FA.
Next frame actually says "Failed" with a 7F response, but this seems to be normal in alot of VPW based ecus.. even though its successful.
Final frame requests to begin live data (0x2A), timer priority is 0x24 and to run DPIDs FB,FC,FD and FE.

The priority is basically a timer, you can only have so many loaded on each timer which is why they are split over two.

This is genuinely interesting. How'd you figure this out? lol. I thought they were PIDs.

So you're saying there's a different mode I should use to request the single PID from the ABS module instead of building a DPID list with 1 PID lol.

jlvaldez wrote:This is genuinely interesting. How'd you figure this out? lol. I thought they were PIDs.

So you're saying there's a different mode I should use to request the single PID from the ABS module instead of building a DPID list with 1 PID lol.

Yes correct!

I actually had the user Jayme on here explain it to me in one of my other threads. I was reverse engineering the tech2 frames for the engine computer which does exactly the same as your ABS module.

Bug check ...

Open PcmHammer015-B-Preview.
If not already done, select your device and OK out.

Now that your device is selected.

Open the 'Select Device' dialog.
Select: Cancel

Then select anything from the Operations box or the Tools menu.

got the chance to try it out with the MDI2 tonight. Full read and test write worked great

Excellent!

Thank you!

I've updated the zip file in the first post. Please give it a try!

The same code that's in the zip file has been submitted to the Windows app store as "PCM Hammer (Beta)" and "PCM Logger (Beta)"

If they work well for everyone else too, I'll resubmit them without the "Beta" part.