Date   

Re: Error during compilation of SDRangel on Mac OSX Mojave #osx

Žiga S.
 

Hello,

I think that the same error happened to me, when I moved all my build to Mojave machine....
will check out if that was the same issue, but the DMG that I produced and was posted was built on osx Sierra.

Sorry if I am that backward :)

It may be, that we would need to use higher Qt version for Mojave.
(I started experimenting with Mojave, but I was unable to find more time to get through)

Thanks for the input,
Cheerz, Z


Re: Test sdrangel port for Mac OSX Mojave #osx

Žiga S.
 

Hello Everybody,

Thanks again for some fresh inputs into macOS build,
I am very delighted that things are basically happening on their own!
Kudos to all!

At the moment I am in quite a stress for other projects, 
but let me know if there is some hot question, that may be I could help somebody clear compilation process?

Quite a lot happened in last two weeks, is there any brief info?

Thanks,
Cheerz, Z


Re: Test sdrangel port for Mac OSX Mojave #osx

Fabio IZ0IBA 2220156
 

Just to see if work i cloned the git repository of libhackrf,  

hackrf-2018.01.1_0.darwin_18.x86_64.tbz2 

hackrf-2018.01.1_0.darwin_18.x86_64.tbz2.rmd160

compiled, installed the source. Now i have this components in my system

iMac-di-Fabio:build fabiocapozzi$ ls -l /opt/local/lib/libhackrf*

-rwxr-xr-x  1 root  admin  26756  5 Ott 01:46 /opt/local/lib/libhackrf.0.5.0.dylib

-rwxr-xr-x  1 root  admin  27140  6 Mar 18:04 /opt/local/lib/libhackrf.0.5.0.dylib.mp_1552418121

lrwxr-xr-x  1 root  admin     21  5 Ott 01:46 /opt/local/lib/libhackrf.0.dylib -> libhackrf.0.5.0.dylib

lrwxr-xr-x  1 root  admin     21  6 Mar 18:04 /opt/local/lib/libhackrf.0.dylib.mp_1552418121 -> libhackrf.0.5.0.dylib

-rw-r--r--  1 root  admin  20672  5 Ott 01:46 /opt/local/lib/libhackrf.a

-rw-r--r--  1 root  admin  22616  6 Mar 18:04 /opt/local/lib/libhackrf.a.mp_1552418121

lrwxr-xr-x  1 root  admin     17  5 Ott 01:46 /opt/local/lib/libhackrf.dylib -> libhackrf.0.dylib

lrwxr-xr-x  1 root  admin     17  6 Mar 18:04 /opt/local/lib/libhackrf.dylib.mp_1552418121 -> libhackrf.0.dylib

iMac-di-Fabio:build fabiocapozzi$ ls -l /opt/local/bin/hackrf*

-rwxr-xr-x  1 root  admin  18124  6 Mar 18:04 /opt/local/bin/hackrf_clock

-rwxr-xr-x  1 root  admin  13788  5 Ott 01:46 /opt/local/bin/hackrf_cpldjtag

-rwxr-xr-x  1 root  admin  18876  5 Ott 01:46 /opt/local/bin/hackrf_debug

-rwxr-xr-x  1 root  admin  13992  5 Ott 01:46 /opt/local/bin/hackrf_info

-rwxr-xr-x  1 root  admin  18092  6 Mar 18:04 /opt/local/bin/hackrf_operacake

-rwxr-xr-x  1 root  admin  18104  5 Ott 01:46 /opt/local/bin/hackrf_spiflash

-rwxr-xr-x  1 root  admin  24468  5 Ott 01:46 /opt/local/bin/hackrf_sweep

-rwxr-xr-x  1 root  admin  30388  5 Ott 01:46 /opt/local/bin/hackrf_transfer

iMac-di-Fabio:build fabiocapozzi$ 


Now i compiled again SDRAngel and you found the new file here ....

https://drive.google.com/file/d/1UT8-TRz_Jt6t1fYAxmtQTQGpryj4nf6c/view?usp=sharing

The deploy.sh script report this output. in yellow you find the reference to HackRF

iMac-di-Fabio:build-sdrangel.macos-Desktop_Qt_5_12_1_clang_64bit-Release fabiocapozzi$ ./deploy.sh

DeployLIB: liblibhackrf.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployLIB: libsdrbase.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployLIB: libqrtplib.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployLIB: libswagger.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployLIB: libliblimesuite.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployPLUGIN: libmodnfm.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channeltx

DeployPLUGIN: libremotesource.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channeltx

DeployPLUGIN: libmodssb.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channeltx

DeployPLUGIN: libmodwfm.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channeltx

DeployPLUGIN: libmodatv.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channeltx

DeployPLUGIN: libmodam.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channeltx

DeployPLUGIN: libudpsource.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channeltx

DeployPLUGIN: libinputremote.dylib to app/SDRangel.app/Contents/Frameworks/plugins/samplesource

DeployPLUGIN: libinputlimesdr.dylib to app/SDRangel.app/Contents/Frameworks/plugins/samplesource

DeployPLUGIN: libinputtestsource.dylib to app/SDRangel.app/Contents/Frameworks/plugins/samplesource

DeployPLUGIN: libinputsoapysdr.dylib to app/SDRangel.app/Contents/Frameworks/plugins/samplesource

DeployPLUGIN: libinputhackrf.dylib to app/SDRangel.app/Contents/Frameworks/plugins/samplesource

DeployPLUGIN: libinputrtlsdr.dylib to app/SDRangel.app/Contents/Frameworks/plugins/samplesource

DeployPLUGIN: libinputfilesource.dylib to app/SDRangel.app/Contents/Frameworks/plugins/samplesource

DeployPLUGIN: liboutputremote.dylib to app/SDRangel.app/Contents/Frameworks/plugins/samplesink

DeployPLUGIN: liboutputhackrf.dylib to app/SDRangel.app/Contents/Frameworks/plugins/samplesink

DeployPLUGIN: liboutputlimesdr.dylib to app/SDRangel.app/Contents/Frameworks/plugins/samplesink

DeployPLUGIN: liboutputfilesink.dylib to app/SDRangel.app/Contents/Frameworks/plugins/samplesink

DeployPLUGIN: liboutputsoapysdr.dylib to app/SDRangel.app/Contents/Frameworks/plugins/samplesink

DeployPLUGIN: libdemodbfm.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channelrx

DeployPLUGIN: libchanalyzer.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channelrx

DeployPLUGIN: libdemodssb.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channelrx

DeployPLUGIN: libremotesink.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channelrx

DeployPLUGIN: libdemodatv.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channelrx

DeployPLUGIN: libdemodam.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channelrx

DeployPLUGIN: libdemodwfm.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channelrx

DeployPLUGIN: libdemodnfm.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channelrx

DeployPLUGIN: libudpsink.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channelrx

DeployPLUGIN: libdemodlora.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channelrx

DeployPLUGIN: libdemoddsd.dylib to app/SDRangel.app/Contents/Frameworks/plugins/channelrx

DeployLIB: libhttpserver.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployLIB: libcm256cc.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployLIB: libfcdlib.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployLIB: libfcdhid.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployLIB: libsdrgui.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployLIB: liblogging.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployLIB: libmbelib.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployLIB: libdsdcc.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployLIB: libdevices.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployLIB: liblibsoapysdr.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

DeployLIB: liblibrtlsdr.1.0.0.dylib to app/SDRangel.app/Contents/Frameworks

 
I hope this work .. this is the best i can do without having here the hardware. 
73, Fabio.
 



 


Re: Test sdrangel port for Mac OSX Mojave #osx

Fabio IZ0IBA 2220156
 

André i do not have the HackRF so i cannot test if the build works.
However i enabled the hackRF support uncommenting the following rows in the  "strangel.macos.pro"  QT Creator configuration file

SUBDIRS += libhackrf
SUBDIRS += plugins/samplesource/hackrfinput
SUBDIRS += plugins/samplesink/hackrfoutput

I didn't receive any compilation error nor linking error. However reading the sdrangel GitHub repository i found the note below about HackRF.  May be this will help you. 

I guess that if we want a working OSX version that run against all hardware devices we need to form a "building OSX user group" each person focused on contributing for specific hardware and merge our work in a unique build. 

I tested my build with LimeSDRmini and RTL-SDR because i have them so i'm sure they work.
If you want i can compile again SDRAngel but i am not sure about what to do for HackRF support.
May be the sdrangel creator will help up....

73, Fabio.
 





HackRF

HackRF is supported through the libhackrf library. Please note that you will need a recent version (2015.07.2 at least) of libhackrf that supports the sequential listing of devices and the antenna power control (bias tee). To be safe anyway you may choose to build and install the Github version: https://github.com/mossmann/hackrf.git. Note also that the firmware must be updated to match the library version as per instructions found in the HackRF wiki.

HackRF is better used with a sampling rate of 4.8 MS/s and above. The 2.4 and 3.2 MS/s rates are considered experimental and are way out of specs of the ADC. You may or may not achieve acceptable results depending on the unit. A too low sampling rate will typically create ghost signals (images) and/or raise the noise floor.



Does SDRAngel employ a PTT feature, and how does it handle USB relays...?

Marty Wittrock
 

Hello Everyone,

Does anyone know for certain if there a Push-To-Talk (PTT) feature in SDRAngel that mutes the receive channel while the transmitter is engaged and will release the transmitter and enter receive with audio when deactivated? I haven't seen this on the SDRAngel GUI and would like to have Half-Duplex capability. Is this a part of SDRAngel now (if it is, I haven't seen it) or is this employed in the REST API and if so, are there any examples to see how this is done?

Also, does anyone know if SDRAngel employs a means to identify and activate/deactivate USB relays? I have a USB relay that acts like a COM port device and requires the following command strings to engage/disengage the relay:

ON = 0xA0 0x01 0x01 0xA2

OFF = 0xA0 0x01 0x00 0xA1

Is it possible to employ this kind of USB relay either in SDRAngel or though the REST API and if so, are there any examples to see how this is done?

Any information on the above will be greatly appreciated. I recently used SDRAngel to operate in Beacon Mode (transmit only) on WSPR using the LimeSDR and a 3W brick amplifier and it performed excellent..! So now I'm off to see if I can add half-duplex to the Lime using SDRAngel so I can run WSPR and other digital modes using the Lime for further research.

Thanks in advance for the information - 73 de Marty, KN0CK 


Re: Test sdrangel port for Mac OSX Mojave #osx

Andre Neitzel
 

Thanks Fabio, but new compiled DMG dont found my hackRF - RTLsdr is working, but hackRF not :-( 
hackRF_info found module and its working with other Apps like GqRX... Is the latest DMG recognize HackRF by someone other? 
I installed Mac OS Mojave 10.14.3 completly new to get sure that my installation is not corrupted, but thats not the solution.

regards, André

Am Mo., 11. März 2019 um 22:06 Uhr schrieb Fabio IZ0IBA 2220156 <f.capozzi@...>:


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: REST API in Windows 10 issues in SDRAngel 4.4.5 #windows

Edouard Griffiths
 

Hi Roger,

I have spotted the error that made the Qt 5.12.1 build capsize but may also have silent consequences in the former Qt versions. It is here: https://github.com/f4exb/sdrangel/blob/f76ed4a4664b6563292770258da3703df7616d87/plugins/channelrx/demoddatv/demoddatv.pro#L65 "sdrbase" is wrong this should be "sdrgui". The resources file in sdrbase is precisely the one containing the SwaggerUIBundle stuff so it seems to me it could be impacting the proper inclusion of this resource.

Brgds, Edouard.


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

901 - 920 of 1575