Description
Walking through the docs (https://github.com/open-flight/openflight/blob/main/docs/build/ops243-uart.md)lets you run this script:
uv run python scripts/hardware-test/test_rolling_buffer_persist.py --setup \ --port /dev/ttyAMA0
The following output comes in:
============================================================
Phase 1: Configure & Persist Rolling Buffer Mode
============================================================
Connecting to radar...
Connected on: /dev/ttyAMA0
Transport: UART at 230400 baud (dump ~2.0s)
Firmware: 1.3.0
[1/2] Entering rolling buffer mode and saving (S#12, S=30)...
[RADAR] Entering rolling buffer mode (S#12, S=30)...
[RADAR] Rolling buffer mode ACTIVE (S#12, 30ksps)
[RADAR] Settings saved to persistent memory.
[RADAR] Power cycle the board (unplug USB, wait 3s, replug).
Done — settings saved
[2/2] Disconnecting...
Done
============================================================
ACTION REQUIRED: Power cycle the radar board now!
Disconnect 5V from OPS J3 pin 9, wait 3 seconds, reconnect it.
(No USB cable and no reset line on this wiring — the 5V jumper
is the power cycle. Leave TX/RX and ground connected.)
The LED should come on in rolling buffer mode.
Then run:
uv run python scripts/hardware-test/test_rolling_buffer_persist.py --test
============================================================
After the power cycle you have to run uv run python scripts/hardware-test/test_rolling_buffer_persist.py --test as mentioned. Here the problem starts wit the following output (at the end):
ConnectionError: No OPS243 radar found on USB. If it is wired to the Pi GPIO UART (J3 pins 6/7), pass the port explicitly — e.g. --radar-port /dev/ttyAMA0 — since a raw UART has no USB descriptors to auto-detect.
But you can't use --radar-port as a variable, as mentioned in the usage attention:
usage: test_rolling_buffer_persist.py [-h] [--setup] [--test] [--port PORT] [--baud BAUD] [--pre-trigger PRE_TRIGGER] [--sample-rate SAMPLE_RATE] [--timeout TIMEOUT] test_rolling_buffer_persist.py: error: unrecognized arguments: --radar-port
FIX in error should be to address to:
ConnectionError: No OPS243 radar found on USB. If it is wired to the Pi GPIO UART (J3 pins 6/7), pass the port explicitly — e.g. --port /dev/ttyAMA0 — since a raw UART has no USB descriptors to auto-detect.
Steps to reproduce
See at description
Area
Sound trigger
Hardware setup
No response
Relevant logs or session data
Description
Walking through the docs (https://github.com/open-flight/openflight/blob/main/docs/build/ops243-uart.md)lets you run this script:
uv run python scripts/hardware-test/test_rolling_buffer_persist.py --setup \ --port /dev/ttyAMA0The following output comes in:
After the power cycle you have to run
uv run python scripts/hardware-test/test_rolling_buffer_persist.py --testas mentioned. Here the problem starts wit the following output (at the end):ConnectionError: No OPS243 radar found on USB. If it is wired to the Pi GPIO UART (J3 pins 6/7), pass the port explicitly — e.g. --radar-port /dev/ttyAMA0 — since a raw UART has no USB descriptors to auto-detect.But you can't use --radar-port as a variable, as mentioned in the usage attention:
usage: test_rolling_buffer_persist.py [-h] [--setup] [--test] [--port PORT] [--baud BAUD] [--pre-trigger PRE_TRIGGER] [--sample-rate SAMPLE_RATE] [--timeout TIMEOUT] test_rolling_buffer_persist.py: error: unrecognized arguments: --radar-portFIX in error should be to address to:
ConnectionError: No OPS243 radar found on USB. If it is wired to the Pi GPIO UART (J3 pins 6/7), pass the port explicitly — e.g. --port /dev/ttyAMA0 — since a raw UART has no USB descriptors to auto-detect.Steps to reproduce
See at description
Area
Sound trigger
Hardware setup
No response
Relevant logs or session data