Ignition Control for Vehicle Tablets — What Happens When the Key Turns, and What the Dock Has to Do About It
A vehicle tablet that stays on after the key is removed drains the battery. A tablet that shuts down immediately when the key turns off loses session state, interrupts a firmware update, or leaves a driver waiting for the device to boot at the next shift. The behaviour between ignition on and ignition off is not a single setting. It is a sequence of states that the dock, the tablet, and the application layer each control in part. This guide covers the sequence, the hardware switch that enables it, and the software hooks that let the application define what happens at each transition.
Table of Contents
1. The Four Power States
A vehicle tablet does not have two states, on and off. It has four states that matter for deployment: running, screen-off, sleep, and shut down. Each state draws a different current, responds differently to the ignition signal, and has a different recovery time when the key turns back on.
The deployment question is not “should the tablet turn off when the key turns off.” It is “which of these four states should the tablet be in, at which point in the ignition sequence, and how does the application control that choice.” A delivery van that runs two shifts per day may want screen-off during short stops and sleep after the shift ends. A long-haul truck may want the tablet to stay running while the driver is on a mandated break, because the ELD session must not drop. The vehicle power architecture page covers the input range and filtering that support these states.
2. The Ignition Switch on the Dock
The dock carries a physical switch that determines whether the tablet follows the vehicle ignition or ignores it. The default position is ignition independent — the tablet is powered whenever the dock receives 9–36V, regardless of the key state. The alternative position is ignition control — the tablet powers on and off with the ACC signal.
The switch position is set at the factory and is not intended to be changed in the field. A fleet that requires ignition control must specify it at the time of order. A fleet that receives the standard ignition-independent configuration and then wants ignition control later cannot simply flip a switch — the dock harness has to be changed.
This is a procurement decision, not a deployment detail. The ignition behaviour is determined before the devices ship, and it determines the wiring harness, the dock firmware, and the application-level power hooks that are available. The docking station matrix lists the ignition configuration for each dock model.
TOPICON MDT880 / MDT865 Vehicle Docking Guide
Vehicle docking installation with RAM mount, 9–36V wiring harness, and ignition switch demonstration.
3. The Transition Sequence
In an ignition-controlled deployment, the tablet sees four transitions over a typical shift.
• During operation: the ACC line stays high. The tablet remains in the running state. If the driver leaves the seat briefly, the application may choose to keep the screen on or dim it, depending on the workflow.
• Key off: the ACC line goes low. The dock signals the tablet that the ignition is off. What happens next depends on the application: immediate sleep, delayed sleep, or shutdown after a configured interval.
• Key on again: the tablet wakes from sleep or boots from shutdown, depending on the previous state. The application must restore its session or re-authenticate the driver.
The failure mode that matters most is the transition between key-off and key-on. If the tablet sleeps too quickly, a driver who returns within a few minutes has to wait for the wake and re-authentication. If the tablet stays running indefinitely after key-off, the battery drains. The application layer controls this trade-off. The dock provides the ignition signal; the application decides what to do with it.
4. Software Control at Each Transition
The tablet exposes an API that lets the application monitor the ignition state and control the power behaviour. Three capabilities are relevant.
• Sleep and shutdown control: the application can request that the tablet enter sleep or shut down after a configured delay. It can also cancel a pending shutdown if the driver returns before the delay expires.
• Screen behaviour: the application can keep the screen on while the ACC is high, set a screen-off timeout, and choose whether the device wakes on touch or requires a physical button press.
The TOPICON MDM platform can push the power configuration to a fleet, but the application-level behaviour is defined by the software vendor. The tablet provides the hooks; the application decides what happens. The MDT865 and MDT880 both expose this API through the Android BSP, and the OEM customization program covers deeper integration if required.
5. Common Failure Modes
Three failures recur in ignition-controlled deployments. Each has a different root cause and a different fix.
The first failure is a procurement issue, not a software issue. If the dock ships in ignition-independent mode, no amount of application code will make the tablet follow the key. The second and third failures are installation and wiring issues. The direct wiring vs docking station guide covers the harness routing that avoids these failures.
Single Point of Failure
The ignition switch position is the single point of failure that cannot be corrected after the devices ship. A fleet that receives ignition-independent docks and then discovers it needs ignition control has two options: replace the docks, or accept the battery drain. Neither is cheap. The switch position is determined at the time of order, and it determines the wiring harness, the dock firmware, and the application hooks that are available. This is not a configuration detail that can be changed in the field. It is a procurement decision that must be confirmed before the purchase order, alongside the tablet model and the mount type.
6. Deployment Checklist
Before specifying a vehicle tablet deployment, confirm the following.
• Sleep vs shutdown: should the tablet sleep after key-off and wake on key-on, or shut down and boot? Sleep is faster; shutdown saves more battery.
• Delay interval: how long should the tablet stay running after key-off? A short delay favours quick re-entry; a longer delay favours session continuity.
• Application hooks: does the application handle the ignition event broadcast? It should save state and close transactions before sleep or shutdown.
• Power tap point: is the dock connected to a point on the circuit that is not shared with the starter or the hydraulic pump?
• Converter sizing: does the DC-DC converter maintain the tablet’s input voltage during cranking and load switching?
• ACC wiring: is the ACC signal wired to the dock harness, and is it verified at installation?
• MDM configuration: can the power behaviour be pushed to the fleet through the MDM platform, or does it require per-device configuration?
7. Frequently Asked Questions
Can the ignition switch be changed after the dock ships?
No. The switch position is set at the factory and determines the wiring harness and the dock firmware. A dock that ships in ignition-independent mode cannot be changed to ignition control in the field. The configuration must be specified at the time of order.
Should the tablet sleep or shut down when the key turns off?
It depends on the workflow. Sleep is faster to resume and preserves the session, but draws more current. Shutdown saves battery but requires a full boot at the next key-on. A short-stop delivery workflow usually favours sleep; a vehicle that sits overnight favours shutdown. The application layer controls the choice.
Why does the tablet stay on after the key is removed?
The dock is likely in ignition-independent mode, which means it supplies power whenever it receives 9–36V regardless of the key state. The alternative is that the application does not handle the ignition event. Confirm the dock switch position and the application behaviour.
Why does the tablet reboot when the engine starts?
The starter motor draws a large current during cranking, which causes a momentary voltage drop on the battery circuit. If the dock is connected to a point that sees that drop, or if the DC-DC converter is undersized, the tablet’s input voltage falls below its operating range. The cranking voltage guide covers the fix.
Can the power behaviour be configured remotely?
The TOPICON MDM platform can push the power configuration to a fleet. The application-level behaviour — what the app does when it receives the ignition event — is defined by the software vendor and deployed through the normal application update path.
Specifying Ignition Control for a Vehicle Fleet?
The ignition switch position, the power tap point, and the application-level power hooks determine whether the tablet behaves correctly across the key-on and key-off sequence. Request a hardware evaluation kit or discuss the power configuration for your deployment.
