Running goesrecv on beaglebone black wireless board #116
Comments
|
In case it is helpful, here are a few lines from the Pi captured this morning: |
{{ message }}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a goes receiver setup temporarily and working. There is a grid dish pointed in the right direction and I have both goesrecv and goesproc running on a raspberry Pi4. At the base of the dish I have a USB hub that connects to the nesdr smartTee and the SAWbird+GOES LNA. Inside the house I have a Pi4 connected to a long USB cable running out the window to the USB hub. It is getting towards winter and I will not be able to run the USB cable out the window. The window is a double hung window and needs to be as sealed against the weather as possible. What I would like to work towards is having goesrecv running on a beaglebone black wireless board which will be mounted at the dish in a large PVC pipe with 12V and ground run to the enclosure and a small buck-boost switching regulator to provide 5V to the beagle and the LNA, with goesproc running on the Pi4 indoors. I was able to build and install goestools on the beagle. When I first start goesrecv on the beagle, the first 2 or so lines reflect dropped packets, the next 4 or so appear to be properly received with no errors, then as the normalized gain increases packets start getting dropped. Initially I though the normalized gain was an issue somehow so I tried limiting it in the code and recompilling/installing. The limit worked, but packets still ended up being dropped. Here is a the beginning of a capture on the beagle with the goesrecv code untouched:
<debian@BeagleDish:~$ goesrecv -v -i 1 -c ~/goesrecv.conf
Found Rafael Micro R820T tuner
Disabled direct sampling mode
[R82XX] PLL not locked!
Exact sample rate is: 2000000.052982 Hz
Allocating 15 zero-copy buffers
2021-10-10T23:17:47Z [monitor] gain: 3.11, freq: 11.6, omega: 2.158, vit(avg): 1402, rs(sum): 0, packets: 0, drops: 5
2021-10-10T23:17:48Z [monitor] gain: 6.45, freq: 462.2, omega: 2.157, vit(avg): 602, rs(sum): 9, packets: 11, drops: 4
2021-10-10T23:17:49Z [monitor] gain: 9.62, freq: 531.0, omega: 2.157, vit(avg): 310, rs(sum): 0, packets: 15, drops: 0
2021-10-10T23:17:50Z [monitor] gain: 11.89, freq: 504.8, omega: 2.158, vit(avg): 311, rs(sum): 6, packets: 17, drops: 0
2021-10-10T23:17:51Z [monitor] gain: 13.35, freq: 520.1, omega: 2.157, vit(avg): 317, rs(sum): 17, packets: 16, drops: 0
2021-10-10T23:17:52Z [monitor] gain: 14.24, freq: 527.7, omega: 2.158, vit(avg): 313, rs(sum): 22, packets: 16, drops: 0
2021-10-10T23:17:53Z [monitor] gain: 14.81, freq: 490.1, omega: 2.157, vit(avg): 443, rs(sum): 10, packets: 11, drops: 4
2021-10-10T23:17:54Z [monitor] gain: 15.13, freq: 541.0, omega: 2.157, vit(avg): 391, rs(sum): 8, packets: 9, drops: 5
2021-10-10T23:17:55Z [monitor] gain: 15.35, freq: 538.1, omega: 2.157, vit(avg): 324, rs(sum): 12, packets: 9, drops: 5
2021-10-10T23:17:56Z [monitor] gain: 15.53, freq: 501.2, omega: 2.157, vit(avg): 631, rs(sum): 17, packets: 9, drops: 4
2021-10-10T23:17:57Z [monitor] gain: 15.63, freq: 514.6, omega: 2.157, vit(avg): 351, rs(sum): 26, packets: 11, drops: 5
2021-10-10T23:17:58Z [monitor] gain: 15.70, freq: 534.9, omega: 2.157, vit(avg): 605, rs(sum): 18, packets: 9, drops: 4
2021-10-10T23:17:59Z [monitor] gain: 15.73, freq: 517.1, omega: 2.158, vit(avg): 613, rs(sum): 14, packets: 11, drops: 5
2021-10-10T23:18:00Z [monitor] gain: 15.75, freq: 520.4, omega: 2.158, vit(avg): 620, rs(sum): 26, packets: 11, drops: 4
2021-10-10T23:18:01Z [monitor] gain: 15.77, freq: 490.1, omega: 2.158, vit(avg): 490, rs(sum): 13, packets: 10, drops: 5
2021-10-10T23:18:02Z [monitor] gain: 15.76, freq: 516.2, omega: 2.157, vit(avg): 476, rs(sum): 17, packets: 12, drops: 4
2021-10-10T23:18:03Z [monitor] gain: 15.77, freq: 510.8, omega: 2.157, vit(avg): 614, rs(sum): 16, packets: 10, drops: 5
2021-10-10T23:18:04Z [monitor] gain: 15.78, freq: 494.0, omega: 2.158, vit(avg): 633, rs(sum): 27, packets: 11, drops: 4
2021-10-10T23:18:05Z [monitor] gain: 15.79, freq: 528.1, omega: 2.157, vit(avg): 508, rs(sum): 25, packets: 9, drops: 5
2021-10-10T23:18:06Z [monitor] gain: 15.77, freq: 533.0, omega: 2.157, vit(avg): 573, rs(sum): 24, packets: 11, drops: 4
2021-10-10T23:18:07Z [monitor] gain: 15.78, freq: 523.5, omega: 2.158, vit(avg): 639, rs(sum): 14, packets: 11, drops: 4
2021-10-10T23:18:08Z [monitor] gain: 15.78, freq: 504.2, omega: 2.157, vit(avg): 609, rs(sum): 23, packets: 10, drops: 5
2021-10-10T23:18:09Z [monitor] gain: 15.78, freq: 481.8, omega: 2.157, vit(avg): 590, rs(sum): 24, packets: 11, drops: 4>
If I have goesproc running on the Pi, for the lines that have 0 dropped packets it appears goesproc is accumulating packets to write an image, then once the drops start happening goesproc starts giving errors. Oddly on the beagleboard, if I limit the processor speed to 300MHz there are a lot more lines with 0 dropped packets.
I have copied the config file from the Pi to the beagle.
If someone could advise me as to what is going wrong I would appreciate it. I would really like to use the beagle in this application-it runs a lot cooler than a pi, and it draws 1/3 the power a pi does. Also networking on the beagle is a lot more robust than on the pi, the beagle has wire antennas that provide a bit more gain. Our house is brick and I don't want to drill a big enough hole in the side to get a USB cable out the wall. In the lower level there is a hole where I have some RG8x cables running out and it has just about enough room to get a small 2 conductor cable through for power and ground.
The text was updated successfully, but these errors were encountered: