| 11 | | }}} |
| | 11 | }}} |
| | 12 | |
| | 13 | 4. Q: How can I save my image? We are having problem saving our image, can you please advise? [[BR]] |
| | 14 | A: You have to use Fully Qualified Domain Name (FQDN) of the node as an argument i.e. if you have a reservation for DCGNUR14 and want to save image from node3-13 you have to issue a command: |
| | 15 | {{{ |
| | 16 | omf save -n node3-13.grid.orbit-lab.org |
| | 17 | }}} |
| | 18 | NOTE: All nodes used in DARPA SPectrum Challenge are part of '''grid.orbit-lab.org''' domain. |
| | 19 | |
| | 20 | 5. Q: '''Given that they don't have USRP hardware, what is the purpose of zDCXX domains?''' [[BR]] |
| | 21 | A: The zDCXX domains are general purpose only, and can't be used for USRP testing. However, they might be useful for other functions, such as working with images, debugging, working with omf (useful tool to get familiar with), etc. |
| | 22 | 1. Q: '''Are we set up for full-duplex communication, i.e., can we have a return path for ACKs, etc.?''' [[BR]] |
| | 23 | A: The final evaluation for Hurdle 3 will be done on a pair of nodes with the SBX front-end. Bi-directional communications is allowed as long as it is done within the 2.5 MHz channel. Teams are advised to be aware of their schedule assignment during the development period since some USRPs have the XCVR front-end. Teams are advised to fully understand the limitations of the SBX front-end when trying to implement sophisticated protocols, as well as the limitations that might be faced when developing on the XCVR for eventual testing with the SBX. |
| | 24 | 1. Q: '''Is there some recommended image to use which combines in some way ath5k or ath9k devices and gnuradio? Can we use exisitng WiFI radios for feedback channel?''' [[BR]] |
| | 25 | A: Teams are not allowed to use communication interfaces other than USRP (whether wired or wireless). In other words, you can't use WiFi/Bluetooth/ZigBee/Ethernet devices to talk between the two nodes. |
| | 26 | 1. Q: '''Why are we getting repeated connection timeouts when running benchmark_tx2.py?''' [[BR]] |
| | 27 | A: There is a hard limit on number of sessions that the packet source can handle at a time, and when you witness connection timeouts this is due to too many teams making simultaneous requests to the packet source. |
| | 28 | 1. Q: '''Are there any requirements to maintain any of the existing structure of the tx/rx modules, as long as the rx timeout and packet server source/sinks remain unchanged?''' [[BR]] |
| | 29 | A: The requirements are that you must retain the packet structure reading from the packet source, and the packet structure going into the packet sink. Failure to do this will mean that you will not pass the checking mechanism. You must also keep the same “center frequency” argument structure on the command-line of your program since we will use this to launch your code for evaluation (and keep corresponding logging functions). Generally, you may do whatever else you wish with the radio (without touching the FPGA or stepping outside of the 2.5MHz baseband - we will check to make certain you stay in the band). Please note that your radio module must automatically set many of its own parameters (such as gain) since the evaluators will not try to optimize parameter selection for teams. |
| | 30 | 1. Q: '''For Hurdle 3, timing and evaluation are handled by the server. Should the TX/RX modules continuously until the 10 minute RX timeout is reached?''' [[BR]] |
| | 31 | A: Yes, you should continuously transmit packets until the timeout. We will evaluate on a 5 minute chunk of time during your run. A performance monitoring server will be running during the Qualification Period and will send you an email with number of packets that were successfully received in the 5minute period. |
| | 32 | |
| | 33 | |
