| Last Modified: 05-13-2024 | 6.11:8.1.0 | Doc ID: RM1000000026EDL |
| Model Year Start: 2023 | Model: GR Corolla | Prod Date Range: [09/2022 - ] |
| Title: MY SETTINGS: MY SETTINGS SYSTEM: VEHICLE CONTROL HISTORY (RoB); 2023 - 2025 MY Corolla Corolla Hatchback Corolla HV GR Corolla [09/2022 - ] | ||
VEHICLE CONTROL HISTORY (RoB)
NOTICE:
- If the vehicle or vehicle controls are operated (for example, during initial inspection when the vehicle is brought in for repair) before vehicle control history (RoB) has been read out and saved, the vehicle control history (RoB) information could be lost.
- The function "Read vehicle control history (RoB)" uses the current system time setting inside the GTS and the time counter inside the controlling ECU to calculate the timings shown in the vehicle control history (RoB). For this reason, before reading out the vehicle control history (RoB), first make sure that the GTS system clock is accurately set to the current time.
- The time counter in the control ECU may deviate by up to +/- 10% due to the characteristics of the time counter.
- The time counter in the control ECU is reset approximately 34 days before the "Current" value due to the characteristics of the time counter. Therefore, the time information stored before the 34th day may not be accurately displayed.
Vehicle Control History (RoB)
HINT:
Vehicle control history (RoB): The main body ECU (multiplex network body ECU) records the my setting system vehicle control history (RoB), which can be read out using the GTS.
(a) Read the Vehicle Control History (RoB) according to the display on the GTS.
Body Electrical > Main Body > Utility
|
Tester Display |
|---|
|
Vehicle Control History (RoB) |
|
RoB Code |
RoB Item |
Item description |
Note |
|---|---|---|---|
|
X230A |
My Setting Driver Switch Operation |
Stores the reason for the my setting driver being switched |
Stores my setting driver switch operations |
|
X230B |
My Setting Driver Switch Operation |
Stores the reason for the my setting setting being changed |
Stores my setting setting change operations |
|
X230C |
My Setting Relation Key Change History |
Stores the reason for the my setting key association setting being changed |
Stores my setting key association setting change operations |
|
X231D |
My Setting Relation Digital Key Operation |
Stores the reason for the my setting digital key association being changed |
Stores my setting digital key association change operations |
(b) Following the instructions on the screen, save the vehicle control history (RoB).
|
Vehicle Control History (RoB) List |
|---|
|
Guest was selected on Welcome Screen |
|
Driver 1 was selected on Welcome Screen |
|
Driver 2 was selected on Welcome Screen |
|
Driver 3 was selected on Welcome Screen |
|
Guest was selected on Personalize Screen |
|
Driver 1 was selected on Personalize Screen |
|
Driver 2 was selected on Personalize Screen |
|
Driver 3 was selected on Personalize Screen |
|
Guest (initialization) was selected on Personalize Screen |
|
Guest was detected on Driver Detection Screen |
|
Driver 1 was detected on Driver Detection Screen |
|
Driver 2 was detected on Driver Detection Screen |
|
Driver 3 was detected on Driver Detection Screen |
|
Guest was recognized by an electronic key |
|
Driver 1 was recognized by an electronic key |
|
Driver 2 was recognized by an electronic key |
|
Driver 3 was recognized by an electronic key |
|
Driver information was revised to Guest by an electronic key |
|
Driver information was revised to Driver 1 by an electronic key |
|
Driver information was revised to Driver 2 by an electronic key |
|
Driver information was revised to Driver 3 by an electronic key |
|
Driver information was made into Guest |
|
Guest was recognized by fingerprint authentication |
|
Driver 1 was recognized by fingerprint authentication |
|
Driver 2 was recognized by fingerprint authentication |
|
Driver 3 was recognized by fingerprint authentication |
|
Guest was recognized by face authentication |
|
Driver 1 was recognized by face authentication |
|
Driver 2 was recognized by face authentication |
|
Driver 3 was recognized by face authentication |
|
Guest was recognized by a smartphone |
|
Driver 1 was recognized by a smartphone |
|
Driver 2 was recognized by a smartphone |
|
Driver 3 was recognized by a smartphone |
|
Guest was recognized by a digital key |
|
Driver 1 was recognized by a digital key |
|
Driver 2 was recognized by a digital key |
|
Driver 3 was recognized by a digital key |
|
My Setting was enabled (Guest) |
|
My Setting was enabled (Driver 1) |
|
My Setting was enabled (Driver 2) |
|
My Setting was enabled (Driver 3) |
|
My Setting was disabled (Guest) |
|
My Setting was disabled (Driver 1) |
|
My Setting was disabled (Driver 2) |
|
My Setting was disabled (Driver 3) |
|
The automatic switch function of driver was enabled (Guest) |
|
The automatic switch function of driver was enabled (Driver 1) |
|
The automatic switch function of driver was enabled (Driver 2) |
|
The automatic switch function of driver was enabled (Driver 3) |
|
The automatic switch function of driver was disabled (Guest) |
|
The automatic switch function of driver was disabled (Driver 1) |
|
The automatic switch function of driver was disabled (Driver 2) |
|
The automatic switch function of driver was disabled (Driver 3) |
|
Key ID 1 was related with Driver 1 on key assignment screen |
|
Key ID 2 was related with Driver 1 on key assignment screen |
|
Key ID 3 was related with Driver 1 on key assignment screen |
|
Key ID 4 was related with Driver 1 on key assignment screen |
|
Key ID 5 was related with Driver 1 on key assignment screen |
|
Key ID 6 was related with Driver 1 on key assignment screen |
|
Key ID 7 was related with Driver 1 on key assignment screen |
|
Key ID 1 was related with Driver 2 on key assignment screen |
|
Key ID 2 was related with Driver 2 on key assignment screen |
|
Key ID 3 was related with Driver 2 on key assignment screen |
|
Key ID 4 was related with Driver 2 on key assignment screen |
|
Key ID 5 was related with Driver 2 on key assignment screen |
|
Key ID 6 was related with Driver 2 on key assignment screen |
|
Key ID 7 was related with Driver 2 on key assignment screen |
|
Key ID 1 was related with Driver 3 on key assignment screen |
|
Key ID 2 was related with Driver 3 on key assignment screen |
|
Key ID 3 was related with Driver 3 on key assignment screen |
|
Key ID 4 was related with Driver 3 on key assignment screen |
|
Key ID 5 was related with Driver 3 on key assignment screen |
|
Key ID 6 was related with Driver 3 on key assignment screen |
|
Key ID 7 was related with Driver 3 on key assignment screen |
|
Key ID 1 was related with Driver 1 on key assignment proposal screen |
|
Key ID 2 was related with Driver 1 on key assignment proposal screen |
|
Key ID 3 was related with Driver 1 on key assignment proposal screen |
|
Key ID 4 was related with Driver 1 on key assignment proposal screen |
|
Key ID 5 was related with Driver 1 on key assignment proposal screen |
|
Key ID 6 was related with Driver 1 on key assignment proposal screen |
|
Key ID 7 was related with Driver 1 on key assignment proposal screen |
|
Key ID 1 was related with Driver 2 on key assignment proposal screen |
|
Key ID 2 was related with Driver 2 on key assignment proposal screen |
|
Key ID 3 was related with Driver 2 on key assignment proposal screen |
|
Key ID 4 was related with Driver 2 on key assignment proposal screen |
|
Key ID 5 was related with Driver 2 on key assignment proposal screen |
|
Key ID 6 was related with Driver 2 on key assignment proposal screen |
|
Key ID 7 was related with Driver 2 on key assignment proposal screen |
|
Key ID 1 was related with Driver 3 on key assignment proposal screen |
|
Key ID 2 was related with Driver 3 on key assignment proposal screen |
|
Key ID 3 was related with Driver 3 on key assignment proposal screen |
|
Key ID 4 was related with Driver 3 on key assignment proposal screen |
|
Key ID 5 was related with Driver 3 on key assignment proposal screen |
|
Key ID 6 was related with Driver 3 on key assignment proposal screen |
|
Key ID 7 was related with Driver 3 on key assignment proposal screen |
|
Key ID 1 was related with Driver 1 on key setting screen |
|
Key ID 2 was related with Driver 1 on key setting screen |
|
Key ID 3 was related with Driver 1 on key setting screen |
|
Key ID 4 was related with Driver 1 on key setting screen |
|
Key ID 5 was related with Driver 1 on key setting screen |
|
Key ID 6 was related with Driver 1 on key setting screen |
|
Key ID 7 was related with Driver 1 on key setting screen |
|
Key ID 1 was related with Driver 2 on key setting screen |
|
Key ID 2 was related with Driver 2 on key setting screen |
|
Key ID 3 was related with Driver 2 on key setting screen |
|
Key ID 4 was related with Driver 2 on key setting screen |
|
Key ID 5 was related with Driver 2 on key setting screen |
|
Key ID 6 was related with Driver 2 on key setting screen |
|
Key ID 7 was related with Driver 2 on key setting screen |
|
Key ID 1 was related with Driver 3 on key setting screen |
|
Key ID 2 was related with Driver 3 on key setting screen |
|
Key ID 3 was related with Driver 3 on key setting screen |
|
Key ID 4 was related with Driver 3 on key setting screen |
|
Key ID 5 was related with Driver 3 on key setting screen |
|
Key ID 6 was related with Driver 3 on key setting screen |
|
Key ID 7 was related with Driver 3 on key setting screen |
|
The relation with the key was canceled on settings information deletion screen (Driver 1) |
|
The relation with the key was canceled on settings information deletion screen (Driver 2) |
|
The relation with the key was canceled on settings information deletion screen (Driver 3) |
|
The relation with the key was canceled on key setting screen (Driver 1) |
|
The relation with the key was canceled on key setting screen (Driver 2) |
|
The relation with the key was canceled on key setting screen (Driver 3) |
|
The relation with the key was canceled by key code erasure (Driver 1) |
|
The relation with the key was canceled by key code erasure (Driver 2) |
|
The relation with the key was canceled by key code erasure (Driver 3) |
HINT:
Some items are not displayed depending on the vehicle.
|
|