Before leaving a live session: Stop, confirm idle, and save your files.
CAPTURE / IWR6843AOP
Make every observation count.
Connect your radar, record a session, and review what happened. Your recordings stay on this computer.
HARDWARE PREVIEW · 0.9.0-preview.5
Before you connect · browser support, privacy & saving
Hosted edition · free access · v0.9.0-preview.5
Open directly in desktop Chrome or Edge with Web Serial for USB radar access. Your browser must support Web Serial, run in a secure context and permit device selection; managed devices may restrict access. Other browsers can use compatible local playback and offline tools without USB access. Start here: coverage, setup and limits
Selected recordings, models, configuration files and serial data are processed in your browser; this app does not upload them. Hosting still receives ordinary page requests. Save downloads before reloading. No firmware or private recordings are bundled. The optional camera review uses a bundled, licensed pose model. Source-available No-Resale License · Attribution and third-party notices
01
Choose your firmware workflow
Select the firmware already installed on your board.
Match the firmware already flashed on your board. Changing this selection never flashes, configures or starts the device.
Board and setup downloads · official sources
To use the hosted viewer, you need a desktop/ChromeOS browser with Web Serial and matching firmware already on the board. No SDK or compiler is required for viewing.
TI Radar Toolbox is optional for separate TI demos; it is not required for this original firmware workflow.
mmWave SDK and a matching compiler are developer-only requirements for building firmware.
These are external official downloads. This viewer does not redistribute TI firmware, SDKs or demo configuration files. See downloads and exact requirements.
Connecting, configuring and pairing do not start RF. Start stays locked until the device and session checks pass. Keep control connected, this tab active, and the PC awake.
Supported firmware & required checks
The gate accepts the reviewed 0.3.1-rc1 build abb27b48c1bdb956c0de704b for timed tests and the software-tested 0.3.2-rc1 build 87589b2c32638ae119334c72 for timed or continuous runs, each with self-test version 2. First verify status/ACK and no-RF port pairing; Start remains a separate manual action. Old one-port firmware cannot unlock this preview. A current successful onboard self-test and fault-free idle are required before Configure. Start requires a separate data-port nonce proof and fresh matching control status. Timed tests run for 1–5 seconds. Run until stopped requires the separately identified 0.3.2-rc1 continuous firmware and a healthy control heartbeat. Physical sensing, calibration and activity remain unvalidated.
Connect both radar ports
Choose both interfaces on the same IWR6843AOPEVM: Enhanced is command/status at 115200 baud; Standard is measurement data at 921600 baud. Both are 8N1. The data port is read-only. Connection, configuration and port pairing never start RF.
A control-issued random nonce must be echoed on the data port and confirmed on control before Start. This detects mismatched ports and stale sessions; it is correlation, not authentication. If data is lost during a run, the viewer attempts Stop through control. Keep control connected. Timed tests have a firmware duration cap. In continuous mode, firmware stops if the matching control heartbeat is absent for five seconds. Keep this tab active and the PC awake.
Initial no-RF checkpoint: Query control status → enter and confirm mounting → Configure only → Verify port pairing · no RF → save capture JSON and both raw UART streams → stop for receipt review. Later separately authorized sensing: repeat fresh gates → separate manual Start in the configured mode. Pairing is unavailable until Configure succeeds.
Editable starting values: 1219 mm bracket-top height and 0° tilt; antenna offset stays unknown. Other users must enter their actual measured height and tilt. Defaults are not measurement confirmation or calibration.
Downward tilt is positive; upward tilt is negative. Optional signed vertical antenna offset is relative to bracket top after tilt. Leave it blank if unknown. These inputs are declarations, not phase/axis calibration, and do not enable world height. Staged commands: orConfig 1; profile room64_v1; mount your-measurements; detect 4 30 64 8; session N; commit.
Browser action result
Device replies · control and data diagnostics
Control · parsed device replies
Latest 16 actual decoded control replies. Formatting is for readability; raw bytes are saved separately.
Data · latest matched device JSON
Last matched data probe or admitted frame. This is received device content, not a browser command result.
Guided recording sessions
Plan separate bounded takes. A participant alias is optional for recording and required for training. Prompts describe intended actions, never observed labels. Bounded training captures use 1–5 second takes. Continuous monitoring downloads retain only a diagnostic window. Save each capture; reopen a fresh viewer tab after confirming idle and disconnecting to start a new named session.
No named session prepared. Mounting, firmware, configuration and exact raw bytes remain in the capture.
Keyboard shortcuts outside form fields: W walking, S standing, I sitting, [ transition start, ] end, U undo, M sync marker. Click timing has unknown latency. Camera recording is optional and controlled separately below. No upload is performed.
OPTIONAL / VIDEO + RADAR
Optional camera + radar recording
Choose any camera exposed by your browser, including a built-in or USB camera. Logitech C920e is our test device; other cameras have not been individually verified. Permission is requested only when you find or open a camera. Audio stays off.
No camera opened.
Use the session name above. Choose a local folder and start recording before you configure, pair and start radar. The recording contains video segments, exact received UART bytes and timing records. Video segment boundaries may have gaps; camera and radar clocks are not automatically synchronized.
Camera closed. No recording started.
Recording continues until stopped, while the page, camera and disk remain available. Completed files have hashes; a crash can lose the open segment. A disk or camera failure attempts radar Stop and reports an incomplete recording. Keep this tab active and the PC awake.
Candidate IDs associate radar peaks, not people. IDs are temporary and never a stable human identity. Reflections can split or merge; at most three peaks arrive per frame. No people count or sitting/standing model is available. Motion cues are unvalidated. Sensor coordinates only: phase/axis calibration and physical accuracy remain unverified. The grid is not a room floor; no world height is inferred.
Display: X ±20 m, Y 0–20 m, Z ±20 m. Orthographic sensor coordinates.
Display only: a 20 m view does not establish 20 m detection or human-tracking range. Current room64_v1 search bins cover approximately 0.8–5.9 m; physical human-detection range is unvalidated. RF profile and safety gates are unchanged. Select a nearer range or zoom to inspect close objects. Drag to orbit; wheel/pinch or +/− keys zoom; Home resets the camera.
No candidate tracks.
Unobserved candidates are listed but not plotted. Trails contain measured positions only; no predicted positions are rendered. All processing stays in this browser. Raw captures remain unchanged.
Timestamped human annotations
Click at the observed activity or transition. Host UTC and the latest received sensor timestamp are kept separately; clocks are not synchronized and human timing latency is unknown. Labels remain unreviewed annotations, never inferred activity or ground truth.
KEEP YOUR SESSION
Save locally
Capture JSON keeps exact received bytes as separate labelled control/data base64 streams, timestamps, per-port events/errors, flags and separate annotations. Each JSONL download preserves only that port’s original bytes, including malformed or incomplete lines. The streams are never byte-interleaved into a fictional single UART. Annotations never rewrite sensor records. Unsaved data is lost on reload; the sole persistent browser value is the unconfirmed-stop safety flag. No uploads. Save does not stop the radar.
Drag to orbit · scroll or pinch to zoom · arrow keys to rotate · +/− to zoom · Home to reset. Track IDs are reported by firmware; detection and tracking accuracy are unverified. Display range is a viewport setting, not proof of physical coverage or 20 m human-detection range. This is not a map of the whole house.
Detected point Firmware-reported track · ID labels
Vital signs
Firmware estimates · not medical measurements
No vital-sign samples received in this session.
ORIGINAL APPLICATION / EXPERIMENTAL
Motion Signature Lab
Train your own sitting / walking / standing model from observed labels. The browser features and classifier are original; the current TI demo firmware still supplies points and tracks. This is a research prototype, not a safety or medical system.
No posture is treated as truth automatically. No real-world accuracy has been established. Use one consenting adult in an uncluttered test area. Capture and calibration guide
1 · Verify coordinates and repeatable mounting
Measure floor → flat top of the mounting bracket, just before the mounting screws. Add the signed vertical offset from that surface to the AOP antenna center (+ above, − below). These are measured values, not an exact guarantee. Your existing sensorPosition may already transform tracks; verify points and tracks separately. Unknown coordinates block collection.
World mode means the same floor origin and axes as the calibrated sensor transform. Zero roll and upright mounting are required; verify +X sideways, +Y forward, +Z up. Only this lab applies calibration; the main 3D viewer remains in incoming coordinates.
Not calibrated
2 · Select one target and record observed labels
Select the target you are observing. The geometric gate is not a TI point-to-track assignment; nearby tracks are rejected. A session keeps its role. Stop and restart live listening between independent takes. One continuous capture cannot count as two training sessions or mix training and held-out roles.
Optional observed transition annotations are saved in the complete UART capture. Start-up movement is not automatically walking. These markers are human button timestamps, not detected event boundaries; the three-state model does not classify transitions.
No transition event annotation.
No session. Choose a label only after the person is stably in that state; pause before transitions.
MODEL OUTPUTunknown
No trained model
WINDOW QUALITY
Waiting for setup
3 · Train and independently evaluate
Collect all three labels in at least two independent training sessions and one separate held-out session. Features are standardized using training data only. Scores are heuristics, not calibrated probabilities. Missing or uncertain observations remain unknown.
No held-out evaluation yet.
4 · Record all available UART output
This independent recorder preserves every received UART byte and every decoded frame while active, including classifier-rejected observations. It is board-only serial output, not raw ADC. Arrival timestamps are the computer’s receipt time, not a synchronized sensor acquisition clock. Recording stops visibly at its memory limit; keep captures short and export each take.
No UART capture. Dataset licensing is pending; exports are private by default.
5 · Save your labeled features
Data stays in memory until you explicitly download it. Reloading loses unsaved work. Export includes derived feature windows, observed labels, calibration and session metadata; treat it as private. No server upload or automatic storage. Import replaces current data after confirmation; only import your own trusted capture files. Export is not a raw UART recording.