DUDU7 / Toyota Sequoia 2008 / HiWorld 7405862 — vehicle speed present in received packets but unavailable as CAN speed
@dudu-lai
Please help check CAN speed decoding/integration on my DUDU7.
Important wiring detail: My 2008 Sequoia did not have a CAN-H/CAN-L connection available at the original head-unit connector. I therefore added a twisted pair from the vehicle’s OBD-II connector to the HiWorld decoder: OBD pin 6 (CAN-H) → decoder pin 11, and OBD pin 14 (CAN-L) → decoder pin 12. The remaining decoder connections use the supplied harness. The attached driving log was recorded with this wiring.
Vehicle: Toyota Sequoia II Platinum, 2008, factory JBL.
CAN decoder: HiWorld TYF 2.20 (GB), H1H2TYF23A-260317.
Selected profile: Hiworld → Toyota → Sequoia → 2010–2012, ID 7405862.
CAN-H/CAN-L are connected to the vehicle OBD-II CAN pair.
Installed software:
- OS version shown: 2026.02.10
- DuDuOS Base: 1.004025
- Dudu Launcher Pro7870: 1.015091
- com.syu.ms: 26.0920D, versionCode 2126092016
CANBUS is selected as the priority speed source, but I cannot obtain working CAN speed in DUDU.
The attached driving log contains speed values matching my acceleration, steady driving and stops:
0x32 packet: payload[5] matches speed in km/h.
0x1A packet: ((payload[3] << 8) | payload[4]) / 10 matches speed in km/h.
Payload indexes above are zero-based, starting immediately after the command byte. These are decoder-to-head-unit packet types, not vehicle CAN IDs.
Examples from log_2026-10-12_1.txt:
21:45:09 — 20 km/h
21:45:40 — 40 km/h
21:45:54 — 60–61 km/h
21:46:16.951 — 0 km/h
21:47:23.521 — 51 km/h
21:47:32.674 — 0 km/h
Static analysis of my installed com.syu.ms indicates that profile 7405862 maps to protocol 294 / variant 113, using module.canbus.r. Its U2 handler processes packets 0x32 and 0x1A but does not extract these speed fields.
However, com.syu.ms also exposes raw packets through callback 1019, so DUDU Base may have a separate decoder. Please check both paths; I am not assuming the issue is exclusively in com.syu.ms.
Could you confirm whether this profile is supported for CAN speed and advise which compatible software update or fix is needed? My goal is to make vehicle speed available to navigation software, not just display GPS speed.
Secondary issues: RPM is unavailable, and coolant/tyre temperatures show 215°C. The log contains FF in the suspected coolant field and the four tyre-temperature fields.
System screenshots, decoder label and the original driving log are attached. I can test a compatible fix.
