<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>I remember doing some tests with my Mercury-Penelope setup while Warren was developing PureSignal, but don't remember details. I think the key was to have identical processing for the sampled amplifier output (using Mercury) and the data sent to the DAC on Penny--so that both signals would be go through identical CIC-FIR filters and decimation. Mercury has some capability for multiple receivers, but I'm not sure how that processing might compare to what's needed for PureSignal. I would think that, if Mercury were to digitize the much-attenuated amplifier output (perhaps using a relay), it might be possible to do the comparison using the original Tx signal before it is upconverted, rather than a downconverted-upconverted Tx signal. There would be significant delay to be taken into account, but this might be deduced mathematically. Unfortunately, I'm not familiar with the details of the PureSignal algorithm. While I have some experience with Verilog design and implementation, I suspect it might be insufficient to make required changes to FPGA code.</p>
<p>I, too, would love to be able to use PureSignal with my legacy hardware...</p>
<p>David WA8YWQ</p>
<p>On 2023-05-28 06:41, laurence@nicklebyhouse.co.uk wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">***** High Performance Software Defined Radio Discussion List *****<br /> <br /> I don't think it is possible. The reason is:<br /> <br /> Puresignal uses an ADC to digitise the amplified output; that bit is<br /> possible with just one Mercury. It also needs a downconverted *digital*<br /> sample stream from the upconverted digital TX signal, which would need the<br /> TX board to fee out a downconverted signal - and as far as I know that isn't<br /> possible.<br /> <br /> <br /> <br /> Regards,<br /> <br /> Laurence Barker<br /> <a href="mailto:laurence@nicklebyhouse.co.uk">laurence@nicklebyhouse.co.uk</a><br /> <br /> -----Original Message-----<br /> From: Hpsdr <<a href="mailto:hpsdr-bounces@lists.openhpsdr.org">hpsdr-bounces@lists.openhpsdr.org</a>> On Behalf Of George Byrkit<br /> Sent: Sunday, May 28, 2023 12:45 PM<br /> To: <a href="mailto:hpsdr@lists.openhpsdr.org">hpsdr@lists.openhpsdr.org</a><br /> Subject: Re: [hpsdr] PureSignal for HPSDR/Penelope/Mercury<br /> <br /> ***** High Performance Software Defined Radio Discussion List *****<br /> <br /> While it might be technically possible, there are lots of hurdles to<br /> overcome, and PureSignal was not designed/implemented to work on the Mercury<br /> receiver.<br /> <br /> 1) PureSignal needs an additional phase/clock-synchronous receiver channel<br /> to get the feedback to correct the signal. Mercury only has ONE receiver<br /> channel. You'd have to hand-stack multiple Mercury boards to begin with...<br /> <br /> 2) PureSignal needs more FPGA memory space for code and everything. A<br /> Cyclone III doesn't really have that available for you.<br /> <br /> 3) perhaps bus timing and all are also in the way.<br /> <br /> You should reach out to Dr Warren Pratt, NR0V, who implemented PureSignal.<br /> <br /> 73,<br /> George Byrkit, K9TRV<br /> <br /> -----Original Message-----<br /> From: Hpsdr <<a href="mailto:hpsdr-bounces@lists.openhpsdr.org">hpsdr-bounces@lists.openhpsdr.org</a>> On Behalf Of Michael Carey<br /> Sent: Sunday, May 28, 2023 4:57 AM<br /> To: <a href="mailto:hpsdr@lists.openhpsdr.org">hpsdr@lists.openhpsdr.org</a><br /> Subject: [hpsdr] PureSignal for HPSDR/Penelope/Mercury<br /> <br /> ***** High Performance Software Defined Radio Discussion List *****<br /> <br /> <br /> _______________________________________________<br /> HPSDR Discussion List<br /> To post msg: <a href="mailto:hpsdr@openhpsdr.org">hpsdr@openhpsdr.org</a><br /> Subscription help:<br /> <a href="http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org" target="_blank" rel="noopener noreferrer">http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org</a><br /> HPSDR web page: <a href="http://openhpsdr.org" target="_blank" rel="noopener noreferrer">http://openhpsdr.org</a><br /> Archives: <a href="http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/" target="_blank" rel="noopener noreferrer">http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/</a><br /> <br /> _______________________________________________<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" target="_blank" rel="noopener noreferrer">http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org</a><br /> HPSDR web page: <a href="http://openhpsdr.org" target="_blank" rel="noopener noreferrer">http://openhpsdr.org</a><br /> Archives: <a href="http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/" target="_blank" rel="noopener noreferrer">http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/</a><br /> </div>
</blockquote>
</body></html>