|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
|
|
Fedora Core 9 - DS9490R problemHello,
I installed OWFS on a Fedora 9 machine. I'm using USB version of the controller, with a DS19s20 temperature sensor. All is working fine, but after 10-20 temperature readings, somethis is happening and I can only see "invalid argument" instead of the temperature. repluging the USB doest nothing, only a system reboot will work. I tested the sensor on a Vista machine (with OneWireViewer) and it was working fine for more than 1 hour. I also made a script to read each second the id of the controller, and it worked without any problem 4-5 hours. Is there a patch or something for this problem ? Thanks, Cristi ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Owfs-developers mailing list Owfs-developers@... https://lists.sourceforge.net/lists/listinfo/owfs-developers |
|
|
Re: Fedora Core 9 - DS9490R problemThis is a new type of error. Let's explore it a bit.
1. It sounds like the underlying hardware is ok, since Vista doesn't complain. 2. Is it only the temperature reading? Can you read temphigh without problems, even after the error? 3. Are you using owfs, owserver, owhttpd? 4. Which version of owfs are you usnig? (owfs --version) Paul Alfille On Sat, Jun 14, 2008 at 6:44 PM, Cristi Tudora <cristi.tudora@...> wrote: Hello, ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Owfs-developers mailing list Owfs-developers@... https://lists.sourceforge.net/lists/listinfo/owfs-developers |
|
|
Re: Fedora Core 9 - DS9490R problem2. I only have one sensor (DS18s20). I tryed to read temperature and temphigh. The same thing is happening. After error, I can't see the 10.* device, not even 81.* device. Here is a ls -l /mnt/1-wire:
drwxr-xr-x 1 root root 8 2008-06-15 19:59 bus.0 drwxr-xr-x 1 root root 8 2008-06-15 19:59 settings drwxr-xr-x 1 root root 8 2008-06-15 19:59 statistics drwxr-xr-x 1 root root 30 2008-06-15 19:59 structure drwxr-xr-x 1 root root 8 2008-06-15 19:59 system drwxr-xr-x 1 root root 8 2008-06-15 19:59 uncached 3. I tryed owfs and owhttp. Same error. 4. ./owfs version: 2.7p4 libow version: 2.7p4 Here is the log from initial owfs start: ./owfs -u1 -m /mnt/1-wire --foreground --error_level=9 CONNECT: fuse mount point: /mnt/1-wire CALL: PARSENAME path=[] CONNECT: Adapter found: 001/002 DEFAULT: Opened USB DS9490 adapter at 001/002. DATA: DS9490_setup_adapter: done (ret=0) DEBUG: Start of directory path= device=00 00 00 00 00 00 00 00 DEBUG: Selecting a path (and device) path= SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DEBUG: Clearing root branch DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Transaction send = 0 DEBUG: Transaction end = 0 DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Index 0 DEBUG: Got 16 bytes from USB search DEBUG: DS9490 directory gulp. Adding element 0:10 00 83 50 01 08 00 7B DEBUG: DS9490 directory gulp. Adding element 1:81 B3 50 29 00 00 00 82 DEBUG: DS9490_next_both SN found: 10 00 83 50 01 08 00 7B DEBUG: BUS_next return = 0 10 00 83 50 01 08 00 7B DEBUG: Selecting a path (and device) path= SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: ok DEBUG: Index 1 DEBUG: DS9490_next_both SN found: 81 B3 50 29 00 00 00 82 DEBUG: BUS_next return = 0 81 B3 50 29 00 00 00 82 CONNECT: Good DS1421 tag found for 001/002 DEFAULT: Set DS9490 001/002 unique id to 81 B3 50 29 00 00 00 82 DEBUG: fuse_mnt_opt=[(null)] DEBUG: fuse_open_opt=[(null)] unique: 1, opcode: INIT (26), nodeid: 0, insize: 56 INIT: 7.9 flags=0x0000000b max_readahead=0x00020000 INIT: 7.8 flags=0x00000001 max_readahead=0x00020000 max_write=0x00020000 unique: 1, error: 0 (Success), outsize: 40 ........... --- OneWireQuery done DEBUG: Cache_Get 10 00 83 50 01 08 00 7B size=8 IsUncachedDir=0 DEBUG: Get from cache sn 10 00 83 50 01 08 00 7B pointer=0x1692ec index=0 size=8 DEBUG: value not found in cache DEBUG: Cache_Get_Internal 10 00 83 50 01 08 00 7B size=1 DEBUG: Get from cache sn 10 00 83 50 01 08 00 7B pointer=0x169148 index=-2 size=1 DEBUG: value not found in cache DEBUG: Selecting a path (and device) path=/10.008350010800/temperature SN=10 00 83 50 01 08 00 7B last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset DATA: DS9490_reset: error sending reset ret=-110 DEBUG: Transaction select = 1 DEBUG: Selecting a path (and device) path=/10.008350010800/temperature SN=10 00 83 50 01 08 00 7B last path=00 00 00 00 00 00 00 00 DATA: DS9490_reset And here is the output of repetitive cat for temphigh: Sun Jun 15 19:45:52 2008 75 Sun Jun 15 19:45:53 2008 75 Sun Jun 15 19:45:54 2008 75 Sun Jun 15 19:45:56 2008 75 Sun Jun 15 19:45:57 2008 75 cat: /mnt/1-wire/uncached/10.008350010800/temphigh: Invalid argument Sun Jun 15 19:46:13 2008 cat: /mnt/1-wire/uncached/10.*/temphigh: No such file or directory Sun Jun 15 19:46:19 2008 After the error, if I try to start owfs (firs I killed old owfs): [root@localhost bin]# ./owfs -u1 -m /mnt/1-wire --foreground --error_level=9 CONNECT: fuse mount point: /mnt/1-wire CALL: PARSENAME path=[] CONNECT: Adapter found: 001/002 CONNECT: Failed to set configuration on USB DS9490 adapter at 001/002. Could not open the USB adapter. Is there a problem with permissions? DEFAULT: Cannot open USB adapter DEBUG: fuse_mnt_opt=[(null)] DEBUG: fuse_open_opt=[(null)] unique: 1, opcode: INIT (26), nodeid: 0, insize: 56 INIT: 7.9 flags=0x0000000b I also tryed to run owfs, read temperature, kill owfs and so on, but did not solved the problem. Here is the script: #!/usr/bin/perl while(1) { `./owfs -u1 /mnt/1-wire`; $v1=`cat /mnt/1-wire/uncached/10.*/temphigh`; # $v2=`cat /mnt/1-wire/10.*/temphigh`; # $v3=`cat /mnt/1-wire/81.B35029000000/id`; `killall owfs`; print " ".localtime(); print "$v1 $v2 $v3"; print "\n"; sleep(1); } On Sun, Jun 15, 2008 at 3:25 AM, Paul Alfille <paul.alfille@...> wrote: This is a new type of error. Let's explore it a bit. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Owfs-developers mailing list Owfs-developers@... https://lists.sourceforge.net/lists/listinfo/owfs-developers |
|
|
Re: Fedora Core 9 - DS9490R problemAccording to the log, you receive a ETIMEDOUT (110) error after
reading/writing to the usb-adapter. DEBUG: Selecting a path (and device)
path=/10.008350010800/temperature SN=10 00 83 50 01 08 00 7B last path=00 00 00
00 00 00 00 00 Your usb-interface seem to have problem after the write-error
happens, and I think this is some kind of hardware or kernel-problem in your computer. The default is to use the usb_flextime speed, but you might try
to use the slower regular time instead and see if this works better for you. # owserver -u --usb_regulartime # owfs -s 4304 /mnt/1wire You should now see that flexible timing isn’t used. # cat /mnt/1wire/bus.0/bus.0/interface/settings/flexible_timing 0 Can you try it and see if it works better for you? Also check dmesg for usb-errormessages if it happens again. It
could be good to know what your kernel says about the usb-interface and the
errors. It should be possible to just unload the usb-modules and reload
them again if the problem happens again. # /sbin/rmmod ehci_hcd # /sbin/rmmod ohci_hcd # /sbin/rmmod uhci_hcd # /sbin/modprobe uhci_hcd # /sbin/modprobe ohci_hcd # /sbin/modprobe ehci_hcd # /sbin/lsusb And hopefully you can use the usb-adapter again. /Christian From: owfs-developers-bounces@...
[mailto:owfs-developers-bounces@...] On Behalf Of Cristi
Tudora 2. I only have one sensor
(DS18s20). I tryed to read temperature and temphigh. The same thing is
happening. After error, I can't see the 10.* device, not even 81.* device. Here
is a ls -l /mnt/1-wire: ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Owfs-developers mailing list Owfs-developers@... https://lists.sourceforge.net/lists/listinfo/owfs-developers |
|
|
Re: Fedora Core 9 - DS9490R problemthanks. Yes, with rmmod and insmod is working.
On Tue, Jun 17, 2008 at 4:10 PM, Christian Magnusson <mag@...> wrote:
------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Owfs-developers mailing list Owfs-developers@... https://lists.sourceforge.net/lists/listinfo/owfs-developers |
| Free Forum Powered by Nabble | Forum Help |