https://orca.hisnr.com/docs/radar/sdr-interface/Recent content in Radar Code on Open Radar Code ArchitectureHugoenhttps://orca.hisnr.com/docs/radar/sdr-interface/config/Mon, 01 Jan 0001 00:00:00 +0000https://orca.hisnr.com/docs/radar/sdr-interface/config/<p>The entire configuration that controls the radar is defined in a single configuration file. This file is provided at runtime to <code>run.py</code> and encapsulates all of the settings needed to run various experiments on different hardware setups. Configuration files are specified in the YAML format and contained in the <code>config/</code> folder of the ORCA repository. Default configuration files are included to run the code on a B205mini-i (<code>default_b205.yaml1</code>) and on an X310 (<code>default_x310.yaml</code>). Here we explain the basics behind the settings available to the user via the config file.</p>https://orca.hisnr.com/docs/radar/sdr-interface/host-interface/Mon, 01 Jan 0001 00:00:00 +0000https://orca.hisnr.com/docs/radar/sdr-interface/host-interface/<p>The maximum duty cycle you can achieve is a function of the SDR you use, the host computer, and the bandwidth you need. This page outlines suggestions for how to figure out an achievable duty cycle and what parameters can be tweaked to maximize this.</p> <h2 id="general-process-for-benchmarking-duty-cycle">General process for benchmarking duty cycle</h2> <h3 id="determine-the-maximum-achievable-bandwidth-with-benchmark_rate">Determine the maximum achievable bandwidth with benchmark_rate</h3> <p>Use the USRP example benchmark_rate program (located at <code>&lt;path to conda install&gt;/envs/&lt;uhd environment name&gt;/lib/uhd/examples</code>) to determine the approximate maximum duty cycle you can achieve. For instance, with a Pi 4 and b205mini, I can reach about a 25% duty cycle &ndash; defined as sample rate divided by desired sample rate (14 Msps / 56 Msps in this case) &ndash; while consistently getting 0 dropped packets.</p>