Conditional Experimental Mode automatically switches your car between standard driving and Experimental Mode based on real-time road conditions, so you don't have to press any buttons. Think of it as a co-pilot who watches the road and decides when to shift into a more cautious, camera-driven driving style: approaching a red light, following a slow car, nearing a sharp curve, or turning at an intersection. It's one of FrogPilot's most powerful features for drivers who want smarter, hands-free mode management.
What It Is
Conditional Experimental Mode monitors your driving environment every moment and automatically activates Experimental Mode when conditions call for it.
To understand why this matters, you need to know that openpilot has two fundamentally different ways of controlling your speed. In standard mode (sometimes called "Chill Mode"), openpilot follows the car ahead and maintains your set speed using conventional cruise control logic. In Experimental Mode, the system uses its camera-based driving model to make end-to-end driving decisions: it can slow for red lights, stop at stop signs, and navigate complex intersections by interpreting what the camera sees.
Without Conditional Experimental Mode, you'd have to manually toggle Experimental Mode on and off. Imagine driving through a suburban neighborhood, approaching a traffic light, needing Experimental Mode to stop, then switching back to standard mode once you're cruising on a straight road. Conditional Experimental Mode handles all of that switching for you. It's like having an assistant who flips between "careful city driving" and "relaxed highway cruising" exactly when needed.
The system checks a prioritized list of conditions (your speed, detected curves, lead vehicles, navigation turns, stop lights, and turn signals) and activates Experimental Mode the instant any enabled condition is met. When all conditions clear, it returns to standard mode.
Before You Start
Conditional Experimental Mode requires your car to support openpilot gas and brake control (openpilot longitudinal).
If your car relies on its own factory cruise control for gas and braking (stock longitudinal), Conditional Experimental Mode won't appear in your settings. This includes many older Toyotas with Toyota Safety Sense P (unless you have a comma pedal or Smart DSU), some Honda models, and other vehicles where openpilot only handles steering. You can check whether your car supports openpilot longitudinal control on the comma.ai car compatibility page.
Once Conditional Experimental Mode is enabled, it activates automatically whenever one of your configured trigger conditions is met while openpilot is engaged. You can still manually override the mode at any time by tapping the steering wheel icon on your driving screen, which cycles between forcing Experimental Mode on, forcing it off, and returning to automatic control.
⚠️ Warning: Experimental Mode relies on the driving model's camera-based predictions, which are not perfect. openpilot does not explicitly detect traffic lights or stop signs. It may stop when there's no clear reason, or miss a stop it should have caught. Always be ready to brake yourself.
Settings
Every trigger condition is a separate setting you can enable or disable, giving you precise control over when Experimental Mode activates.
| Setting | Default | Tuning Level | Type | What it does |
|---|---|---|---|---|
| Below (No Lead) | 0 mph (Off) | Standard | Speed slider | Activates below this speed when no car is ahead |
| Below (With Lead) | 0 mph (Off) | Standard | Speed slider | Activates below this speed when following a car |
| Conditional Experimental Mode | On | Standard | Toggle | Master switch for the entire feature |
| Curve Detected Ahead | Off | Standard | Toggle | Activates when a curve is detected |
| ↳ With Lead | Off | Standard | Sub-toggle | Also activates for curves when following a car |
| "Detected" Stop Lights/Signs | On | Standard | Toggle | Activates when the model predicts a stop (simplified mode) |
| Lead Detected Ahead | Off | Standard | Toggle | Activates for slow or stopped lead vehicles |
| ↳ Slower Lead | Off | Standard | Sub-toggle | Triggers for a lead driving much slower than you |
| ↳ Stopped Lead | Off | Standard | Sub-toggle | Triggers for a completely stopped lead |
| Navigation-Based | On | Advanced | Toggle | Activates near intersections and turns on your route |
| ↳ Intersections | Off | Advanced | Sub-toggle | Triggers for intersections with stop signs or lights |
| ↳ Turns | On | Advanced | Sub-toggle | Triggers for upcoming route turns |
| ↳ With Lead | On | Advanced | Sub-toggle | Also activates for navigation events when following a car |
| Predicted Stop In | 8 seconds | Developer | Numeric slider | Activates when a stop is predicted within this time |
| Status Widget | On | Advanced | Toggle | Shows trigger reason on the driving screen |
| Turn Signal Below | 55 mph | Advanced | Speed slider | Activates when signaling below this speed |
| ↳ Not For Detected Lanes | On | Advanced | Sub-toggle | Skips activation if an open lane is detected |
Conditional Experimental Mode (Master Toggle)
| Property | Value |
|---|---|
| Default | On |
| Recommended | On for most drivers |
When On, the system monitors all your enabled trigger conditions and switches between standard and Experimental Mode automatically. When Off, openpilot stays in whichever mode you set manually, and none of the sub-settings have any effect.
What this means for you: Leave this on unless you prefer to manage Experimental Mode entirely by hand. The default "On" means FrogPilot ships ready to use this feature out of the box.
Below (No Lead)
| Property | Value |
|---|---|
| Default | 0 mph (Off) |
| Recommended | 25–35 mph for city driving |
| Range | 0 – 99 mph (0 – 150 kph) |
| Units | mph or kph (matches your unit setting) |
Sets a speed threshold for activating Experimental Mode when there's no car directly ahead of you. When your speed drops below this value, the system switches to Experimental Mode. Setting it to 0 disables this trigger entirely.
At low values (10–20 mph), Experimental Mode only kicks in during very slow neighborhood driving or parking lot situations. At moderate values (25–40 mph), it covers most city streets. At high values (50+ mph), it activates even at suburban highway speeds, which may cause unnecessary mode switches.
What this means for you: This is your primary city-driving trigger. If you often drive through areas with traffic lights and stop signs at 25–35 mph, setting this to match those speeds means Experimental Mode will automatically handle those situations while standard mode handles your highway cruising.
Below (With Lead)
| Property | Value |
|---|---|
| Default | 0 mph (Off) |
| Recommended | 0–25 mph for stop-and-go traffic |
| Range | 0 – 99 mph (0 – 150 kph) |
| Units | mph or kph (matches your unit setting) |
Works like the "No Lead" threshold, but only applies when you're following another vehicle. Setting it to 0 disables this trigger.
What this means for you: If you're stuck in bumper-to-bumper traffic at low speeds, this ensures Experimental Mode is active so the system can make smarter braking decisions behind the car ahead. You can set this lower than the "No Lead" value since the system's standard following behavior already handles many lead-following scenarios.
Curve Detected Ahead
| Property | Value |
|---|---|
| Default | Off |
| Recommended | On for winding roads |
When On, Experimental Mode activates whenever the driving model and road curvature data indicate an upcoming curve. The detection uses a smoothing filter that requires the curve signal to persist for roughly one second before triggering, preventing false activations from brief road wobbles.
When Off, curves don't trigger Experimental Mode (though Curve Speed Controller, if enabled separately, still slows you for curves).
What this means for you: Enable this if you frequently drive on winding roads and want the driving model's end-to-end predictions to manage your speed through curves. On straight highways, this trigger stays dormant.
💡 Tip: This trigger only activates above roughly 11 mph (the internal cruising speed threshold of 5 m/s), so it won't fire while you're crawling through a parking lot.
With Lead (Curves)
| Property | Value |
|---|---|
| Default | Off |
| Recommended | Off for most drivers |
When On, the curve trigger also fires even when you're following a car. When Off, curve detection is suppressed while a lead vehicle is present, since the lead car's braking behavior often naturally guides your speed through curves.
"Detected" Stop Lights/Signs
| Property | Value |
|---|---|
| Default | On |
| Recommended | On |
This is the simplified version of the stop prediction trigger, visible when your tuning level is below Developer. When On, it enables stop light and stop sign detection using the default prediction window (approximately 8 seconds of lookahead). When Off, the system won't switch to Experimental Mode for predicted stops.
This setting and the Predicted Stop In slider (visible at Developer tuning level) control the same underlying behavior. At Standard and Advanced tuning levels, you see this simple on/off toggle. At Developer level, this toggle is replaced by the numeric slider that lets you fine-tune the prediction time window.
⚠️ Warning: openpilot does not explicitly detect traffic lights or stop signs. In Experimental Mode, it makes end-to-end driving decisions from the camera, which means it may sometimes stop when there's no clear reason, or fail to stop when you expect it to.
Lead Detected Ahead
| Property | Value |
|---|---|
| Default | Off |
| Recommended | Off for most drivers; try On if you want smoother braking behind slow/stopped cars |
When On, enables the two sub-triggers below for slow and stopped lead vehicles. When Off, lead vehicle status alone won't trigger Experimental Mode.
Slower Lead
| Property | Value |
|---|---|
| Default | Off |
| Recommended | Off for most drivers |
When On (requires Lead Detected Ahead to also be on), activates Experimental Mode when the car ahead is driving significantly slower than you (more than roughly 11 mph slower, based on the internal 5 m/s cruising speed threshold). This detection uses a smoothing filter to avoid flickering on and off.
What this means for you: Useful on roads where you frequently catch up to much slower vehicles and want Experimental Mode's braking decisions to handle the deceleration more smoothly.
Stopped Lead
| Property | Value |
|---|---|
| Default | Off |
| Recommended | Off for most drivers |
When On (requires Lead Detected Ahead to also be on), activates Experimental Mode when the car ahead is nearly stopped (below roughly 2 mph, based on the internal 1 m/s threshold).
Navigation-Based
| Property | Value |
|---|---|
| Default | On |
| Recommended | On if you use Navigate on openpilot |
When On, enables Experimental Mode when approaching intersections or turns on your active navigation route. This requires Navigate on openpilot to be set up with a destination. If no route is active or GPS data is unavailable, these triggers simply don't fire.
The navigation data comes from Mapbox's routing service. When you set a destination, the route includes information about upcoming intersections (with stop signs and traffic signals) and turns. The system calculates your distance to these points and activates Experimental Mode when you're close enough, factoring in your current speed.
What this means for you: If you regularly use Navigate on openpilot for commuting or road trips, this feature makes the system automatically shift to Experimental Mode before each intersection and turn on your route, then shift back to standard mode afterward.
Intersections
| Property | Value |
|---|---|
| Default | Off |
| Recommended | On for city driving with navigation active |
When On, triggers Experimental Mode when approaching intersections along your route that have stop signs or traffic signals. The detection range scales with your speed: at higher speeds, it activates further in advance to give the system more time to slow down.
What this means for you: This is especially helpful on routes through cities where many intersections have signals. The system uses the map data from your route to know about intersections before the camera can even see them.
Turns
| Property | Value |
|---|---|
| Default | On |
| Recommended | On |
When On, triggers Experimental Mode when approaching a turn maneuver on your route (like a right turn at a street or a highway exit ramp). Like intersections, the detection range scales with your speed.
With Lead (Navigation)
| Property | Value |
|---|---|
| Default | On |
| Recommended | On |
When On, navigation triggers also fire when you're following a lead vehicle. When Off, navigation-based triggers are suppressed while following another car.
Predicted Stop In
| Property | Value |
|---|---|
| Default | 8 seconds |
| Recommended | The default of 8 seconds works well for most drivers |
| Range | 0 – 9 |
| Units | seconds |
This slider is only visible at the Developer tuning level. It replaces the simpler "Detected" Stop Lights/Signs toggle with precise control over how far ahead the driving model must predict a stop before switching to Experimental Mode. Setting it to 0 disables this trigger entirely.
The value represents a time horizon. The system compares how far the model projects your car will travel against how far it would travel at cruising speed within this many seconds. If the model predicts you'll stop sooner than expected, it switches to Experimental Mode.
At low values (1–3 seconds), Experimental Mode only activates when a stop is imminent, giving you less preparation time but fewer false activations. At moderate values (5–8 seconds), the system has a comfortable window to slow down gradually. At high values (9 seconds), it reacts very early to predicted stops, which may cause more frequent mode switches on roads where the model sees potential stops that don't materialize.
The default of 8 seconds is derived from the driving model's maximum planning horizon (10 seconds) minus 2 seconds of buffer.
💡 Tip: This trigger is suppressed when you're following a lead vehicle or when Traffic Mode is active, since those situations have their own speed management logic.
Turn Signal Below
| Property | Value |
|---|---|
| Default | 55 mph |
| Recommended | The default of 55 mph works well for most drivers |
| Range | 0 – 99 mph (0 – 150 kph) |
| Units | mph or kph (matches your unit setting) |
When you activate your turn signal and your speed is below this threshold, the system switches to Experimental Mode. Setting it to 0 disables this trigger. The default of 55 mph means this trigger covers city and suburban turns but won't activate during highway lane changes at highway speeds.
What this means for you: When you signal for a left or right turn on a city street, Experimental Mode activates to help the system make smarter braking and speed decisions for the turn. On the highway at 65 mph, your lane-change signal won't unnecessarily trigger the switch.
Not For Detected Lanes
| Property | Value |
|---|---|
| Default | On |
| Recommended | On |
When On, the turn signal trigger checks whether there's actually an open lane in the direction you're signaling. If a clear lane is detected (meaning you're likely just changing lanes, not turning), the trigger is suppressed. When Off, any turn signal below the speed threshold activates Experimental Mode regardless of lane availability.
This works by checking the width of the adjacent lane on the side you're signaling. If the lane is wide enough (based on your Lane Detection Width setting from Lane Change Customizations), the system assumes it's a lane change rather than a turn.
What this means for you: Leave this on to avoid unnecessary Experimental Mode activations during highway lane changes where a clear lane exists beside you.
Status Widget
| Property | Value |
|---|---|
| Default | On |
| Recommended | On |
When On, displays a widget on your driving screen showing which condition triggered Experimental Mode (or showing standard mode if no conditions are active). The widget displays an animated icon and a colored border indicating the current driving mode.
What this means for you: This gives you instant visual feedback about why the system chose its current mode. Glance at the widget and you'll know whether it switched because of a curve, a stopped car, an upcoming turn, or any other trigger.
How It Works
Conditional Experimental Mode runs a prioritized checklist every time the driving model updates (roughly 20 times per second), and the first matching condition wins.
Here's the order the system checks conditions, from highest to lowest priority:
- Manual override: If you've tapped the steering wheel icon to force a mode, that override holds until you tap again or openpilot disengages.
- Speed threshold: If your speed is below your configured threshold (checked separately for with-lead and no-lead situations), Experimental Mode activates immediately.
- Turn signal: If your blinker is on and you're below the signal speed threshold, and no open lane is detected in that direction (when lane detection is enabled), the mode switches.
- Navigation: If you're approaching an intersection or turn on your active route (and the lead-vehicle sub-toggle permits it), the mode switches.
- Curve ahead: If road curvature has been consistently detected for roughly one second (and the lead-vehicle sub-toggle permits it), the mode switches.
- Slow or stopped lead: If the car ahead is significantly slower or completely stopped (with smoothing to prevent flickering), the mode switches.
- Predicted stop: If the driving model predicts a stop within your configured time window and you're not following a lead vehicle, the mode switches.
- Speed Limit Controller fallback: If the Speed Limit Controller can't find a speed limit and its fallback is set to "Experimental Mode," that also triggers Experimental Mode through this system.
If none of these conditions are met, the system writes a status of 0, and openpilot stays in (or returns to) standard mode. The transition back to standard mode isn't instant: because all detections use smoothing filters, the signal must decay below the activation threshold before the condition clears, providing natural hysteresis that prevents rapid flickering between modes.
When you tap the steering wheel icon on screen while Conditional Experimental Mode is active, you cycle through three states: if you're currently in standard mode, you force Experimental Mode on. If you're in Experimental Mode, you force standard mode. Tapping again clears the override and returns to automatic control.
Status Indicators
The status widget shows an animated icon and colored border that tell you exactly what's happening at a glance.
The widget appears near the driver monitoring icon on your driving screen. Its border color and icon change based on the current mode and trigger:
| Icon | Border | Status Code | Meaning |
|---|---|---|---|
 | Black | 0 | Standard mode, no conditions active |
| Yellow | 1 | You manually overrode to standard mode |
 | Orange | 2 | You manually overrode to Experimental Mode |
 | Orange | 3 | Below speed threshold (following a car) |
| Orange | 4 | Below speed threshold (no car ahead) |
 | Orange | 5 | Turn signal active below threshold |
 | Orange | 6 | Approaching a navigation intersection |
| Orange | 7 | Approaching a navigation turn |
 | Orange | 8 | Curve detected ahead |
 | Orange | 9 | Stopped vehicle ahead |
| Orange | 10 | Slower vehicle ahead |
| Orange | 11 | Stop predicted ahead (model detection) |
| Orange | 12 | Stop predicted ahead (force stop active) |
| Orange | 13 | Speed Limit Controller using Experimental Mode fallback |
The border color tells you the current driving mode at a glance:
- Black border: standard mode (no Experimental Mode active)
- Orange border: Experimental Mode is active (any trigger)
- Yellow border: you manually overrode to standard mode
Feature Interactions
Conditional Experimental Mode connects with several other FrogPilot features that share speed data or affect the same driving outputs.
Curve Speed Controller (Works alongside)
Both Curve Speed Controller and the "Curve Detected Ahead" trigger in Conditional Experimental Mode respond to road curvature. They serve complementary roles: Curve Speed Controller calculates a target speed for the curve and slows you down, while the curve trigger in Conditional Experimental Mode switches to Experimental Mode so the driving model can also contribute its end-to-end predictions. Both features use the same underlying curvature data from the planner but make independent decisions.
Force Stop (Works alongside)
The Force Stop feature (under Quality of Life) works alongside Conditional Experimental Mode's stop prediction. When a stop is predicted and Force Stop is active, the status widget shows code 12 instead of 11, indicating that the system is actively forcing a stop rather than just switching modes. Both features read the same model-stopped detection, and Force Stop determines the tracked stopping point while Conditional Experimental Mode handles the mode switch.
Speed Limit Controller (Enhances)
Speed Limit Controller directly feeds into Conditional Experimental Mode's decision-making. When the Speed Limit Controller is active but can't find a posted speed limit, and its fallback setting is configured to "Experimental Mode," this triggers Conditional Experimental Mode with status code 13. This means the system enters Experimental Mode to use the driving model's judgment in areas where no speed limit data is available.
Limitations & Known Issues
- GPS and navigation data quality: Navigation-based triggers depend on having an active route in Navigate on openpilot with good GPS signal. In tunnels, urban canyons, or areas with poor GPS reception, the navigation triggers won't fire. The route data also only knows about intersections and turns that Mapbox's routing data includes.
- Model prediction accuracy: The stop prediction trigger relies entirely on the driving model's forward projection. Different driving models have different prediction qualities. The model may predict stops that don't exist (causing unnecessary mode switches) or miss stops (failing to activate Experimental Mode).
- Traffic Mode suppression: The stop light/sign detection is automatically suppressed when Traffic Mode is active, since Traffic Mode has its own close-following behavior that doesn't benefit from mode switching.
- Tuning level gates: Many sub-settings are hidden below your current tuning level. Navigation triggers require Advanced, and the precise stop prediction slider requires Developer. Raising your tuning level reveals more controls.
- Unmapped or newly built roads: If a road isn't in the Mapbox database or has been recently changed, navigation triggers won't have accurate intersection or turn data.
- Curve detection requires minimum speed: Curve detection only activates above roughly 11 mph (the internal 5 m/s cruising speed threshold) to prevent false triggers in parking lots or while creeping.
Setup Recommendations
Start with the defaults and adjust one setting at a time as you learn how each trigger behaves on your daily routes.
| Driving Scenario | Recommended Settings |
|---|---|
| City commute with navigation | Below (No Lead): 25–35 mph, Turn Signal Below: 55 mph, Navigation-Based: On with Intersections and Turns, "Detected" Stop Lights/Signs: On |
| Highway-only driving | Below (No Lead): 0 (Off), Curve Detected Ahead: Off, Turn Signal Below: 0 (Off) or keep lane detection on, Navigation-Based: On with Turns only |
| Mixed suburban/highway | Below (No Lead): 30 mph, Curve Detected Ahead: On, Turn Signal Below: 55 mph (default), Navigation-Based: On |
| Stop-and-go traffic | Below (With Lead): 20–30 mph, Lead Detected Ahead: On with Stopped Lead |
💡 Tip: If you find Experimental Mode activating too often on the highway, lower the "Below" speed thresholds. If it's not activating enough in the city, raise them. The turn signal trigger at 55 mph is well-calibrated for most drivers, as it covers city turns while ignoring highway lane changes.
Q: Conditional Experimental Mode isn't showing up in my settings. Where is it?
A: This feature requires your car to support openpilot gas and brake control (openpilot longitudinal). If your car uses its factory cruise control for gas and braking, this setting won't appear. Check your car's compatibility, and make sure you haven't disabled openpilot longitudinal control in your Vehicle Settings. Also verify your tuning level is at least Standard, since Conditional Experimental Mode is gated at the Standard tuning level.
Q: Conditional Experimental Mode is on, but the system never switches to Experimental Mode. What's wrong?
A: First, confirm that Experimental Mode is enabled and confirmed on your device (you need to acknowledge the Experimental Mode warning at least once). Second, check that at least one trigger condition is enabled in the Conditional Experimental Mode sub-settings. The defaults ship with "Detected" Stop Lights/Signs on and Navigation-Based on, but the speed thresholds default to 0 (off), so you may need to set a speed value to see speed-based triggers.
Q: The system keeps switching to Experimental Mode on the highway. How do I stop that?
A: This usually happens because a speed threshold is set too high or the curve trigger is firing on gentle highway curves. Lower your "Below (No Lead)" and "Below (With Lead)" values so they're well under your highway cruising speed. If curves are the issue, turn off "Curve Detected Ahead" or make sure it's off when you primarily drive straight highways. Also check that your Turn Signal Below value is lower than your typical highway speed.
Q: Experimental Mode activates every time I signal for a lane change. How do I prevent this?
A: Make sure the "Not For Detected Lanes" sub-toggle under Turn Signal Below is turned on (it's on by default). This checks whether there's an open lane in the direction you're signaling. If it detects a lane (meaning you're changing lanes, not turning), it suppresses the trigger. If you're still getting false activations, you can also lower the Turn Signal Below speed threshold or set it to 0 to disable the signal trigger entirely.
Q: I enabled the Navigation Intersections trigger but it never fires. Why?
A: Navigation triggers require an active route in Navigate on openpilot. If you don't have a destination set, or if your GPS signal is poor (like in a tunnel or urban canyon), the navigation data won't contain intersection information. Also, the route must include intersection data from Mapbox's database, so intersections on unmapped or newly built roads won't be detected.
Q: The mode seems to flicker between standard and Experimental. Is something wrong?
A: Some flickering can happen when you're right at the boundary of a trigger condition, such as driving exactly at your speed threshold or approaching a curve that the model detects intermittently. The system uses smoothing filters (requiring conditions to persist for roughly 0.5 to 1 second before activating), but borderline situations can still cause transitions. Try adjusting your speed thresholds to be clearly above or below your typical driving speeds for the roads where this occurs.
Q: The status widget isn't showing on my driving screen. How do I enable it?
A: The Status Widget setting is at the Advanced tuning level with a default of On. If you're at Standard tuning level, the widget uses its default (on), so it should appear. If it's still missing, open the Conditional Experimental Mode sub-settings and make sure "Status Widget" is toggled on. The widget also only appears while openpilot is engaged.
Q: I switched to metric units, but the speed values seem off. What happened?
A: When you change between imperial and metric units, FrogPilot automatically converts your saved speed values. The "Below" thresholds, Turn Signal Below, and other speed settings are converted from mph to kph (or vice versa). After switching, check your values to make sure they're still set where you want them. The UI ranges also change: imperial shows 0–99 mph, while metric shows 0–150 kph.
Q: I tapped the steering wheel icon and now Conditional Experimental Mode isn't working automatically anymore. How do I fix it?
A: Tapping the steering wheel icon while Conditional Experimental Mode is active creates a manual override (forcing either standard or Experimental Mode). Tap the icon again to clear the override. The status widget shows a yellow border when you've overridden to standard mode, or an orange border with the Experimental Mode icon when you've forced Experimental Mode. Tapping once more returns to automatic control with a black border (standard) or condition-based switching.
Q: Does Conditional Experimental Mode affect my steering? I also have Always On Lateral enabled.
A: No. Conditional Experimental Mode only controls which gas and braking mode openpilot uses (standard vs. Experimental Mode). Always On Lateral controls whether steering stays active when cruise control is off. These two features operate on completely independent systems with no interaction. Enabling or disabling one has no effect on the other.
Related Features
Conditional Experimental Mode works best when paired with features that provide speed and road data.
| Feature | Relationship | How it interacts |
|---|---|---|
| Curve Speed Controller | Works alongside | Both respond to road curvature data. Curve Speed Controller sets a target speed for curves, while the curve trigger in Conditional Experimental Mode switches to Experimental Mode. They complement each other with independent decisions. |
| Force Stop | Works alongside | Both use the driving model's stop prediction. Force Stop actively brings the car to a halt, while Conditional Experimental Mode switches to the appropriate driving mode. Status code 12 indicates both are active simultaneously. |
| Speed Limit Controller | Enhances | When Speed Limit Controller can't find a speed limit and its fallback is set to "Experimental Mode," it triggers Conditional Experimental Mode (status code 13), adding coverage for roads without speed limit data. |
