[hpsdr] questions about the protocol (v1.36)

[David McQuate]

(4th question):   --

   If multiple Mercury boards are to be used some jumpers on the boards 
must be set.  These identify which Mercury is #1, etc.  If multiple 
receivers on a single Mercury are to be used, no jumper changes are 
needed.  (See info on diversity setup)

(from USB_protocol_V1.36.doc) --

The low order bit of c0 (the MOX bit) switches the radio to Tx if the 
bit is 1.
If you click the "MOX" button on PowerSDR or KISS Konsole, that program 
sets this bit, which controls the T/R relay.

If C0 is (binary) 0000 001x, the content of c1, c2, c3, c4 specifies the 
frequency for Penelope, PennyLane and (future) Apollo ATU.

if c0 is 0000 010x, c1,c2,c3,c4 specifies the frequency (in Hz) for 
receiver 1 (numbering starts with 1)
similarly
c0
0000 011x   receiver 2
0000 100x  receiver 3
0000 101x  receiver 4

(While this document shows that there are provisions in the PC to HPSDR 
data protocol for more receivers (up to 7), there is no Mercury firmware 
that supports more than 4 receivers.  The Mercury FPGA usage is near 
100%, so, unless there's a major change in algorithm and re-writing, 4 
will remain the upper limit.

When using more than one receiver on a single Mercury, when c0 = 0000 
000x,   in c4, the 3 bits indicated by "rrr" xxrr rxxx should be set as 
follows:   000 means one receiver, 001 means two recevers, etc

73,
Dave
wa8ywq


On 3/17/2012 8:13 AM, Erik Anderson wrote:
> ***** High Performance Software Defined Radio Discussion List *****
>
>
>
> I've been going over the protocol spec for a little while now (there's 
> an awful lot of stuff in here) and there are a few questions I could 
> use some clarification on:
>
> (*) What is MOX?
>
> (*) How do I interrogate the CC bits (for autodetection purposes) 
> without actually fully turning the radio on?  I'm assuming that it's 
> inherently impossible to do this (unless [00]C1[67]=00 has any 
> meaning), in which case I'm curious as to whether there is a neutral 
> configuration that I can send that would work in all cases so I can 
> turn it on long enough to get the CC codes (i.e. without unnecessary 
> clicking, alex filter swaps, conflict with custom clock rewriting, 
> blowing out the ADC, etc)
>
> (*) Should the PC reset its sending sequence number on every EFFE04 
> command?  The documentation makes multiple references to "start" and 
> "stop" commands, although after sending an EFFE0401 command, there is 
> no really clear indication as to whether EFFE0402 is a "stop" or a 
> "start" command (it's both).  Am I resetting only when the board is 
> going completely idle (i.e. only after EFFE0400)?
>
> (*) (I'm fairly sure this one has come up often enough to be on a FAQ 
> somewhere) I remember reading that the current mercury firmware now 
> supports 4 receivers on the stable branch.  However the protocol makes 
> no distinction between receivers and boards, permitting you to receive 
> from up to 4 receivers and set the frequency on up to 7.  How does one 
> specify which board each receiver is assigned to?
>
>
> _______________________________________________
> HPSDR Discussion List
> To post msg: hpsdr at openhpsdr.org
> Subscription help: http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
> HPSDR web page: http://openhpsdr.org
> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20120317/4a62cbc1/attachment-0004.htm>