AIR II FAQ
AIR II Series Frequently Asked Questions
Question | Answer |
How does the AIR II handle low light or night conditions? | It is equipped with active IR LEDs for night vision support. |
How does the AIR II record and when? | Video is recorded in driving mode. While in driving mode, the camera records in a constant looping mode. If the camera detects abnormal movement, as in a collision, a highlight video is automatically generated for easy location by the user. This highlight recorded to the camera's SD card is available upon request and viewable after it has been successfully retrieved from the Portal. |
How long is the recording for an event identified by the AIR II? | Driver behavior events will upload 15 seconds of footage; 8 seconds before the triggered event and 7 seconds afterwards. |
How does the AIR II mount to the windshield and is it removable? | The camera comes with a custom mount that attaches securely to the windshield with heat-resistant adhesive tape. |
How long are video clips stored? | Successfully requested camera events are available in the Portal for 30 days after the event has been triggered. |
When can I expect camera footage to be available once requested? | The camera will upload footage to the cloud when it is powered on and has a good cellular signal. This process typically takes about 5-10 minutes to upload, if available. |
Does the AIR II gather diagnostic information from the vehicle? | Yes, if installed with a diagnostic cable directly to the vehicle's diagnostic port, then the device will attempt to report engine data if supported and provided by the vehicle. |
What engine diagnostic data can be reported by the AIR II? | The AIR II currently supports the following data: DTC alerts, Odometer, Fuel Level, Voltage, Coolant Temp. Note: Diagnostic reported data varies by make/model/year, not guaranteed. |
Can the AIR II report power loss? | Yes, using the existing Power Disconnect Alert, users can take advantage of the camera's internal battery, enabling them to receive power loss alerts if/when the camera loses power. |
Will I be able to run alerts and reports on the AIR II camera? | Yes, though alerts may be limited to general GPS tracking and various diagnostic data (if vehicle supported). |
What are the dimensions of the AIR II? | Length: 87mm; Height: 126mm; Width: 46mm; Weight: 212g |
How is video encrypted on the AIR II? | The camera's data transmission is TLS/SSL encrypted. TLS and SSL are widely recognized as secure protocols that enable server authentication, client authentication, data encryption, and data integrity over networks. |
What format are AIR II videos saved? | Videos are recorded in .TS format which is considered standard. Most universal players support this format. |
Why is the camera still in driving mode if I have already turned off the car? | Under normal circumstances, it will enter parking mode for a short period of time after the vehicle has turned off. If the camera does not enter parking mode for a long time after the vehicle has turned off, contact support. |
Where is event video stored on the AIR II? | The camera uploads video evidence to the Cloud upon user request while also recording to a MicroSD card. |
How do you install the AIR II power connection? | Please refer to the installation guide: Conventional Hardwire Install Guide, Diagnostic Port Install Guide |
How do I install a camera on a Freightliner or other heavy-duty vehicle? | Use a 3-wire J1939 9-pin harness cable, or other applicable heavy-duty cables (RP1226, Hino, Volvo/Mack) as needed (available for purchase). |
How is AIR II powered? | With the included power cable (direct wire, OBD, or 9-pin), the camera in the vehicle can provide 24/7 protection for weeks with easy and straightforward installation. |
To what extent can the AIR II see behind the vehicle? | Like the human eye, the camera can see anything that is visible through the vehicle windshield and windows. Also, like the human eye, the camera is limited by dark tinting and solid objects such as the vehicle body or passengers or privacy screens. |
What are AIR II Operating/Standby Temperatures? | -20°C to +70°C (Parking Mode); -20°C to +45°C (Driving Mode) |
How does the AIR II handle heat? | The camera is intended to stay mounted to the windshield to protect the vehicle at all times, so several technical measures went into its design to ensure it performs well even in hot conditions. The on-board thermal monitoring system proactively adjusts machine activity under different thermal conditions. Under the worst heat conditions, the camera knows to turn itself off to protect its electronic components. |
Does the AIR II record audio? | The camera can record audio; this feature is disabled by default. |
Can I use the AIR II internationally? | Since the camera is a connected product that requires certification, we offer service only in the United States, Mexico, and Canada. |
What happens if the camera loses power mid-incident? | The camera is equipped with a 600mAH backup battery, capable of capturing up to 10 minutes runtime after power loss. |
What is the length of the power harness for the AIR II camera? | 10 feet. |
What is considered "Dangerous Driving" for the AIR II? | The driver will hear two types of in-cab alerts: Harsh and Severe. The Portal doesn't differentiate between these two in terms of scoring but the events are triggered from different thresholds (mg = mili g force). Acceleration (.25s duration): Harsh 267 mg / Severe 297 mg. Braking (.25s duration): Harsh -350 mg / Severe -430 mg. Turning (.19s duration): Harsh 310 mg / Severe 350 mg. |
Does the AIR II report engine diagnostic data? | Yes, through a diagnostic cable installation the device is capable of reporting an array of engine diagnostics, dependent on Year/Make/Model. |
What types of engine diagnostic data is possible with the AIR II? | VIN, DTC codes, RPM, Vehicle Speed, Vehicle Battery Voltage, Coolant Temp, Odometer, Fuel Level, and more (not guaranteed). |
How long are videos stored on the cloud? | By default, all video clips will be stored on the cloud for 180 days. |
SD Card Frequently Asked Questions
Question | Answer |
What is the default SD card shipped with the camera? | The camera is shipped with a 128GB SD card. You can update this SD Card to 512GB independently in the field, if preferred. |
How does the AIR II manage storage on the microSD card? | For video storage on the camera, we recommend high-endurance SD cards (class 10 or higher MLC MicroSD cards) with a minimum size of 32GB, accommodating SD cards up to 512GB. (Use of non-high-endurance SD cards or SD cards with 8GB or less is not recommended.) |
What microSD cards are recommended for the AIR II? | We recommend using a high-endurance SD card (class 10 or higher MLC MicroSD card, 32-512GB) designed for continuous recording situations. Other cards will work but are much more prone to card errors and failures due to the high frequency of IO for video applications. |
What is the AIR II microSD card capacity? | The camera accepts MicroSD Cards up to 512 GB. |
What is the AIR II record time and media capacity? | The record time for the camera will vary based on the user preferences for event detection and microSD card capacity. See the MicroSD Card Chart below for estimated recording times. |
Why does the SD card in my camera no longer record video? | Over time, all microSD cards degrade due to repeated overwriting. Since dash cameras (including AIR II and Drive360) record non-stop, the memory card may eventually need to be replaced. Devices ship with a 128GB SD Card, which typically sees some degradation after ~24 months; it's recommended the SD card be replaced approximately every 18-24 months. |
What carrier bands are supported with the AIR II? | Provided SIM and carrier plan are correct, the device can support the following global bands: (2, 4, 5, 12, 17). |
MicroSD Card Chart* (assumes average 40 hours runtime per week, includes telematics history)
MicroSD Card Size | Driving Time / Max Events Stored |
32gb | 8 hrs/680 |
67gb | 20 hrs/680 |
128gb | 40 hrs/1370 |
256gb | 86 hrs/1370 |
512gb | 177 hrs/1370 |
Fleet All-in-One with AI Frequently Asked Questions
Question | Answer |
What events are reported by the device when AI is enabled? | Road Facing: Forward Collision Warning (disabled by default; users with permissions can enable), Close Following, Lane Departure, Stop Sign, Pedestrian Collision Warning (disabled by default; users with permissions can enable). Driver Facing: Drowsiness/Fatigue, Cell Phone Use, Distracted Driving, Seatbelt. |
What are the definitions for each event? | See the AI-Based Road-Facing and AI-Based Driver-Facing Event Type Definitions tables below. |
How does the camera detect Seatbelt? | Up to 15 fps, the camera looks for a seatbelt across the chest or over the shoulder. When drivers fail to fasten their seatbelt and begin driving, the detection delay triggers after 20 seconds of drive time. |
How does the camera detect Cell Phone Use? | Up to 15 fps, the camera looks for a cell phone in the driver's hand, then checks for phone up to the ear, and head position/eye gaze looking at the phone. The driver must maintain this posture for 8 seconds for the alert to trigger. |
How does the camera detect Distracted Driving? | Up to 15 fps, the camera reads head pose and eye gaze. When eyes/eye gaze can't be determined (e.g., sunglasses), head pose alone is used. The driver must maintain this posture for 3 seconds for the alert to trigger. |
How does the camera detect Drowsiness/Fatigue? | Up to 15 fps, the camera reads head pose, eye state, and mouth to detect yawning, head nodding, scratching the face, and eye closure over a rolling 120-second window. The driver must maintain some variation of this state for 5 seconds for the alert to trigger. |
How does the camera detect Forward Collision Warning? | Sends a notification when a high-threat vehicle in the same lane and direction poses a collision threat, based on time to collision. A vehicle must be traveling a minimum of 40km/h (24.85 mph), triggering if time to collision is 1 second or less. |
How does the camera detect Lane Departure? | Sends a notification when the vehicle laterally approaches a configured lane boundary marker (e.g., solid lane crossing at high speed). A vehicle must be traveling 50km/h (31.06 mph), triggering if the violation surpasses 1.5 seconds. |
How does the camera detect Stop Sign Violations (SSV)? | The camera's ADAS locates MUTCD/MUTCDC stop signs and detects "rolling stops" rather than complete, speed-zero stops — looking for egregious rolling vehicles that never fall below 10 mph through the sign. |
What user permissions are needed to configure cameras? | Upon initial activation, configuration access is limited to the Admin user; other users can be given access via the Roles/Permissions tab in People Admin. |
Where can I enable or disable reported events? | In the Portal, Admin users can navigate to the Admin: Dashcams tab, then click the Edit Camera Settings link. |
Can I enable or disable the in-cab alerts to control event notifications to the driver? | Yes, a user with permissions can click the "In-cab alert" toggle from the Edit drawer in the Admin: Dashcams tab. |
Can I enable or disable the ability to record the in-cab audio to manage fleet privacy? | Yes, a user with permissions can check/uncheck the "Audio" option from the Edit drawer in the Admin: Dashcams tab. |
Can I enable or disable the in-cab camera? | Yes, a user with permissions can check/uncheck the "Driver" option from the Edit drawer in the Admin: Dashcams tab. |
Why isn't my change to my camera configuration taking effect on the camera? | Make sure you're clicking the Save changes button after making your edit selections. Changes apply the next time the camera wakes; allow 1-2 trips before the full configuration takes effect. |
Does the camera allow for any safety alert settings to help coach the driver for better behavior? | Yes, the camera warns the driver with a safety assistance alarm for Close Following, Distracted Driving, Seatbelt, and Cell Phone Use, allowing correction before the event triggers. |
How does the camera admin page know what settings are applied/saved at the device level? | When a user loads the Camera Admin Edit window, a request is made to the camera to confirm active settings, which are then represented as enabled/disabled in the Edit window. |
Will my drivers be warned before they trigger an event? | Yes. For some event types, the driver receives a warning before the trigger. See the Road-Facing/Driver-Facing tables below. |
Will my drivers know when they have triggered an event? | Yes. Drivers hear a violation sound. See the Road-Facing/Driver-Facing tables below. |
AI-Based Road-Facing Event Type Definitions, Warning Sounds, & Violation Sounds
Event | Definition | Warning Sound | Violation Sound |
Forward Collision Warning | A fast approach to the stopped vehicle ahead is detected. (Disabled by default; users with permissions can enable it.) | – | "Collision Warning" |
Lane Departure | Detected when crossing solid and double solid lines while traveling at a high speed. | – | "Lane Departure Violation" |
Stop Sign Violations | Detected when the driver does not perform a safe stop at an intersection containing a stop sign. | – | "Stop Sign Violation" |
Pedestrian Collision Warning | Detected when time to collision with a pedestrian in the vehicle lane is less than 6 seconds. (Disabled by default; users with permissions can enable it.) | Announcement ring, "Pedestrian" | "Pedestrian Violation" |
AI-Based Driver-Facing Event Type Definitions, Warning Sounds, & Violation Sounds
Event | Definition | Warning Sound | Violation Sound |
Drowsiness/Fatigue | Driver drowsiness detected over a rolling 120-second window; combines yawning, head nodding, eye gaze, blink rate. | – | "Drowsy Driving Violation" |
Cell Phone Use | Detects phone held up to ear/near face, or in hand while driver looks down. | Announcement Ring, "Cell Phone Warning" | "Cell Phone Violation" |
Distracted Driving | Head pose and eye gaze detectors determine when driver is looking down or away from the road. | Announcement Ring, "Pay Attention" | "Distracted Driving Violation" |
Seatbelt | Detects seatbelt over the shoulder and across the chest to determine seatbelt state. | Announcement Ring, "Fasten Seatbelt" | "Seatbelt Violation" |
Fleet All-in-One Auxiliary Camera Frequently Asked Questions
Question | Answer |
Can the views of the different cameras be moved within the video? | No, the camera feeds are uniquely positioned within the video view to ensure all feeds are displayed accurately and effectively. |
What happens if some cameras have aux cameras and some do not? Will the cameras without aux cameras display blank spaces? | Vehicles with auxiliary cameras display the correct auxiliary feeds; vehicles without them only show the in-cab and road-facing camera views (if active). |
Why are the aux camera views upside down, or sideways? | If an auxiliary camera is installed incorrectly and rotation settings aren't properly updated in the install app, the feed may display at an incorrect angle. Refer to the installation guide: Accessory: AIR II Auxiliary Camera. |
When installing the aux camera, will the install app show the real-time view to confirm rotation is correct? | Yes, the installer app provides a real-time view to help confirm correct installation. |
What are the specs of the aux camera? | The specs of the aux camera can be found here: Aux Cam Spec Sheet. |
Does the AIR II support auxiliary cameras for added internal or external visibility? | Yes, the AIR II supports up to two additional aux cameras. |
My AIR II aux camera feed isn't working correctly, what do I do? | If you are only using one AUX, make sure it is plugged into the rightmost (E1) port; otherwise, contact Support. |
My AIR II aux feeds are upside down or sideways when viewing the video, what do I do? | Using the manufacturer's (Waylen's) installation app, ensure the final rotation settings are accurate based on the install guide. |
Event Validation Frequently Asked Questions
| Question | Answer |
|---|---|
| How does the system verify safety events? | When the camera detects a driver safety event, it is automatically reviewed using advanced AI before being delivered to your platform. This additional review helps confirm that the detected event is legitimate. |
| Why are detected events reviewed? | The additional review helps reduce false alerts, so you receive more accurate notifications and spend less time reviewing events that didn't actually occur. |
| Which events are currently reviewed? | The system currently verifies the following event: Potential Incident (Collision). |
| What happens if an event is determined to be inaccurate? | If the system determines that a detected event is a false alert, it is not sent to your platform. The event is still retained in the cloud for reference if it needs to be reviewed later. |
| Does this change how the camera detects events? | No. The camera continues to detect events as usual. The review process adds a layer of validation to improve the accuracy of the events you receive. |