PCM Hammer Release 012

[Gampy]

Holy shizzles, that's not a "Low Cost" unit ...

I've been looking at that unit, I need a good j-box to develop with.

Not sure about the buffer empty message, but it looks like it is adding a byte to each received packet, I dunno know.

[MudDuck514]

Hi all,

Gampy, I think one could buy several AVT cables for the cost of ONE of those!
Definitely NOT cheap!
Still waiting for the XPro to be released.

Mike

[Gampy]

Yes sir, that's a fact!

I don't use them, I'm just a wanna be developer.

Therefore why have what other developers already have working.

The only justification is education ...

[ironduke]

Is that extra byte the crc or something??? normally not displayed by the logs...

[Gampy]

If it is I couldn't figure it out ... that's no surprise to me, if it's other then 1+1 I'm lost and I get confused with that now and again!

[antus]

Yeah it looks like the crc. Its odd that it only starts being added part way through the process. Maybe there is a j2534 command to hide crc, and maybe we just leave it at the default which is dont send it for other devices. (I havnt checked).

[RoninDusette]

Will this work with an obdlink sx? I have a few and I know you can configure the firmware. Is there a supported vehicle list? I member trying it out a while ago and couldn't get it to work for me but I imagine it was my lack of hardware, knowledge, and/or a compatible platform.

[antus]

Yes obdlink sx, while one of the slowest interfaces, is supported and does work. Pcmhammer will read and write p01 and p59 computers (512kb and 1024kb). You need to find and XDF that suits your operating system to do the tune editing in tunerpro once you've read the bin file. You may decide to change to a different and more common OS if you cant find definitions for yours.

[Tazzi]

Looking at the log, the CRC is showing in the received messages.

Even though J2534 is standardized, not all companies implement it properly and this is a prime example. So the CRC is not meant to be displayed under any circumstance as per J2534 compliance. Since if the CRC was incorrect, it shouldnt have been displayed so its pointless having it display.
So pcmhammer code needs to be updated to not worry about the extra byte. Needs to bascially ensure the correct frame is received based off the mode request, ensure it meets the minimum length and then grab only the bytes it needs.

[Gampy]

Tazzi, that is exactly what I've been working on, teaching PcmHammer to ignore the extra byte(s), however that could take me weeks ... If I can even figure it all out!

I did build a custom version that ignored the extra byte in the unlock Key response, it then unlocked the unit, but ultimately still failed.

The funny thing is PcmHammer 10 works on that Autel, TE27Levin has sent me several junk yard bins currently and in the past ripped with v10 by jumping the short pin to get past the unlock.