Per: https://forum.dudu-auto.com/d/476-important-notice-vehicle-information-and-upcoming-plans/60, I have a DUDU7 running DUDUAUTO 3.5 with a OD-OLO-02 canbus decoder in a Volvo XC90 MY2008 and am only able to detect reverse, use next + previous, volume up/down on my SWC. No other signals or keys are shown/understood by my DUDU7.
I have been reading up on how the CANbus decoder interfaces with the head unit (great summarizing post here: https://xdaforums.com/t/canbox-can-decoder-reverse-engineering.4057759/post-89765171 for those curious).
My understanding is that the reason for limited vehicle integration support is either:
1) only a subset of the OD-OLO-02 UART byte sequence mappings are implemented in DUDUAUTO (requires DUDUAUTO developers to implement wider support for the OD-OLO-02 canbus decoder UART byte sequences)
2) the firmware currently running in the CANbus decoder simply does not relay UART byte sequences to the head unit (requires new firmware on the CANbus decoder).
I'm interested in getting support for as many signals as possible without having to wait for anyone else to address above by writing my own firmware that maps the CAN signals on my vehicle to UART byte sequences that are currently supported by the head unit/DUDUAUTO.
My question to DUDUAUTO developers is:
1) Which CANbus decoder protocol (Eg Raise/VW/MPQ, HiWorld/Volvo/XC90 etc) is currently best supported in DUDUAUTO (has the most UART byte sequences mapped to car state signals?).
2) Could you share the target UART byte sequences to car state / keys for that protocol so I can implement the CAN signal > UART byte signal mapping in my firmware? I am primarily interested in hang-up call, pick-up call, back, enter, up, down, left, right, and rear parking sensor distances.
Thanks in advance!