I recently moved to working with an X310, after previously working with an N210. When working with the N210 I was able to run my code which scans multiple frequencies, and only use 5000 msec as my dwell time on each frequency. With the N210, 5000 msec was enough time to task the N210 and collect my data at the frequency to which I tuned. To do this at each frequency changed I stopped the service, then restarted the service sending the commands to the N210 at each new frequency.
With the X310 I am finding much difficulty in scanning from frequency to frequency while keeping the same dwell time. I am sending the exact same commands to set up the X310 as I was with the N210. Are there additional commands that the X310 needs? Is there extra latency I don’t know about? Has the command structure change from the N210 to the x310? Any help on this would be GREATLY appreciated. Thank you Mark
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
