1. sdrangel@groups.io
   Date   
Re: Stupid API tricks (notes on things I am playing around with just for amusement).

James Dallas
 

Hi Eduoard,

I was just able to get RYRYRY to work readably, if not reliably (error about every 5-10 characters), after adding the start/stop bits.

I'll keep experimenting. My guess is that it's just t about the cusp of being workable, hoping going to a more "real time" language will help. But your point re: latency is well taken, that is why I described it as a "stupid" and possibly abusive trick.

However, for FSK modes that are slower than RTTY... maybe WSPR (4FSK at something like 1.5 baud...).? Lots of fun to be had!


On Tue, Mar 12, 2019 at 11:05 AM Edouard Griffiths <f4exb06@...> wrote:
Hi James,

could be fun indeed but for your point #1 bear in mind that the REST API is not designed for real time operation in particular mind the network latency if not using localhost. However RTTY is relatively slow so this may work. The point #2 seems more reasonable. I don't remember the length limit for the CW string (or if there is one) but this should not be too hard to find in the code. The CW keyer is in the sdrbase/dsp folder.

Brgds, Edouard.

Re: Test sdrangel port for Mac OSX Mojave #osx

Gaston LU5AGQ
 

Hi Fabio, thanks for taking the time on this. Unfortunately didn't recognize my HackRF wich works fine with other applications such as GQRX and CubicSDR to mention a few.

Any idea?

73

On Mon, Mar 11, 2019 at 6:06 PM Fabio IZ0IBA 2220156 <f.capozzi@...> wrote:

Hi, i compiled support for hackRF input and output. 
You can download DMG file here https://drive.google.com/file/d/1UT8-TRz_Jt6t1fYAxmtQTQGpryj4nf6c/view?usp=sharing

73, Fabio.



--

Re: Stupid API tricks (notes on things I am playing around with just for amusement).

Edouard Griffiths
 

Hi James,

could be fun indeed but for your point #1 bear in mind that the REST API is not designed for real time operation in particular mind the network latency if not using localhost. However RTTY is relatively slow so this may work. The point #2 seems more reasonable. I don't remember the length limit for the CW string (or if there is one) but this should not be too hard to find in the code. The CW keyer is in the sdrbase/dsp folder.

Brgds, Edouard.
Stupid API tricks (notes on things I am playing around with just for amusement).

James Dallas
 

Hi everyone,

I've started playing around with the REST API, possibly in an abusive/not-intended-by-Eduoard-way. Here are some updates/musings --

1. I am currently trying to see if it is possible to trigger tone frequency changes with the SSB modulator (either using real FSK by changing the TX offset, or AFSK using different audio tones) to create a RTTY transmitter.

One of the reasons I started building from source was so that I could start trying to develop my own modulator plugin; it occurred to me yesterday that I might be able to just use the API to generate FSK tones instead of writing a new modulator in C (which I am familiar with at about the "hello world" level, but not really fluent). My first attempts were with bash/curl and javascript/XMLHttpRequest. I would say they were semi-successful in generating alternating tones, but couldn't quite nail the 22ms per bit timing of 45.45 baud RTTY. I will try using Python or Java instead, because I think I might be able to control timing better.

Also, I need to learn a little bit more about baudot code to actually generate anything useful (I was thinking I could generate an RYRYRY test signal just by shifting every 22ms from mark to space, but I think I neglected to take into consideration start/stop bits.. so when I re-implement later in a faster language I will do it the "right" way).

I will update as this goes along. Obviously, piping audio in/out to fldigi is easier, but I think it would be neat to build a RTTY transmitter entirely in sdrangel.


2. In addition to RTTY, automation could be used (probably a bash script would suffice) to change the CW string. So we could then break a larger text into chunks and then send that out line by line / chunk by chunk using the CW keyer. Could be useful in case anyone wants to transmit "War and Peace" on 900 MHz ISM band just for fun.
Re: REST API in Windows 10 issues in SDRAngel 4.4.5 #windows

Roger Rehr W3SZ
 

Thanks Edouard!

For 4.4.5 I was using your WIndows Build...4.0.3 was my own build.
Do you have any plans to fix this in your build?
I will keep using my 4.0.3 build for now because I am in the middle of another project with a deadline and don't currently have the time to delve into making the 4.4.5 build work here.

Thanks for all that you do!  The REST API gives amazing power and capability to SDRAngel, and with the web page documentation you have made available for it, a 3rd grader could implement use of the REST API in a few minutes using your instructions.  Thank You Very Much for all of it!!!

73,

Roger Rehr
W3SZ
Re: Test sdrangel port for Mac OSX Mojave #osx

Fabio IZ0IBA 2220156
 


Hi, i compiled support for hackRF input and output. 
You can download DMG file here https://drive.google.com/file/d/1UT8-TRz_Jt6t1fYAxmtQTQGpryj4nf6c/view?usp=sharing

73, Fabio.
Re: Test sdrangel port for Mac OSX Mojave #osx

Gaston LU5AGQ
 

Many thanks for taking the time.

73

On Mon, Mar 11, 2019 at 3:55 PM Fabio IZ0IBA 2220156 <f.capozzi@...> wrote:
The dmg here was not mine but has been made by Francois. I will try to enable HackRF but i do not have any library so if some compilation error pops out i can fix it ... 
let see what happen ..

73, Fabio



--

Re: Test sdrangel port for Mac OSX Mojave #osx

Fabio IZ0IBA 2220156
 

The dmg here was not mine but has been made by Francois. I will try to enable HackRF but i do not have any library so if some compilation error pops out i can fix it ... 
let see what happen ..

73, Fabio
Re: Test sdrangel port for Mac OSX Mojave #osx

Gaston LU5AGQ
 

Ciao Fabio! I just noticed that. Downloaded your binary but didn't found either my HackRF One nor my BladeRF Mini.
If you can compile the latest version with support for those sdr tranceivers will be great.

73

On Mon, Mar 11, 2019 at 2:32 PM Fabio IZ0IBA 2220156 <f.capozzi@...> wrote:
Hi Gaston, i compiled SDRAngel for iMac Mojave, but i have configured the build only for RTL-SDR and for LimeSDR. 
What SDR device you have ?

73, Fabio.



--

Re: Test sdrangel port for Mac OSX Mojave #osx

Fabio IZ0IBA 2220156
 

Hi Gaston, i compiled SDRAngel for iMac Mojave, but i have configured the build only for RTL-SDR and for LimeSDR. 
What SDR device you have ?

73, Fabio.
Re: Test sdrangel port for Mac OSX Mojave #osx

Gaston LU5AGQ
 

Hello there! Is there someone of you that can compile the latest version of SDRangel?

Many thanks in advance.

On Sun, Mar 10, 2019 at 6:10 PM Fabio IZ0IBA 2220156 <f.capozzi@...> wrote:
Tnx for you help Francois, 
i built and run my application.

Unfortunately the problem i experienced with the already built application did not solve. This it the reason to start building myself because i was confident that upgrading to the last release will solve the 
problem. i'm sad .. this is not the case. 
I found my device and i am able to start reception. But if i stop RX i am not able to rearm it again. 
I have to close Sdrangel unplug device and replug again.  Also i have troubles in regulating gain since the sliders 
apart the one i am regulating move randomly ... as i shown in this link  https://youtu.be/salnSteT5gs

So i guess there is some problem in the soapy driver or in the LimeSuite driver. 
I don't know how to solve it ... i wonder if any people are using LimeSDR mini with SDRangel without troubles ....

However tnx for you help.
73, Fabio IZ0IBA



--

Re: REST API in Windows 10 issues in SDRAngel 4.4.5 #windows

Edouard Griffiths
 

It looks like there was an issue at build time. The browser console says "Uncaught ReferenceError: SwaggerUIBundle is not defined
    at window.onload" 
I have spotted issues when trying to compile with Qt 5.12.1 where it would simply produce a compile time error complaining about something similar but I thought it was OK until 5.12.1.

Brgds, Edouard.
Re: REST API in Windows 10 issues in SDRAngel 4.4.5 #windows

Roger Rehr W3SZ
 

This is with LimeSDR using  Version 18.04.1 of LimeSuite and gateware 2.16 loaded in the LimeSDR USB.

If I first access REST API with 4.0.3 using the browser and SWAGGER and then re-send the same query (e.g. curl -X GET "http://127.0.0.1:8091/sdrangel" -H "accept: application/json" ) after shutting down 4.0.3 and starting 4.4.5, I get the proper response from 4.4.5 without error.

 But if I shut down the browser page that was opened and try again to access the REST API via the browser and SWAGGER while 4.4.5 is running I get a blank web page only.

I have to shut 4.4.5 down, restart 4.0.3, bring up the REST API browser page with SWAGGER, shut down 4.0.3 and restart 4.4.5, and then I can again access the REST API via the browser and SWAGGER with 4.4.5 running.

73,  Roger Rehr W3SZ
REST API in Windows 10 issues in SDRAngel 4.4.5 #windows

Roger Rehr W3SZ
 

Hi,

I just installed 4.4.5 release for Windows and running SDRAngel 4.4.5 on Windows 10 I have noticed 2 issues:  a new problem with the REST API and a problem with GPS control.  Both of these were working perfectly in SDRAngel 4.0.3 on Windows 10.

I had been using the REST API both via webpage and via a C# app that I wrote to programatically sweep LimeSDR frequency with SDRAngel 4.0.3 GUI with no issues at all; everything was working perfectly.

Today I upgraded to SDRAngel 4.4.5 GUI and I find that the swagger SDRAngel weblink no longer works:  a blank webpage is produced when I use URL: http://127.0.0.1:8091/doc/swagger-ui/index.html#/DeviceSet/devicesetChannelSettingsGet

And my C# App which had been working perfectly with no problems with SDRAngel 4.0.3 causes SDRAngel GUI to crash.without giving any error messages...SDRAngel just disappears from the screen when my app sends it a json steam.  My app is trivial, it just sends a json stream to the URL "http://127.0.0.1:8091/sdrangel/deviceset/1/channel/0/settings", and again was and still is working perfectly with SDRAngel 4.0.3 but not with 4.4.5.

I am hoping that someone can point me to the changes in the SDRAngel REST API that are causing these issues so that I can correct this situation here.

Also, the GPS function in SDRAngel had been working fine in 4.0.3 (with a couple of LimeSDRs).  With 4.4.5 when GPS is activated in SDRAngel, SDRAngel stops responding with no error message and must be exited and restarted.

Thanks in advance and 73,

Roger Rehr
W3SZ 
Re: Test sdrangel port for Mac OSX Mojave #osx

Fabio IZ0IBA 2220156
 

Tnx for you help Francois, 
i built and run my application.

Unfortunately the problem i experienced with the already built application did not solve. This it the reason to start building myself because i was confident that upgrading to the last release will solve the 
problem. i'm sad .. this is not the case. 
I found my device and i am able to start reception. But if i stop RX i am not able to rearm it again. 
I have to close Sdrangel unplug device and replug again.  Also i have troubles in regulating gain since the sliders 
apart the one i am regulating move randomly ... as i shown in this link  https://youtu.be/salnSteT5gs

So i guess there is some problem in the soapy driver or in the LimeSuite driver. 
I don't know how to solve it ... i wonder if any people are using LimeSDR mini with SDRangel without troubles ....

However tnx for you help.
73, Fabio IZ0IBA
Re: Test sdrangel port for Mac OSX Mojave #osx

Numlock
 

Is inside the source folder : /apple 

https://github.com/f4exb/sdrangel/tree/dev/apple

You copy the file in the root of your build folder and chmod +x deploy.sh

and before run the script you must edit the settings :

#!/bin/bash
SDRANGEL_VERSION="4.3.2"
QT_VERSION="5.12.1"
QT_HOME="/Applications/Dev/Qt/${QT_VERSION}"

for me i have installed Qt in the folder : /Applications/Dev/Qt
 
Re: Test sdrangel port for Mac OSX Mojave #osx

Fabio IZ0IBA 2220156
 

May be ... but i'm not sure if my compilation will work :-) ... this is my first time in compiling with QT Creator ...
Unfortunately i do not find any deploy.sh script in the building dir ... i only have this files.
Should i have to include something in the building configuration ?

iMac-di-Fabio:build-sdrangel.macos-Desktop_Qt_5_12_1_clang_64bit-Release fabiocapozzi$ ls -l

total 664

-rw-r--r--    1 fabiocapozzi  staff  339441 10 Mar 18:28 Makefile

drwxr-xr-x    5 fabiocapozzi  staff     160 10 Mar 19:13 app

drwxr-xr-x    9 fabiocapozzi  staff     288 10 Mar 19:07 cm256cc

drwxr-xr-x   27 fabiocapozzi  staff     864 10 Mar 19:07 devices

drwxr-xr-x   34 fabiocapozzi  staff    1088 10 Mar 19:07 dsdcc

drwxr-xr-x   10 fabiocapozzi  staff     320 10 Mar 19:06 fcdhid

drwxr-xr-x   10 fabiocapozzi  staff     320 10 Mar 19:07 fcdlib

drwxr-xr-x   31 fabiocapozzi  staff     992 10 Mar 19:02 httpserver

drwxr-xr-x    7 fabiocapozzi  staff     224 10 Mar 18:35 liblimesuite

drwxr-xr-x    7 fabiocapozzi  staff     224 10 Mar 18:35 librtlsdr

drwxr-xr-x    7 fabiocapozzi  staff     224 10 Mar 18:35 libsoapysdr

drwxr-xr-x   21 fabiocapozzi  staff     672 10 Mar 19:04 logging

drwxr-xr-x   13 fabiocapozzi  staff     416 10 Mar 19:07 mbelib

drwxr-xr-x    6 fabiocapozzi  staff     192 10 Mar 18:29 plugins

drwxr-xr-x   37 fabiocapozzi  staff    1184 10 Mar 19:02 qrtplib

drwxr-xr-x  142 fabiocapozzi  staff    4544 10 Mar 19:05 sdrbase

drwxr-xr-x  178 fabiocapozzi  staff    5696 10 Mar 19:06 sdrgui

drwxr-xr-x  141 fabiocapozzi  staff    4512 10 Mar 19:04 swagger

iMac-di-Fabio:build-sdrangel.macos-Desktop_Qt_5_12_1_clang_64bit-Release fabiocapozzi$ 
Re: Test sdrangel port for Mac OSX Mojave #osx

Numlock
 

Hello, you must use the deploy.sh script in the build folder : build-sdrangel.macos-Desktop_Qt_5_12_1_clang_64bit-Release to create the packaged SDRangel.app and SDRangel.dmg file.

Look at bottom of the ReadmeMacOS.md in the script you must change the release of Qt and path of your Qt installation.

I have recompiled the software and it's very strange i have not same size of the package SDRangel.app but i think you dont need my dmg :-)

Best regards.
Re: Test sdrangel port for Mac OSX Mojave #osx

Fabio IZ0IBA 2220156
 

Hi, i finish compile the project without errors, but the applicazione does not start. I got this message

18:47:09: Starting /Users/fabiocapozzi/sdrangel_work/build-sdrangel.macos-Desktop_Qt_5_12_1_clang_64bit-Release/app/SDRangel.app/Contents/MacOS/SDRangel...

dyld: Library not loaded: @rpath/libswagger.1.dylib

Referenced from: /Users/fabiocapozzi/sdrangel_work/build-sdrangel.macos-Desktop_Qt_5_12_1_clang_64bit-Release/app/SDRangel.app/Contents/MacOS/SDRangel

Reason: image not found

18:47:09: The program has unexpectedly finished.

18:47:09: The process was ended forcefully.


However, looking at the build directory i indeed find the library on its place ...

iMac-di-Fabio:build-sdrangel.macos-Desktop_Qt_5_12_1_clang_64bit-Release fabiocapozzi$ ls -l swagger/libswagger.*

-rwxr-xr-x  1 fabiocapozzi  staff  2028992 10 Mar 18:31 swagger/libswagger.1.0.0.dylib

lrwxr-xr-x  1 fabiocapozzi  staff       22 10 Mar 18:31 swagger/libswagger.1.0.dylib -> libswagger.1.0.0.dylib

lrwxr-xr-x  1 fabiocapozzi  staff       22 10 Mar 18:31 swagger/libswagger.1.dylib -> libswagger.1.0.0.dylib

lrwxr-xr-x  1 fabiocapozzi  staff       22 10 Mar 18:31 swagger/libswagger.dylib -> libswagger.1.0.0.dylib


May be i do something wrong in QT Creator .... 
How do you fixed that ?

Tnx, Fabio
Re: Test sdrangel port for Mac OSX Mojave #osx

Numlock
 

Hello Fabio,

I will try to update the library and create a new build this end afternoon. 

I give you a feedback after. 

François 


Le dim. 10 mars 2019 à 10:16, Fabio IZ0IBA 2220156 <f.capozzi@...> a écrit :
Hi, I test you build. It starts, but i do not find my LimeSDR Mini device. May be you compiled the source with the v0.7.0 library and API, while i have the v0.8.0
I don't know if there is a dependance against the device library at compile time or this is an other issue. 
If you have the Application compiled and you upgrade your device libraries the Application should continue to recognise devices, but this seems to be not the case. 

73, Fabio.

901 - 920 of 1568  
More
Home Messages Hashtags About Features Pricing Updates Terms Help Twitter