pothosware / soapyredpitaya

SoapySDR Red Pitaya module

Soapy SDR module for Red Pitaya

Build Status

• Travis:

Dependencies

• SoapySDR - https://github.com/pothosware/SoapySDR/wiki

Documentation

• https://github.com/pothosware/SoapyRedPitaya/wiki

soapyredpitaya's Issues

findSoapyRedPitaya() should find a device when "addr" is present

Even though we may not have automatic discovery, the findSoapyRedPitaya() should still "discover" the red pitaya when the device address is specified. Some client code must be able to find the device through the enumeration API before it will instantiate it.

Ideally the findDevice() call plays an important role of test connecting, adding metadata like serials, filtering based on additional keys, and ultimately returning a set of key/values that are passed to the makeDevice() call; which should be able to make a successful connection.

Two options for findSoapyRedPitaya:

1. The simple: return the args only when "addr" is specified. This may break using the default address of 192.168.1.100 -- not sure if that's important.

2. or more complicated but better: perform a test connection to "addr" and check if its red pitaya before yielding the result. This could also check the default address of 192.168.1.100 as well.

3. or even better, multicast discovery of some sort: #2

findSoapyRedPitaya() device discovery not implemented

There currently isnt a way to discover RedPitayas on a local network. Some drivers require that the user explicitly enter the IP address (Ex addr=192.168.10.100). I put this issue here because it may be worthwhile to implement a discovery multicast/broadcast discovery protocol. Example SSDP: https://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol Also, there may be some existing service to run on the RedPitaya size like avahi.

Possible buffering issue in Modem-Example0

EDIT: Looking through the other SoapySDR device repos, it seems as though getHardwareTime( ) is a common function they have, but we can't seem to find it in the SoapyRedPitaya source code, even though the modem example requires this. Is there a workaround?

---

Making use of the Pothos Flow modem demo (found here: https://github.com/pothosware/PothosDemos/wiki/Modem-Example0), I was able to transmit messages from the OUT1 channel to IN1 channel of a Red Pitaya STEM 125-14 board. Some chatbox messages weren't received at all, while others would have an incorrect letter, or be a duplicate of a previous message. I don't believe that these issues are due to channel loss, as the input and output ports are connected directly.

When replacing the transmission side's chat box with a message generator, and using text file sinks at the output of this block, and the end of the receiving diagram, I get the below output. Some bytes are received (green), repeated from previous messages (blue), or missing completely (red). Is this a buffer issue of some sort, or is this related to block settings?

Any guidance would be a huge help, as I'm trying to develop a system using 2 of these boards, and would like to make sure everything functions correctly before moving on.

Unable to transmit with SoapyRedPitaya

Hello,

I am testing Sdrangel with the redpitaya SDR tranceiver under Ubuntu 18.04 and with the soapysdr/SoapyRedPitaya module.

I have hardcoded the IP address of the RP in the SoapyRedPitaya.cpp file so sdrangel and soapysdr have no problem to find the RP.

This works fine in reception but not in transmission. When I try to transmit after having defined a proper sink in Sdrangel, then nothing happens. I think there is something wrong with the SoapyRedpitaya module. Sdrangel does not report any errors.... and works fine in transmission mode with my PlutoSdr and its soapysdr, so.....
Thanks
Regards
Peter

create git tag for first release

@pavel-demin How do you feel about SoapyRedPitaya being ready for a release tag? Any preference for the version number? year.month, major.minor? I am looking to upload to the drivers ppa once there is tag: https://launchpad.net/~myriadrf/+archive/ubuntu/drivers/+packages

debian packaging directory

• also upload to https://launchpad.net/~myriadrf/+archive/ubuntu/drivers/+packages