CARRITO.NET // MOTORSPORT

RacerOS Motorsport User Manual

Learn how to use Racer Vision, Drag timing, Race Room 1:VS1, Circuit, Teams, Hosts, Timeslips and event tools.

⚠ Safety First

Use Carrito.net Motorsport only at safe, legal and controlled motorsport venues. Motorsport involves risk. Mount your device before the vehicle moves and never operate the interface while driving.

GPS, browser sensors and Racer Vision may provide estimated timing. Browser-generated results should be treated as unofficial unless verified by an authorized timing source or Host.

RacerOS does not control your throttle, brakes, steering, transmission, ignition or vehicle launch. Automatic launch refers only to detecting vehicle movement and starting the timing process.

Manual

01 // Quick Start

A typical RacerOS session follows this workflow:

01
Safety Check

02
Select Mode

03
Driver Ready

04
Lights

05
Movement

06
Timing

07
Result

02 // Motorsport Cockpit

The Motorsport Cockpit is the main control center. RacerOS uses dialog-style navigation so drivers and teams can move between modules without repeatedly loading separate pages.

SOLO

Practice and independent test runs.

1:VS1

Driver challenges and Race Room sessions.

VISION

Racer Vision light and race-state detection.

CIRCUIT

Lap, sector, stint and pit tools.

TEAM

Crew, strategy and team communications.

HOST

Events, rules, race control and verification.

03 // Timing Modes

Mode	Sources	Best Use
Digital	Browser GPS + Device Motion	Mobile test runs
Analog	Compatible sensor input	External sensor workflows
Hybrid	Digital + compatible sensors	Multi-source detection
Racer Vision	Camera + browser sensors	Light-state assisted timing
Manual	Driver/Host input	Fallback and testing

04 // Device Permissions

Location: required for GPS timing and Auto Lap.
Camera: required when Racer Vision uses visual light detection.
Motion: may be required for movement-assisted launch detection.

Only enable the capabilities needed for the session. Browser support and permission behavior vary by device.

05 // Racer Vision

Racer Vision helps the system understand race-light states using the device camera and compatible browser sensors.

CALIBRATE → PRE-STAGE → STAGE → AMBER → GREEN → MOVEMENT → TIMING

Supported Light Profiles

Full staging sequence
Dual full
Dual Red / Yellow / Green
Red / Yellow / Green
Red / Green
Green only
Vertical or horizontal presentation

Racer Vision should be calibrated while stationary. Visual detection can be affected by sunlight, reflections, distance, camera exposure and venue lighting.

06 // Driver Ready

DRIVER READY tells RacerOS that the driver and device are prepared for the timing sequence.

DRIVER READY → ARM SENSORS → WAIT FOR GREEN → DETECT MOVEMENT → START TIMER

Driver Ready does not physically launch the vehicle. It prepares the timing system to detect the start of the run.

07 // Drag Test Run

Drag Test Run can monitor common distance checkpoints and create a Carrito.net timeslip at the end of a session.

Checkpoint	Recorded Data
Reaction	R.T.
60 ft	Elapsed Time
330 ft	Elapsed Time
1/8 mile	ET + estimated MPH
1000 ft	Elapsed Time
1/4 mile	ET + estimated MPH

Automatic Movement Launch

After GREEN, RacerOS can wait for vehicle movement before starting the active run timer. Depending on the selected mode, movement may be corroborated using GPS, device motion, Racer Vision or compatible sensor input.

08 // Race Room 1:VS1

DRIVER A READY + DRIVER B READY → BOTH READY → LIGHTS → GREEN → RUN → RESULTS

Race Room connects two drivers to the same Match. Each racer can maintain an independent result while both timeslips remain associated with the race.

09 // Timeslip by CARRITO.NET

TIMESLIP BY

CARRITO.NET

MODE — SOLO / DRIVER VS DRIVER

R.T. — Reaction Time

60 FT · 330 FT · 1/8 · 1000 FT · 1/4

STATUS — UNOFFICIAL / HOST VERIFIED

Timeslips can be stored, reviewed and shared. A browser-generated timeslip remains unofficial until an authorized source verifies it.

10 // Circuit

Sessions

Practice
Time Attack
Qualifying
Sprint
Feature Race
Endurance

Timing

Manual Lap
Auto Lap
Last Lap
Best Lap
Live Delta
Sectors

Race Operations

Pit In / Out
Stints
Team
Strategy
Communications

Auto Lap

Set the start/finish location while stationary or during the controlled setup procedure. RacerOS can then use GPS to detect departure from and return to the configured zone and create subsequent laps automatically.

11 // Team & Pit

DRIVER
Vehicle and session.

CREW CHIEF
Run planning and pit calls.

ENGINEER
Setup and data.

SPOTTER
Traffic and incidents.

PIT CREW
Service workflow.

STRATEGY
Stints and race plan.

12 // Communications

RacerOS can provide communication areas for Race Room participants, teams, events and spectators.

Race Room: race-related participant communication.
Team: driver, crew and strategy communication.
Event: Host announcements and event information.
Spectator: public-facing event updates where enabled.

Never read, type or send messages while driving. During an active run, communications should be handled by authorized team members.

13 // Host & Race Control

Host tools are designed for organizers, tracks and authorized race-control personnel.

Create events.
Assign Rule Profiles.
Configure light profiles.
Manage race formats.
Review results.
Verify authorized results.
Manage points and rankings.
Configure event communications.
Use Event Automations.

14 // Events & Automation

Event Automations allow a Host to create workflows triggered by race activity.

BOTH READY → AUTOMATION → EVENT ANNOUNCEMENT

RESULT POSTED → AUTOMATION → RESULT UPDATE

CALL TO STAGE → AUTOMATION → DRIVER / EVENT NOTICE

SAFETY REMINDER → AUTOMATION → PARTICIPANT NOTICE

15 // Spectator Experience

When enabled by the event, spectators can follow public information such as event updates, selected results, announcements and sponsor content.

Spectators must remain in designated safe areas and follow all instructions from venue and event personnel.

16 // Understanding Result Status

Status	Meaning
UNOFFICIAL	Generated using browser, GPS, motion, Racer Vision or another unverified source.
HOST VERIFIED	Submitted or confirmed through an authorized Host timing workflow.

17 // Troubleshooting

The timer does not start after GREEN.

Confirm DRIVER READY is active, GPS or the selected movement source has permission, the device is mounted securely and the selected timing mode is armed. MANUAL LAUNCH remains available as a fallback.

GPS is inaccurate.

Move to an open outdoor area at the venue and wait for improved GPS accuracy before beginning the session. Buildings, roofs and other obstructions can reduce positioning accuracy.

Racer Vision does not recognize the lights.

Recalibrate while stationary. Check camera permissions, framing, glare, exposure and the selected light profile.

Auto Lap does not record another lap.

Verify that a start/finish location was established, Auto Lap is enabled, GPS remains active and the minimum lap-time requirement has been satisfied.

Before Every Session

Use a legal, controlled motorsport venue.
Follow Host and venue rules.
Secure the device before moving.
Confirm permissions and timing mode while stationary.
Never interact with the device while driving.
Treat browser timing as unofficial until properly verified.

CARRITO.NET // MOTORSPORT
RacerOS Motorsport User Manual