Bad Install

Bad Installation Detection is an automated diagnostic feature that ensures your customers get the most accurate telematics data possible by instantly identifying devices that are loosely mounted, improperly angled, or not horizontally level.

By utilizing Raven’s internal sensors, the device can compensate for minor misalignments. However, if angles fall beyond the acceptable range for 2.5 minutes, the system automatically flags a "Bad Install." This unlocks three value pillars for your customers:

• Data Integrity: Automatically suppresses acceleration-based events (aggressive acceleration, harsh braking, and harsh cornering) while improperly mounted, ensuring driver scorecards aren't skewed by a dangling camera.
• Cost Management: Prevents the system from triggering hundreds of false-positive harsh driving alerts, saving fleets from unnecessary cellular data consumption and alert fatigue.
• Proactive Maintenance: Instantly alerts management (and optionally the driver) that a device needs physical adjustment, reducing device downtime. Once the device is correctly mounted for 5 continuous minutes, the system automatically clears the event and resumes normal tracking.

To support these goals, we have exposed a set of flexible configuration options via the RC-API (BadInstallConfig). Below is a guide to these settings and how they shape the user experience.

Configuration Guide: Tailoring the Diagnostic Experience

Different fleets handle hardware maintenance differently. Some rely on drivers to fix their own equipment, while others require fleet technicians to handle all adjustments. These API settings allow you to customize how alerts are routed and displayed.

The Master Switch: Enabling Detection

API Setting: enabled

This is the foundational setting that toggles the diagnostic monitoring on or off.

• The Experience: When set to true, Raven actively monitors its physical orientation. If it detects an issue lasting longer than 2.5 minutes, it flags the Bad Install, alerts the cloud, and begins suppressing harsh driving events.
• Why use it: This must be enabled to protect the integrity of the fleet's telematics data and to utilize any of the alerts below.

Screen Notifications: Visual Alerts and Frequency

API Settings: visual_alert_enabled and visual_alert_frequency_mins

Visual screen alerts provide a persistent or recurring reminder to the driver to adjust the device.

• The Experience: When visual_alert_enabled is set to true, Raven displays a specific warning graphic on its screen. You can then use visual_alert_frequency_mins to dictate exactly how often this warning interrupts the screen flow (e.g., reminding the driver every 15 minutes). 

• Why use it: For vehicles where drivers are responsible for the hardware, recurring visual prompts ensure the issue is addressed. For fleets using union drivers who are strictly forbidden from touching the hardware, you can disable this to prevent driver frustration.

In-Cabin Driver Feedback: Audio Alerts

API Setting: audio_alert

Audio alerts draw attention to the device, helping reinforce the visual toast notification.

• The Experience: This setting dictates what type of auditory chime or warning the Raven device plays in the cabin when a bad install is detected.
• Why use it: It prompts the driver to fix the device immediately (e.g., re-securing it to the windshield) without requiring dispatch to call them.

Customer Profile and Recommended Configurations

Customer Profile	Recommended Configuration	Why?
Owner-Operators / Light Commercial	audio_alert: Enabled visual_alert_enabled: true	Drivers are responsible for their own vehicles. High in-cabin alerting ensures they fix the mount themselves immediately.
Unionized / Heavy Duty Fleets	audio_alert: Disabled visual_alert_enabled: false	Drivers may not be permitted to touch telematics hardware. Suppress in-cab alerts to avoid frustrating the driver; rely on cloud alerts for mechanics to fix during the next yard visit.
Rental / Shared Pool Fleets	auto_video_upload: true visual_alert_frequency_mins: High (e.g., 60)	Frequent driver turnover increases the chance of device tampering. Video uploads help management assess if the device was intentionally knocked down or just fell.