KAIRUHS Manual


Hardware	v2.4
Battery Telemetry Board	v1.2
Firmware	v3.04
Built	in the US

1. Introduction

KAIRUHS is a modular telemetry, HUD, and radar system built for RC pilots and drivers of every kind — from casual FPV flyers who just want a clean HUD, up to full sim‑style rigs with a dashboard, a sim wheel, and live telemetry pulled straight from a real RC vehicle.

Key capabilities:

Up to four independent displays, each assignable to almost any role on the fly
Radar that sees and tracks any other KAIRUHS board in range, regardless of what kit or vehicle it’s mounted on
Fully Wi‑Fi based configuration — no physical menu buttons
Radio Slave pairing and long‑range radio behavior (FastLink and LoRa)
WebDash — turns a phone, tablet, or laptop into an extra screen
Standalone operation without a flight controller
MAVLink and MSP telemetry integration for flight controllers

This manual covers:

The KAIRUHS main board (hardware v2.4) and the optional battery telemetry board (v1.2)
Display setup, rotation, and role assignment across up to four screens
Wi‑Fi based configuration
Radar, radio slave pairing, and long‑range radio behavior
WebDash
Standalone operation
MAVLink and MSP integration
Setup, troubleshooting, and firmware update guidance

⚠️ Mixing hardware revisions. If you’re combining components from different KAIRUHS board revisions — rather than using everything that shipped together as one set — double‑check port orientation and polarity before connecting anything. Port layouts can differ between hardware revisions, and an incorrect connection can permanently damage a component.

Kits that arrive together as a complete package are already wired correctly and are plug‑and‑play.

If you’re unsure about a specific pairing, contact support before powering anything on.

💾 Before you update. Every KAIRUHS unit is fully tested before it leaves our shop, but before installing any firmware update:

Export a backup of your current configuration from the Backup tab (see Section 12)

If you have a battery telemetry board, keep your emailed factory calibration values saved somewhere safe

Both make it painless to get back to exactly where you started if anything unexpected happens during an update.

2. Startup Behavior

Normal power‑up sequence:

Board boots directly into normal operation and shows whatever screen roles are assigned.
Depending on System Mode, it either looks for a flight controller connection (MAVLink or MSP), or — in Standalone mode — runs a short sensor boot and calibration first.
A splash screen briefly shows your current firmware version, followed by a quick system status check.

Splash screen status indicators:

System	Green	Red
Telemetry (MAVLink/MSP)	Connected and reporting data	Not connected / not detected
Radio	Active and communicating	Not connected / not detected

This is a fast way to confirm you’re getting telemetry and/or radio data before you head out.

Standalone mode boot check: Watch the artificial horizon right after boot. If it immediately rolls or tips over rather than sitting level, the Board Orientation setting doesn’t match how the board is physically mounted — see Board Orientation under the Advanced tab.

Default active screen ports: How many screen ports are active out of the box depends on what you purchased.

Example: a 2‑screen kit ships with only the first two display ports active, since rendering unused ports costs performance.
You can enable additional ports later under Display Speed and Screen Management in the Advanced tab if you add more screens.

3. Entering AP Mode & Live Screen Editing

All configuration is done over Wi‑Fi through a browser — there’s no physical menu system on the board itself.

Steps to enter AP Mode:

Power on the board, then immediately hold the BOOT button.
Keep holding it for at least 5 seconds.
- Letting go too early, or pressing the wrong sequence, either boots the system normally or leaves you with a blank screen (bootloader mode) instead of AP mode.
- If that happens: power cycle and try again.
A splash screen confirms AP mode and shows the Wi‑Fi network name and password.
Connect your phone, tablet, or laptop to that network:
- Default network name: KAIRUHS_Config
- After you’ve saved a Vehicle ID: KAIRUHS_(your vehicle ID)
- Password: kairuhs123
Open a browser and go to http://192.168.4.1.

Tested and confirmed working on iPhone, Android, and Windows.

Why the network name changes with your Vehicle ID:

Keeps two units from ever appearing as the same access point — which would otherwise risk one person accidentally editing another person’s saved settings.
⚠️ If you change your Vehicle ID, the network name changes too, and your device treats it as a brand‑new access point. You’ll need to re‑enter the password again, even if you’d saved the old network before.

Once connected, you land on the Basics page. The header shows:

Current firmware version
Reboot Device button
Vehicle/Pilot ID fields

Radar and GC7 pairing are intentionally disabled while in config mode.

Live Screen Editing:

While in AP mode, only one screen renders at a time, chosen from the header (Screen 1–4).
Any change (gauge position, size, colors, HUD offset) updates on that screen immediately — no save-and-reboot required, unlike older firmware.
Running more than one screen at once in AP mode isn’t recommended and may cause instability — stick to the single live screen while configuring, unless you’re using Unlock Enabled Screens (see Section 6).

4. Menu Tour

The configuration menu is organized into these tabs: Basics, Gauges, Radio, Ground, Advanced, Telemetry, Backup, WebDash, and Manual.

Basics

The primary setup tab — also the only place screen size is selected for each port.

System Mode

Determines how the board gets its telemetry: Standalone, MSP, or MAVLink.
Standard boards connect to a flight controller over MSP or MAVLink.
Boards with the factory‑installed Standalone IMU can run fully on their own — but Standalone hardware doesn’t lock you out of FC‑based telemetry either. Those boards can still connect to a flight controller over MSP or MAVLink if you’d rather use one.
INAV 8 or 9: use MSP — MAVLink is not reliable on these versions.
Other FC firmware: MAVLink can be hit or miss depending on the specific build; MSP is quickly becoming the more consistent standard overall (see Section 9).
Board Orientation (under Advanced) is available regardless of protocol, to correct roll/pitch/yaw if your FC reports differently than expected.

Displays and Rotation

Screen Size	Resolution
1.44″	128×128
1.14″	135×240
1.9″	170×320
1.47″	172×320
2″	240×320
1.54″	240×240

Rotation options: 0°, 90°, 180°, 270° — plus mirrored versions of each, for reflective HUD setups.

Roles

Not locked to specific screen sizes — every screen size works the same way, regardless of which one you use.
Air roles (PFD, MFD, HUD, gauges) → square or portrait orientation.
Ground roles (dashboards, radar) → landscape orientation.
Thermal → works in either orientation (available as both an Air and Ground role).
Running a role in the wrong orientation may crop or scale the layout rather than break it outright.

HUD Settings

Vertical offset: 0–112 (lines the HUD up with your camera level on a 1.14″ screen)
HUD style — choose one of:
- Traditional telemetry‑heavy HUD
- Static reticle styles: dot, skull, skull and bones, cat face, X, heart, smiley, KAIRUHS smiley, star
- Numbered crosshair styles (circles with center dots, plain crosses, line and box reticles, and similar variations)
HUD icon behavior: tracks roll/pitch with the horizon (traditional), or stays fixed

Warnings

Warning	Notes
Stall	Threshold configurable
Overspeed	Threshold configurable
Voltage	Threshold configurable
Low Altitude	Threshold configurable
Altitude Ceiling	Threshold configurable
Overcurrent	Threshold configurable
Thermal	Works in any system mode (Standalone, MSP, MAVLink) as long as a temperature probe is connected

When a warning trips: bold overlay flashes on PFD, Radar, HUD, and Thermal.
MFD does not display warning overlays.
On Radar, HUD, and Thermal specifically, you can also enable a full‑grid red flash alongside the overlay for extra visibility. PFD shows the overlay only — no full‑grid flash option.

Thermal Settings (requires a temperature probe — a solder‑on accessory)

Monitors motor, ESC, engine temperature, or ambient air
Label what the probe is reading
Choose °C or °F
Set a history graph interval
Installation is aimed at more advanced users — contact support for help
Light sensor bundle (optional, separate accessory): auto‑dims screens, but only works in MSP or MAVLink mode with a flight controller connected — it does not function properly in Standalone mode

Units and Display

Speed units: mph / kmh / knots
Altitude/distance units: feet / meters / yards
MFD fuel gauge style: voltage or fuel‑bar
PFD compass layout: compact or full
Brightness: 1–10
AHI sky/ground colors, with reset‑to‑default option

Identity

Vehicle ID: up to 8 characters
Pilot/Driver ID: up to 8 characters
Team selection: 0 or 1 (color‑codes other live radar targets as friendly or hostile)

Radar

Visible range (feet)
Target visibility filter: Friends / Hostiles / All
Labels shown: ID, distance, altitude
ID label source: pilot ID or vehicle ID
Eject Factor: controls how far past your set range a target can travel before disappearing from radar
- 1.0 = ejects right at the edge of range
- 1.2 (example) = drifts slightly past the edge before dropping off

📌 The AP Live Screen selector in the header works throughout every tab, so you can flip to whichever screen you’re actively tuning at any time.

Gauges

Controls the four air gauge pages and everything on them.

Theme Color (global): sets the color used across all dashboard gauges
AHI Dim Mode: tones down the artificial horizon’s brightness so it doesn’t wash out neighboring gauges on the same page

Available gauge types:

Gauge	Details
Airspeed (IAS)	Forward speed using 3D ground speed. Follows Speed Units setting (MPH/KMH/Knots).
Altimeter	Altitude display. Follows Alt/Dist Units setting (Feet/Meters/Yards).
VSI (Vertical Speed)	Climb/sink rate. Follows altitude units setting.
Turn Coordinator	Bank/roll indicator with realistic slip‑ball physics.
Heading	Compass heading indicator.
RPM	Derived from throttle position, with smoothing.
Manifold Pressure	Simulated from throttle position and current draw.
Oil Pressure	Simulated from throttle and amp draw with realistic dynamics.
Oil Temperature	Simulated from throttle, current draw, and airflow (3D ground speed). Scale: 0–300°F, green/yellow/red bands.
Fuel Quantity	Based on per‑cell voltage (total V ÷ cell count). Maps ~3.30–4.20V to 0–100%, left/right mirror needles.
Coolant Temperature	Simulated from throttle, current draw, and airflow (3D ground speed). Scale: ‑50–150°C.
Attitude (AHI)	Classic blue/brown artificial horizon with roll and pitch. Includes Dim Mode.
Mono AHI (Page 4)	High‑contrast monochrome artificial horizon for low‑glare layouts.
Gear Indicator (Page 4)	Green = up, Red = down. Channel assigned in Advanced tab.
Flaps Gauge (Page 4)	Green = 0°, Yellow = 20°, Red = 40°. Channel assigned in Advanced tab.
Battery Voltage Gauge (Page 4)	Segmented red/yellow/green arcs; flashes when voltage crosses the warning threshold set in Basics.

Positioning any gauge:

Assign to any of the 4 pages — put everything on one page, or spread across all four
X = left to right, Y = top to bottom (measured from the gauge’s top‑left corner, in pixels)
Face size setting (values under 50px start to look cramped)
Resize All Gauge Faces — bulk tool to apply one size across the board
Reset — factory reset for every gauge’s position and size (⚠️ cannot be undone)

Live Screen Editing applies here too — watch a gauge move and resize in real time as you adjust it.

Radio

Radio can stay active while in AP mode, but reliability depends on how many screens are running at once — for the most stable experience, keep only the AP live screen on and disable everything else while configuring.

Master Radio Status: shows whether radio is active.

Radio Mode: Off / FastLink / LoRa — only one mode runs at a time; they aren’t used together.

Mode	Speed	Range
FastLink	Higher speed	Mid‑range
LoRa	Lower speed	Long‑range

FastLink Settings

Channel: US 1–11 (pick a quiet channel if you notice interference)
TX Power: adjustable — higher power can increase noise or cause instability, especially with multiple screens active
Long‑Range (LR) toggle: extended‑range mode — check your local regulations before enabling

LoRa Settings

Region: US (902–928 MHz), EU (863–870 MHz), or Custom
Center Frequency: US 915.0 MHz; EU 869.5 MHz is a common choice
Bandwidth: EU typically 125/250 kHz; US may use 500 kHz
TX Power: adjustable
⚠️ Never transmit without a properly matched antenna connected

Quick band reference

Region	Band	Notes
US (FCC)	902–928 MHz ISM	500 kHz permitted
EU (RED)	863–870 MHz	Sub‑bands: 868.0–868.6, 868.7–869.2, 869.4–869.65 MHz. 869.5 MHz is a common EU selection.

You’re responsible for confirming frequency, power, and duty‑cycle compliance for your region.

LoRa support is present and functional but still lightly used compared to FastLink — we’re always looking for radar testers if you fly or drive in a group (see Section 13).

Ground

Settings specific to ground‑vehicle dashboards:

Speed units: MPH / KMH / Knots
Speed scale multiplier: makes GPS speed feel like full‑scale speed on a smaller RC vehicle
G‑force meter multiplier: amplifies the accelerometer reading shown on WebDash’s G‑force meter — higher values = more sensitive to small movements; 1 = true G‑force
Theme colors: Track Dash, Inclinometer, Ground Radar
RC channel mapping for throttle: invert option + throttle‑bottom trim (for reverse/mid‑point calibration)
Steering Channel: MSP/MAVLink only — reads the channel your flight controller reports rather than a dedicated board input (a future board revision may add direct steering input)

Advanced

Home for transmitter‑channel assignments that don’t happen automatically anywhere else: flaps, gear, steering (where applicable), radar range scaling, screen select, and role select. All must be manually assigned to a channel here if you want to use them.

Board Orientation

Applies across every telemetry mode
Covers roll/pitch/yaw (0/90/180/270), pitch/roll trim offset, and per‑axis invert options
No on‑board indicator of “default” orientation — as a reference, default is with the KAIRUHS logo facing up and the pin‑header side of the IMU sensor board facing forward
Getting this wrong makes the AHI unstable — the clearest sign is the AHI immediately rolling over right after boot

Radio Slave and GC7 — covered in full in Section 7.

Display Speed and Screen Management

Enable/disable individual screen ports — anywhere from a full 4‑screen setup down to a single screen optimized for speed
Refresh speed options:

Speed	Notes
16 MHz	Most stable
20 MHz
27 MHz
40 MHz
80 MHz	Fastest, most sensitive to setup

Allowed Roles Per Screen

Controls which roles are available when cycling screens via your transmitter
Useful for skipping certain roles during in‑air/on‑the‑move switching
If a screen isn’t showing the role you expect, check here first — it may be disabled for that screen

Simulation — populate radar with simulated targets for testing/demo purposes, without needing another live board nearby.

Setting	Function
Sim Enabled (0/1)	Master toggle
Spawn Chance %	Probability of a new simulated target appearing per tick
Max Sims on Radar	Cap on concurrent simulated targets
Pursuers Enabled (0/1)	Allows chase‑style logic
Pursuer Chance %	Probability a new sim spawns as a pursuer
Friendly Pursuer %	How often a pursuer is friendly rather than hostile
Pursuit Aggressiveness (1–10)	How tightly pursuers turn and close distance
Follow Distance (ft)	Nominal pursuit spacing
Min/Max Chase Speed (ft/s)	Speed band for pursuit logic
Vertical Gain (ft/s per ft)	Climb/sink response to altitude error
Show Sims Mode	Filter: All / Friendly / Hostile / None

Battery Telemetry Settings

Improved for more proportional, accurate amp and voltage readings
Old amp/volt offset fields removed — a properly calibrated board doesn’t need them
Includes a warning debug/test option that previews warning overlays without needing the vehicle armed (warnings normally only display in an armed state)

Telemetry

Live, real‑time readout of everything the system is currently receiving:

roll · pitch · heading · altitude · climb rate · ground speed · total & per‑cell voltage · cell count · current · power · battery percentage · RSSI · GPS lat/long/altitude · satellite count · GPS fix status · arm state · active telemetry mode · throttle percentage · flap position · gear position · radar range · system mode

Great first stop if something looks off and you want to confirm what data the board is actually receiving.

Backup

Export your entire configuration to a file, save it, and re‑import later
Restore a previous configuration from a saved file
Genuinely worth using before any large batch of changes, or before a firmware update

WebDash Tab

Covered in full in Section 6.

Manual Tab

An in‑progress, in‑UI version of this manual for quick reference without leaving the config page.

5. Screen Roles

Every role uses the same underlying telemetry data, just laid out differently.

Category	Applies to
Air roles	Square or portrait orientation
Ground roles	Landscape orientation
Thermal	Works in either orientation (available as both an Air and Ground role)

Air roles: PFD, MFD, HUD, Air Radar, Thermal, Gauges Pages 1–4

Page 4 adds a monochrome AHI, gear indicator, flaps gauge, and battery voltage gauge to the usual gauge set.

Ground roles: Thermal, Inclinometer, Track Dash 1–3, Street Dash 1–3, Ground Gauges, Radio, License Plate, Ground Radar, GPS Navigation (Static)

Newer / less obvious roles:

Thermal — Speed, altitude, heading, satellite count up top; bar gauge + live temperature reading in the middle alongside your warning threshold line; history graph tracking temperature over the session. Threshold line timing and history graph interval are adjustable from Thermal Settings (Basics). Requires a temperature probe (solder‑on accessory); works regardless of system mode.
Inclinometer — Compass + roll/pitch attitude display. Genuinely useful for off‑road or crawling.
GPS Navigation (Static) — Simple, non‑scrolling GPS readout, not a moving map.
Track Dash 3 — Motorsport‑cluster inspired. Shows RPM (from throttle), speed, heading, satellite count, arm status/timer, voltage, current, throttle position, temperature.
Street Dash 1 — Subaru‑inspired classic look. RPM, speed, temperature, fuel gauge (from voltage).
Street Dash 2 — BMW E36‑inspired. Fuel (from voltage), speed, RPM, temperature.
Street Dash 3 — Nissan 300ZX‑inspired, most feature‑rich. Turn signals (from steering channel), GPS‑based speed, fuel (from battery voltage), RPM, probe temperature, current draw, battery voltage; mph or kph. Also available in WebDash.

All roles support customizable colors.

6. WebDash

WebDash turns any phone, tablet, laptop, or other browser‑capable device into an additional live screen — no extra hardware required. Anything that can connect to your board’s network and open a browser can display it; it can even be cast to a larger screen.

Dashboard layouts:

Street Dash 3 — mirrors the 300ZX‑inspired ground dash: turn signals (steering channel), GPS speed, fuel (voltage), RPM, probe temperature, current draw, battery voltage. mph/kph switch, fullscreen mode, zoom control.
Street Gauges — simple layout: voltage + temperature with a warning lamp, plus a fuel gauge derived from voltage.
Motorsport Dash — most detailed option:
- RPM bar gauges across the top, steering position bar beneath them
- Center: speed, prominently displayed
- Side info boxes: voltage / cell count / cell voltage (one side); board link status / satellite count / temperature (other side)
- Run timer and lap counter (dedicated lap‑timing support coming, likely before GC7, no confirmed date)
- Bottom status bar flags: low cell voltage, high current draw, braking, redline, high temperature, arm state — flashes red when a threshold is crossed
RPM/Speed cluster layout — traditional cluster with side gauges for temperature and voltage
Center speed gauge layout — large center speed gauge with G‑force and heading gauges to the side

Both simpler gauge layouts are designed to look good on a phone screen, and since they run in‑browser, they can be screen‑recorded and overlaid on your own flight or drive footage for a video‑game‑style HUD effect.

Convenience options:

Always Boot Into AP Config — skips the BOOT‑button step, puts you straight into config mode with WebDash reachable on every power‑up (useful if you mainly use WebDash)
Unlock Enabled Screens — bypasses the “one live screen at a time” AP‑mode rule; every enabled screen port renders at once, even while technically still in AP mode.
- Use case: running WebDash on a sim wheel stand or under‑dash display while your car/rig’s own physical screens stay active elsewhere
- Works well as long as you don’t navigate away from WebDash after enabling it — the page should already be loaded and ready
- ⚠️ Always defaults back to off on every boot, for safety

⚠️ Running radio and WebDash together at the same time hasn’t been fully validated yet — treat that combination as experimental.

🚧 WebDash is still in active development. You may occasionally see a page fail to load or a brief connection drop. This doesn’t affect other screens or settings — just reboot into AP mode and reconnect. Feedback on anything unusual is welcome.

7. Radar, Radio Slave & GC7

Radar gives real‑time position tracking of any other KAIRUHS board within range — aircraft, car, or anything else.

Works over FastLink (higher speed, mid‑range) or LoRa (longer range, lower speed) — set your preference in the Radio tab
Available in Air layout (circular display) and Ground layout (landscape grid)

INAV Radar & ADS‑B

On INAV, KAIRUHS radar data can be injected directly into your flight controller — tracked targets also show up on your INAV OSD, not just your KAIRUHS screens
Basic ADS‑B receiver support: lets real‑world aircraft appear alongside simulated and other KAIRUHS targets. Newer feature, not fully field‑validated — treat as a helpful bonus, not a primary safety input, for now

Radio Slave (separate concept from GC7)

Any KAIRUHS main board can be put into slave mode and wirelessly paired, over radio, to a GC7 screen
Once paired, the slave board receives and mirrors all radio telemetry back to the GC7 — acting as a range extender
Use case: pair GC7 to a slave board, and it relays telemetry from a main board that’s much farther out
If the GC7 doesn’t pair with a radio slave, it simply acts as its own station and shows that board’s own local data

GC7

Larger companion display, currently in development
Intended for scoring overlays, ATC‑style readouts, radar screens, and sim‑wheel dashboards
Has its own onboard radar functionality — can see every KAIRUHS board nearby on a bigger screen
Uses the Radio Slave concept above for extended reach

Tested range: ground‑to‑air links using slave/relay setups have reached over 1500 feet; ground‑to‑ground tends to fall short of that, especially with onboard antennas.

8. Standalone Mode

Lets the board operate without a flight controller, using its own onboard sensor module:

BMP388 barometer
ICM‑20948 6‑axis IMU

On its own, Standalone mode provides: altitude, heading, attitude, G‑force. Add the optional battery telemetry board for: current and voltage as well.

🔁 Standalone hardware doesn’t restrict you to running without a flight controller. A board with the factory‑installed Standalone IMU can still connect to a flight controller and run on MSP or MAVLink just like a standard board — use FC telemetry, the onboard sensors, or switch between the two as needed.

To get the most out of Standalone mode:

GPS module → GPS port — an M10‑class module in the 250 size (e.g. Foxeer, GEPRC) plugs in directly. ⚠️ Verify wiring before powering.
Throttle PWM cable → PWM port, for throttle position

Power sources (use only ONE at a time):

Flight‑controller port
Rear solder pads
PWM port
USB

⚠️ If powering through anything other than the PWM port while the PWM cable is still connected, remove its 5V pin first to avoid a conflict.

On boot: Standalone mode runs a short sensor calibration before settling in. If the AHI rolls over immediately instead of sitting level, double‑check Board Orientation under Advanced — it must match how the board is physically mounted.

9. Flight Controller Integration (MAVLink / MSP)

Requires a flight controller for MSP or MAVLink modes.

Connector: 6‑pin JST‑GH UART port — true plug‑and‑play with FCs that already expose the same connector (e.g. SpeedyBee F405)
Many FCs don’t include a JST‑GH port — solder pads on the back of the board give you a direct wired option regardless of connector type

UART wiring (solder pads) — standard color/pin assignment:

Wire	Function
Green	→ FC RX (connects to your flight controller’s TX)
Yellow	→ FC TX (connects to your flight controller’s RX)
Red	→ +5V
Black	→ GND

Wiring checklist:

✅ TX and RX crossed correctly (board’s TX → FC’s RX, and vice versa)
✅ Ground connected along with both data lines
✅ FC’s UART baud rate set to 115200 for either protocol
✅ FC’s UART set to output the matching protocol (MSP or MAVLink) in its own configurator

Protocol notes:

INAV 8 or 9: use MSP — MAVLink has proven unreliable on these versions
Other FC firmware: results vary; MSP is becoming the more consistent standard generally — worth trying if MAVLink looks inconsistent
ArduPilot: used successfully
Betaflight: not yet confirmed
Inverted axes on AHI/HUD, regardless of protocol → check Board Orientation under Advanced

10. Battery Telemetry Board

Sits inline between your battery and your RC vehicle — roughly the size of a small ESC
Rated up to: 100 amps, 2–6S — ⚠️ exceeding either limit will damage the board
Provides dedicated 5V power to the main board and screens
Reports current and voltage back to the main board for display
Runs no firmware of its own and is never flashed/updated independently — all firmware updates happen on the main board

Calibration & swapping:

Each board is factory‑calibrated and paired to your specific main board
Swapping boards? Save your calibration settings first — a replacement board needs those values re‑entered (or a manual recalibration with an amp/volt meter) to read accurately again
Bought one separately? We’ll email you its factory values — entry instructions live on the Advanced tab, step by step

11. Troubleshooting

Symptom	Cause / Fix
No MAVLink/MSP data	Check TX/RX aren’t reversed · confirm FC’s UART outputs the correct protocol at 115200 baud · confirm ground is connected with the data lines · if MAVLink is failing, try MSP (and vice versa)
No radar targets showing	Confirm radio is enabled and set to the same mode (FastLink or LoRa) as other pilots/drivers · confirm channel matches (default is channel 1) · confirm region and bandwidth match · check your visibility filter · confirm antenna is properly connected — never run radio without an antenna
Screen or radar display looks unresponsive/stuck	Usually the wrong telemetry protocol is selected — check the Basics tab
Blank display	One of three causes: (1) that port isn’t enabled — ports beyond your kit’s included count ship disabled by default; (2) the assigned role has been excluded from cycling; (3) the board is in AP mode, which only renders one screen at a time unless Unlock Enabled Screens is active
Missing pitch ladder/speed tape, offset layouts, or a static‑looking dashboard background	Almost always a mismatched screen size setting — go to Basics and confirm the selected screen size matches the physical screen on that port

12. Firmware Updates, Backup & Restore

Before You Flash — Read This

Recommended tool: Kairuhs Board Tools (our official flashing app)

Writes firmware to the correct location automatically
Preserves your existing configuration — no reconfiguring needed afterward
Download: https://drive.google.com/file/d/1p3MiyOxArNQyHqr0J3go2DttgAHa1rO5/view?usp=drive_link

If using the older NodeMCU PyFlasher tool instead:

PyFlasher writes firmware starting at a fixed address, with no custom‑offset option
Most .bin files we provide are built to skip past the bootloader/saved‑settings region — this only works correctly via Board Tools
If you must use PyFlasher, you need the merged.bin file specifically — the only version built to flash correctly at PyFlasher’s fixed address
⚠️ Using a standard (non‑merged) .bin with PyFlasher writes firmware to the wrong location and can brick your board — usually shows up as a white screen on boot that doesn’t resolve even after re‑flashing

Need the latest firmware file, or running into trouble? Contact support@kairuhshq.com and specify whether you’re using Board Tools or PyFlasher so we can send the correct file.

Updating Firmware — Legacy PyFlasher Method

No longer the recommended path — use Board Tools if you can.

You’ll need:

Your KAIRUHS board
A USB‑C cable
A Windows or Mac computer
The correct firmware file for PyFlasher (the merged.bin — contact us to get it)
NodeMCU PyFlasher (free): https://github.com/marcelstoer/nodemcu-pyflasher/releases

⚠️ Use caution while flashing — an interrupted install can brick the board.

Hold BOOT, then plug in. While holding BOOT on the board, connect it to your computer via USB‑C.
Confirm the serial port. On Windows, open Device Manager and confirm a new COM port appears (e.g. COM8) — confirms the board is in serial bootloader mode.
Open PyFlasher and set it up:
- Serial Port: your board’s COM port
- Baud Rate: 115200
- Firmware: the merged.bin file
- Flash Mode: DIO
- Erase Flash: yes (recommended for a clean update)
- Click Flash NodeMCU
Wait for it to finish. Takes a little over a minute — look for “Done” or “Hard resetting…” in the log.
Disconnect and reboot. Unplug USB‑C, reconnect power normally (USB or 5V from your flight controller). Board boots into the updated firmware.

Check your current firmware version any time by powering on the board and watching the boot screen — the version number appears briefly on startup.

Backup & Restore

Export a full backup of your configuration as a file, any time, from the Backup tab
Restore from that file later if needed
Works cleanly every time — genuinely worth doing before any firmware update or a large batch of setting changes

13. Support & Community

Channel	Link
Email	support@kairuhshq.com (previous address kairuhsconsole@gmail.com still works too)
Facebook Page	https://www.facebook.com/KairuhsHQ/
Facebook Group	https://www.facebook.com/groups/1231576258453632/
Instagram	https://www.instagram.com/kairuhshq/
TikTok	https://www.tiktok.com/@kairuhshq
YouTube	https://www.youtube.com/@Kairuhshq
Thingiverse	https://www.thingiverse.com/kairuhshq/designs

We’re always open to requests for new screen layouts, dashboard styles, or features — send your ideas along with build photos or footage of your setup in action, and we may feature it or build it into a future update.

We’re also actively looking for radar testers. If you regularly fly or drive alongside other KAIRUHS users, especially over longer distances, real‑world feedback on radar and LoRa performance is some of the most valuable data we can get — reach out if you’re interested.

Thanks for flying KAIRUHS. Fly low. Fly fast. Fly smart.