[motorhead1991]

Options for QH users are slim, but here's one that we can add to the list. I have a basic UI done already, as well as the serial communication done and functional. All that's left to do is connect the two.

gauge_cluster.png (40.93 KiB) Viewed 5961 times

So far, it's 100% python based, with a modular approach taken into consideration. Porting it to other ADX (besides Deciphas universal one) is done in one file, while gauge themes are in another, separate from the core.

[serfma]

Alright, color me interested. How are you communicating with the QH?

[motorhead1991]

Alright, color me interested. How are you communicating with the QH?

Over serial via USB. I'm still working on the UI side of things.

[wwhite]

Push your repository to git, we all can help.

If you really want 'universal', we should decode all the DCL_DM_Transmit both PID and DMR, then all PIDs are already mapped in CPU, just have to read out the order, does not matter adx or cpu. That's how ForDiag does it.
All the information is already in CPU, its accessing it is the hard part.

[motorhead1991]

Push your repository to git, we all can help.

If you really want 'universal', we should decode all the DCL_DM_Transmit both PID and DMR, then all PIDs are already mapped in CPU, just have to read out the order, does not matter adx or cpu. That's how ForDiag does it.
All the information is already in CPU, its accessing it is the hard part.

It's on git, just on publicly . I wanted to get it working first, but that may be out of my skillset.

My main audience is the OBD1 Fords, which are more complicated to access. OBD2 is all defined and fairly well documented.