OpenWebRX HL2 Support Update

[Jim Ancona]

Hi,

I've updated https://github.com/jancona/hpsdrconnector, which provides
HL2 support for OpenWebRX (https://www.openwebrx.de/) If you're not
familiar with it, OpenWebRX provides a nice-looking web interface to a
many SDRs.

The big news in this release of hpsdrconnector is multiple receiver
support. You can now define multiple HPSDR devices in OpenWebRX and
the connector will map them to separate receivers. So with the
standard gateware, you can define up to four devices.

This support should appear in the OpenWebRX 1.2 release. For the time
being, you can get it using the OpenWebRX experimental Debian and
Ubuntu repositories, or the ":latest" Docker image. Please note that
all of these are bleeding-edge development builds, so caveat emptor.
I've only tested the Docker build, so let me know if you run into
issues with one of the others. I couldn't get the OpenHPSDR discovery
to work with Docker's default bridge network driver. You can either
use host networking or specify the HL2 IP address in the OpenWebRX
profile. See https://github.com/jketterl/openwebrx/wiki/HPSDR-(including-Hermes-Lite-2)-device-notes
for details.

I'm happy to answer questions, provide support or take bug reports
here or on the OpenWebRX mailing list. You can also report bugs or
make feature requests on the Github repo at
https://github.com/jancona/hpsdrconnector/issues.

If you want to take a look, my development OpenWebRX server is
intermittently available at http://home.anconafamily.com:8073/ (It
runs on my development laptop using my only HL2, so no guarantees that
it will be there when you try it!)

Jim N1ADJ

[Steve Haynal]

Hi Jim,

Thanks for the update. I just listened to some 40M SSB on your development server and it sounds great!

For kiwiSDRs on openwebrx, you can zoom in and out to any arbitrary amount of the spectrum. I don't think the kiwiSDR sends the full spectrum back to the computer. How is that accomplished? What would we need to add to the HL2 protocol to do the same? With the HL2 on openwebrx we can see a maximum of 384kHz at a time.

73,

Steve

kf7o

[Jim Ancona]

On Sat, Sep 11, 2021 at 12:19 AM Steve Haynal <softerh...@gmail.com> wrote:
> For kiwiSDRs on openwebrx, you can zoom in and out to any arbitrary amount of the spectrum. I don't think the kiwiSDR sends the full spectrum back to the computer. How is that accomplished? What would we need to add to the HL2 protocol to do the same? With the HL2 on openwebrx we can see a maximum of 384kHz at a time.

That's a good question Steve, and I don't know the answer. kiwiSDR's
web UI is based on a fork of OpenWebRX, but I'm not sure how they do
what they do. I spoke to Jakob DD5JFK, who maintains OWRX. He said
"My guess is that for each client, they let the FPGA generate a
low-bandwidth IQ stream (somewhere around 20-50 kS/s) and an FFT
excerpt. The CPU will then run the necessary demodulation on the IQ
and pass everything to the client. The demodulation may even happen
inside the FPGA as well, so maybe the CPU only needs to pass an audio
stream. not sure. ... OpenWebRX expects IQ data from the SDR and does
all of the work itself simply because that's the only common
denominator across all the supported devices."

With the current architecture, my HPSDR connector would have to stream
IQ data at 30 MHz to support a full-width waterfall. That won't work.
So if the HL2 protocol was extended to do something like what Jakob
thinks kiwiSDR is doing, it would be a lot of work to incorporate that
into OWRX while maintaining broad compatibility with lots of different
hardware. (Note that, other than the quote above, this is my take, not
Jakob's.)

Hope this helps!

Jim

[PA3GSB]

Jim, Steve

Jim thanks for sharing. Great Jakob added this functionality.

Kiwisdr is using a spectrum ddc and a audio ddc.

For the spectrum a zoom function is used.

http://kiwisdr.com/   Look for the design review document ; it contains a good explanation!

73 Johan

PA3GSB

Op zaterdag 11 september 2021 om 06:19:20 UTC+2 schreef softerh...@gmail.com:

[Jiri Culak]

Hi all

that is good thread - since I own three HL2's (one with somehow dud DAC part of AD9866...since GW with 10 RX Slices) I was hoping to add OpenWebRX and push it to public IP address as way of payback to all those stuck in a citites (I have ultra-quiet location at 500m asl...well, until neighbour put up solar panel inverters at least lol....) so to hear that OpenwebRX can support multiple band-slots is great news. Now the question which arose from previous exchange - KiwiSDR allows multiple users to listen in and good feature is the CAMP feature (when there is a local weather net, it allows indefinite amount of users to just jump on the same spot and listen in. Does OpenWebRX supports same features as KiwiSDR GUI, since its a fork? I am still struggling to understand, if i.e. I have a 10 slices for 10 bands, running 192kHz, so abt. 2MHz worth of spectrum, coming as I/Q into RPI4b or if needed a beefier hardware -> OpenWebRX then processes the whole of the band-slots and whoever connects and "tunes" in n, then gets a part of the I/Q pushed onto demodulator (so if 10 users then 10 paralel demodulators?) am I right?

I am just trying to figure out, what is the best approach to a server, if RPi4B is enough or for more users I should use some older i5 / i7 laptop perhaps?

(BTW - some older hardware like laptops contains good GPUs...nVidia etc. - would it be option to compile source which allows GPU to be utilised to process FFTs?)

Br

Jirka OK2IT

Dne sobota 11. září 2021 v 22:25:45 UTC+2 uživatel PA3GSB napsal:

[Jim Ancona]

Hi Jirka,

I'm the developer of the OpenWebRX HPSDR connector. I've been travelling, so apologies for the delay in responding. I'll try to answer your questions, but there is more general OWRX expertise on that mailing list, so you may get better answers to non-HL2 OWRX questions there. I also monitor that list, but I'm more likely to see a message there quickly if it mentions the hpsdrconnector.

I'm not familiar with the KiwiSDR fork of OWRX, but in standard OWRX the station owner defines one or more devices each of which can have one or more profiles. When using the HPSDR connector, each receiver is a device which can have as many profiles as you want to define. Each profile is a slice of the band with a width defined by the sample rate. (You must define the same sample rate for all receivers on a single HL2 even though OWRX sees them as separate devices.) Users see the separate devices and profiles and select which one to listen to. If multiple users select the same device and profile, they all hear it and each can independently select different frequencies and modes within the frequency range of that profile. But if one user starts listening to a profile on a device and a second user selects a different profile on the same device, the first user is switched to the new profile--it's just last selection wins. I don't have a KiwiSDR, but my understanding is that each user gets exclusive use of a receiver, and then camping lets other users listen-in without having any ability to change anything. Assuming I have that right, it's a different paradigm.

The result is, ignoring CPU and network bandwidth constraints, a hypothetical ten receiver OWRX node using an HL2 could support more than ten users, but unless you configure it for one profile per receiver, it's possible for one user to interfere with another's listening. I'm not sure how much of an issue this is in practice. I don't run a dedicated OWRX node and the ones I've used don't seem that busy, but it certainly can happen.

The connector should support 10 receivers on the HL2, but I don't think I've ever tested it. Four receivers at 384k pretty much saturates the CPU on my test machine (2017 Dell laptop with an i7-6600U) so I'm not too optimistic that you could actually have 10 receivers active simultaneously on the Pi. Now that Pi's are becoming available again, I should pick up a RPi4b (or a 5) to test with. I also should profile the connector to see if the CPU usage could be reduced. 

I hope this helps.

Jim

N1ADJ

--
You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/d0c76e38-b13d-4e39-a669-f07999b15febn%40googlegroups.com.

[Don [N5SKT]]

Assuming then that this would also work on the Radioberry?

Don - N5SKT

To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/CAKYY9AKkPb8ZBXSZVLod%2BzHJyvYjaMoY%2BBcYFRzr1Sb-GHCPmw%40mail.gmail.com.

--

Best Regards,

Don - N5SKT

[Jim Ancona]

I don't know because I don't have one to test with. Since it's based on the HL2, I suspect will work. If you try and it doesn't, let me know and I'll try to fix it.

Jim

N1ADJ 

[Pez]

Hello Jim,

Thanks for your work, good timing! I have been running OpenWebRX+ (  https://github.com/luarvique/openwebrx  and  https://www.youtube.com/watch?v=YGd9Ym96pFY ) on a Pi4B for the last week, and it is so good that it is now a permanent fixture in my station. :) The connector plays nicely with other SDR software on my network, such as Thetis and SDR Console, without getting "in the way" of my TX operations, or locking me out of a session with Thetis, etc...) It seems to just sit there and work without causing any issues. The remote RX capability and decoding is extremely impressive. The connection to one (1) of my HL2's has been rock solid.

I currently have 1 x HL2 and 1 x RTL-SDR V3 (via rtl_tcp) connected and working, perfectly. However, I have a problem with adding my second HL2. Maybe you can help with this?:

My network config is well proven and stable with the 2 x HL2's. One of my HL2's is 192.168.1.123, and the other is 192.168.1.124. They both have different MAC addresses. I added the HL2 on .124 to OpenWebRX+ first, this is working great. When I add the second HL2 on .123, it cannot be reached, and instead the HL2 on .124 responds - the wrong radio is being used!... It looks like the directed UDP packet on UDP 1024 isn't working correctly, based on the static "   Remote IP  " address I enter in OpenWebRX+? Maybe it is still doing a UDP broadcast? (which I don't want). Or there is some kind of logic problem?

So at this this point, I can only have 1 x HL2 on the system. I will add the log below this message. Are you able to shine any light on this? (I hope you don't mind!).


Another quick question: How do you, or can you define the 4 x "RX Slices" separately in OpenWebRX? I currently add the HL2 once, then I can add as many profiles as I like. But I can't see how to define what "RX Slice" I want to use? Assuming if that works, I could have 4 different remote users, on 80m, 20m, 15m, and 10m, all the same time?

I understand the logic around the "last selection wins" you mentioned. That is exactly how it is working for me now and is all good, but I am wondering if there is a way to get more than one RX slice out of this... 

73

The log from 192.168.1.123 (when actually controlling the other HL2 on .124):

2023-10-06 01:29:09,761 - owrx.source.5dd09915-f4c5-4836-81bd-ba3c99807e05 - INFO - Started sdr source: hpsdrconnector --radio 192.168.1.123 --gain 0 --samplerate 384000 --frequency 14200000 -p 41001 -c 47657
2023-10-06 01:31:46,540 - owrx.source.5dd09915-f4c5-4836-81bd-ba3c99807e05 - INFO - STDOUT: 2023/10/06 01:31:46 client: Received an interrupt, stopping...

[Mike Lewis]

I have a RPi running OpenWebRX+ successfully working with 2 HL2s, a CaribouLite, and RTLSDR all at the same time.  The CaribouLite via SoapySDR is flaky (Caribou Lite software issues) but the HL2s have been solid. Don’t recall any magic to get them both working.

To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/98064d26-f53c-4e76-b871-515be37871d0n%40googlegroups.com.

[Pez]

I assume you have both HL2's set with a static IP (or static DHCP) address? And are your 2 x HL2's on the same LAN? 

73

[Mike Lewis]

Same LAN, DHCP reservation.   Before this config had them both working at the same time with other SDR apps like SparkSDR or my 2 PiHPSDR controllers and mixes of PC and Pi controller/apps.   I recently moved and on the new shack setup I had trouble with accessing the 2. After initially working OK, the radios randomly stopped responding to discovery attempts from SDR apps, the hermeslite.py script, and no ping responses.  At various times the MAC address would show up in Quisk and SparkSDR.  As part of the troubleshooting process I changed out a TP-Link 16 port managed switch I previously used OK with a unmanaged switch.  Not sure this was the issue but what I was seeing had me suspecting some sort of switch MAC address table entry memory gumming up the works.  I moved the radio to different switch ports and of course operated one at a time, played with assigning static Ips, reassigned MACs, deleted and hand entered new router MAC address DHCP assignments, and toggled Favor-DHCP options until I finally got things working again.  Don’t know the source of the issue, has not come back, everything back to my original DHCP reservation assignments.  I am running both at the same right now a few weeks later with no hiccups.  Mystery.

To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/8e3301c1-3647-4b42-b6c8-ab1e26f60efen%40googlegroups.com.

[Pez]

Thanks for the info. After lots of initial testing and experimentation, mine are both working perfectly with all other software. Thetis, SDR Console, SparkSDR and QUISK and PhHSPDR, all fine over LAN / VPN and even WAN, so I'm confident in my network, but regardless, your HL2's are obviously working in OpenWebRX+, so it is a mystery for now! 

73

[Jim Ancona]

Hi Pez, 

I've been travelling and haven't had much time to respond to emails. I'll be home later this week and hope to catch up then. I don't have a second HL2 to test with, so I suspect that we will have to rely on debug logs to troubleshoot. The code looks like it's doing the right thing. 

With OpenWebRX not running and both your HL2's on the network, please try running hpsdrconnector from the command line with debugging enabled like this:

hpsdrconnector --radio 192.168.1.123 --gain 0 --samplerate 384000 --frequency 14200000 --debug

The --radio parameter is the IP address of the HL2 you want to connect to. It should log some stuff to the terminal and then hang, waiting for a connection. At that point you can hit CTRL-C to stop it and copy the logs. If you can try that once for each radio, then we can compare the output. That may give us something to go on.

I'll reply to your question about multiple profiles when I get home where I'll have access to my HL2 and I can give you examples of what I mean.

Best wishes,

Jim

N1ADJ

To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/98064d26-f53c-4e76-b871-515be37871d0n%40googlegroups.com.

[Jiri Culak]

I managed to test it today and it works with all the hardware I have.   

Hermes 

Hermes LITE 2

RedPitaya. 

I have to admit I haven’t tried multi receiver or slices over four   That is standard gateware. But all I can say is it was working well. I compiled it manually on TV box with Ubuntu.22.04. 

4GB ram 

Atomcpu

Odesláno z iPhonu

12. 10. 2023 v 3:24, Jim Ancona <j...@anconafamily.com>:



You received this message because you are subscribed to a topic in the Google Groups "Hermes-Lite" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/hermes-lite/kJ7eg1hzv-Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to hermes-lite...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/CAKYY9AJCthiOM6oFAtKpD%2BCEqvi7_HHdFY__cRsnsoSvjb5Zqw%40mail.gmail.com.

[Jim Ancona]

I've updated the OpenWebRX wiki to better explain how to use multiple receivers with a single HL2:

Each receiver should be defined as a separate device in the OWRX settings. You can then set up profiles for each device. The connector will automatically start a receiver for each device. The same sample rate is used for all receivers, so starting a profile with a different sample rate will affect other running devices. To avoid problems, it's best to use a single sample rate for all profiles.

Does that make sense? If not, let me know and I'll try to explain further and improve the wording.

Jim

N1ADJ

[Jim Ancona]

Hi Jiri,

When you say it worked with Hermes, HL2 and Red Pitaya, was that testing each one individually or all three at the same time I've been reviewing the code and I don't think it will support running multiple radios at the same time. I do have some ideas about how to make it work. I don't have a second HL2 to test with, but I do have a RS-HFIQ/PiSDR that I plan to set up as a second radio. I'll report back when I know more.

Jim

N1ADJ

[Jiri Culak]

Hi Jim 

Right. Only one at a time. Also I don’t know if it’s possible but when four slices are enabled by gateware I was expecting to be able to tune to 160.80.40 and 20 all at the same time. It seems though that only single slice is currently working. When I change band on one instance it will change on all other instances 

Jiri

Odesláno z iPhonu

16. 10. 2023 v 3:52, Jim Ancona <j...@anconafamily.com>:



[Jim Ancona]

Here's an example of how I set up a single HL2 radio to use multiple receivers.

I created four OWRX devices, one for each receiver named HL2 Receiver 1-4. The settings for each device are the same.

Then I created one profile for each device, named for the band I want that receiver to be on. Example for the first receiver:

With one profile per receiver, multiple users can access the HL2 without interfering with one another. If you add multiple profiles per device, if one user of a device (== HL2 receiver) switches profiles, other users of that device will be affected. (If you are testing this, you must use multiple computers or browsers. Just opening multiple windows in the same browser will confuse things.)

Does that clarify things?

Jim

N1ADJ

[Jiri Culak]

Yep that makes sense. 

I win give it a go. I have a spare HL2 so might do 10 slices RX OpenWebRx. 

Sounds good. 

Just 

Odesláno z iPhonu

16. 10. 2023 v 14:43, Jim Ancona <j...@anconafamily.com>:



Here's an example of how I set up a single HL2 radio to use multiple receivers.

I created four OWRX devices, one for each receiver named HL2 Receiver 1-4. The settings for each device are the same.

<SDRDeviceSettings.png>

Then I created one profile for each device, named for the band I want that receiver to be on. Example for the first receiver:

[luc laureys]

Hi,

Have doing some tests..

4rx with Hl2 no problems

5Rx with redpitaya...8rx version of Pavel's software..No problems..(384version)....

Buth...it's only Hl2 OR Redpitaya NOT the both in same configuration of openwebrx last version...

Normal??

greeting Frm ON7KEC

Op maandag 16 oktober 2023 om 14:49:37 UTC+2 schreef m0i...@gmail.com:

[Jim Ancona]

Thanks Luc!

I've run a similar set of tests with my HL2 and a PiSDR+/RS-HFIQ and with similar results. In reviewing the code, it's clear that the connector currently only supports a single radio at a time. 

For the time being, I suggest that anyone running multiple HPSDR radios on their network choose one of them to use with OWRX and then identify it by IP address in the device profiles. Otherwise the connector will choose whichever radio responds first to its discovery request. If you specify profiles with different IPs, it will use whichever radio you activate first and then ignore the second IP, using the first radio instead.

It's possible for me to update the connector to support multiple radios, but it will be a fair amount of work. Is there anyone who will actually use this to regularly run multiple radios at the same time?

Thanks,

Jim

N1ADJ

To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/c3390e03-31df-4949-8d7a-1f4f5de23da3n%40googlegroups.com.

[Jiri Culak]

Hi Jim

Good question. I was thinking of using two HL2s one would have XVRTr for VHF but since this could done by using BPF and possibly dropping 10m for IF…..

I can only assume that it would be handy when I would offer multiple HPSDRs from two or more locations. If its too much work to do I guess it could wait?

Jirka 

Odesláno z iPhonu

22. 10. 2023 v 15:51, Jim Ancona <j...@anconafamily.com>:



To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/CAKYY9AJGJ-04VNem_smTXzMdikXCvE-EUmWuDANc-n1oSaZaAA%40mail.gmail.com.

[G4ZAL]

Hi Jim,

Slightly off topic but I have been testing my Radioberry with an FTDI FT2232H USB device, a so called 'juice' board (no need for the radioberry to be plugged onto the R-Pi)

I am trying to get it running with Openwebrx as a completely stand-alone unit.

With this setup it is possible to have 6 Rx's running at the same time.

However, there is a problem as the juice board uses port 1024 and so does the hpsdrconnector, creating a conflict and it cannot work as-is.

I have had it running on 2 seperate machines and when the juice and owrx are seperated on the network, it works fine.

Radioberry thread

https://groups.google.com/g/radioberry/c/3WRp30qC_lQ

Johan has created an issue on your github

https://github.com/jancona/hpsdrconnector/issues/8

I for one would love a solution to this if it's possible ;-)

OWRX does work fine with any one of my HL2's but 6 rx's is apealing without tying up my HL2.

Sorry for the bandwidth here.

Nigel

G4ZAL

[Jim Ancona]

Yes, I saw Johan's issue. I'll look in the next few days to see if I can change the UDP port used during discovery.

Also, I may have something to report on supporting multiple radios soon.

Jim

N1ADJ

To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/d5a79639-a058-4a24-a011-42769bbd8914n%40googlegroups.com.

[G4ZAL]

Hi Jim,

It was me that found the problem and reported on the radioberry forum.

I grabbed the armhf deb package from your github and installed it in my R-Pi 4/OWRX

Happy to report in now finds and runs my rb-juice board with 127.0.0.1 configured in each OWRX profile for the IP address.

Need to properly test more over the coming days.

Many thanks for your rapid response.

Nigel

G4ZAL

[Jim Ancona]

Hi,

The latest development release of OWRX now supports running multiple HPSDR radios. In order to do that, you must: 

1. Specify the IP address for each HPSDR radio using Remote IP in Device Settings.

2. Set a unique value for each HPSDR radio using Server port in Device Settings. If Server port isn't set, it defaults to port 7300. So you can use the default on one radio and 7301 for the second one.

Also, the new release contains code that should address G4ZAL's issue with the Radioberry.

Let me know how this works for you.

Jim

N1ADJ

[Jim Ancona]

I'd be careful using the packages from my repo because they're liable to conflict with the OWRX packages. Now that you've confirmed it works you might want to uninstall my package and install the updated one from the official repo.

Jim

N1ADJ

To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/bb4a9a09-12b1-4067-87be-5bb5ee1822e2n%40googlegroups.com.

[luc laureys]

Tks Jim,

So now it's possible to use my Pitay and the Hl2 together...would be great..;Pitaya for the "small" bands (192) and the Hl for the bigger one (384)

i did in the past a patch for the pitaya to work also on 384 buth i have problems now..dont work anny more..;

so for the 2 it sould be like 192.168.178.2:7300 and 192.168.178.5:7301 in the device settings? correct Jim??

Buth i must solve the other problem..high server cpu valeu...90% and higher even with one connection...any clue for that Jim?

already integrated in the last version of owrx??

Tks for the good job 73

On7kec - Luc

Op zondag 29 oktober 2023 om 01:46:00 UTC+2 schreef Jim Ancona N1ADJ:

[Jim Ancona]

Trying to track down the high CPU usage in the connector is on my todo list.

Jim

N1ADJ

To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/3a072e03-acae-4dc7-a875-6c1b72872332n%40googlegroups.com.

[Jim Ancona]

I did some investigation of the hpsdrconnector code and made some changes that have lowered CPU usage in the connector and in OpenWebRX itself. My crude measurements show around a 15 to 20% decrease in CPU for the hpsdrconnector process and a 50% decrease for the openwebrx.py process. I'll be interested to hear if that's noticeable.

Jim

N1ADJ

[G4ZAL]

Hi Jim,

I just installed 0.6.5 deb in my R-Pi4 OWRX+ test setup and can confirm the CPU now sits at ~40% with 4 clients connected on 4 bands at 192kHz bandwidth.

Big improvement on previous as before 4 clients regularly hit 90-100% CPU.

BTW, I'm not concerned about breaking my test setup and if that did happen it's only minutes to burn a new SD card and start afresh.

Thanks for your efforts Jim, much apreciated.

Nigel

G4ZAL

[Jiri Culak]

Hello, I cannot seem to be able to update from regular to OWRX plus. Shall I just do clean install ??

I also tested manual connector and confirm that multiple clients work very well  

Odesláno z iPhonu

30. 10. 2023 v 17:10, G4ZAL <devon...@gmail.com>:

Hi Jim,

To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/a8f9f477-a147-408b-a857-d993defed0cbn%40googlegroups.com.

[G4ZAL]

Hi Jiri,

To upgrade to OWRX+ depends a bit on your original install method and OS, but something in here should get you up and running...

https://luarvique.github.io/ppa/

HTH

Nigel

G4ZAL

[luc laureys]

Hi Jim,

Is there a limitation to the number of rx in your connector?

Why...i did the following test..

HL2 with the ip 123.123.123.100:7300 and for every rx a take a other port number...so max of 4 for the HL2

after that i try to connect my Redpitaya with 6 receiver 384Sr version of Pavel

so is did then exmpl..123.123.123.111:7400 to 7406

thats works for 1rx of the pitaya and after the fifth its end...no longer possible to use more bands...

same with the 6rx Pitaya after 5 its game over...

Normal Jim?

Greetings and tks for good job...

ON7KEC

Op dinsdag 31 oktober 2023 om 10:15:05 UTC+1 schreef G4ZAL:

[Jim Ancona]

Hi Luc,

Sorry, you've misunderstood or I haven't explained it well enough. Here is the wiki page on the setup: https://github.com/jketterl/openwebrx/wiki/HPSDR-(including-Hermes-Lite-2)-device-notes

You need a Server Port for each radio, not for each receiver. Since you have two radios you need two server ports.

On Thu, Nov 2, 2023 at 6:53 AM luc laureys <ic706m...@gmail.com> wrote:

HL2 with the ip 123.123.123.100:7300 and for every rx a take a other port number...so max of 4 for the HL2

No, all the HL2 receivers should be defined with Server Port 7300.

 

after that i try to connect my Redpitaya with 6 receiver 384Sr version of Pavel

so is did then exmpl..123.123.123.111:7400 to 7406

All the  Redpitaya receivers must be defined with the same Server Port, so 7400 in your example.

 

I hope that clarifies things. Let me know if you can suggest better wording on the wiki page.

Jim

N1ADJ

[luc laureys]

Hi To All,

Good afternoon...

So Jim EVERYTHING running verry good now with the new hpsdrconnector..great job

I have now running a Hermesligt2 with 4 receivers together with a Redpitaya with 6 Receivers both with 384ks

indeed like you say..ip and port for every hardwareRx...

buth ist only  available in the "DEV" version...correct?,

Do i have the possibility to insert this my self in the owrx?,

Tks Jim and 73,

ON7KEC

Op donderdag 2 november 2023 om 12:46:41 UTC+1 schreef Jim Ancona N1ADJ:

[Jim Ancona]

On Sat, Nov 4, 2023 at 10:12 AM luc laureys <ic706m...@gmail.com> wrote:

I have now running a Hermesligt2 with 4 receivers together with a Redpitaya with 6 Receivers both with 384ks

indeed like you say..ip and port for every hardwareRx...

Great! How is CPU usage with many active receivers?

buth ist only  available in the "DEV" version...correct?,

Yes.

 

Do i have the possibility to insert this my self in the owrx?,

All of my changes to support multiple radios are in owrx/source/hpsdr.py. So installing the new hpsdrconnector plus hpsdr.py from Jakob's develop branch on top of version 1.2.2 might work. I haven't tried it. Obviously changes like this might also break your installation.

Good luck,

Jim

N1ADJ

[Jon AB8WU]

Here's a 4 segment HL2 that I have up on my fiber at least this week for testing if you want to see how the load and latency works. It's fed by an Alphaloop military vertical with some added ground plane.

https://owrx.soolabs.ca

Jon

AB8WU/VE3

[ic706mk2]

hi Jim

so i did the test with a version of 6rx(384Ks) and one with 8rx(192Ks) of Pavels software for redpitaya and the hpsdrconnector tells me every time

sparksdr tells me Hermes6 and Hermes8 with the difference software!

server(7301): Listening to radio on 192.168.178.150:1024
2023-11-06 14:38:27,547 - owrx.source.4337955b-4ebd-4e2b-b024-624ef903ed87 - INFO - STDOUT: 2023/11/06 14:38:27 [INFO] server(7301): Starting Hermes radio with up to 5 receivers on 192.168.178.150:1024

why the connector only find 5Rx

greets

Op zo 5 nov 2023 om 18:37 schreef Jon AB8WU <jrho...@gmail.com>:

--

You received this message because you are subscribed to a topic in the Google Groups "Hermes-Lite" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/hermes-lite/kJ7eg1hzv-Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to hermes-lite...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/90cd7e82-58ab-4bd8-9a70-00f79ed003e1n%40googlegroups.com.

[Jim Ancona]

As I mentioned earlier, the number of receivers in the log message is reported by the radio during discovery. So the Red Pitaya firmware is evidently reporting 5 even though it supports more. You can try turning on debug in the device profile and sending me the logs. Ideally this would be fixed in the radio software, but I may be able to work around it. You might also ask Pavel what his software reports.

Jim

You received this message because you are subscribed to the Google Groups "Hermes-Lite" group.

To unsubscribe from this group and stop receiving emails from it, send an email to hermes-lite...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/CAJ2gCnZHwpo7Aj3UGZ%3DrTJmWcfHZpM3vdVf_D1r2P%2BBnK%3DCPaQ%40mail.gmail.com.

[Alan Hopper]

Hi Jim,

my experience with receiver numbers (from memory):-

sending the number of receivers in the discovery packet was an extension to the protocol for Hermes Lite (1&2). The standard Hermes and other Anan radios generally don't send it so spark does a best guess based on radio type and version for them. Spark does check the discovery for receiver count on the off chance on non Hermes lite (type 6) radios. If the red pitaya is reported by spark as Hermes 6 or Hermes 8 it indicates it is reporting as a type 1 radio (Hermes) but with the extra data in the discovery packet (as 6 and 8 are not known values for Hermes).

73 Alan M0NNB

[Jim Ancona]

Thanks, Alan! That was helpful.

I checked my code and the log message again and I think Luc's Red Pitaya is reporting that it's a Hermes (type 2). Currently that's hard-coded as 5 receivers. I probably got that from some other code I looked at. If I get the debug logs, I may be able to come up with code that will handle this better. 

Luc, the ideal would be if you could capture logs for discovery with the different software versions you've tried. The lines I'm looking for are the ones containing the string "[DEBUG] discover". You can stop capturing as soon as the OWRX client starts receiving.

Thanks,

Jim

N1ADJ

To view this discussion on the web visit https://groups.google.com/d/msgid/hermes-lite/19677aba-c6d8-46e9-962f-5ad05b4ddff8n%40googlegroups.com.

[Jim Ancona]

Luc was very helpful in collecting debug information and I was able to implement improved Red Pitaya support so that the connector recognizes the number of receivers properly. Luc has tested the fix and tells me it works. It's now available in the OWRX experimental repository. 

Thanks to Alan and Luc for their help with this!

Jim

N1ADJ