-T A:1 or -T B:1 tuple out of range?

We’re getting tuple out of range when specifying port 1 on either side
for an LFTX board. Specifying -T A:0 or -T B:0 on does seem to work on
several of the transmitter apps we’ve tried.

[[email protected] ~]# usrp_siggen.py -T A:0 -f 5M -i 128 --sine -a 16000 -g 0
Using TX d’board A: LF Tx
[[email protected] ~]# usrp_siggen.py -T A:1 -f 5M -i 128 --sine -a 16000 -g 0
Traceback (most recent call last):
File “/usr/local/bin/usrp_siggen.py”, line 184, in ?
main ()
File “/usr/local/bin/usrp_siggen.py”, line 164, in main
tb.subdev = usrp.selected_subdev(tb.u, options.tx_subdev_spec)
File “/usr/local/lib64/python2.4/site-packages/gnuradio/usrp.py”, line
393, in selected_subdev
return weakref.proxy(u.db[side][subdev])
IndexError: tuple index out of range
[[email protected] ~]#

[[email protected] ~]# usrp_siggen.py -T B:0 -f 5M -i 128 --sine -a 16000 -g 0
Using TX d’board B: Basic Tx
[[email protected] ~]# usrp_siggen.py -T B:1 -f 5M -i 128 --sine -a 16000 -g 0
Traceback (most recent call last):
File “/usr/local/bin/usrp_siggen.py”, line 184, in ?
main ()
File “/usr/local/bin/usrp_siggen.py”, line 164, in main
tb.subdev = usrp.selected_subdev(tb.u, options.tx_subdev_spec)
File “/usr/local/lib64/python2.4/site-packages/gnuradio/usrp.py”, line
393, in selected_subdev
return weakref.proxy(u.db[side][subdev])
IndexError: tuple index out of range

Receiver seems happy to take :1

[[email protected] ~]# usrp_rx_cfile.py -R A:0 -d 8 -f 5M -g 0 out.dat
Using RX d’board A: LF Rx
USB sample rate 8M
[[email protected] ~]# usrp_rx_cfile.py -R A:1 -d 8 -f 5M -g 0 out.dat
Using RX d’board A: LF Rx
USB sample rate 8M

Have I missed another post about new syntax? This is latest SVN as of a
couple days ago.
Please let me know if I’m doing something else silly…

On Fri, Aug 29, 2008 at 06:15:24PM -0500, Brett L. Trotter wrote:

We’re getting tuple out of range when specifying port 1 on either side for
an LFTX board. Specifying -T A:0 or -T B:0 on does seem to work on several
of the transmitter apps we’ve tried.

Lots of code assumes that the two DACs are always being used in
quadrature, thus there is no -T A:0 or -T A:1, just -T A.

If you’re willing to do a substantial amount of work, it’s possible to
use the two DACs for a given daughterboard separately. The first
place to start would be to read and understand all the fine points in
the AD9862 data sheet that have to do with the transmit path. Once
you understand the underlying h/w you’d be prepared to evaluate the
required software modifications.

Eric

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs