Trying to tune 04 monte carlo ss

[Professwrx]

Can anybody help me figure out if I'm missing hardware or having a more fun problem.

I have an OBDXpro VT that easily connects to my 04 tahoe. I thought it could also read my Monte PCM, but PCM hammer attempts to get the VIN and times out.

Is this hardware even compatible? I used to use a DHP 10 years ago, but I no longer have the hardware.

Can somebody hold my hand a bit?

If it should connect, I'm wondering if I have a BCM issue, but an ELM can read out data to my phone. I don't have cruise control and my power door locks don't unlock, but they will lock. Not sure if it's BCM caused or other issues. I just bought the car 3 days ago.

[kur4o]

Latest beta of pcmhammer should be able to read 04 monte pcm, unless it is some odd ball year change.
Do you have a vin or pic of the pcm.

[Professwrx]

Latest beta of pcmhammer should be able to read 04 monte pcm, unless it is some odd ball year change.
Do you have a vin or pic of the pcm.

How do I get the beta? I have the last release but I saw some new work done for it.

I don’t even know where the pcm is. I haven’t looked for it but I know it’s not in the air box like my gtp.

[kur4o]

It might be some newer pcm being used. Do you have a vin to check p/n.

For latest release check pcmhacking.net

[Professwrx]

It might be some newer pcm being used. Do you have a vin to check p/n.

For latest release check pcmhacking.net

2g1wz121049342922

[Professwrx]

I looked around pcm hacking but didn’t see any beta work. Only release 021 which I have already.

im not that familiar with the site and I’m on my phone so I could have easily missed it if it’s there.

[TriumphR3]

PCM location:
It is mounted in the bottom of the actual air box assembly. The airbox will come apart in two places. The front comes off to service the air filter. It also will come apart in the middle so that you can gain access to the PCM.

[kur4o]

Looks like some connection issue, or obdx cable issue.

To diagnose you will need some other type of software called Universal Patcher.

Use the built in logger and check you got any response. Try the dtc tab to see if there is any communication. If bcm freaks out it can spam bus with some long string piece of crap data that makes communication real hard. You can also start pulling fuses to silence other modules, and see if that helps.

[Professwrx]

Looks like some connection issue, or obdx cable issue.

To diagnose you will need some other type of software called Universal Patcher.

Use the built in logger and check you got any response. Try the dtc tab to see if there is any communication. If bcm freaks out it can spam bus with some long string piece of crap data that makes communication real hard. You can also start pulling fuses to silence other modules, and see if that helps.
It connected at a basic level


Connecting (VPW)...
Connection failed. Check settings
Connecting (VPW)...
Connection failed. Check settings
Connecting (VPW)...
Protocol2 have connection from client
J2534 client initializing...
Initializing J2534 Device
J2534 client: Device initialization complete.
Connected to the device, ID: 1
Connected protocol: J1850VPW Speed: ISO14230
Removing all filters
Device initialization complete.
Versions: Firmware: L*?s, DLL: ", Api: L*?s
Battery Voltage is: 12.585
Start logging...
No profile configured
Requesting DTC codes for [10] PCM
Done
Requesting DTC codes for [10] PCM
Done
VIN Code:2G1WZ121049342922
Waiting for devices... [Done]
Waiting for devices... [Done]
Querying modules..J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
.J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
Requesting DTC codes for [10] PCM
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
Done
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
.Requesting DTC codes for [10] PCM
Done
....Requesting DTC codes for [10] PCM
Done
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
No respond to Query devices message
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
.J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
.J2534 client Message sent fail.
J2534 WriteMsgs error: ERR_FAILED ()
J2534 client Message sent fail.

[Professwrx]

[09:58:24:767] PCM Hammer 021
[09:58:24:767] Tuesday, October 03 2023 @09:58:24:76
[09:58:24:767] Initializing J2534 Device
[09:58:24:767] DLL already loaded, unloading before proceeding
[09:58:24:767] Existing DLL successfully unloaded.
[09:58:24:767] Loaded DLL
[09:58:25:485] Connected to the device.
[09:58:25:501] Battery Voltage is: 12.531
[09:58:25:532] Protocol Set
[09:58:25:548] Device initialization complete.
[09:58:28:157] TX: 6C 10 F0 3C 01
[09:58:30:252] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:58:30:255] VIN query failed: Timeout
[09:58:30:309] J2534 setting VPW 4X
[09:58:30:382] TX: 6C 10 F0 20
[09:58:30:403] J2534 setting VPW 1X
[09:58:30:448] TX: 6C 10 F0 20
[09:59:03:956] Will save to C:\Users\ScottAnderson\Desktop\g.bin
[09:59:06:164] Querying operating system of current PCM.
[09:59:06:231] TX: 6C 10 F0 3C 0A
[09:59:08:283] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:08:289] Sending 'test device present' notification.
[09:59:08:289] TX: 8C FE F0 3F
[09:59:10:327] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:10:328] Sending 'test device present' notification.
[09:59:10:330] TX: 8C FE F0 3F
[09:59:12:367] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:12:368] Sending 'test device present' notification.
[09:59:12:368] TX: 8C FE F0 3F
[09:59:14:406] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:14:407] Sending 'test device present' notification.
[09:59:14:408] TX: 8C FE F0 3F
[09:59:16:447] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:16:448] Receive timed out. Attempt #5, Timeout #5.
[09:59:16:449] TX: 6C 10 F0 3C 0A
[09:59:18:488] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:18:489] Sending 'test device present' notification.
[09:59:18:489] TX: 8C FE F0 3F
[09:59:20:529] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:20:529] Sending 'test device present' notification.
[09:59:20:530] TX: 8C FE F0 3F
[09:59:22:568] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:22:569] Sending 'test device present' notification.
[09:59:22:570] TX: 8C FE F0 3F
[09:59:24:608] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:24:610] Sending 'test device present' notification.
[09:59:24:610] TX: 8C FE F0 3F
[09:59:26:641] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:26:641] Receive timed out. Attempt #5, Timeout #5.
[09:59:26:641] Operating system query failed, will retry: Error
[09:59:26:688] J2534 setting VPW 4X
[09:59:26:751] TX: 6C 10 F0 20
[09:59:26:782] J2534 setting VPW 1X
[09:59:26:829] TX: 6C 10 F0 20
[09:59:26:891] TX: 6C 10 F0 3C 0A
[09:59:28:929] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:28:944] Sending 'test device present' notification.
[09:59:28:960] TX: 8C FE F0 3F
[09:59:31:029] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:31:029] Sending 'test device present' notification.
[09:59:31:044] TX: 8C FE F0 3F
[09:59:33:094] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:33:110] Sending 'test device present' notification.
[09:59:33:125] TX: 8C FE F0 3F
[09:59:35:195] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:35:196] Sending 'test device present' notification.
[09:59:35:212] TX: 8C FE F0 3F
[09:59:37:259] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:37:275] Receive timed out. Attempt #5, Timeout #5.
[09:59:37:290] TX: 6C 10 F0 3C 0A
[09:59:39:358] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:39:369] Sending 'test device present' notification.
[09:59:39:369] TX: 8C FE F0 3F
[09:59:41:420] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:41:435] Sending 'test device present' notification.
[09:59:41:435] TX: 8C FE F0 3F
[09:59:43:495] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:43:499] Sending 'test device present' notification.
[09:59:43:499] TX: 8C FE F0 3F
[09:59:45:558] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:45:573] Sending 'test device present' notification.
[09:59:45:573] TX: 8C FE F0 3F
[09:59:47:620] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:47:636] Receive timed out. Attempt #5, Timeout #5.
[09:59:47:636] Operating system query failed: Error
[09:59:47:652] Unable to get operating system ID. Will assume this can be unlocked with the default seed/key algorithm.
[09:59:47:652] Sending 'test device present' notification.
[09:59:47:667] TX: 8C FE F0 3F
[09:59:54:066] Sending 'test device present' notification.
[09:59:54:081] TX: 8C FE F0 3F
[09:59:54:128] Using OsID: 0
[09:59:54:128] Suppressing VPW chatter.
[09:59:54:144] TX: 6C FE F0 28 00
[09:59:54:175] Sending 'test device present' notification.
[09:59:54:191] TX: 8C FE F0 3F
[09:59:56:261] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:56:429] Sending seed request.
[09:59:56:444] TX: 6C 10 F0 27 01
[09:59:58:514] ReadMsgs OBDError: ERR_BUFFER_EMPTY
[09:59:58:516] No response to seed request.
[09:59:58:516] Unlock was not successful.

[kur4o]

Communication looks good. At least it gets VIN query.
When connected with Universal patcher, you can go to vpw console tab, check screen checkbox and uncheck buffered checkbox. It will log idle traffic and you can run some communication tests,

Than send [use enter for sending]

6c fe f0 20

and in a while

6c fe f0 28 01



I suspect there is some timing issues with obxpro device.
Go to settings tab ->timeouts and play with this setting.

TimeoutJ2534Write from 0 to 100 in 10 increment.

[Professwrx]

Communication looks good. At least it gets VIN query.
When connected with Universal patcher, you can go to vpw console tab, check screen checkbox and uncheck buffered checkbox. It will log idle traffic and you can run some communication tests,

Than send [use enter for sending]

6c fe f0 20

and in a while

6c fe f0 28 01



I suspect there is some timing issues with obxpro device.
Go to settings tab ->timeouts and play with this setting.

TimeoutJ2534Write from 0 to 100 in 10 increment.



6C FE F0 20 looks like it resets the dash and probably restarts the PCM?
[13:28:22.516] 6C FE F0 20
[13:28:22.534] 6C F0 10 60
[13:28:22.575] 6C F0 40 60
[13:28:22.613] 6C F0 58 60
[13:28:22.646] 6C F0 28 60
[13:28:22.684] 6C F0 60 60
[13:28:22.719] 6C F0 61 60
[13:28:22.756] 6C F0 80 60
[13:28:22.792] 6C F0 89 60
[13:28:22.817] 6C F0 99 60
[13:28:22.846] 28 FF 40 06 07 0B 0B
[13:28:22.873] C8 7B 60 01 00 CA FB 19
[13:28:22.910] 28 FF 40 06 07 0B 0B
[13:28:22.949] A8 33 60 05
[13:28:22.984] 28 93 40 01 FF FF



6C FE F0 28 01 seems to do nothing

[13:27:22.125] 6C FE F0 28 01
[13:27:22.158] 6C F0 99 7F 28 01 12
[13:27:22.181] 6C F0 40 7F 28 01 12
[13:27:22.201] 6C F0 10 7F 28 01 12
[13:27:22.220] 6C F0 58 7F 28 01 12
[13:27:22.243] 6C F0 28 7F 28 01 12
[13:27:22.264] 6C F0 60 7F 28 01 12
[13:27:22.284] 6C F0 80 7F 28 01 12
[13:27:22.302] 6C F0 61 7F 28 01 12
[13:27:22.322] 6C F0 89 7F 28 01 12
[

[kur4o]

Try
6C FE F0 28 00

Look for 5 seconds silence after command being send.

After you connect you can go to vpw console tab->upload script->select attached file

[Professwrx]

Try
6C FE F0 28 00

Look for 5 seconds silence after command being send.

After you connect you can go to vpw console tab->upload script->select attached file
saw 5 seconds silence

looks like its dumping code in blocks with the script

I saved that as bin file. Is that my entire PCM content? That's incredible man.
it's only 192kb. Tiny tuner can't open it.

[kur4o]

Can you save the full dump for diagnosis. Looks like some blocks are missing and at some point it lost communication. Some timing adjustments may be needed. Size should be 512kb,
On another note tinytuner database is fully integrated in universal patcher tuner section, so you can tune from there.

[Professwrx]

Can you save the full dump for diagnosis. Looks like some blocks are missing and at some point it lost communication. Some timing adjustments may be needed. Size should be 512kb,
On another note tinytuner database is fully integrated in universal patcher tuner section, so you can tune from there.

Ah, I wondered if it was a trial read of a smaller set of blocks or if I missed some. File attached. I will attempt another read as soon as I can.

Definitely possible that the cable was loosened. I can't find my better usb cable for the obdx so the one I'm using is only 12" and loose.

What other databases are in your program??! Your work is amazing.

[Professwrx]

looking at the log, to my amateur eyes it looks like it send another request but received nothing back after 07 F0 00 <-- is that the address of the next data block requested? I've done some in depth disassembly so I'm not completely oblivious.

[kur4o]

07 F0 00 is the address of last block. I suspect the communication dropped earlier than that point. The usb cable might be one of the reason.

When you do more testing can you save all the bus messages in vpw console. It will help alot where it fails and what needs to be optimized.

Universal patcher have support for ls1 calibration, and most v6 FWD, and covers lots of gm pcm for DTC editing and checksums, some limited tuning available for e38.

[Professwrx]

07 F0 00 is the address of last block. I suspect the communication dropped earlier than that point. The usb cable might be one of the reason.

When you do more testing can you save all the bus messages in vpw console. It will help alot where it fails and what needs to be optimized.

Universal patcher have support for ls1 calibration, and most v6 FWD, and covers lots of gm pcm for DTC editing and checksums, some limited tuning available for e38.

Here's the VPW console stuff from that.

I'm going to make a second attempt right now.

[Professwrx]

Here's the VPW console stuff from that.

I'm going to make a second attempt right now.

This second attempt was an obvious fail. Didn't make the file at all.

[Professwrx]

This second attempt was an obvious fail. Didn't make the file at all.

This one got further, but still failed. I accidently saved it in a weird place again. Searching on windows 8 is impossible for me so I have no idea where the files are, but I don't think it matters

[Professwrx]

This also looks like after the app gets spooked, the communication continues and it dumps the remaining blocks after.

When this is happening the guages reset and it stops and wants to save, but it's definitely before the end of the data stream. Somewhere in the 02 80 00 area. Then I notice the data come through significantly faster. These attempts are very slow data transfers. Each block takes 5 seconds or so. Not sure what's normal.

[kur4o]

First and last log does seem complete. On first at some point timestamps get lost, by any chance you have unchecked the timestamp checkbox mid script. Last log don`t have timestamps at all and is also complete. Does the bin saved in full 512kb and can be opened in tuner.

The communication looks solid now. Now we need to debug why it fails with pcmhammer.

On the 2 failed logs I think script file got messed somehow. If you have done some modification to it, it might lost some encoding and the program can`t read it.

[Professwrx]

First and last log does seem complete. On first at some point timestamps get lost, by any chance you have unchecked the timestamp checkbox mid script. Last log don`t have timestamps at all and is also complete. Does the bin saved in full 512kb and can be opened in tuner.

The communication looks solid now. Now we need to debug why it fails with pcmhammer.

On the 2 failed logs I think script file got messed somehow. If you have done some modification to it, it might lost some encoding and the program can`t read it.
I'll try again with the timestamp back on. Not sure why I turned it off, but I did uncheck it. I cannot find the files saved from those logs. I don't know if they saved at all.

I definitely didn't modify the script, I wouldn't know what I'm doing at all.

[Professwrx]

I'll try again with the timestamp back on. Not sure why I turned it off, but I did uncheck it. I cannot find the files saved from those logs. I don't know if they saved at all.

I definitely didn't modify the script, I wouldn't know what I'm doing at all.

I got it! Thanks!

Now... how do I upload and since this has been experimental and temperamental should I worry about an issue happening and bricking the PCM?

[kur4o]

Uploading is a bit tricky, It is easy to make a script, but there is no error detection and retries.

Great news is pcmhammer beta is finally released. It have been tested really well, but it is still a beta so use on your own risk. I think getting a spare pcm from ebay will be 20-40$ and will get you a piece of mind if something bad happens.

Here is the link

https://pcmhacking.net/forums/viewtopic.php?f=4&t=8008&p=124498#p124498

[Professwrx]

Uploading is a bit tricky, It is easy to make a script, but there is no error detection and retries.

Great news is pcmhammer beta is finally released. It have been tested really well, but it is still a beta so use on your own risk. I think getting a spare pcm from ebay will be 20-40$ and will get you a piece of mind if something bad happens.

Here is the link

https://pcmhacking.net/forums/viewtopic.php?f=4&t=8008&p=124498#p124498

wow, that is some shocking timing for that to be released!!
thanks for everything you’ve done man.
time to order a back up PCM for sure.

[Professwrx]

Ok, so I put in a new PCM with the same part number, but I'm having the same issue with PCM hammer. It doesn't recognize it at all. YFXS is the code on this new PCM. I can't get the logger to see any chatter. I can't pull any codes from it. It might be completely dead or there's a major step I'm not aware of.

[Professwrx]

PCM hammer beta does not work for my car. I was able to get my account set up on PCMhacking so I posted there. Hopefully this can be sorted shortly. Stock driveability is lacking.