PothosDemos
PothosDemos copied to clipboard
pothosware
pothos won't accept the demo
I downloaded the Simple _FM_demod demo but Pothos won't open it saying that it is invalid. You should probably fix it or remove it.
Before this, I downloaded the latest PothosSDR Windows package from the website because I hadn't used my LimeSDR for a few months. Previously, I was using SDRconsole and SDRuno with the LimeSDR without any problems, but now they don't recognize the LimeSDR. LimeSDR Suite still works, but an application that I wrote to perform spectrum analysis with the PothosSDR library now crashes when I try to initialize the LimeSDR. Previously, it was working perfectly. Also, I had multiple .pothos files that worked, but now fail. Something has changed. Any actual help would be appreciated.
Whats the error when the file is loaded? Does it freeze, is there an error message printed?
That sucks, I just build what Lime posts to the github. So I dont know whats wrong, and I dont have my limesdr at the moment. But if you can share what some of the command line tools say:
LimeUtil --info
The next ones are contingent on the limesdr showing up in the device manager: LimeUtil --find LimeUtil --make
SoapySDRUtil --info SoapySDRUtil --find SoapySDRUtil --make
That would possibly help determine if there is anything wrong with the device, or the install perhaps.
Actually i get the Error too. It says: [06:59:04.678847] PothosFlow.GraphEditor: Error parsing JSON: illegal value
Actually i get the Error too. It says: [06:59:04.678847] PothosFlow.GraphEditor: Error parsing JSON: illegal value
In fact, I made a mistake. I didn't right click on "RAW" but downloaded the link directly. The stupid thing is that the file you download is even called .pothos. I only noticed it when I opened the file with a text editor and saw that it contains HTML code.
I have no idea what to do; one can can check files into github, and when you look at the nice colored HTML browser in github for that file, thats just how the file is presented. When downloading that page, naturally its going to have the HTML that describes the github page with logos and colored text. Its the same for any C source file or header too. Ex: wget a header full of useful macros, try to compile it, and there is going to be the same issue.