first attempt at radioradar
This commit is contained in:
@@ -9,6 +9,7 @@ Available models:
|
||||
librevna
|
||||
librevna_multi
|
||||
compact_m_k209
|
||||
kamil_adc
|
||||
```
|
||||
|
||||
Example configs in the repository root:
|
||||
@@ -18,6 +19,7 @@ run_config_librevna.example.json
|
||||
run_config_librevna_multi.example.json
|
||||
run_config_compact_m_k209.example.json
|
||||
run_config_compact_m_k209_local_mock_switches.example.json
|
||||
run_config_kamil_adc.example.json
|
||||
run_config_simulator.example.json
|
||||
```
|
||||
|
||||
@@ -47,6 +49,7 @@ The GUI process supervisor starts the correct producer automatically:
|
||||
- `librevna` -> `build/bin/sweep_orchestrator`
|
||||
- `compact_m_k209` -> `build/bin/sweep_orchestrator`
|
||||
- `librevna_multi` -> `python_app.scripts.multi_device_raw_producer`
|
||||
- `kamil_adc` -> `python_app.scripts.kamil_adc_raw_producer`
|
||||
|
||||
## Pure Simulator
|
||||
|
||||
@@ -220,6 +223,63 @@ For a command-line connection check from the Raspberry Pi:
|
||||
|
||||
The Raspberry Pi does not need S2VNA or NI-VISA in this remote mode.
|
||||
|
||||
## Kamil ADC With Laser Control
|
||||
|
||||
Use this mode for the ADC collector from `/home/europa/Documents/kamil_adc`
|
||||
and the laser board configured through `laser_control`. The external
|
||||
`kamil_adc` project is not modified by `radar_system`; the producer launches
|
||||
the configured executable and reads its TTY stream.
|
||||
|
||||
Config:
|
||||
|
||||
```json
|
||||
"radar": {
|
||||
"model": "kamil_adc",
|
||||
"serial": "kamil_adc",
|
||||
"driver_mode": "native",
|
||||
"kamil_adc": {
|
||||
"project_dir": "/home/europa/Documents/kamil_adc",
|
||||
"executable_path": "/home/europa/Documents/kamil_adc/kamil_adc_capture",
|
||||
"tty_path": "/tmp/ttyADC_data",
|
||||
"args": [
|
||||
"profile:phase",
|
||||
"clock:internal",
|
||||
"internal_ref_hz:2000000",
|
||||
"mode:diff",
|
||||
"channels:2",
|
||||
"ch1:2",
|
||||
"ch2:3",
|
||||
"do1_toggle_per_frame",
|
||||
"do1_pair_subtract_avg"
|
||||
]
|
||||
},
|
||||
"laser_control": {
|
||||
"enabled": true,
|
||||
"port": "/dev/ttyUSB0",
|
||||
"mode": "variation"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
Notes:
|
||||
|
||||
- `executable_path` is mandatory and must name the real Raspberry Pi binary.
|
||||
- The producer appends `tty:<tty_path>` automatically; do not put `tty:` in
|
||||
`radar.kamil_adc.args`.
|
||||
- The laser-control driver is vendored under `python_app.hardware_full.laser_control`.
|
||||
- `laser_control` and `kamil_adc` are treated as one hardware configuration.
|
||||
Changing either section requires restarting acquisition so the lasers are
|
||||
configured before the ADC collector starts.
|
||||
- The TTY frame `0x000A step data1 data2` is imported as `S21 = data1 + j*data2`.
|
||||
`S11` is filled with explicit zeros.
|
||||
|
||||
Manual raw-producer run:
|
||||
|
||||
```bash
|
||||
.venv/bin/python -m python_app.scripts.kamil_adc_raw_producer \
|
||||
--config run_config_kamil_adc.example.json
|
||||
```
|
||||
|
||||
## K209 Remote Performance
|
||||
|
||||
The remote K209 path keeps one persistent TCP connection open. Configuration
|
||||
|
||||
Reference in New Issue
Block a user