Two-Way Radio Simulation

Simulated two-way radio with an instructor (controller) handset and a student (field) handset/display. Channel switching mimics the real-world distinction between dispatch, hospital-direct, and tactical frequencies. Students push-to-talk; instructors play different roles on different channels (dispatcher, ED charge nurse, IC, medical control). Components to build: - Radio display (student side): channel name, signal indicator, last-traffic timestamp, PTT button, mimics a real handset/console - Channel list: Dispatch, Hospital 1, Hospital 2, Tac 1, Tac 2, Med Channel, etc. Configurable per session - PTT (push-to-talk): browser microphone capture, transmits to anyone on the same channel - Controller voice: instructor speaks as dispatcher, ED charge nurse, IC, medical control, switching channels to play different roles - Recording: every transmission logged with timestamp, channel, speaker - powerful for debrief - Selective audibility: students on Tac 1 do not hear Hospital 2 traffic - Optional radio reception artifacts: static, breakup, key-up tones (skinnable) - Async/text fallback: type your transmission, others see it as a transcribed radio call Key engineering challenges: - WebRTC for live voice adds infrastructure (TURN servers, signaling) - a real complexity jump from TMA's current state - Latency and quality: bad radio sim is worse than no radio sim - Bandwidth and hosting cost: voice is expensive at scale; TMA is free forever so this needs a sustainability plan - Browser permissions: microphone access prompts, iOS Safari quirks, classroom IT policies that block WebRTC Strategic note: real radio comms training is a major gap in EMS education with almost no free tools addressing it. However this is the most engineering-heavy and cost-heavy feature in the v2/v3 brainstorm and most clearly redefines what TMA is. Recommended sequencing: ship Reference Library first, then Mini CAD, then Two-Way Radio - giving the positioning question time to resolve and validating demand before the largest investment. Open questions before spec: voice (live WebRTC) vs async/text vs hybrid; hosting cost projection at concurrency; integration with CAD or independent ship; radio procedure scope (US EMS / UK ambulance / generic); browser audio compatibility audit.

Share update with 0 linked conversations as well

Upvoters
Status

Backlog

Board
πŸ’‘

Feature Request

Date

1 day ago

Subscribe to post

Get notified by email when there are changes.