<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Phil, <div><br></div><div>Passing the phase word instead of the actual frequency seems to improve things when using multiple Mercury receiver boards on Atlas but it's not good enough, I'm afraid. The phase relationships between boards seem to be stable under frequency/band changes alright but the values change after a power cycle of the Atlas bus. </div><div><br></div><div>It appears to me that the approach used in Angelia is the better method; i.e., multiple ADCs on a single board. Unless, of course, I'm not implementing the approach you suggested in the precise way that you did. Actually, we can't do it precisely the same way, as you know, because you are working with a single board, Hermes, not a Penny/Merc combination for your VNA. </div><div><br></div><div>In my test I simply calculate the phase word in Metis as it normally would be done in Mercury then pass the 32-bit phase word to the Merc boards as one of the frequencis in the Atlas broadcast to the Mercs which then use it as a direct input to the receiver module(s) in Mercury instead of using the original C122_sync_phase_word variable that is calculated in Mercury. </div><div><br></div><div>Thanks for the suggestion though; it does seem to help, but not enough for repeatable nulling/steering/DF applications with multiple Mercs, I think. To solve this issue properly we'll need to put all the ADCs on a single board, in my opinion. </div><div><br></div><div>Abhi and I are presently discussing how we might do that very thing using 4 ADCs on a single board on the Atlas bus.</div><div><br></div><div>73, Joe K5SO</div><div><br></div><div><br><div><div>On Aug 5, 2012, at 6:13 AM, Joe Martin K5SO wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">***** High Performance Software Defined Radio Discussion List *****<br><br><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Phil, <div><br></div><div>That is wonderful news!! In fact, if the "phase word" approach works for multiple Mercury boards too then this may be the breakthrough approach I was seeking and could make using perhaps up to five Mercury boards for DF and beam steering feasible with the Atlas bus. </div><div><br></div><div>I'll definitely check it out! Great observation! Thanks!!</div><div><br></div><div>73, Joe K5SO</div><div><br><div><div>On Aug 5, 2012, at 1:08 AM, Phil Harman wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space" dir="ltr">
<div dir="ltr">
<div style="FONT-FAMILY: 'Arial'; COLOR: #000000; FONT-SIZE: 10pt">
<div>Hi Joe,</div>
<div> </div>
<div>There may be a solution to this issue. I’ve been writing the code to
turn Hermes into a Vector Network Analyser. IN which case I need to guarantee
the phase relationship between the Tx and Rx is totally consistent and
repeatable across numerous power cycles. Since the Tx and Rx FPGA
code run off the same clock on the Hermes board then that is half the
problem solved.</div>
<div> </div>
<div>What I found is if I feed the same frequency to the individual
frequency-to-phase converter code for the Tx and Rx CORDICs then every
time I change frequency the phase relationship varies in a totally uncontrolled
manner. However, if I calculate the phase word from the frequency and feed
the phase word to *both* CORDICs then the phase relationship is rock
steady under all conditions that I’ve tested so far. </div>
<div> </div>
<div>In which case if we run all the Mercury boards off the same 122.88 MHZ
clock and feed the phase word, calculated in say Metis, over the Atlas bus
rather than the frequency then we may find an improvement.</div>
<div> </div>
<div>73 Phil....VK6APH </div>
<div> </div>
<div> </div></div></div></div></blockquote></div></div></div>_______________________________________________<br>HPSDR Discussion List<br>To post msg: <a href="mailto:hpsdr@openhpsdr.org">hpsdr@openhpsdr.org</a><br>Subscription help: <a href="http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org">http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org</a><br>HPSDR web page: <a href="http://openhpsdr.org">http://openhpsdr.org</a><br>Archives: <a href="http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/">http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/</a></blockquote></div><br></div></body></html>