tuple index out of range

What steps will reproduce the problem?
1. wrote the firmware to RZUSBSTICK
2. tried to execute zbstumbler but I get "tuple index out of range" error

What is the expected output? What do you see instead?

Listing the available devices with zbid works just fine - 
Dev Product String  Serial Number
002:007 KILLERB001  0004251CA000

When I execute zbstumbler I get this - 

zbstumbler: Transmitting and receiving on interface '002:007'
ERROR: Failed to set channel to 11
tuple index out of range

When I try a different channel I get this - 

zbstumbler: Transmitting and receiving on interface '002:007'
Traceback (most recent call last):
  File "/usr/local/bin/zbstumbler", line 163, in <module>
    kb.set_channel(channel)
  File "/usr/lib/python2.6/dist-packages/killerbee/__init__.py", line 345, in set_channel
    self._set_mode(RZ_CMD_MODE_AC)
  File "/usr/lib/python2.6/dist-packages/killerbee/__init__.py", line 261, in _set_mode
    self.__usb_write(RZ_USB_COMMAND_EP, [RZ_CMD_SET_MODE, RZ_CMD_MODE_AC])
  File "/usr/lib/python2.6/dist-packages/killerbee/__init__.py", line 219, in __usb_write
    response = self.handle.bulkRead(RZ_USB_RESPONSE_EP, 1)[0]
IndexError: tuple index out of range

What version of the product are you using? On what operating system?

I am using the firmware provided in the tar file

Please provide any additional information below.

A similar requested was posted in December but I did not see a resolution. As I 
mentioned I installed the new killberbee firmware from the tar file on a 
RZUSBSTICK and when I run zbstumbler I get the error"tuple index out of range". 

I am working under backtrack 5.0. Also, like Nick, I am curious to know if the 
LED is suppose to be blue or amber/yellow? I've written the firmware to 4 
sticks and none of them light up the blue led. According to the ATMEL docs 
amber/yellow indicates buffer overflow in either the zigbee coordinator more or 
Aircapture mode. 

Also, is stick suppose to show up as an available network device for use with 
wireshark? If so, its not showing up as such. It does show up as usb0 if I 
write the 6lowpan firmware to it though; so I know the stick is working and the 
header is soldered on correctly.
Original issue reported on code.google.com by komp...@gmail.com on 16 Mar 2012 at 10:01
Merged into: #8
monk-dot / killerbee

tuple index out of range #11
