How fy403/webrtc works
This is a low-latency remote-control system for RC vehicles. The principal workflow runs from browser input through WebRTC data channels to RC-frame parsing and motor actuation, with telemetry flowing back; a separate video/audio path streams vehicle media to the browser. Shell access uses its own WebRTC data channel, and signaling coordinates connection setup. The README documents these system-level links; source excerpts show selected receiver pipelines and motor-driver dispatch. Other source relationships are not inferred where the sampled evidence does not establish them.
Main entry points: signaling-server.js Signaling server · webrtc_receiver.cpp WebRTC receiver · data_rtc.js Data channel client · webrtc_publisher.cpp WebRTC publisher
Components 24
Browser control
- Input controllers
web/controller_manager.js - Control curves
web/curve_manager.js - Data channel client
web/data_rtc.js - Video client
web/video_rtc.js - Shell client
web/cmd_rtc.js
WebRTC connectivity
- Signaling server
signaling_server/nodejs/signaling-server.js
Media streaming
- WebRTC publisher
av_track/src/webrtc_publisher.cpp - Audio/video capture
av_track/src/video_capturer.cpp - WebRTC receiver
recv/av_track/src/webrtc_receiver.cpp - Video decode pipeline
recv/av_track/src/video_pipeline.cpp - Virtual camera output
recv/av_track/src/v4l2_output.cpp - Audio decode pipeline
recv/av_track/src/audio_pipeline.cpp - Audio output
recv/av_track/src/pulse_audio_output.cpp
Vehicle control and telemetry
- Control service
data_track/src/main.cpp - RC client
data_track/src/rc_client.cpp - Motor controller
data_track/src/motor_controller.cpp - Motor drivers
data_track/src/crsf_driver.cpp - System telemetry
data_track/src/system_monitor.cpp
Remote services
- Shell service
cmd_track/src/main.cpp - Command execution
cmd_track/src/shell_executor.cpp - MCP protocol
recv/mcp/src/protocol.ts - Device client
recv/mcp/src/device_client.ts
Other components
- Operator
- Vehicle hardware
Connections 24
- Operator → Input controllers: selects input
README.md - Input controllers → Control curves: shapes controls
- Input controllers → Data channel client: sends controls
README.md - Data channel client → Signaling server: exchanges setup
README.md - Video client → Signaling server: exchanges setup
README.md - Shell client → Signaling server: exchanges setup
README.md - WebRTC publisher → Signaling server: exchanges setup
README.md - WebRTC publisher → Audio/video capture: publishes captured media
README.md - WebRTC publisher → Video client: streams media
README.md - Data channel client → RC client: sends RC frames
README.md - RC client → Motor controller: dispatches controls
data_track/src/motor_controller.cpp - Motor controller → Motor drivers: selects driver
data_track/src/motor_controller.cpp - Motor drivers → Vehicle hardware: actuates motors
- RC client → System telemetry: reads status
- System telemetry → Data channel client: returns telemetry
README.md - Shell client → Shell service: sends commands
README.md - Shell service → Command execution: executes commands
- WebRTC receiver → Signaling server: exchanges setup
README.md - Video client → WebRTC receiver: streams RTP
README.md - WebRTC receiver → Video decode pipeline: routes video
- Video decode pipeline → Virtual camera output: writes frames
recv/av_track/src/video_pipeline.cpp - WebRTC receiver → Audio decode pipeline: routes audio
- Audio decode pipeline → Audio output: writes PCM
recv/av_track/src/audio_pipeline.cpp - Device client → MCP protocol: uses protocol
recv/mcp/src/device_client.ts