Guided link check (listens only, sends nothing)
- Plug the USB-RS232 adapter (genuine FTDI preferred) into this laptop. Use Connect hardware above and pick it in the browser's port chooser; or press Use virtual Eagle 754 to rehearse without hardware.
- Cable: the ventilator's 9-pin female port is on the side of the AC power supply module. Pin 2 = vent Send, pin 3 = vent Receive, pin 5 = Ground. Plug the adapter's DB9 male straight in, or use a straight-through M-F cable (not a null-modem). Connect the supply to the EXTERNAL POWER jack and to mains: the port is dead on battery.
- Fit a test lung. Turn MODE from OFF to A/C; the unit self-checks and starts cycling. MUTE silences the PM advisory tone.
- Press Listen. The dashboard listens at the selected baud for 8 s, then tries the other rates if needed, and tells you whether the two frame cadences from the OEM manual (pressure every 100 ms, status every 1 s) are present.
- Squeeze the test lung on the Monitor tab: the pressure trace should follow the bar graph. Then follow the Service procedure (Routes A/B/C).
Live monitor
Pressure trace (heuristic: the fastest-changing byte of the 100 ms frame). Squeeze the test lung to confirm.
Offline analysis of a capture file
Accepts captures from this dashboard or from the Python toolkit (same JSON Lines format).
No capture loaded.
Record one OEM CAL.EXE session and learn the commands
Topology: OEM PC ⇄ (second USB adapter, null-modem to the PC) ⇄ this dashboard ⇄ (first adapter) ⇄ ventilator. Everything is forwarded both ways and logged. Press a marker before each OEM key: init (connect), hold (F5), rtc_reset (F3), release (F5), exit (F10).
No session recorded.
PM advisory reset (Hold → Reset RTC → Release)
Checks the stream is live, sends hold and verifies the stream stops, asks you to confirm FACTORY CALIBRATION on the LCD, sends the reset, sends release and waits for the stream. On any problem it releases the unit only when the line shows it is really held. Afterwards: MODE → CAL, then USER PROGRAMS should show 0 Hrs / 0 Dys.
Load commands.json (from the Bridge tab or the Python toolkit).
Probe for command bytes (no OEM software)
No probe run.
Analyzer emulator for the OEM program (RT-200 / Model 100)
Opens a second serial port (the one the OEM program expects the analyzer on) and answers its requests. Rules come from the toolkit's rule files; unknown requests are logged so the rules can be extended after the first run.
Stopped.
Self-tests (run in this browser against the virtual Eagle 754)
| Test | Result | ms | Detail |
|---|
How this fits together
This page is the browser edition of the eagle754 Python toolkit. It uses the browser's Web Serial API (Chrome, Edge, Opera on Windows/macOS/Linux/ChromeOS) to talk to a USB-RS232 adapter after you click to allow it. Firefox and Safari do not support Web Serial; use the Python toolkit there.
- Connect wizard and Monitor confirm the link using the OEM manual's description of the stream (2400/1200 baud, 8N1; status every 1 s, pressure every 100 ms).
- Analyze recovers frame structure and checksums from a capture; files are interchangeable with the Python toolkit.
- Bridge & learn records an OEM CAL.EXE session (second adapter) and extracts hold / rtc_reset / release into
commands.json. - PM reset replays those commands with the same safety logic as the Python toolkit; download the service log for the unit's record.
- Probe and Analyzer emulator cover the no-OEM-software route and the OEM program's analyzer requirement.
- Tests run the algorithm and safety tests against the virtual unit; use them to verify a browser before bench work.
Full procedure, hardware notes, safety and sources: Service procedure · Hardware · Safety · OEM capture · Source.
Nothing leaves this browser: no data is uploaded anywhere. Captures and logs are downloaded to your computer when you ask.