Date   

#windows #windows

Alexander Sevryukov
 

Hello

When working with ssb modulator and especially with the compressor, the signal spectrum expands. This is not only visible in the panorama, but also transmitted. If I reduce the microphone gain or compression, the expansion of the spectrum becomes less noticeable, but such a signal is already quite quiet and not “dense” (almost without compression). How can the ssb modulator and levels be properly tuned so that the spectrum does not expand and at the same time the signal remains loud and "dense" (with good compression)?


[Haiku] It builds!

Kevin Stabel
 

Hello.

Thought you folks might get a kick out of this.
Not very useful at this time, as haiku does not have 3D acceleration, yet ... there is hope.
Might have a look at the libhackrf FreeBSD implementation next.

There are quite a few bugs, such as each UI window gets it's own window in the window manager, so that royally messes with things to say the least ...

https://imagebin.ca/v/4fVXtoRSwE0v


Re: limesdr not seen (docker on ubuntu)

alexandre CASTELLANE
 

Hi all,

this was it !?? thanks.

One comment then, did I miss something, or should I clone sdrangel-docker AND sdrangel also afterwards to get this dir ?

Does it make sense to provide the udev dir into sdrangel-docker ?

Now the bad surprise : I came to bare metal because the TX windows was partially unavailable on my virtualbox.

Some history :

using virtual box (ubuntu over windows on another Lenovo PC): I got the TX windows OK first, able to see the antenna selector for example at first test. Then at second test (may be a reboot, or so after) I lost the half bottom of the window, frame is OK, but no pixels.

This decided me to switch to bare metal, and I get the same issue, would this be lenovo hardware related ?

note : apparently I must have solved this limesdr not seen on VB, but I didn't remember it :)

Thanks for support

Alexandre, F5SFU

On 29/04/2019 23:32, Edouard Griffiths wrote:
Hello Alexandre,

I think you missed the udev rules thing. You still need it either in the Docker host or the Virtualbox guest.

For Docker, in a VBox guest replace "host" by "guest":
"In order to be able to access the USB hardware on the host the udev rules must be properly set for your user (or system wide) on the host. The??udev-rules folder??in the SDRangel Github repository contains these rules and a script to install them to be run with??sudo install.sh."

Brgds,
Edouard.


Re: limesdr not seen (docker on ubuntu)

Edouard Griffiths
 

Hello Alexandre,

I think you missed the udev rules thing. You still need it either in the Docker host or the Virtualbox guest.

For Docker, in a VBox guest replace "host" by "guest":
"In order to be able to access the USB hardware on the host the udev rules must be properly set for your user (or system wide) on the host. The udev-rules folder in the SDRangel Github repository contains these rules and a script to install them to be run with sudo install.sh."

Brgds,
Edouard.


Re: limesdr not seen (docker on ubuntu)

Michael Durkin
 

odd that " I can't see the card with "lsusb" tough "

give the print out of lsusb .. and uname -a

might need some usb updates .. but shouldn't ...

Is the 3 led's on the Lime flashing all green or any red ?

On 4/29/19, alexandre CASTELLANE via Groups.Io <f5sfu=yahoo.fr@groups.io> wrote:
Hello,

after some troubles I never got the limesdr seen on a virtual linux box,
I decided to run the docker version on a brand new ubuntu bare metal
installation.

after some new troubles, I think I have prepared a docker image on my
linux. But still I can't see the card.

I installed limesdr driver on the bare linux, and the lime test sees the
card properly, but still not the docker. I can't see the card with
"lsusb" tough.

Any idea ? I tried sudo the command, same result.

running it with the command :?? ./run.sh -g -t vanilla?? provides :

[....]

2019-04-29 09:16:14.106 (D) SoapySDRInputPlugin::enumSampleSources: 0
SoapySDR devices. Enumerate these with Rx channel(s):
09:16:14.106535 WARN:???? xtrxllpciev0_discovery:243 [PCIE] XTRX PCIe
driver isn't loaded
libusb: error [_get_usbfs_fd] libusb couldn't open USB device
/dev/bus/usb/004/004: Permission denied
libusb: error [_get_usbfs_fd] libusb requires write access to USB device
nodes.
2019-04-29 09:16:14.116 (D) LimeSDROutputPlugin::enumSampleSources:
Could not find any LimeSDR device
ERROR: Unable to find host: Name or service not known
2019-04-29 09:16:19.122 (D) SoapySDROutputPlugin::enumSampleSinks: 0
SoapySDR devices. Enumerate these with Tx channel(s):
09:16:19.122511 WARN:???? xtrxllpciev0_discovery:243 [PCIE] XTRX PCIe
driver isn't loaded

Best 73

F5SFU





limesdr not seen (docker on ubuntu)

alexandre CASTELLANE
 

Hello,

after some troubles I never got the limesdr seen on a virtual linux box, I decided to run the docker version on a brand new ubuntu bare metal installation.

after some new troubles, I think I have prepared a docker image on my linux. But still I can't see the card.

I installed limesdr driver on the bare linux, and the lime test sees the card properly, but still not the docker. I can't see the card with "lsusb" tough.

Any idea ? I tried sudo the command, same result.

running it with the command :?? ./run.sh -g -t vanilla?? provides :

[....]

2019-04-29 09:16:14.106 (D) SoapySDRInputPlugin::enumSampleSources: 0 SoapySDR devices. Enumerate these with Rx channel(s):
09:16:14.106535 WARN:???? xtrxllpciev0_discovery:243 [PCIE] XTRX PCIe driver isn't loaded
libusb: error [_get_usbfs_fd] libusb couldn't open USB device /dev/bus/usb/004/004: Permission denied
libusb: error [_get_usbfs_fd] libusb requires write access to USB device nodes.
2019-04-29 09:16:14.116 (D) LimeSDROutputPlugin::enumSampleSources: Could not find any LimeSDR device
ERROR: Unable to find host: Name or service not known
2019-04-29 09:16:19.122 (D) SoapySDROutputPlugin::enumSampleSinks: 0 SoapySDR devices. Enumerate these with Tx channel(s):
09:16:19.122511 WARN:???? xtrxllpciev0_discovery:243 [PCIE] XTRX PCIe driver isn't loaded

Best 73

F5SFU


Re: SDRangel crashes after executing the command REST API #windows

Alexander Sevryukov
 

Hello, Edouard

Already downloaded the latest build for Windows (4.5.4), no changes yet. I'll try to do it through presets.

Best regards,
Alexander


Re: Proper call of some REST API methods #windows

Alexander Sevryukov
 

Thanks, Edouard

if r.status_code // 100 == 2:

It works :)


Re: Proper call of some REST API methods #windows

Edouard Griffiths
 
Edited

HTTP code 202 is not an error like any of the 200's range. 
As far as I can see the HTTP code is tested like this: 
"if r.status_code / 100 == 2:"
Depending on the version of Python you may need to force Euclidean division like this:
"if r.status_code // 100 == 2:"

Brgds, Edouard.


Re: SDRangel crashes after executing the command REST API #windows

Edouard Griffiths
 

Your script works with SDRangel on Linux and the latest version (v4.5.5).
Brgds, Edouard.


Permanent error when trying to run any command under Windows #windows

Alexander Sevryukov
 

I am trying to use commands, but any selected file (.py from the examples, empty .bat or .py with one empty main function) returns Error: Failed to Start in the command output window.



I tried to run sdrangel as an administrator. No effect. What could be wrong?
 
In the log file, the last entry is the launch of the command.
Command :: run: I: /Hobby/Ham/SDR/sdrangel/commands/empty.py
 
Windows 7, SDRangel 4.5.3


Proper call of some REST API methods #windows

Alexander Sevryukov
 

When trying to modify one of the .py examples, I ran into the fact that r.status_code = 202 returned. Perhaps this happens when calling commands that require some time to execute. For example, here I add Sink T0
 
        deviceset_index_rx = 1
        deviceset_url = "/ deviceset /% d"% deviceset_index_rx
        r = callAPI (deviceset_url + "/ device", "PUT", None, {"hwType": "HackRF", "tx": 1}, "setup device on Tx device set")
# if r is None:
# exit (-1)
        time.sleep (2)
 
I had to remove error handling, but add a pause before the next calls. Where can I see how to handle this correctly? I saw something similar in devicesets_config.py, but there it was somehow completely different.
 
To apply a preset to T0, I need to add it and install the "hwType": "HackRF" call the PATCH method to the preset as done here (devicesets_config.py) with the command
    ["/ preset", "PATCH", None, {"deviceSetIndex": 0, "preset": {"groupName": "OM144", "centerFrequency": 145480000, "type": "R", "name": "Rept + Simplex + DV"}}, "load preset on Rx 0"]]? (but "deviceSetIndex": 0, "type": "T"). So far I have failed.

Windows 7, SDRangel 4.5.3


SDRangel crashes after executing the command REST API #windows

Alexander Sevryukov
 

I create a configuration .py file. It adds (or changes) R0 - HackRF, sets the necessary settings, adds Sink T0 - HackRF, reads the settings, but when you try to change them, the application crashes. Here at this moment
 
we get the settings
 
         deviceset_index_rx = 1
         deviceset_url = "/ deviceset /% d"% deviceset_index_rx
         settings_tx = callAPI (deviceset_url + "/ device / settings", "GET", None, None, "Get device settings")
 
trying to update them (no changes)
 
         r = callAPI (deviceset_url + "/ device / settings", "PATCH", None, settings_tx, "Patch device settings")
 
application crashes.
 
It should not be ? How to do it right?

(full code in attachement)

Windows 7, SDRangel 4.5.3


DATV not working - stops after brief waterfall display?

David J Taylor
 

I haven't run the DATV software for a couple of months, and now when pressing Play a spectrum and waterfall are briefly displayed (~0.5 seconds), and then the program exits. The same software & hardware work correctly on broadcast FM. There has been a Windows update on that PC.

Has anyone else seen the same symptoms?

Thanks,
David
--
SatSignal Software - Quality software for you
Web: http://www.satsignal.eu
Email: david-taylor@...
Twitter: @gm8arv


Re: LimeSDR Mini Power Output at 2.4Ghz

Edouard Griffiths
 

Hi,

issue opened: https://github.com/f4exb/sdrangel/issues/325
 
Brgds, Edouard.


Re: LimeSDR Mini Power Output at 2.4Ghz

Mick
 

Edouard,

I dont mind either way, the tool tip will also need to be changed as it states the frequencies for each setting.

I think Hi and Lo would probably be better for people who are not SDR experts, but TX1 and TX2 is obviously accurate.

Are you able to validate my findings with your own mini?

Kind regards

Mick


Re: LimeSDR Mini Power Output at 2.4Ghz

Edouard Griffiths
 

Hi Mick,

according to https://wiki.myriadrf.org/LimeSDR-Mini_v1.1_hardware_description TX1 is for high band and TX2 is for low band so "Hi" and "Lo" might be swapped since it does not match the natural order. Since it should work for all versions of Lime SDR maybe they should just be labeled "TX1" and "TX2".

Brgds,
Edouard.


Re: LimeSDR Mini Power Output at 2.4Ghz

Mick
 

Edouard,

I believe the antenna controls in SDRAngel for the LimeSDR Mini are labelled incorrectly, I have done another test at 144 Mhz CW and get 18.8dBm on Hi and -0.6dBm on Lo

Cany you please double check my findings. Its not really an issue once you know and I used the graph in the linked information to confirm what I should be seeing:
https://discourse.myriadrf.org/t/limesdr-s-maximum-transmitting-power-at-different-frequencies/1649

Kind regards

Mick


LimeSDR Mini Power Output at 2.4Ghz

Mick
 
Edited

Hi,

Decided to start this as a separate thread.

The attached image shows my power output on the Lime mini using both the Hi and Lo antenna options. It seems that the Lo setting is better than the Hi, this is confirmed when amplified and sent to the QO100 satellite.

Are these readings close to accurate and is there an issue with the antenna setting in SDRAngel?
The measurments are made with a cheap chinese OLED meter found on ebay, the 3000 version.

I have also uploaded my settings which might help with the SSB thread.

kind regards

Mick


Re: Audio Settings in SDRAngel for Windows not holding or disappearing

Marty Wittrock
 

Okay - I've kind of answered my own question here...The only way to make your system defaults work in Windows is to SET THEM THAT WAY. I ended up setting my receive input audio port to the PC's audio resources and then set my transmit output up to work from a USB audio dongle. This way the my VOX RF Switch works because audio is present at the USB dongle and SDRAngel pulls the audio from the dongle's audio stream.

So, it's fixed..! I just have to set Windows audio resources in the WINDOWS AUDIO CONTROL PANEL IN WINDOWS SETTINGS and then force the defaults (i.e. 'Set as Default'). 

Working perfectly with SDRAngel on Windows now... :)

73 de Marty, KN0CK