Api-Mote Detection Support

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Connecting an api-mote base
2. Best reproduced with a TelosB/Tmote also connected
3. Run 'sudo zbid'

What is the expected output? What do you see instead?
$ lsusb
...
Bus 005 Device 020: ID 0403:6001 Future Technology Devices International, Ltd 
FT232 USB-Serial (UART) IC
Bus 005 Device 025: ID 0403:6015 Future Technology Devices International, Ltd 
Bus 006 Device 002: ID 03eb:210a Atmel Corp. 

Sometimes it works correctly:
$ sudo zbid
Dev Product String  Serial Number
006:002 KILLERB001  A60400A01C25
/dev/ttyUSB1    GoodFET Api-Mote    
/dev/ttyUSB0    GoodFET TelosB/Tmote    
Found 3 devices.

However, the issue is that about 50% of the time, we don't get apimote 
detection:
$ sudo zbid
Dev Product String  Serial Number
006:002 KILLERB001  A60400A01C25
/dev/ttyUSB0    GoodFET TelosB/Tmote    
Found 2 devices.

Original issue reported on code.google.com by rmspe...@gmail.com on 2 Aug 2012 at 2:46

[GoogleCodeExporter]

Also will show up when relying on device detection in a tool...

Ex it fails here:
$ sudo zbdump -i /dev/ttyUSB1 -f 11 -w /tmp/test.pcap
Traceback (most recent call last):
  File "/usr/local/bin/zbdump", line 91, in <module>
    kb = KillerBee(device=arg_devstring)
  File "/usr/local/lib/python2.7/dist-packages/killerbee/__init__.py", line 116, in __init__
    raise KBInterfaceError("KillerBee doesn't know how to interact with serial device at '%s'." % self.dev)
killerbee.kbutils.KBInterfaceError: KillerBee doesn't know how to interact with 
serial device at '/dev/ttyUSB1'.

But other times, like here, it works.
$ sudo zbdump -i /dev/ttyUSB1 -f 11 -w /tmp/test.pcap
zbdump: listening on '/dev/ttyUSB1', link-type DLT_IEEE802_15_4, capture size 
127 bytes
^C2 packets captured

Original comment by rmspe...@gmail.com on 2 Aug 2012 at 3:29

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

To get around the issue, usually a physical disconnect and reconnect of the 
device is required. When running zbstumbler the first time, the application 
functions and terminates as expected. However, upon running the application for 
the second time, interaction with the device fails. This leads me to believe 
that perhaps we are not terminating the serial connection gracefully when 
exiting the application after the first run.

rmelgares@gares-air ~ $sudo zbstumbler -s 2 -c 18
zbstumbler: Transmitting and receiving on interface 
'/dev/tty.usbserial-M4AEIAHH'
^C
1 packets transmitted, 0 responses.

rmelgares@gares-air ~ $sudo zbstumbler -s 2 -c 18
Traceback (most recent call last):
  File "/sw/bin/zbstumbler", line 154, in <module>
    kb = KillerBee(device=arg_devstring)
  File "/sw/lib/python2.7/site-packages/killerbee/__init__.py", line 116, in __init__
    raise KBInterfaceError("KillerBee doesn't know how to interact with serial device at '%s'." % self.dev)
killerbee.kbutils.KBInterfaceError: KillerBee doesn't know how to interact with 
serial device at '/dev/tty.usbserial-M4AEIAHH'.

Original comment by melgares on 2 Aug 2012 at 4:55

[GoogleCodeExporter]

I'm having the same issue on ubuntu 13.10 saucy, kernel 3.9

lsubs shows it but zbid doesn't find it.
and not 50% of times, but 100%!
I must say I'm on virtualbox, anyway I don't think this is a problem with usb 
proxy
Never had this problem on ubuntu 12.10.

Will try 13.04 now.

Original comment by costamag...@gmail.com on 7 May 2013 at 2:46

[GoogleCodeExporter]

The problem for me is only when I use virtualbox.
So something related to usb proxy?

Original comment by costamag...@gmail.com on 9 May 2013 at 7:22

[GoogleCodeExporter]

Likely is the USB proxy timing or something in this case if limited to VBox. Do 
other emulation platforms do any better?

Original comment by rmspe...@gmail.com on 9 May 2013 at 11:55