NorwegianWould
Joined: 07 Jan 2006
Posts: 23
|
 Posted: Sat Jan 21, 2006 2:51 am Post subject: USB datalogger problems |
 |
|
Hi,
Has anyone seen this with their setup? I have the USB datalogger, and about once a day or so it disconnects for no apparent reason and then reconnects. I do not believe that this is a wview problem, but I was hoping someone in this community might be able to shed some light on it.
When the disconnect-reconnect happens, the datalogger comes back as /dev/ttyUSB1. This causes several things to happen; wview loses contact (I told it to use USB0), wview gets very upset by this and fills up syslog with:
| Code: |
Jan 20 16:46:54 localhost wviewd[3538]: <3900647674> : wakeupConsole: Write ERROR!
Jan 20 16:46:56 localhost wviewd[3538]: <3900650176> : wakeupConsole: Write ERROR!
Jan 20 16:46:58 localhost wviewd[3538]: <3900652691> : wakeupConsole: Write ERROR!
Jan 20 16:47:01 localhost wviewd[3538]: <3900655193> : wakeupConsole: Write ERROR!
Jan 20 16:47:03 localhost wviewd[3538]: <3900657717> : wakeupConsole: Write ERROR!
Jan 20 16:47:06 localhost wviewd[3538]: <3900660229> : wakeupConsole: Write ERROR!
Jan 20 16:47:06 localhost wviewd[3538]: <3900660229> : wviewd:vproErrorState: received stimulus 5
Jan 20 16:47:06 localhost last message repeated 8 times
|
The vproErrorState message then continues ad-infinitum, many times per second and usually my root partition is full before I realise. Killing wview is also hard. I have to use kill -9, and then remove the ipcs by hand. (The vproErrorState message could be less aggressive and exit after, say, 10 times, if this is possible in a future version Mark?)
I am using ubuntu linux kernel 2.6.12-10-386
Looking at Davis' web site, it looks like this is a problem others have experienced, but no one knows how to solve it. I contacted Davis and got some help, but still no solution. I am trying now with an external powered hub to see if that helps.
Any comments or experiences anyone?
Jeremy |
|
chrisale
Joined: 09 Nov 2005
Posts: 187
|
| Posted: Sat Jan 21, 2006 9:48 am Post subject: |
|
|
my biggest problems with the USB data logger have been USB extension-related... though I've never had the problem of the USB device coming back on a different tty.... to me, that would seem like an OS or kernel related problem with how it loads/unloads drivers.
My data logger was losing its' connection every couple days... but since I took out the extension and am just using the USB cable supplied by Davis, it has worked flawlessly
*knocks on wood* |
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
