🔔 OBD Auto Shutdown: Preventing False Alarms
Sign in
🔔

OBD Auto Shutdown: Preventing False Alarms

Overview

The OBD Auto Shutdown module is designed to prevent specific vehicle models from entering "alarm mode" (triggering the factory alarm) when the OBD port is accessed or locked too quickly after the engine is turned off.

By deactivating OBD communication when the engine is idle, this module ensures no unnecessary requests are sent over the vehicle's CAN BUS, maintaining electrical harmony and preventing security system interference.

[!IMPORTANT] To ensure accurate trip reporting when using "Enabled for all vehicles" mode, you must verify that your device configuration uses the field MDI_JOURNEY_STATE for trip detection, rather than DIO_IGNITION.

    Configuration Steps

  1. Access the App: Log in to Morpheus (Device) Manager. Go to the Dashboard > Apps and select OBD Auto Shutdown.

      1. Create a New Configuration: Click New Configuration and enter a descriptive name (e.g., BMW_Alarm_Fix).

      2. Module Activation (Select Mode): Choose the behavior that matches your specific vehicle requirements:

Enabled - Vehicles equipped with alarms (Recommended for Alarm Issues)

    • Use Case: Select this mode specifically to resolve factory security systems triggering after engine shutdown.

    • Why use it: It applies targeted logic tailored to vehicle alarm systems without universally forcing restrictive OBD behavior across non-affected assets.

Enabled for all vehicles

    • Use Case: Broad, global activation across your entire fleet.

    • Risk Warning: This mode should not be used as a shortcut to fix alarm issues. If selected, you must ensure your device configuration uses the field MDI_JOURNEY_STATE for trip detection instead of DIO_IGNITION. Failure to do so will cause missed or broken trip reporting across your fleet.

Enabled - Default behaviour

    • Use Case: Standard module activation. (Note: Do not use for Start & Stop vehicles).

Enabled - BMW configuration

    • Use Case: Specific to BMW models; requires the BMW ignition stack.

Disabled

  • Use Case: Deactivates the module entirely

Set Thresholds (Advanced Settings): The following default values are typically applied. Only modify these if instructed by technical support:

  1. High level threshold: 500

  2. Low level threshold: -500

  3. Interval between checks: 30000 (ms)

Save: Click Save Changes.

    1. Deployment via Campaigns

    • Navigate to Campaigns: Select Campaigns from the left menu and click Add a configuration campaign.

    • Fill the Form:

      • Campaign Name: Enter a name for the rollout.

      • Configuration Name: Select the configuration you created in Step 3.

      • Targeted Assets: Choose the specific vehicles requiring the fix.

    • Launch: Click Save, then click Launch to push the configuration to the devices.

Note: After launching the campaign, check the Status bar. If a vehicle shows as "Pending," it will receive the update the next time the device wakes up and connects to the server.