tvelliott / charon Goto Github PK

hi,
I have discover your project and looks amazing.

I guess this task is not possible because the adalm pluto processor has limited resources and can't process at higher rates so the 140khz bandwidth is the highest it can achieve without loosing samples.

you have tried to enable the dual core?.

witch part or the code is the more CPU demanding(profiling)?.

if I'm wrong what can it be done to increase it and make it working? a higher sample rate could give you more sub-carriers with same space between them so more bitrate.

Hi,
I tried to build charon with a toolchain based on Vivado 2018.2. It compiles vanilla pluto firmware v0.31 correctly, but there arise several issues when trying to build charon and its custom configured packages (fftw, liquid-dsp, linux-utils).
I propose to update the project to support Vivado 2018.2 and Pluto v0.31, as it as well gets harder and harder to set up a build environment which supports Vivado 2016 and Pluto 0.28.

First of all, great project! Love to see people doing cool things with Pluto.

With regards to some of the carrier offset tuning. It might be useful to just use the CFO estimate (nco_crcf_get_frequency) of the OFDM preamble to tune the XO correction in Pluto. Even with bad packets, this might get you closer.

There is also a little app we use to calibrate the XO with a tone at a known frequency (https://github.com/analogdevicesinc/plutosdr_scripts/blob/master/cal_ad9361.c). You can just run this once so you don't have to guess when setting the XO correction value. You can just use the BIST tones on one Pluto to calibrate against (similar to https://github.com/analogdevicesinc/rfsom-box-gui/blob/master/bin/send_tone.sh).

Hi,

I loaded in the pre-built firmware image. It successfully flashes and the device reboots. Afterwards, I am unable to ping the device with the ip address listed in the config file. Is this a known issue?

Thanks,
Harit