2006 P59 XDF Files Inside

[josh420710]

I went to flash my truck today and I got this error. has anyone encountered this before? I'm using OBD link ex cable, pcm says this scan tool device is not supported we're going to default to very small package sizes which will make everything slow but at least it'll probably work. I've flashed before with the same setup im using. I checked all file checksums those are all good. Idk what to do here.

[antus]

Cant see the voltage in any of that but its usually because the hardware couldnt do it because of low voltage or electrical interfearance. Check your power supply is quality and battery voltage is above 12.5.

[josh420710]

Okay next time I do it I'll make sure I get the voltage in there and should I keep on using this ex cable or should I upgrade to the obdlink pro VX?

[antus]

I would upgrade, xpro is a lot faster and more reliable. And if you buy it through this link it helps support the site and pcmhammer. https://obdxpro.com/?ref=pcmhacking

[AngelMarc]

Idk what to do here.

Press the windows key and type "snipping tool".

Capture.PNG

Your welcome.

[josh420710]

So i attempted to do the flash today with the obdxpro vx and this is what I got now. I haven't had a problem up until now. All checksums are good with the bin. The only thing I did different from before me post on the forms when I had it work successfully I used tuner pro and pcm hammer with the matching xdf, this bin I've been trying to flash is edited through universal patcher and using pcm hammer. I used universal patcher this time because it what a little more straight forward then tuner pro. Could this be my issue even though my checksums for the bin check good?

[antus]

Something is very wrong with your interface or bench wiring. Errors galore. You should not see response truncated, kernel version should not be all 0000000 and neither should the chip id.

If you are trying to flash in car you likely have something like an after market stereo or a bad module that is mashing the communications. Sometimes people find unplugging an aftermarket stereo or pulling some fuses can solve it. But it takes time to try everything and is safter to bench flash anyway, so that is always recommended.

Dont proceed like that, you are almost certainly going to brick with so many data errors if you get "lucky" and get a bit further through the checks and trigger an erase. 100% make sure you can reliably test write first. That'll test your vehicle communications.

[josh420710]

I did recently put a aftermarket radio in ill try removing the fuse for it and try the test write.

[Phoenix]

All you can really do without a dyno or good data logging, is disabling traction control and "abuse" limits. Or things like switching between electric or cable throttle, 4L80 swap. You're not going to do much else.
If you want good support, go 12587603 and sort out the details as you go. Whatever it is, you'll be able to make it work right again. Discrete gauges vs serial data gauges, different fuel sender voltage vs level, security settings, VIN change, whatever.
I've spent many hours looking at the P59 in UniversalPatcher (P59 + CB450). There's a lot.
https://youtu.be/g_Q6pFgmySY?si=f5Uc1q_9eH7GCiOV&t=26
That's a 2004 Chevy Aveo tachometer by the way.

Are you able to go past 8192 rpm? Or does the P59 limit you there?

[AngelMarc]

I think the ECU shits it's pants with all the code it runs. With a crank signal generator, I've had it try at 20,000, but the output looks horrendous, and just over 9,000, OBD disconnects.
https://www.youtube.com/watch?v=e32bYJsmmgw