Drive Mode and Drive Mode sub menus is an actual thing like Terrain Mode Module that can be selected by alfaOBD. Look at the swf files and you will see many menu screens for Drive Mode stuff. Things like Drive Mode Launch Control etc., but not relevant to most of our cars. Terrain status LED (the LED that lights up when you select AUTO, SAND, MUD etc) is on our cars, but like yaw is not mapped from CAN to PPS files.ORP Update
Managed to source an 18.45.01 update ISO for a MY18 TH.
1. DRM.jar - I am now using the DRM.jar from the KIM24 xlets directory, which has DRM exceptions for both ORP and Performance pages! My Performance pages now also work. Woohoo
2. Sensor_properties.json - the json file contains a few new entries for YAW data, Terrain Status LED (1-5, which I assume represents the five different selec-terrain statuses auto/snow/sand/mud/rock), and GlobalDriveModeStatus.
This is where things get super confusing to me. GlobalDriveModeStatus defines itself as an INT data type, with values being 0 or 1. ORP uses GlobalDriveModeStatus and expects the value to be either of {4, 13, 1, 12, 6}. I must be missing something, but I can't seem to work out how the selec-terrain page could possibly work with this sensor mapping. There must be some form of data transformation layer between the received sensor data, and other inputs.
As a test, I reloaded the original ORP app, and updated my own sensor_properties file with all mappings present in the 18.45.01 update. Selec-terrain page doesn't work even though I have defined GlobalDriveModeStatus and all other terrain-related sensor mappings. Changed it back to Mark's version as it overrides the terrain mode status to TerMdStat which is supported for earlier WK2 (MY14-MY16?)
3. Now that I have this ISO, I will commence the grueling task of searching for the holy grail CAN PPS definition for Pitch and Roll degrees. Will update if/when I find something.
Navigation update
I have tried to load the Squithy ROW 2019 and 2016 nav content and licenses, but always comes back with a prompt for my navigation activation code, despite the fact I already have a VP4 model.
Strangely the 'Original ROW' upload licenses pass the nav activation detection.
Have already switched over the NaviServer2.
I suppose Squithy's license files arent pre-activated?
Next step will be to pull my finger out and actually buy an iGo license and load the Aus content/license. Will provide an update - but if anyone has encountered the same issue it would be great to get some guidance. Potentially there's something very very obvious that I've missed.
The directory list from page 1: https://pastebin.com/BKfSptbH
The IPC stuff looks like it could be relevant.
/dev/ipc/ch2 thru /dev/ipc/ch28
These channels appear to be used to send and maybe recieve data.
From boot.sh
echo "**********Resetting the hardware********************"
echo -n "\\0021" > /dev/ipc/ch4
Hopefully the CAN to PPS file conversion is not hardcoded in a compiled bin or lib.
Last edited: