Skip to content

Debugging ECU-response dependent UI flows #80

Description

@Mattwmaster58

This was mentioned in #79, but really should have a seperate tracking issue IMHO.

Is there a way to debug this without having to be connected to the car? I am interested in fixing this but not if I have to be tethered to the car.

@jglim response:

I don't think there's a quick and easy way to do that; if I remember correctly, I hacked up some j2534 library to sufficiently respond like a target ECU when I had to test stuff out, just the basics like session requests, testerpresent, identification.

If you go for this route, you'll probably want to pick your preferred language to build the emulation DLL. From my experience, .net (via DllExport : https://github.com/3F/DllExport) is alright to work with and I think works okay with Diogenes, but Vediamo does not like that and will crash. Vediamo prefers a regular MSVC DLL. Rust looks promising too but I'm not experienced enough to comment more about that.

And my response to that:

I think that there could be some value in just a simple record/replay framework. Going way lower level hopefully wouldn't be necessary? Just for the level of eg trying to load up the variant coding in eg #79. I will prototype it if I have the time, some time

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions