5 | | |
6 | | ORBIT has 2 [http://nutaq.com/en/products/zeptosdr ZeptoSDR]. They are attached to a Gen4 Node as the host machine via gigabit ethernet. |
7 | | |
8 | | The ZeptoSDR has a Zedboard FPGA, and Nutaq's RADIO420X board. It is tunable from 300MHz to 3.8GHz, with bandwidth between 1.5 and 28 MHz. |
| 6 | ORBIT has 2 [http://nutaq.com/en/products/zeptosdr ZeptoSDR]. |
| 7 | * They are attached to a Gen4 Node as the host machine via gigabit ethernet. |
| 8 | * In addition, they are powered by the host nodes, for remote on/off capability. |
| 9 | * The ZeptoSDR has a Zedboard FPGA, and Nutaq's RADIO420X board. |
| 10 | * It is tunable from 300MHz to 3.8GHz, with bandwidth between 1.5 and 28 MHz. |
14 | | ORBIT has 2 [http://nutaq.com/en/products/picosdr PicoSDR2x2-E]. Each has a Perseus 601x FPGA, a Radio420M FMC stack, and a SAMC-514 embedded CPU, with an Intel Core i7 CPU running at 2.1 GHz. |
15 | | |
16 | | They are integrated with the orbit experiment control infrastructure, with the lead unit installed as node 12-1 in the Grid. A Raspberry Pi is running the CMC management service, and using telnet to control the PicoSDR's backplane. |
| 16 | ORBIT has 2 [http://nutaq.com/en/products/picosdr PicoSDR2x2-E]. |
| 17 | * Each is an independent ORBIT node, due to its embedded SAMC-514 computer, with an Intel Core i7 CPU running at 2.1 GHz. |
| 18 | * Each has a Perseus 601x FPGA, and a Radio420M FMC stack. |
| 19 | * They are integrated with the orbit experiment control infrastructure, as nodes 12-1 and 20-1. A Raspberry Pi is running the CMC management service, using telnet to control the PicoSDR's backplane. |