http://openhpsdr.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=K5SO 2026-04-08T04:32:01Z User contributions MediaWiki 1.26.0 http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4524 2014-02-13T21:43:31Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This option is supported by current versions of OpenHPSDR PowerSDR on Windows, cuSDR on Windows and Linux, KISS Konsole on Windows, and ghpsdr3 on Linux.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 13FEB2014)<br /> <br /> This option is supported by current versions of OpenHPSDR PowerSDR and cuSDR. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two Mercury receiver boards is implemented in Open HPSDR PowerSDR. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 13FEB2014)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4523 2014-02-13T21:40:07Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This option is supported by current versions of OpenHPSDR PowerSDR on Windows, cuSDR on Windows and Linux, KISS Konsole on Windows, and ghpsdr3 on Linux.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 13FEB2014)<br /> <br /> This option is supported by current versions of OpenHPSDR PowerSDR and cuSDR using two, three, or four Mercury boards, Angelia (2 ADCs), and (in development, Orion with 3 ADCs). <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two Mercury receiver boards is implemented in Open HPSDR PowerSDR. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 13FEB2014)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4522 2014-02-13T21:38:17Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This option is supported by current versions of OpenHPSDR PowerSDR on Windows, cuSDR on Windows and Linux, KISS Konsole on Windows, and ghpsdr3 on Linux.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 13FEB2014)<br /> <br /> This option is supported by current versions of OpenHPSDR PowerSDR and cuSDR using two, three, or four Mercury boards, Angelia (2 ADCs), and (in development, Orion with 3 ADCs). <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two Mercury receiver boards is implemented in Open HPSDR PowerSDR. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 27JUL2012)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect a twisted-wire pair to pins 4 &amp; 5 of J1 (LVDS header) of the &quot;master&quot; Mercury board and the other end to pins 1 &amp; 2 of J1 (LVDS header) on the &quot;slave&quot; Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4521 2014-02-13T21:36:45Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This option is supported by current versions of OpenHPSDR PowerSDR on Windows, cuSDR on Windows and Linux, KISS Konsole on Windows, and ghpsdr3 on Linux.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 13FEB2014)<br /> <br /> This option is supported by current versions of OpenHPSDR PowerSDR and cuSDR using two, three, or four Mercury boards, Angelia (2 ADCs), and (in development, Orion with 3 ADCs). <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two Mercury receiver boards is implemented in Open HPSDR PowerSDR. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v3.1 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: current OpenHPSDR firmware for Metis, Mercury, and Penelope.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 27JUL2012)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect a twisted-wire pair to pins 4 &amp; 5 of J1 (LVDS header) of the &quot;master&quot; Mercury board and the other end to pins 1 &amp; 2 of J1 (LVDS header) on the &quot;slave&quot; Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4520 2014-02-13T21:30:43Z

<p>K5SO: /* Multiple Receivers on a single Mercury */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This option is supported by current versions of OpenHPSDR PowerSDR on Windows, cuSDR on Windows and Linux, KISS Konsole on Windows, and ghpsdr3 on Linux.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 7NOV2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury using two Mercury boards and PowerSDR v.2.2.3.triple_Mercury using three Mercury boards. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 26OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v3.1 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> '''Triple Mercury board setups (Windows):'''<br /> Operation using three coherent Mercury receivers is implemented in PowerSDR v2.2.3.triple_Mercury (K5SO 7NOV2011). This program is ALPHA code and is under active development and is frequently changed. The goal is to develop a beam steering program for three-antenna receiving arrays by means of appropriate phasing of the three independent, coherent, IQ data streams. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis. PowerSDR v2.2.3.triple_Mercury will run with 1, 2, or 3 Mercury boards. The firmware and the PC program are available for download at http://k5so.com.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 27JUL2012)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect a twisted-wire pair to pins 4 &amp; 5 of J1 (LVDS header) of the &quot;master&quot; Mercury board and the other end to pins 1 &amp; 2 of J1 (LVDS header) on the &quot;slave&quot; Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4519 2014-02-13T21:30:24Z

<p>K5SO: /* Multiple Receivers on a single Mercury */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by current versions of OpenHPSDR PowerSDR on Windows, cuSDR on Windows and Linux, KISS Konsole on Windows, and ghpsdr3 on Linux.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 7NOV2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury using two Mercury boards and PowerSDR v.2.2.3.triple_Mercury using three Mercury boards. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 26OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v3.1 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> '''Triple Mercury board setups (Windows):'''<br /> Operation using three coherent Mercury receivers is implemented in PowerSDR v2.2.3.triple_Mercury (K5SO 7NOV2011). This program is ALPHA code and is under active development and is frequently changed. The goal is to develop a beam steering program for three-antenna receiving arrays by means of appropriate phasing of the three independent, coherent, IQ data streams. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis. PowerSDR v2.2.3.triple_Mercury will run with 1, 2, or 3 Mercury boards. The firmware and the PC program are available for download at http://k5so.com.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 27JUL2012)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect a twisted-wire pair to pins 4 &amp; 5 of J1 (LVDS header) of the &quot;master&quot; Mercury board and the other end to pins 1 &amp; 2 of J1 (LVDS header) on the &quot;slave&quot; Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4355 2012-07-27T18:40:11Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 7NOV2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury using two Mercury boards and PowerSDR v.2.2.3.triple_Mercury using three Mercury boards. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 26OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v3.1 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> '''Triple Mercury board setups (Windows):'''<br /> Operation using three coherent Mercury receivers is implemented in PowerSDR v2.2.3.triple_Mercury (K5SO 7NOV2011). This program is ALPHA code and is under active development and is frequently changed. The goal is to develop a beam steering program for three-antenna receiving arrays by means of appropriate phasing of the three independent, coherent, IQ data streams. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis. PowerSDR v2.2.3.triple_Mercury will run with 1, 2, or 3 Mercury boards. The firmware and the PC program are available for download at http://k5so.com.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 27JUL2012)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect a twisted-wire pair to pins 4 &amp; 5 of J1 (LVDS header) of the &quot;master&quot; Mercury board and the other end to pins 1 &amp; 2 of J1 (LVDS header) on the &quot;slave&quot; Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4354 2012-07-27T18:39:19Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 7NOV2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury using two Mercury boards and PowerSDR v.2.2.3.triple_Mercury using three Mercury boards. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 26OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v3.1 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> '''Triple Mercury board setups (Windows):'''<br /> Operation using three coherent Mercury receivers is implemented in PowerSDR v2.2.3.triple_Mercury (K5SO 7NOV2011). This program is ALPHA code and is under active development and is frequently changed. The goal is to develop a beam steering program for three-antenna receiving arrays by means of appropriate phasing of the three independent, coherent, IQ data streams. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis. PowerSDR v2.2.3.triple_Mercury will run with 1, 2, or 3 Mercury boards. The firmware and the PC program are available for download at http://k5so.com.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 18DEC2011)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect a twisted-wire pair to pins 4 &amp; 5 of J1 (LVDS header) of the &quot;master&quot; Mercury board and the other end to pins 1 &amp; 2 of J1 (LVDS header) on the &quot;slave&quot; Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4258 2011-12-19T01:56:16Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 7NOV2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury using two Mercury boards and PowerSDR v.2.2.3.triple_Mercury using three Mercury boards. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 26OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v3.1 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> '''Triple Mercury board setups (Windows):'''<br /> Operation using three coherent Mercury receivers is implemented in PowerSDR v2.2.3.triple_Mercury (K5SO 7NOV2011). This program is ALPHA code and is under active development and is frequently changed. The goal is to develop a beam steering program for three-antenna receiving arrays by means of appropriate phasing of the three independent, coherent, IQ data streams. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis. PowerSDR v2.2.3.triple_Mercury will run with 1, 2, or 3 Mercury boards. The firmware and the PC program are available for download at http://k5so.com.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 18DEC2011)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect a twisted-wire pair to pins 1 &amp; 2 of J1 (LVDS header) of the &quot;master&quot; Mercury board and the other end to pins 4 &amp; 5 of J1 (LVDS header) on the &quot;slave&quot; Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4257 2011-12-19T01:54:56Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 7NOV2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury using two Mercury boards and PowerSDR v.2.2.3.triple_Mercury using three Mercury boards. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 26OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v3.1 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> '''Triple Mercury board setups (Windows):'''<br /> Operation using three coherent Mercury receivers is implemented in PowerSDR v2.2.3.triple_Mercury (K5SO 7NOV2011). This program is ALPHA code and is under active development and is frequently changed. The goal is to develop a beam steering program for three-antenna receiving arrays by means of appropriate phasing of the three independent, coherent, IQ data streams. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis. PowerSDR v2.2.3.triple_Mercury will run with 1, 2, or 3 Mercury boards. The firmware and the PC program are available for download at http://k5so.com.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 31OCT2011)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect a twisted-wire pair to pins 1 &amp; 2 of J1 (LVDS header) of the &quot;master&quot; Mercury board and the other end to pins 4 &amp; 5 of J1 (LVDS header) on the &quot;slave&quot; Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4219 2011-11-08T01:23:05Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 7NOV2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury using two Mercury boards and PowerSDR v.2.2.3.triple_Mercury using three Mercury boards. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 26OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v3.1 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> '''Triple Mercury board setups (Windows):'''<br /> Operation using three coherent Mercury receivers is implemented in PowerSDR v2.2.3.triple_Mercury (K5SO 7NOV2011). This program is ALPHA code and is under active development and is frequently changed. The goal is to develop a beam steering program for three-antenna receiving arrays by means of appropriate phasing of the three independent, coherent, IQ data streams. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis. PowerSDR v2.2.3.triple_Mercury will run with 1, 2, or 3 Mercury boards. The firmware and the PC program are available for download at http://k5so.com.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 31OCT2011)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect, using a small coaxial cable, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> <br /> ''Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to another Mercury board via the LVDS (low voltage differential signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> ''<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4218 2011-11-08T01:19:52Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 7NOV2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury using two Mercury boards and PowerSDR v.2.2.3.triple_Mercury using three Mercury boards. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 26OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v3.1 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> '''Triple Mercury board setups (Windows):'''<br /> Operation using three coherent Mercury receivers is implemented in PowerSDR v2.2.3.triple_Mercury (K5SO 7NOV2011). This program is ALPHA code and is under active development and is frequently changed. The goal is to develop a beam steering program for three-antenna receiving arrays by means of appropriate phasing of the three independent, coherent, IQ data streams. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis. The firmware and the PC program are available for download at http://k5so.com.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 31OCT2011)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect, using a small coaxial cable, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> <br /> ''Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to another Mercury board via the LVDS (low voltage differential signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> ''<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4216 2011-10-31T20:22:07Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 31OCT2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury using two Mercury boards and PowerSDR v.19.3.5.steering1 using three Mercury boards. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 10OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v3.1 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> '''Triple Mercury board setups (Windows):'''<br /> Operation using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.5.steering1 (K5SO 18SEP2011). This program is ALPHA code and is under active development and is frequently changed. The goal is to develop a beam steering program for three-antenna receiving arrays by means of appropriate phasing of the three independent, coherent, IQ data streams. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis. The firmware and the PC program are available for download at http://k5so.com.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 31OCT2011)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect, using a small coaxial cable, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> <br /> ''Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to another Mercury board via the LVDS (low voltage differential signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> ''<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4215 2011-10-31T20:21:16Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 31OCT2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury using two Mercury boards and PowerSDR v.19.3.5.steering1 using three Mercury boards. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 10OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v3.1 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> '''Triple Mercury board setups (Windows):'''<br /> Operation using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.5.steering1 (K5SO 18SEP2011). This program is ALPHA code and is under active development and is frequently changed. The goal is to develop a beam steering program for three-antenna receiving arrays by means of appropriate phasing of the three independent, coherent, IQ data streams. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis. The firmware and the PC program are available for download at http://k5so.com.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 31OCT2011)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect, using a small coaxial cable, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> <br /> ''Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to another Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> ''<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4214 2011-10-31T20:20:49Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 31OCT2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury using two Mercury boards and PowerSDR v.19.3.5.steering1 using three Mercury boards. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 10OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v3.1 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> '''Triple Mercury board setups (Windows):'''<br /> Operation using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.5.steering1 (K5SO 18SEP2011). This program is ALPHA code and is under active development and is frequently changed. The goal is to develop a beam steering program for three-antenna receiving arrays by means of appropriate phasing of the three independent, coherent, IQ data streams. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis. The firmware and the PC program are available for download at http://k5so.com.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 31OCT2011)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect, using a small coaxial cable, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> ''Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to another Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> ''<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4213 2011-10-31T20:19:33Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 31OCT2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury using two Mercury boards and PowerSDR v.19.3.5.steering1 using three Mercury boards. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 10OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v3.1 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> '''Triple Mercury board setups (Windows):'''<br /> Operation using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.5.steering1 (K5SO 18SEP2011). This program is ALPHA code and is under active development and is frequently changed. The goal is to develop a beam steering program for three-antenna receiving arrays by means of appropriate phasing of the three independent, coherent, IQ data streams. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis. The firmware and the PC program are available for download at http://k5so.com.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 31OCT2011)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect, using a small coaxial cable, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 5) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to another Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4212 2011-10-31T20:19:03Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 31OCT2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury using two Mercury boards and PowerSDR v.19.3.5.steering1 using three Mercury boards, using a MS Windows OS. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 10OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v3.1 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> '''Triple Mercury board setups (Windows):'''<br /> Operation using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.5.steering1 (K5SO 18SEP2011). This program is ALPHA code and is under active development and is frequently changed. The goal is to develop a beam steering program for three-antenna receiving arrays by means of appropriate phasing of the three independent, coherent, IQ data streams. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis. The firmware and the PC program are available for download at http://k5so.com.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 31OCT2011)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect, using a small coaxial cable, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 5) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to another Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4211 2011-10-31T20:15:15Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 31OCT2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury using two Mercury boards and PowerSDR v.19.3.5.steering1 using three Mercury boars, using a MS Windows OS. Both are available for download from the K5SO website referenced above.<br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 10OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.8 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> '''Triple Mercury board setups (Windows):'''<br /> Operation using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.5.steering1 (K5SO 18SEP2011). This program is ALPHA code and is under active development and frequent change. The goal is to provide beam steering for three antenna arrays by appropriate phasing of the three independent, coherent, IQ data streams. Required firmware: Metis v1.6, Mercury v3.1, and Penelope v1.6; Ozy v2.1 will be loaded automatically on startup of PSDR after a fresh poer up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 31OCT2011)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect, using a small coaxial cable, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 5) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to another Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4210 2011-10-31T20:06:01Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 5OCT2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury on Windows. .<br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 10OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.8 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.8, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 31OCT2011)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board(s),<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board(s)<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on all Mercury boards<br /> <br /> 3d) connect, using a small coaxial cable, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now all Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 5) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to another Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4209 2011-10-31T20:03:48Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 5OCT2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury on Windows. .<br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 10OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.8 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.8, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 31OCT2011)<br /> <br /> Each Mercury board must have jumpers in place to specify a unique address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 3d) connect, using a small coaxial cable, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board(s), see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now both (all) Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The coaxial connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 5) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to the other Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4203 2011-10-16T15:11:00Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 5OCT2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury on Windows. .<br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 10OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.8 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.8, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> (last updated 16OCT2011)<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 3d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 5) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to the other Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4202 2011-10-16T15:09:44Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 5OCT2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury on Windows. .<br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 10OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.8 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.8, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board and a jumper in place to specify that the board is being used simultaneously with other Mercury boards. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0, <br /> <br /> 3,2 = MULTIPLE_MERC<br /> <br /> <br /> 1) All Mercury boards used in multiple-Mercury-board operations must have the MULTIPLE_MERC jumper (GPIO 3,2) in place. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 3d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 5) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to the other Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4201 2011-10-13T18:25:41Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 5OCT2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury on Windows. .<br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 10OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.8 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.8, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 4) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to the other Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4200 2011-10-05T18:54:22Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 5OCT2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury on Windows. .<br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 4OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream relative to the reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.7 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.7, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 4) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to the other Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4199 2011-10-05T18:53:49Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 5OCT2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury on Windows. .<br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 4OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and permits the user to adjust the phase and gain of the non-reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.7 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.7, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 4) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to the other Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4198 2011-10-05T18:51:42Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 5OCT2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury on Windows. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury (K5SO 4OCT2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and uses powerful phasing/gain controls to adjust relative phase and gain of the non-reference IQ data stream to achieve diversity operation and selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.7 must be used with PowerSDR v2.2.3.dual_Mercury, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.7, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 4) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to the other Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4197 2011-09-26T23:44:08Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 26SEP2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury1 on Windows. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury1 (K5SO 25SEP2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and uses a &quot;steering&quot; display to adjust relative phase and/or gain of the non-reference IQ data stream to achieve diversity operation, selective nulling, or beam-forming/directional steering. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.7 must be used with PowerSDR v2.2.3.dual_Mercury1, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.7, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 4) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to the other Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4196 2011-09-26T23:42:45Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 26SEP2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury1 on Windows. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury1 (K5SO 25SEP2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and uses a &quot;steering&quot; display to adjust relative phase and/or gain of the non-reference IQ data stream to achieve diversity operation, selective nulling, or beam-forming and directional steering. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.7 must be used with PowerSDR v2.2.3.dual_Mercury1, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.7, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 4) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to the other Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4195 2011-09-26T23:38:34Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 26SEP2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury1 on Windows. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury1 (K5SO 25SEP2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and uses a &quot;steering&quot; display to adjust relative phase and/or gain of the non-reference IQ data stream to achieve diversity operation, selective nulling, or beam steering. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.7 must be used with PowerSDR v2.2.3.dual_Mercury1, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.7, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 4) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to the other Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4194 2011-09-26T23:31:03Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> (Last updated 26SEP2011)<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury1 on Windows. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury1 (K5SO 25SEP2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and uses a &quot;steering&quot; display to adjust relative phase and/or gain of the non-reference IQ data stream to achieve diversity operation, selective nulling, or antenna beam steering. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.7 must be used with PowerSDR v2.2.3.dual_Mercury1, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.7, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 4) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to the other Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4193 2011-09-26T23:24:24Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury1 on Windows. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury1 (K5SO 25SEP2011). This program is a modification of Doug W5WC's PSDR v2.2.3 and uses a &quot;steering&quot; display to adjust relative phase and/or gain of the non-reference IQ data stream to achieve diversity operation, selective nulling, or antenna beam steering. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.7 must be used with PowerSDR v2.2.3.dual_Mercury1, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.7, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 4) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to the other Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4192 2011-09-26T23:21:26Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury1 on Windows. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury1 (K5SO 25SEP2011). This program is a modification of PSDR v2.2.3 and uses a &quot;steering&quot; display to adjust relative phase and/or gain of the non-reference IQ data stream to achieve diversity operation, selective nulling, or antenna beam steering. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.7 must be used with PowerSDR v2.2.3.dual_Mercury1, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.7, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> 4) Note: An alternative method to use a common 122.88 MHz clock is to pass the clock from one Mercury board to the other Mercury board via the LVDS (low voltage digital signals) header on the Mercury boards. Consult the Mercury schematic diagram to see how this may be done if you wish to use LVDS signals between boards instead of connecting the boards as described above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4191 2011-09-26T23:16:43Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury1 on Windows. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury1 (K5SO 25SEP2011). This program is a modification of PSDR v2.2.3 and uses a &quot;steering&quot; display to adjust relative phase and/or gain of the non-reference IQ data stream to achieve diversity operation, selective nulling, or antenna beam steering. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.7 must be used with PowerSDR v2.2.3.dual_Mercury1, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.7, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4190 2011-09-26T23:14:30Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury1 on Windows. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury1 (K5SO 25SEP2011). This program is a modification of PSDR v2.2.3 and uses a &quot;steering&quot; display to adjust relative phase and/or gain of the non-reference IQ data stream to achieve diversity operation, selective nulling, or antenna beam steering. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.7 must be used with PowerSDR v2.2.3.dual_Mercury1, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.7, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. Photos of Mercury boards addressed for logical 0 (Merc1) and logical 1 (Merc2) are shown on the K5SO download site referenced above.<br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations and disable the on-board 10 MHz and 122.88 MHz oscillators on Mercury 3. <br /> <br /> Now both (or all three, if using triple Mercury boards) Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4189 2011-09-26T23:11:49Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by PowerSDR v2.2.3.dual_Mercury1 on Windows. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v2.2.3.dual_Mercury1 (K5SO 25SEP2011). This program is a modification of PSDR v2.2.3 and uses a &quot;steering&quot; display to adjust relative phase and/or gain of the non-reference IQ data stream to achieve diversity operation, selective nulling, or antenna beam steering. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.7 must be used with PowerSDR v2.2.3.dual_Mercury1, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v6.7, Mercury v6.7, and Penelope v1.5; Ozy v6.7 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present instead of Metis.<br /> <br /> The second Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second Mercury board is simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations and disable the on-board 10 MHz and 122.88 MHz oscillators on Mercury 3. <br /> <br /> Now both (or all three, if using triple Mercury boards) Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4180 2011-08-21T15:11:10Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.5.diversity20, and PowerSDR v1.19.3.5.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.5.diversity20 (K5SO 17AUG2011). This program is a modification of PSDR v1.19.3.5 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation or selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.5.diversity20, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.4, Mercury v6.4 or v6.6, Penelope v1.4, Ozy v6.6 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present.<br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.5.directional1 (K5SO 18AUG2011). This program is also a modification of PSDR v1.19.3.5. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.5.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.4, Mercury v6.6, Penelope v1.4, Ozy v6.6 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and W5WC's PowerSDR v1.19.3.5 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.4 (if Metis is used) and Penelope v1.4 (if Penelope is used) must be used with multiple Mercury boards. <br /> <br /> The second and third Mercury boards can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations and disable the on-board 10 MHz and 122.88 MHz oscillators on Mercury 3. <br /> <br /> Now both (or all three, if using triple Mercury boards) Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4179 2011-08-21T15:09:13Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.5.diversity20, and PowerSDR v1.19.3.5.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.5.diversity20 (K5SO 17AUG2011). This program is a modification of PSDR v1.19.3.5 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation or selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.5.diversity20, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.4, Mercury v6.4 or v6.6, Penelope v1.4, Ozy v6.6 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present.<br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.5.directional1 (K5SO 18AUG2011). This program is also a modification of PSDR v1.19.3.5. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.5.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.4, Mercury v6.6, Penelope v1.4, Ozy v6.6 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy or Magister is present.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and W5WC's PowerSDR v1.19.3.4 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.4 (if Metis is used) and Penelope v1.4 (if Penelope is used) must be used with multiple Mercury boards. <br /> <br /> The second and third Mercury boards can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations and disable the on-board 10 MHz and 122.88 MHz oscillators on Mercury 3. <br /> <br /> Now both (or all three, if using triple Mercury boards) Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4178 2011-08-21T14:17:34Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.5.diversity20, and PowerSDR v1.19.3.5.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.5.diversity20 (K5SO 17AUG2011). This program is a modification of PSDR v1.19.3.5 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation or selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.5.diversity20, the firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.4, Mercury v6.4 or v6.6, Penelope v1.4, Ozy v6.6 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy is present.<br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.5.directional1 (K5SO 18AUG2011). This program is also a modification of PSDR v1.19.3.5. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.5.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com. Required firmware: Metis v1.4, Mercury v6.6, Penelope v1.4, Ozy v6.6 will be loaded automatically on startup of PSDR after a fresh power up of Atlas, if Ozy is present.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and W5WC's PowerSDR v1.19.3.4 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.4 (if Metis is used) and Penelope v1.4 (if Penelope is used) must be used with multiple Mercury boards. <br /> <br /> The second and third Mercury boards can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations and disable the on-board 10 MHz and 122.88 MHz oscillators on Mercury 3. <br /> <br /> Now both (or all three, if using triple Mercury boards) Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4177 2011-08-21T14:06:23Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.4.diversity20, and PowerSDR v1.19.3.5.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.5.diversity20 (K5SO 17AUG2011). This program is a modification of PSDR v1.19.3.5 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation or selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.5.diversity20, the firmware and PC program are available for download at http://k5so.com. <br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.5.directional1 (K5SO 18AUG2011). This program is also a modification of PSDR v1.19.3.5. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.5.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and W5WC's PowerSDR v1.19.3.4 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.4 (if Metis is used) and Penelope v1.4 (if Penelope is used) must be used with multiple Mercury boards. <br /> <br /> The second and third Mercury boards can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations and disable the on-board 10 MHz and 122.88 MHz oscillators on Mercury 3. <br /> <br /> Now both (or all three, if using triple Mercury boards) Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4176 2011-08-11T13:35:10Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.4.diversity20, and PowerSDR v1.19.3.4.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.diversity20 (K5SO 10AUG2011). This program is a modification of PSDR v1.19.3.4 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation or selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.4.diversity20, the firmware and PC program are available for download at http://k5so.com. <br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.directional1 (K5SO 10AUG2011). This program is also a modification of PSDR v1.19.3.4. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.4.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and W5WC's PowerSDR v1.19.3.4 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.3 may be used with multiple Mercury boards. <br /> <br /> The second and third Mercury boards can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations and disable the on-board 10 MHz and 122.88 MHz oscillators on Mercury 3. <br /> <br /> Now both (or all three, if using triple Mercury boards) Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4169 2011-07-29T03:01:51Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.4.diversity20, and PowerSDR v1.19.3.4.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.diversity20 (K5SO 28JUL2011). This program is a modification of PSDR v1.19.3.4 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation or selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.4.diversity20, the firmware and PC program are available for download at http://k5so.com. <br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.directional1 (K5SO 28JUL2011). This program is also a modification of PSDR v1.19.3.4. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.4.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and W5WC's PowerSDR v1.19.3.4 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.3 may be used with multiple Mercury boards. <br /> <br /> The second and third Mercury boards can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations and disable the on-board 10 MHz and 122.88 MHz oscillators on Mercury 3. <br /> <br /> Now both (or all three, if using triple Mercury boards) Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4168 2011-07-29T02:28:06Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.4.diversity20, and PowerSDR v1.19.3.4.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.diversity20 (K5SO 28JUL2011). This program is a modification of PSDR v1.19.3.4 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation or selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.4.diversity20, the firmware and PC program are available for download at http://k5so.com. <br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.directional1 (K5SO 20JUN2011). This program is also a modification of PSDR v1.19.3.4. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.4.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and W5WC's PowerSDR v1.19.3.4 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.3 may be used with multiple Mercury boards. <br /> <br /> The second and third Mercury boards can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations and disable the on-board 10 MHz and 122.88 MHz oscillators on Mercury 3. <br /> <br /> Now both (or all three, if using triple Mercury boards) Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4164 2011-07-08T16:59:30Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.4.diversity20, and PowerSDR v1.19.3.4.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.diversity20 (K5SO 12MAY2011). This program is a modification of PSDR v1.19.3.4 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation or selective nulling. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.4.diversity20, the firmware and PC program are available for download at http://k5so.com. <br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.directional1 (K5SO 20JUN2011). This program is also a modification of PSDR v1.19.3.4. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.4.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and W5WC's PowerSDR v1.19.3.4 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.3 may be used with multiple Mercury boards. <br /> <br /> The second and third Mercury boards can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations and disable the on-board 10 MHz and 122.88 MHz oscillators on Mercury 3. <br /> <br /> Now both (or all three, if using triple Mercury boards) Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4139 2011-06-25T18:15:37Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.4.diversity20, and PowerSDR v1.19.3.4.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.diversity20 (K5SO 12MAY2011). This program is a modification of PSDR v1.19.3.4 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.4.diversity20, the firmware and PC program are available for download at http://k5so.com. <br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.directional1 (K5SO 20JUN2011). This program is also a modification of PSDR v1.19.3.4. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.4.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and W5WC's PowerSDR v1.19.3.4 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.3 may be used with multiple Mercury boards. <br /> <br /> The second and third Mercury boards can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single-Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations and disable the on-board 10 MHz and 122.88 MHz oscillators on Mercury 3. <br /> <br /> Now both (or all three, if using triple Mercury boards) Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4138 2011-06-25T18:15:04Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.4.diversity20, and PowerSDR v1.19.3.4.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.diversity20 (K5SO 12MAY2011). This program is a modification of PSDR v1.19.3.4 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.4.diversity20, the firmware and PC program are available for download at http://k5so.com. <br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.directional1 (K5SO 20JUN2011). This program is also a modification of PSDR v1.19.3.4. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.4.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and W5WC's PowerSDR v1.19.3.4 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.3 may be used with multiple Mercury boards. <br /> <br /> The second and third Mercury boards can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations and disable the on-board 10 MHz and 122.88 MHz oscillators on Mercury 3. <br /> <br /> Now both (or all three, if using triple Mercury boards) Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4137 2011-06-25T18:13:48Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.4.diversity20, and PowerSDR v1.19.3.4.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.diversity20 (K5SO 12MAY2011). This program is a modification of PSDR v1.19.3.4 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.4.diversity20, the firmware and PC program are available for download at http://k5so.com. <br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.directional1 (K5SO 20JUN2011). This program is also a modification of PSDR v1.19.3.4. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.4.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and W5WC's PowerSDR v1.19.3.4 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.3 may be used with multiple Mercury boards. <br /> <br /> The second and third Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations and disable the on-board 10 MHz and 122.88 MHz oscillators on Mercury 3. <br /> <br /> Now both (or all three, if using triple Mercury boards) Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4136 2011-06-25T18:12:01Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.4.diversity20, and PowerSDR v1.19.3.4.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.diversity20 (K5SO 12MAY2011). This program is a modification of PSDR v1.19.3.4 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.4.diversity20, the firmware and PC program are available for download at http://k5so.com. <br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.directional1 (K5SO 20JUN2011). This program is also a modification of PSDR v1.19.3.4. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.4.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and W5WC's PowerSDR v1.19.3.4 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.3 may be used with multiple Mercury boards. <br /> <br /> The second and third Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the two Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4135 2011-06-25T18:11:37Z

<p>K5SO: /* Required Hardware Configurations To Use Multiple Mercury Boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.4.diversity20, and PowerSDR v1.19.3.4.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.diversity20 (K5SO 12MAY2011). This program is a modification of PSDR v1.19.3.4 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.4.diversity20, the firmware and PC program are available for download at http://k5so.com. <br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.directional1 (K5SO 20JUN2011). This program is also a modification of PSDR v1.19.3.4. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.4.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and W5WC's PowerSDR v1.19.3.4 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.3 may be used with multiple Mercury boards. <br /> <br /> The second and third Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> <br /> 1) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> <br /> 2) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 2a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 2b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 2c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 2d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 2e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source. For three Mercury board operations, parallel the 122.88 MHz clock signal from Mercury 2 to Mercury 3 using a twisted wire pair as was done from Mercury 1 to Mercury 2 for dual Mercury operations. <br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the two Mercury boards.<br /> <br /> 3) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4134 2011-06-25T18:05:04Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.4.diversity20, and PowerSDR v1.19.3.4.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.diversity20 (K5SO 12MAY2011). This program is a modification of PSDR v1.19.3.4 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.4.diversity20, the firmware and PC program are available for download at http://k5so.com. <br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.directional1 (K5SO 20JUN2011). This program is also a modification of PSDR v1.19.3.4. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.4.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and W5WC's PowerSDR v1.19.3.4 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.3 may be used with multiple Mercury boards. <br /> <br /> The second and third Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> 3,2 = Channels_8_1 bit<br /> <br /> 1) When using multiple Mercury boards ALL of the Mercury boards must have GPIO pins 3,2 jumpered. This jumper specifies that the data from the board will be sent to a single, board-specific Atlas bus line that is associated with the address indicated on GPIO pins 9-8, 7-6, and 5-4; as opposed to sending its data to Ozy over eight Atlas bus lines as is the case when there is no jumper across GPIO pins 3-2. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 3d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source.<br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the two Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO http://openhpsdr.org/wiki/index.php?title=Multi-Receiver&diff=4133 2011-06-25T18:01:34Z

<p>K5SO: /* Multiple Mercury boards */</p> <hr /> <div>[[Image:dualmercury.jpg|thumb|400px|Example of the connection points on the mercury board (Click for a larger image)]]<br /> The openHPSDR receiver can be run in several configurations. Stand-alone, multiple receivers on a single [[MERCURY]] (one common antenna), and two or more [[MERCURY]] boards plugged into a single [[ATLAS]] (this allows two or more antennas). Each of these configurations require different hardware and software support but all have been successfully accomplished using [[MERCURY]] boards.<br /> <br /> ==Stand-Alone==<br /> <br /> The options is supported by all software and all versions of the verilog code.<br /> <br /> Current verilog code is Mercury 2.9 and Ozy 1.7<br /> <br /> ==Multiple Receivers on a single Mercury==<br /> <br /> This options is supported by [[KISS Konsole]] on Windows and [[ghpsdr3]] on Linux and (Windows under development).<br /> <br /> This option is only supported by the Ozy 1.8 and Mercury 3.0 verilog code.<br /> <br /> ==Multiple Mercury boards==<br /> <br /> This option is supported by KISS Konsole versions &gt;1.0.6, PowerSDR v1.19.3.4.diversity20, and PowerSDR v1.19.3.4.directional1 on Windows and [[ghpsdr3]] on Linux. <br /> <br /> '''Dual Mercury board setups (Windows):''' <br /> Diversity operation using two coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.diversity20 (K5SO 12MAY2011). This program is a modification of PSDR v1.19.3.4 and uses a radar-screen type display to adjust relative gain/phase of the non-reference IQ data stream to achieve diversity operation. Polarization diversity or spatial diversity are possible, depending upon what inputs are provided to the two Mercury boards. Mercury firmware v6.4 or v6.6 should be used with PowerSDR v1.19.3.4.diversity20, the firmware and PC program are available for download at http://k5so.com. <br /> <br /> '''Triple Mercury board setups (Windows):''' <br /> Directional steering and selective nulling using three coherent Mercury receivers is implemented in PowerSDR v1.19.3.4.directional1 (K5SO 20JUN2011). This program is also a modification of PSDR v1.19.3.4. The program provides a large user display interface that allows the user to select the receive direction and independent phase/gain control of the two non-reference Mercury boards. Mercury firmware v6.6 should be used with PowerSDR v1.19.3.4.directional1. Using triple coherent Mercury receivers provides up to 4.8 dB of signal gain relative to a single Mercury board receiver and with careful phase adjustments can provide up to 70 dB of null on selected signals, depending on band conditions. The firmware and PC program are available for download at http://k5so.com.<br /> <br /> Mercury v6.4 and Mercury v6.6 firmware are compatible with the current versions of Bill KD5TFD's PowerSDR v1.10.4, KISS Konsole, and PowerSDR v1.19.3.4 therefore it is not necessary to change the FPGA firmware in the Mercury boards when switching among those programs. Power cycling the HPSDR board set (or alternatively, re-running initozy11.bat without power cycling) is all that is necessary to be able to switch between the programs in order to automatically load the proper Ozy/Magister FPGA code. Metis v1.3 may be used with multiple Mercury boards. <br /> <br /> The second and third Mercury board can remain on the Atlas bus while running the other programs with no ill effects, the second and third Mercury boards are simply ignored by single Mercury programs.<br /> <br /> ==Required Hardware Configurations To Use Multiple Mercury Boards==<br /> <br /> Each Mercury board must have jumpers in place to specify an address for the board. Each board will have a different jumper-selected address. The address is specified by placing jumpers on J5 (GPIO pins) on the Mercury board. Looking at the Mercury board with the Atlas bus connector down, the GPIO pins on J5 are arranged such that the lowest pair of pins (closest to F1) are GPIO pins 1,0. Without a jumper, the logic value for the GPIO pin pair is &quot;0&quot;, with a jumper across the pins the logic value is &quot;1&quot;. The Mercury board address is specified as a 3-bit address according to the jumpers placed on J5. The GPIO pins on J5 are assigned as follows: <br /> <br /> GPIO pairs:<br /> <br /> 9,8 = Mercury ID bit 2,<br /> <br /> 7,6 = Mercury ID bit 1,<br /> <br /> 5,4 = Mercury ID bit 0,<br /> <br /> 3,2 = Channels_8_1 bit<br /> <br /> 1) When using multiple Mercury boards ALL of the Mercury boards must have GPIO pins 3,2 jumpered. This jumper specifies that the data from the board will be sent to a single, board-specific Atlas bus line that is associated with the address indicated on GPIO pins 9-8, 7-6, and 5-4; as opposed to sending its data to Ozy over eight Atlas bus lines as is the case when there is no jumper across GPIO pins 3-2. <br /> <br /> 2) The address of the first Mercury board should be &quot;000&quot;, selected by having no jumpers on GPIO pins 9-8, 7-6, or 5-4. The address of the second Mercury board should be &quot;001&quot;, selected by having a jumper on GPIO pins 5-4; and so on for any additional Mercury boards present. <br /> <br /> Therefore, for dual Mercury boards, the 3,2 GPIO jumper pair should be on both Mercury cards, the first Mercury board is set for Merc_ID = 000 (no jumpers on pins 9-8, 7-6, or 5-4) and the 2nd Mercury card is set for Merc_ID = 001 (a jumper across the 5,4 pair).<br /> <br /> <br /> 3) Configuring the 122.88MHz clocks on the Mercury boards: <br /> <br /> 3a) place a jumper on the CLKSEL &quot;I&quot; pins (lower two pins of the three CLKSEL pins) on one of the Mercury boards (this will be the &quot;master&quot; Mercury board), no such jumper is placed on the equivalent pins of the slave Mercury board,<br /> <br /> 3b) place a jumper on JP9 (enabling the 122.88MHz oscillator) on the master Mercury board but not on the (other) &quot;slave&quot; Mercury board<br /> <br /> 3c) place a jumper from the Atlas C16 pin to J8 (Aux Clk input) pin nearest the FPGA on both Mercury boards<br /> <br /> 3d) connect, with a twisted wire pair, pin 2 of JP1 (CLK SELECT) and a ground connection of the master Mercury board to pin 2 of JP1 (CLK SELECT) and a ground connection of the slave Mercury board, see photos at http://www.k5so.com/Clock%20connections.html.<br /> <br /> 3e) in PowerSDR, select Setup&gt;Excalibur for the 10 MHz clock source and Mercury as the 122.88 MHz clock source.<br /> <br /> Now both Mercury boards will be operating from the single 122.88 MHz oscillator on the master Mercury board. The twisted-wire connection between the Mercury boards is required to achieve long-term coherent operation of the two Mercury boards.<br /> <br /> 4) 10 MHz clock on Mercury: The 10MHz clock for the Mercury boards should be taken from Excalibur (or whatever external 10MHz source you use) via the Atlas C16 pin, with Mercury jumpered as noted in 3d above.<br /> <br /> ==See also==<br /> * [[Multiple independent receivers - how to set up on Windows]] - not the same as above, but related.<br /> <br /> [[Category:Hardware]]</div>

K5SO