BMW Video in Motion: VIM Coding for All iDrive Generations

Video in motion, usually shortened to VIM, removes the factory speed lock that pauses iDrive video playback as soon as the car starts to move. On most BMWs the lock is a software threshold stored in the head unit, so a coding app can change it in minutes. This guide covers CCC, CIC, NBT and NBT EVO units, plus the legal limits. OBDThink is an independent BMW coding and diagnostics app and is not affiliated with BMW AG. What Is Video in Motion and How Does It Work? From the factory, the head unit compares current road speed with a stored limit and pauses every video source above roughly 3 km/h; audio keeps running and a safety notice replaces the picture. Video in motion coding raises that limit or removes the comparison, so DVD, TV and USB video keep playing while the car moves. The change is a pure software parameter and touches nothing else in the car. Driving functions, driver assistance and the instrument cluster read their speed signal from other control units and stay exactly as before. Because only the stored threshold changes, the modification is fully reversible and is not affected by a normal battery disconnection. Feature: video in motion (VIM) Module: head unit, e.g. HU_NBT or HU_NBT2 Parameter family: SPEEDLOCK_X_KMH_MIN and SPEEDLOCK_X_KMH_MAX Typical coded value: 255 km/h, so the lock never engages Scope: video sources shown on the iDrive screen Revert: restore the saved factory values Before you code, note the exact head unit type shown in OBDThink. CIC, NBT and NBT EVO all use the same SPEEDLOCK parameter family; it sits in different modules and coding data sets, and the app selects the matching set automatically. Which BMW Models and Head Units Support VIM Coding? Almost every BMW built since the mid-2000s can run video in motion, because each iDrive generation stores its speed lock in software. What changes between model ranges is the head unit name, the parameter set and how much work the activation takes; the summary is below. • CCC and M-ASK units in early E60, E90 and E70 cars carry the oldest lock; there, video is released by disabling the handbrake condition rather than by raising a speed threshold. • CIC units fitted between 2008 and 2012 pause video above walking pace and release it once the SPEEDLOCK value pair is raised. • NBT units in F20, F30 and F10 cars store the SPEEDLOCK values and are the easiest to code. • NBT EVO with ID4, ID5 or ID6 software keeps the same logic but needs the newer parameter set. • MGU units with iDrive 7 in G20 and G05 cars are locked tighter, and support depends on the software version. • Plain double-DIN radio models without iDrive have no video source, so there is no lock to open. Is Video in Motion Legal, and Who May Watch? In most countries the law targets the driver, not the screen: moving images visible from the driver's seat while driving are prohibited or heavily restricted, while passengers may watch freely. VIM coding changes nothing about the car's roadworthiness, but how you use it on public roads remains your responsibility. • Driver distraction rules differ by country, so check the local traffic code before using video on the front screen. • Watching as the driver on a public road can bring a fine, licence points or insurance trouble after an accident. • Passengers using rear-seat entertainment screens are unaffected, because the factory never speed-locked those displays. • Use on private ground, while stopped in traffic, or while charging and waiting causes no problem in most places. • Periodic inspections do not read head unit parameters, but an accident investigation can, so revert before a sale. How Do You Activate Video in Motion with OBDThink? Activation is a guided toggle rather than raw parameter editing. Connect an ENET or OBD adapter, let OBDThink identify the head unit, back up the current coding and apply the change; the whole process normally takes less than ten minutes. • 1. Park the car, leave the ignition on and connect your OBD or ENET adapter. • 2. Open OBDThink, let it read the vehicle and confirm the detected head unit type. • 3. Create a full coding backup and keep it outside the car, for example in cloud storage. • 4. Find the video in motion toggle in the feature list for your unit. • 5. Apply the change and wait until the unit confirms the new values were written. • 6. Restart the head unit when the app asks, so the new threshold loads. • 7. Play a video source and have a passenger confirm playback continues above walking pace. • 8. Save the session report, so the revert values stay documented for later. IF video pauses above 3 km/h THEN the factory lock is still active IF playback continues but the screen goes dark in reverse THEN the camera logic is separate and unaffected IF the toggle is missing from the list THEN the head unit type was not detected correctly The fastest verification is a two-person check on private ground: one person drives at low speed while the other watches whether playback continues past the old 3 km/h cut-off. How Do You Revert VIM to the Factory State? Reverting means writing the original speed-lock values back into the head unit. If you saved a backup during activation, OBDThink restores it in one step; without a backup, the app writes the known factory defaults for your unit type. • Restore the backup taken during the activation session whenever it is available. • Without a backup, set the speed lock back to the factory default for your unit. • Restart the head unit afterwards, so the restored threshold takes effect immediately. • Confirm with a passenger that video pauses again once the car moves off. • Keep the revert report, because it proves the factory state before an inspection or sale. After a successful revert, video playback no longer continues while driving: the picture pauses at walking pace exactly as delivered, which confirms the factory values are back in place. What Problems Can Occur After VIM Coding? The most common issue is a toggle that appears to do nothing because the car uses a different head unit than expected; the typical case is an NBT EVO detected as plain NBT. Playback then still pauses, and the fix is re-reading the vehicle and applying the matching parameter set. A second group of reports concerns software updates: a dealer update of the head unit can rewrite the coding and silently bring the speed lock back. That change is not harmful, it simply undoes the activation, and running the same toggle again restores video in motion. Never watch video from the driver's seat while the car is moving. This coding exists for passengers and parked use; the legal and safety responsibility for use on public roads stays entirely with you. Which Questions Are Asked Most Often About VIM? Most questions gather around four themes: legality, warranty, software updates and whether the change leaves traces. The short answers below reflect how the lock actually behaves on CIC, NBT and NBT EVO units. • Is video in motion legal? Coding the parameter is not forbidden, but watching as the driver on public roads is prohibited in most countries, so treat it as a passenger feature. • Does VIM survive software updates? Not always. A dealer update can restore the factory coding, and the activation then simply needs to be applied again. • Does the change affect safety systems? No. The speed lock only gates video sources on the iDrive screen; braking, assistance and cluster functions read their own signals. • Can the coding be seen later? Yes; a workshop reading the head unit can compare values with factory data, which is why OBDThink stores a revert backup. Check your head unit type, back up the coding and apply the toggle; that order keeps video in motion a five-minute job you can undo at any time. Reserve playback for passengers and parked situations, and the feature adds comfort without touching a single safety function.