PCM Hammer Release 014

[aaronc7 Profile]

Some cars get a ton of errors, like mine (C5 corvette). Although write seems to be OK, Read is just tons of errors/interruptions.

[Gampy Profile]

GeoNV,

Thank you!

You might want to juice up the battery voltage a bit ...

FYI, A debug log has everything the results log has plus more, so a debug log is a better log to post.

That log has some weird things going on in it ...

[06:17:01:452] Address % Done Time Remaining
[06:17:02:484] 0x000000 0% Measuring read speed...
[06:17:04:532] Elm ID:
[06:17:04:547] 0x000400 0% Measuring read speed...
[06:17:05:610] 0x000800 0% Measuring read speed...
[06:17:06:767] 0x000C00 0% Measuring read speed...
[06:17:07:829] 0x001000 0% Measuring read speed...
[06:17:08:908] 0x001400 0% Measuring read speed...
[06:17:09:986] 0x001800 0% Measuring read speed...
[06:17:11:190] 0x001C00 0% Measuring read speed...
[06:17:12:237] 0x002000 0% 22:41
[06:17:13:284] 0x002400 0% 22:07
[06:17:14:331] 0x002800 0% 21:41
[06:17:15:769] All Pro ID:
[06:17:15:784] 0x002C00 1% 21:54
[06:17:16:847] 0x003000 1% 21:33
[06:17:17:941] 0x003400 1% 21:18
[06:17:19:051] 0x003800 1% 21:05
[06:17:20:176] 0x003C00 1% 20:55
[06:17:21:286] 0x004000 1% 20:46
[06:17:22:395] 0x004400 1% 20:37
[06:17:23:458] 0x004800 1% 20:27
[06:17:24:584] 0x004C00 1% 20:20
[06:17:25:678] 0x005000 1% 20:13
[06:17:27:007] All Pro self test result:
[06:17:27:023] 0x005400 2% 20:18
[06:17:28:086] 0x005800 2% 20:11
[06:17:29:212] 0x005C00 2% 20:05
[06:17:30:291] 0x006000 2% 19:59
[06:17:31:525] 0x006400 2% 19:59
[06:17:32:603] 0x006800 2% 19:53
[06:17:33:781] 0x006C00 2% 19:52
[06:17:34:860] 0x007000 2% 19:47
[06:17:35:985] 0x007400 2% 19:43
[06:17:38:946] All Pro firmware:
[06:17:38:977] 0x007800 2% 20:41

No, it does not say not to do it in vehicle anywhere ... It is perfectly fine to do in vehicle ... However, it is safer on the bench where there is less likely hood of external interference.

If you're going to do either a "Write OS, Callibration & Boot" or "Write Full Flash (Clone)" (i.e. OS swap),
1. Pay close attention to the kernel upload ... if it has errors (retries), question it!
2. ALWAYS do a Test Write, if it has errors (retries), question it!

Otherwise it's pretty darn safe, a failed "Write Calibration" is most likely recoverable.

[GeoNV Profile]

GeoNV,

Thank you!

You might want to juice up the battery voltage a bit ...

FYI, A debug log has everything the results log has plus more, so a debug log is a better log to post.

That log has some weird things going on in it ...

I used a OBD2link Lx. I think that's why it kept jumping between different device names.

I'll definitely be making a bench harness for it- I used to tune my 1995 Fbody LT1 and had so many near panic moments flashing it that I'll never be the same...

Looks like it loaded into Tunerpro OK as far as I can tell- the values for the tables I'm interested in all look correct. I'll do a debug log next time around. Sweet software. So nice to find this!

[Gampy Profile]

The LX should work just fine, I do believe one of the developers (NSFW) uses one.

There should be no spurious log entries like that ... I don't see how it could even be possible.

As long as your XDF is a 12587603 xdf it should work fine.

-Enjoy

[GeoNV Profile]

I built a bench harness after a quick run to the junkyard and cloned my pcm onto it, then wrote a few changes to shift points and test wrote it and then wrote it. looks like it worked fine! I've attached the logs.

[Gampy Profile]

Awesome, Looks good ...

[GeoNV Profile]

The LX should work just fine, I do believe one of the developers (NSFW) uses one.

There should be no spurious log entries like that ... I don't see how it could even be possible.

As long as your XDF is a 12587603 xdf it should work fine.

-Enjoy

I even used one by NSFW! using the same xdf on the bench harness it didn't have any issues at all. Not sure what was up with the first one!

[Gampy Profile]

The XDF is used by TunerPro not PcmHammer.

PcmHammer just writes/reads a binary blob to/from the Pcm through the tool.

The XDF describes where in that binary blob the Parameters are. That is how TunerPro knows where they are.

[GeoNV Profile]

hah! sorry for the confusion. Never good to let people get a glimpse of the chaos of our own minds...

Alright, just wrote wrote a tune to the truck while it was onboard- I think the issues i was having were due to the tablet computer I was using- a Dell Venue 11 Pro. I wrote it this time from a laptop and didn't have too many weird error messages. attached both the log and debug log. Also thought I could have been getting issues from having PCMHammer deep in the documents folder- I know some software gets picky about character length- so moved it to the C drive.

[MudDuck514 Profile]

hah! sorry for the confusion. Never good to let people get a glimpse of the chaos of our own minds...

Alright, just wrote wrote a tune to the truck while it was onboard- I think the issues i was having were due to the tablet computer I was using- a Dell Venue 11 Pro. I wrote it this time from a laptop and didn't have too many weird error messages. attached both the log and debug log. Also thought I could have been getting issues from having PCMHammer deep in the documents folder- I know some software gets picky about character length- so moved it to the C drive.

Hi all,

GeoNV,

Pity that the Dell Tablet doesn't seem to work correctly - I was considering purchasing a Venue 8 Pro to do exactly what you were trying to do!

Oh well, guess I'll pass on that for now.

Mike