================================================== ===================

EDIT: Release 12 is now obsolete, please use the latest release in the future.

================================================== ===================

Open source LS1 tuning just took another small step forward.

Improvements in this release:

• Full writes for the P59 PCMs (aka 1mb PCMs) are now supported.
• Write Parameters (Clone) works again.
• The most frequently used features (Read Properties, Test Write, Write) still have buttons on the main window, however other operations have been moved to a Tools menu at the top of the window.
• You'll also find an Options menu that lets you enable and disable 4x communications. You'll probably want to leave that checked, but some vehicles have modules that send 1x messages during 4x communication, which interrupts reads and writes. Disabling 4x should work around that problem.
• And a few minor bug fixes.

There's just one known issue in this release: Non-ELM devices will report retry counts after a read or write operation. This slow things down a little bit, and we're looking into a solution.

To get the zip file, go here...
https://github.com/LegacyNsfw/PcmHacks/releases
...click "Assets" at the bottom of the release description, and click the zip file.

Extract the zip file to your hard drive, and have fun.

If you're not familiar with PCM Hammer, you might want to read this:
https://github.com/LegacyNsfw/PcmHacks/wiki

 

Thanks for all the hard work that has gone in to this. It has been working great for me on PO1 pcms. I have a P59 that im going to try now that full write is supported!!

 

Thanks for all the hard work

 

Hello,

Maybe I'm doing something wrong but it indicates something to the effect that its "Not yet supported" when I chose an OBDLink Bluetooth device in the pull down. Do I need to change something?

Many thanks,

Rick

 

Which ObdLink device do you have? Does ObdLink's software communicate with the device?

I have their Scantool LX, and I've had some trouble getting the bluetooth part working. I have to go through the pairing process periodically, and now my laptop thinks ir has fourbluetooth COM ports, but once I get the device talking to the laptop, it works just fine.

 

Hello,

It is the OBDLink MX+. I never get to the point of PCM Hammer trying to reach out to the MX+ device. And I now see that the MX devices are mentioned in the Help as not supported. Reading is fundamental and I should have looked around a little harder before asking.

Rick

 

No worries. The quirks of all of the different devices on the market are a headache for everyone.

Unless you're in a big hurry, it might be best to just wait for the device that Pete160 and Tazzi are working on. I've tested a couple of prototypes and they're impressive, much faster than any of the ObdLink devices. I don't know when they will be available, but the latest iteration looks really good so I suspect it won't be much longer.

 

I keep getting this

 

I've seen that once or twice but it has always just gone away after retrying.

My only guess is that 12.2 volts might be a little too low. That's just a guess, but if I remember right my desk power supply is around 13 volts, and I don't think I've encountered this in my car.

 

Thats on a bench harness that I use daily but I know some programs are more voltage sensitive than others. I tried it several times with same result. I will see if any of my other power supply's have more voltage, I though it used to have 13v but could be wrong.

 

I tried with 11.8 volts yesterday, and the flash worked, so I agree that voltage is probably not the issue.

Would you mind searching the Debug pane for "Uploading kernel to PCM" and copy/paste that line plus the next 20 lines or so? I think we'll see something like...

[07:06:36:474] TX: 6C 10 F0 34 00 10 00 FF 80 00
[07:06:37:129] RX: 6C F0 10 7F 34 00...

...where the "34" in the transmitted message means "please let us write some data to RAM" and the "7F 34" in the received message means the PCM refused.

The Results pane shows the seed/key unlock step working, and that's the step that fails for "locked" PCMs. Usually after the PCM unlocks it will happily accept every request we send it, but not this time, which is weird. Are there any wheel / transmission / crank / cam sensor signals in your bench harness? If the PCM sees those, that might cause this sort of thing.

Also if you have another PCM to test with, that could be interesting.

 

I flashed pcm with stock file with hpt and tried again. going to try a different pcm in a min.

 

same error with different pcm

 

Interesting. Thanks for the debug log, and thanks for trying a different PCM.

I'm stumped.

 

Antus & Tazzi have a theory that the PCM might have some trouble codes set, and that could be causing this.

If you power on the PCM and then press the "Halt Kernel" button (yes, even though there's nothing to halt) that will send a "clear codes" message to the PCM.
Then see if you can reflash.
If that doesn't work, try it again but power-cycle the PCM after you click the halt button.
If that doesn't work, try the same thing but power it off in two steps: first turn off the key, then wait a few seconds and turn off all power. I think that's required for a VIN change, and it might be required in this case as well. But I think there's a good chance that you won't have to power cycle it at all.

If this does work without power-cycling, we'll just have the next version of the app send a "clear codes" message before we start reflashing.

 

Same result...tried different pcm and different laptop. I been using a mongoose cable, may try my cardaq 2 later this week.

 

Bummer. Thanks for trying.

 

Release 14 is out now, and I've started a new thread:

https://ls1tech.com/forums/pcm-diagn...l#post20236012