PCM Hammer - CAN BUS Communications

[turbo_v6]

Here is my hacky branch bubba2533_CANBus_Testing. You don't have to tell me how terrible it is because I already know lol.

I'll probably just abandon that branch and start a new one after reevaluating and hearing feedback.

[kur4o]

Awesome work bubba2533. You can definitely optimize from here. The fastest read time I get from 3mb pcm is around 2:40min, packet size is $800. With 4mb 3:30 is possible for sure, but I guess you want to do some clean up before squeezing timings to the limit.

[Gampy]

Awesome job!

CANHammer is alive!

It looks like that's because of line 64 & 65 from "PcmHacks\Apps\PcmLibraryWindowsForms\Devices\J2534Device.cs"

Code: Select all

this.MaxSendSize = 2048 + 12;    // J2534 Standard is 4KB
this.MaxReceiveSize = 2048 + 12; // J2534 Standard is 4KB

And if you look one more row up from that,

Code: Select all

            // Reduced from 4096+12 for the MDI2
            this.MaxSendSize = 2048 + 12;    // J2534 Standard is 4KB
            this.MaxReceiveSize = 2048 + 12; // J2534 Standard is 4KB

You will see why it is set to that ... The MDI2 cannot handle 4096 byte packets!

I suspect it won't be the only abandon branch ... You'll learn something new and wind up starting over, very typical!

Have fun with it, not to worry, I have ZERO interest in contributing ... Though I may make a remark or two (dozen).

-Enjoy

[darkman5001]

Great work. Very interesting.

[turbo_v6]

One question I keep thinking about is: Should there be a selection to go between VPW and CAN?

Or should it try VPW and then try CAN if it fails? In my branch I added a toggle to the device selection, which works, but I just thought it might make it easier on the user.

Obviously that would only make sense if the device is capable of communicating via CAN.

[antus]

I think the step that identifies the PCM type by OSID would try vpw then try can. If it can identify the PCM it then saves it type as it does now, then that type is used to look up the protocol each time it communicates. I also would like to have a pcm type selection page where you can select the pcm type from a list, and skip the osid step so that it can be used to read and write PCMs that are not identifiable by OSID - either its unknown, or incorrect/missing/not responding normally/recovery mode.

[TE27Levin]

We need this thing to pop open t43's! How can I do that?

[antus]

this is just proof of concept for can bus comms. it wont do t43 without a lot more work. never say never, but for now its a no.

[Gampy]

Personally, I think the app should ask what to do, not try to figure it out ...
CAN or VPW
ECM,TCM,BCM, etc...

But it's y'all's gig, I have worse things to do!

-Enjoy

[Vampyre]

kinda with gampy on this one, would make things more streamline if we just had drop downs for protocol, ecu type(bcm, ecm, etc,), and one needed(po1, p04, e38)

make the programmers lives easier