Tom-McDermott / gr-hpsdr

gnuradio interface module for HPSDR Hermes / Metis, and Red Pitaya (using OpenHPSDR protocol 1)
Other
16 stars 19 forks source link

is 8 receivers supported or not? #22

Open jyrts opened 1 year ago

jyrts commented 1 year ago

I'm using RedPitaya SDR in HPSDR receiver mode with CW Skimmer Server - it supports up to 8 receivers no problem.

Does the gr-hpsdr with RedPitaya SDR support 7 or is also capable of 8 receivers?

Tom-McDermott commented 1 year ago

Hi - There is an overlap in register definitions that prevents using the 8th receiver on OpenHPSDR systems. So the limit is 7 receivers.

-- Tom, N5EG

On Mon, Oct 24, 2022 at 9:13 AM jyrts @.***> wrote:

I'm using RedPitaya SDR in HPSDR receiver mode with CW Skimmer Server - it supports up to 8 receivers no problem.

Does the gr-hpsdr with RedPitaya SDR support 7 or is also capable of 8 receivers?

— Reply to this email directly, view it on GitHub https://github.com/Tom-McDermott/gr-hpsdr/issues/22, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZR5HFEN3RTCNAQCQJBKBDWE2YRJANCNFSM6AAAAAARNEJXXQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

pavel-demin commented 1 year ago

I do not think that there is an overlap.

The idea for the 8th receiver comes from HermesIntf.

The receiver compatible with HPSDR for the Red Pitaya board uses same code/address for the 8th receiver as used in HermesIntf.

The code/address used for the 8th receiver is

C0
0 0 1 0 0 1 0 x   C1, C2, C3, C4   NCO Frequency in Hz for Receiver 8

The last code/address described in the HPDSR protocol documentation is

C0
0 0 1 0 0 0 1 x

Thus, the code used for the 8th receiver is outside the range of codes/addresses described in the HPDSR protocol documentation.

Tom-McDermott commented 1 year ago

HI Pavel - nice to meet you (virtually).

The latest version of the HPSDR - USB Data Protocol document I could find is V 1.60. This defines the address for Receiver 7 as C0 0 0 0 1 0 0 0 x which is different from what you have listed.

I am guessing that there is probably some new document that defines changes to the protocol. I do not have that document, and don't even know what it would be called.

Is it possible for you to send me that document?

-- Tom, N5EG

On Tue, Nov 29, 2022 at 2:28 PM Pavel Demin @.***> wrote:

I do not think that there is an overlap.

The idea for the 8th receiver comes from HermesIntf https://github.com/k3it/HermesIntf.

The receiver compatible with HPSDR for the Red Pitaya board uses same code/address for the 8th receiver as used in HermesIntf https://github.com/k3it/HermesIntf.

The code/address used for the 8th receiver is

C0 0 0 1 0 0 1 0 x C1, C2, C3, C4 NCO Frequency in Hz for Receiver 7

The last code/address described in the HPDSR protocol documentation is

C0 0 0 1 0 0 0 1 x

Thus, the code used for the 8th receiver is outside the range of codes/addresses described in the HPDSR protocol documentation.

— Reply to this email directly, view it on GitHub https://github.com/Tom-McDermott/gr-hpsdr/issues/22#issuecomment-1331401616, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABZR5HH7IUCT2JL3456XWATWKZ7SNANCNFSM6AAAAAARNEJXXQ . You are receiving this because you commented.Message ID: @.***>

pavel-demin commented 1 year ago

Sorry for the wrong receiver number in my previous comment. It is receiver 8 of course. I just corrected it in my previous comment.

I was looking at version 1.58 (USB_protocol_V1.58.doc). This was the latest version that was available when I was playing around with the HPSDR protocol.

I see that there is now version 1.60 and it has a new not very well documented command that indeed has the same code/address as the code/address used by HermesIntf for the 8th receiver.

There are still a lot of unused codes/addresses. Is there a code/address you would prefer to use for the 8th receiver? I can easily add this code/address to my application for the Red Pitaya board.

Tom-McDermott commented 1 year ago

Thank you for the information, Pavel. I don't see a need to change the C0 address of Rx_8 at this time. This task will take some time to complete as it is queued behind 3 others (one of which is quite large).