Hi,
I tried to work a bit around the problem.
I created a udev rule in order to have the telosB (IPBaseStation) always
connected to the same /dev/
ATTRS{product}=="Crossbow Telos Rev.B", ATTRS{serial}=="XBT*****",
SYMLINK+="BaseStation"
Unfortunately this doesn't solve the problem. When the telosb reconnects to the
USB the tun0 interface stays up but it doesn't receive packets anymore
Do you you know why?
thanks
Davide
On 7 Jul 2011, at 18:54, Michael Schippling wrote:
> Are you sure that the device didn't actually disconnect?
> Maybe the cable got wiggled, power blipped, or something?
>
> I can't think of an easy way to debug this since it could
> be anything from a bad cable to buggy software. Probably the
> only workaround is to have the USB client attempt to reconnect
> whenever it dies.
>
> MS
>
> [email protected] wrote:
>> Hi,
>>
>> I'm facing a very nasty problem with the USB using Blip and telosb.
>> I've a small testbed set up where few telosb report data to a telosb
>> IPBaseStation connected by USB to a laptop running Ubuntu 10.
>>
>> The ip-driver is running and the tun0 interface works perfectly until, for
>> some reason, the USB disconnects!!!
>>
>> Happened many times already and always after a random period of time (few
>> hours or few days).
>>
>> Has anybody of you had the same problem?
>>
>> Please, have a look to my dmesg:
>>
>> [ 62.583495] device tun0 entered promiscuous mode
>> [181469.402683] hub 1-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
>> [181469.403667] usb 1-1: USB disconnect, address 2
>> [181469.406021] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now
>> disconnected from ttyUSB0
>> [181469.406654] ftdi_sio 1-1:1.0: device disconnected
>> [181469.627963] usb 1-1: new full speed USB device using ohci_hcd and
>> address 3
>> [181469.777676] usb 1-1: configuration #1 chosen from 1 choice
>> [181469.783296] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
>> [181469.784171] usb 1-1: Detected FT232BM
>> [181469.785634] usb 1-1: FTDI USB Serial Device converter now attached to
>> ttyUSB1
>>
>>
>> As you can see the USB went off after more than 2 days of activity!
>> I suspect it's related to the USB hardware rather than applications but, so
>> far, it happens to me only using telosb.
>>
>> I google it a bit but I have not found solution yet
>>
>> Any comment is more than welcome
>>
>>
>> Many thanks
>>
>>
>> Davide
>> _______________________________________________
>> Tinyos-help mailing list
>> [email protected]
>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> _______________________________________________
> Tinyos-help mailing list
> [email protected]
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
