Re: [Owfs-developers] Problems in owfs2.p14 DS9490
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Getting back on this, attached two patches..
This is definitely no fix but more a works-for-me-HACK! though it
might outline where trouble starts..
At least in two of my testbeds it improves owserver running reliable
with multiple DS9490 and long networks for days, instead of minutes.
Though it still doesn't resolve the problem, that when it hits a
reset-error on a null bus without id (which couldn't be), no real
action besides a NOOP-loop is IMHO taken. (as comment in patch)
The stuff in ow_usb_msg.c is only for debugging. Just adding this,
it's easy to see that after an usb-reset the adaptors go on
unitialized with wrong settings.
best regards,
Michael
Am 17.03.2012 17:23, schrieb Michael Markstaller:
I changed the subject..
Am 16.03.2012 14:49, schrieb Paul Alfille:
To hunt this down, you find that heavy USB activity causes
communication failures and puts owfs is an unusable state?
No, I don't think thats a root cause. My last tests where done with
only 1-4 DS9490R on a powered hub without any other USB-devices
active. Maybe heavy USB-traffic or long-lines intensify the problem
but it also happens in simle setups.
Referring to my post:
http://article.gmane.org/gmane.comp.file-systems.owfs.devel/9120
#1) is pretty reproduceable, just a matter of time (minutes to
hours), regardless wether there is one DS9490 and one sensor or 6
and 50.. (leads to #2): the mode-register isn't set after a
subsequent PoR of the DS2490 IMHO, only initially, so it's set to
standard instead of flexible speed which doesn't work
reliable. #3 (long lines): I *think* its mostly #1+#2: reset_errors
occur faster on long lines and after the reset the BM is running at
standard vs. flexible speed which then worses the problem until all
sensors (including the 81.xx id-chip!) is lost.
As fas as I understand the code, what happens then is trying to
reset/reconnect the lost BM resulting in a noop: DEBUG:
ow_ds9490.c:(513) Attempting RESET on null bus DEBUG:
ow_reset.c:(48) Reset error. Reconnection 4/2
until a restart of owserver the whole bus is lost
I experienced the problems with openwrt (current trunk)
owfs2.8p8/p14 and was able to reproduce them easily with 2.8p14 on
ubuntu 11.10
(#4 this might be related or not) - under openwrt I get masses of
usb 1-1.1: usbfs: usb_submit_urb returned -28 in dmesg
I need to create a test bed to mimic and correct this.
Would be no issue to setup some systems for testing!
best regards
Michael
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
___ Owfs-developers
mailing list Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk962lsACgkQaWRHV2kMuAL5oACeKI6g7RXbpcEjuSzmdmiGNUl5
46YAn1wGNog/F24zMGXKjUABMOuM0pt2
=DetY
-END PGP SIGNATURE-
--- owfs-2.8p14/module/owlib/src/c/ow_ds9490.c 2011-12-11 03:29:48.0 +0100
+++ module/owlib/src/c/ow_ds9490.c 2012-04-03 12:39:47.419243139 +0200
@@ -506,8 +506,10 @@
struct connection_in * in = pn-selected_connection ;
int readlen = 0 ;
+ LEVEL_DEBUG(DS9490 RESET. changed %d, flex: %d, in-changed_bus_settings, in-flex) ;
+
if (in-master.usb.usb == NULL || in-master.usb.dev == NULL) {
- LEVEL_DEBUG(Attempting RESET on null bus) ;
+ LEVEL_DEBUG(Attempting RESET on null bus %d/%d, in-master.usb.usb, in-master.usb.dev) ; //FIXME! what doees it mean? no action/reconnect is even tried- shouldn't we just drop this BM and let uscan rediscover it? DS9490 must always have an ID chip..
return BUS_RESET_ERROR;
}
@@ -530,7 +532,8 @@
}
// Send reset
- if ( BAD( USB_Control_Msg(COMM_CMD, COMM_1_WIRE_RESET | COMM_F | COMM_IM | COMM_SE, USpeed, pn)) ) {
+ //FIXME: MM/ changed hard to flexible speed as it gets wrong somewhere, only want flexible
+ if ( BAD( USB_Control_Msg(COMM_CMD, COMM_1_WIRE_RESET | COMM_F | COMM_IM | COMM_SE, ONEWIREBUSSPEED_FLEXIBLE, pn)) ) {
LEVEL_DATA(Reset command rejected);
return BUS_RESET_ERROR; // fatal error... probably closed usb-handle
}
@@ -545,18 +548,41 @@
switch( DS9490_getstatus(buffer, readlen, pn) ) {
case BUS_RESET_SHORT:
/* Short detected, but otherwise no bigger problem */
+ LEVEL_DEBUG(DS9490_Reset: SHORT);
return BUS_RESET_SHORT ;
case BUS_RESET_OK:
+ LEVEL_DEBUG(DS9490_Reset: OK);
break ;
case BUS_RESET_ERROR:
default:
- return BUS_RESET_ERROR;
+ LEVEL_DEBUG(DS9490_Reset: ERROR);
+ /* FIXME: FIXED. In ow_usb_msg.c an USB-reset was was issued:
+ * USB_Control_Msg(CONTROL_CMD, CTL_RESET_DEVICE, 0x, pn) ;
+ * So we need to setup the Adapter again
+ *
[Owfs-developers] ds9097 on embedded boards
Hi folks, I'm trying to make a working temperature logging device on embedded platform (because of consumption reason). I was already trying to prepare before, but haven't succeeded. It works on PC (But I don't want to let running a whole PC ) normally. So I dicided to move this simple thing to a routerboard 433AH. It didn't worked. only gives this directory structure: root@drone:/mnt/1w# ls -la drwxr-xr-x1 root root8 Jan 1 00:21 . drwxr-xr-x5 root root 1024 Jan 1 00:07 .. drwxr-xr-x1 root root8 Jan 1 00:21 bus.0 drwxr-xr-x1 root root8 Jan 1 00:21 settings drwxr-xr-x1 root root8 Jan 1 00:21 statistics drwxr-xr-x1 root root 30 Jan 1 00:21 structure drwxr-xr-x1 root root8 Jan 1 00:21 system drwxr-xr-x1 root root8 Jan 1 00:21 uncached I thought it doesn't work on routerboard. So I bought a wrap board ( http://www.pcengines.ch/alix2d2.htm ), which is x86 based and I'm trying on it to make it work. But the problem is the same :-( Of course I disabled the serial consol Is there anybody can help me, I don't know where to look for the rason of the failure ?! *the --debug says when I start:* *** root@drone:~# owfs --passive=/dev/ttyS0 /mnt/1w/ --8bit --debug CONNECT: owfs.c:main(123) fuse mount point: /mnt/1w/ CONNECT: ow_avahi_link.c:OW_Load_avahi_library(72) No Avahi support. Library libavahi-client couldn't be loaded CONNECT: ow_dnssd.c:OW_Load_dnssd_library(136) Zeroconf/Bonjour is disabled since dnssd library isn't found CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[] DEBUG: owlib.c:SetupTemperatureLimits(79) Globals temp limits 0C 100C (for simulated adapters) DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 0 OWFS DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 1 /mnt/1w/ DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 2 -o DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 3 direct_io DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 4 -f DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 5 -d DEBUG: owfs.c:main(152) fuse_mnt_opt=[(null)] DEBUG: owfs.c:main(154) fuse_open_opt=[(null)] FUSE library version: 2.8.3 nullpath_ok: 0 unique: 1, opcode: INIT (26), nodeid: 0, insize: 56 INIT: 7.13 flags=0x007b max_readahead=0x0002 INIT: 7.12 flags=0x0011 max_readahead=0x0002 max_write=0x0002 unique: 1, success, outsize: 40 *** * When I try to list the mountpoint directory:* **unique: 2, opcode: ACCESS (34), nodeid: 1, insize: 48 unique: 2, error: -38 (Function not implemented), outsize: 16 unique: 3, opcode: GETATTR (3), nodeid: 1, insize: 56 getattr / CALL: ow_fstat.c:FS_fstat(22) path=/ CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/] CALL: ow_fstat.c:FS_fstat_postparse(39) ATTRIBUTES path=/ DEBUG: ow_parsename.c:FS_ParsedName_destroy(54) / unique: 3, success, outsize: 120 unique: 4, opcode: OPENDIR (27), nodeid: 1, insize: 48 unique: 4, success, outsize: 32 unique: 5, opcode: READDIR (28), nodeid: 1, insize: 80 getdir[0] CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/] CALL: owfs_callback.c:FS_getdir(175) GETDIR path=/ DEBUG: ow_dir.c:FS_dir(63) path=/ CALL: ow_dir.c:FS_dir_both(98) path=/ DEBUG: ow_cache.c:Cache_Get_Dir(806) Looking for directory 00 00 00 00 00 00 00 00 DEBUG: ow_cache.c:Cache_Get_Common_Dir(819) Get from cache sn 00 00 00 00 00 00 00 00 pointer=0xb7766f34 extension=0 DEBUG: ow_cache.c:Cache_Get_Common_Dir(843) dir not found in cache DEBUG: ow_search.c:BUS_first(32) Start of directory path=/ device=00 00 00 00 00 00 00 00 DEBUG: ow_select.c:BUS_select(72) Selecting a path (and device) path=/ SN=00 00 00 00 00 00 00 00 last path=FF 00 00 00 00 00 00 00 DEBUG: ow_select.c:BUS_select(77) Clearing root branch DEBUG: ow_transaction.c:BUS_transaction_single(99) send = 0 DEBUG: ow_transaction.c:BUS_transaction_single(168) end = 0 DEBUG: ow_cache.c:Cache_Add_Dir(405) Adding duirectory for 00 00 00 00 00 00 00 00 elements=0 DEBUG: ow_cache.c:Cache_Add_Common(595) Add to cache sn 00 00 00 00 00 00 00 00 pointer=0xb7766f34 index=0 size=0 CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/bus.0] DEBUG: ow_parsename.c:FS_ParsedName_destroy(54) /bus.0 CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/uncached] DEBUG: ow_parsename.c:FS_ParsedName_destroy(54) /uncached CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/settings] DEBUG: ow_parsename.c:FS_ParsedName_destroy(54) /settings CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/system] DEBUG: ow_parsename.c:FS_ParsedName_destroy(54) /system CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/statistics] DEBUG: ow_parsename.c:FS_ParsedName_destroy(54) /statistics CALL: ow_parsename.c:FS_ParsedName_anywhere(90)
Re: [Owfs-developers] ds9097 on embedded boards
hum, check statistics if theres a short counter with value 0 Em 3 de abril de 2012 10:46, Kassai Istvan k...@zhnet.hu escreveu: Hi folks, I'm trying to make a working temperature logging device on embedded platform (because of consumption reason). I was already trying to prepare before, but haven't succeeded. It works on PC (But I don't want to let running a whole PC ) normally. So I dicided to move this simple thing to a routerboard 433AH. It didn't worked. only gives this directory structure: root@drone:/mnt/1w# ls -la drwxr-xr-x 1 root root 8 Jan 1 00:21 . drwxr-xr-x 5 root root 1024 Jan 1 00:07 .. drwxr-xr-x 1 root root 8 Jan 1 00:21 bus.0 drwxr-xr-x 1 root root 8 Jan 1 00:21 settings drwxr-xr-x 1 root root 8 Jan 1 00:21 statistics drwxr-xr-x 1 root root 30 Jan 1 00:21 structure drwxr-xr-x 1 root root 8 Jan 1 00:21 system drwxr-xr-x 1 root root 8 Jan 1 00:21 uncached I thought it doesn't work on routerboard. So I bought a wrap board ( http://www.pcengines.ch/alix2d2.htm ), which is x86 based and I'm trying on it to make it work. But the problem is the same :-( Of course I disabled the serial consol Is there anybody can help me, I don't know where to look for the rason of the failure ?! the --debug says when I start: *** root@drone:~# owfs --passive=/dev/ttyS0 /mnt/1w/ --8bit --debug CONNECT: owfs.c:main(123) fuse mount point: /mnt/1w/ CONNECT: ow_avahi_link.c:OW_Load_avahi_library(72) No Avahi support. Library libavahi-client couldn't be loaded CONNECT: ow_dnssd.c:OW_Load_dnssd_library(136) Zeroconf/Bonjour is disabled since dnssd library isn't found CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[] DEBUG: owlib.c:SetupTemperatureLimits(79) Globals temp limits 0C 100C (for simulated adapters) DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 0 OWFS DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 1 /mnt/1w/ DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 2 -o DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 3 direct_io DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 4 -f DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 5 -d DEBUG: owfs.c:main(152) fuse_mnt_opt=[(null)] DEBUG: owfs.c:main(154) fuse_open_opt=[(null)] FUSE library version: 2.8.3 nullpath_ok: 0 unique: 1, opcode: INIT (26), nodeid: 0, insize: 56 INIT: 7.13 flags=0x007b max_readahead=0x0002 INIT: 7.12 flags=0x0011 max_readahead=0x0002 max_write=0x0002 unique: 1, success, outsize: 40 *** When I try to list the mountpoint directory: **unique: 2, opcode: ACCESS (34), nodeid: 1, insize: 48 unique: 2, error: -38 (Function not implemented), outsize: 16 unique: 3, opcode: GETATTR (3), nodeid: 1, insize: 56 getattr / CALL: ow_fstat.c:FS_fstat(22) path=/ CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/] CALL: ow_fstat.c:FS_fstat_postparse(39) ATTRIBUTES path=/ DEBUG: ow_parsename.c:FS_ParsedName_destroy(54) / unique: 3, success, outsize: 120 unique: 4, opcode: OPENDIR (27), nodeid: 1, insize: 48 unique: 4, success, outsize: 32 unique: 5, opcode: READDIR (28), nodeid: 1, insize: 80 getdir[0] CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/] CALL: owfs_callback.c:FS_getdir(175) GETDIR path=/ DEBUG: ow_dir.c:FS_dir(63) path=/ CALL: ow_dir.c:FS_dir_both(98) path=/ DEBUG: ow_cache.c:Cache_Get_Dir(806) Looking for directory 00 00 00 00 00 00 00 00 DEBUG: ow_cache.c:Cache_Get_Common_Dir(819) Get from cache sn 00 00 00 00 00 00 00 00 pointer=0xb7766f34 extension=0 DEBUG: ow_cache.c:Cache_Get_Common_Dir(843) dir not found in cache DEBUG: ow_search.c:BUS_first(32) Start of directory path=/ device=00 00 00 00 00 00 00 00 DEBUG: ow_select.c:BUS_select(72) Selecting a path (and device) path=/ SN=00 00 00 00 00 00 00 00 last path=FF 00 00 00 00 00 00 00 DEBUG: ow_select.c:BUS_select(77) Clearing root branch DEBUG: ow_transaction.c:BUS_transaction_single(99) send = 0 DEBUG: ow_transaction.c:BUS_transaction_single(168) end = 0 DEBUG: ow_cache.c:Cache_Add_Dir(405) Adding duirectory for 00 00 00 00 00 00 00 00 elements=0 DEBUG: ow_cache.c:Cache_Add_Common(595) Add to cache sn 00 00 00 00 00 00 00 00 pointer=0xb7766f34 index=0 size=0 CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/bus.0] DEBUG: ow_parsename.c:FS_ParsedName_destroy(54) /bus.0 CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/uncached] DEBUG: ow_parsename.c:FS_ParsedName_destroy(54) /uncached CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/settings] DEBUG: ow_parsename.c:FS_ParsedName_destroy(54) /settings CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/system] DEBUG: ow_parsename.c:FS_ParsedName_destroy(54) /system
Re: [Owfs-developers] Problems in owfs2.p14 DS9490
hi, could you add a version information at debug output too? maybe at the start of ow program, just to us know what's the version... this could be easier to know what we are debugging Em 3 de abril de 2012 08:09, Michael Markstaller m...@elabnet.de escreveu: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Getting back on this, attached two patches.. This is definitely no fix but more a works-for-me-HACK! though it might outline where trouble starts.. At least in two of my testbeds it improves owserver running reliable with multiple DS9490 and long networks for days, instead of minutes. Though it still doesn't resolve the problem, that when it hits a reset-error on a null bus without id (which couldn't be), no real action besides a NOOP-loop is IMHO taken. (as comment in patch) The stuff in ow_usb_msg.c is only for debugging. Just adding this, it's easy to see that after an usb-reset the adaptors go on unitialized with wrong settings. best regards, Michael Am 17.03.2012 17:23, schrieb Michael Markstaller: I changed the subject.. Am 16.03.2012 14:49, schrieb Paul Alfille: To hunt this down, you find that heavy USB activity causes communication failures and puts owfs is an unusable state? No, I don't think thats a root cause. My last tests where done with only 1-4 DS9490R on a powered hub without any other USB-devices active. Maybe heavy USB-traffic or long-lines intensify the problem but it also happens in simle setups. Referring to my post: http://article.gmane.org/gmane.comp.file-systems.owfs.devel/9120 #1) is pretty reproduceable, just a matter of time (minutes to hours), regardless wether there is one DS9490 and one sensor or 6 and 50.. (leads to #2): the mode-register isn't set after a subsequent PoR of the DS2490 IMHO, only initially, so it's set to standard instead of flexible speed which doesn't work reliable. #3 (long lines): I *think* its mostly #1+#2: reset_errors occur faster on long lines and after the reset the BM is running at standard vs. flexible speed which then worses the problem until all sensors (including the 81.xx id-chip!) is lost. As fas as I understand the code, what happens then is trying to reset/reconnect the lost BM resulting in a noop: DEBUG: ow_ds9490.c:(513) Attempting RESET on null bus DEBUG: ow_reset.c:(48) Reset error. Reconnection 4/2 until a restart of owserver the whole bus is lost I experienced the problems with openwrt (current trunk) owfs2.8p8/p14 and was able to reproduce them easily with 2.8p14 on ubuntu 11.10 (#4 this might be related or not) - under openwrt I get masses of usb 1-1.1: usbfs: usb_submit_urb returned -28 in dmesg I need to create a test bed to mimic and correct this. Would be no issue to setup some systems for testing! best regards Michael -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk962lsACgkQaWRHV2kMuAL5oACeKI6g7RXbpcEjuSzmdmiGNUl5 46YAn1wGNog/F24zMGXKjUABMOuM0pt2 =DetY -END PGP SIGNATURE- -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Roberto Spadim Spadim Technology / SPAEmpresarial -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] ds9097 on embedded boards
There are two files under the owfs mountpoint named shorts. One in the ./bus.0/interface/statistics/ and one in the ./uncached/bus.0/interface/statistics/ Both of them contains 0 2012-04-03 16:35 keltezéssel, Roberto Spadim írta: hum, check statistics if theres a short counter with value0 Em 3 de abril de 2012 10:46, Kassai Istvank...@zhnet.hu escreveu: Hi folks, I'm trying to make a working temperature logging device on embedded platform (because of consumption reason). I was already trying to prepare before, but haven't succeeded. It works on PC (But I don't want to let running a whole PC ) normally. So I dicided to move this simple thing to a routerboard 433AH. It didn't worked. only gives this directory structure: root@drone:/mnt/1w# ls -la drwxr-xr-x1 root root8 Jan 1 00:21 . drwxr-xr-x5 root root 1024 Jan 1 00:07 .. drwxr-xr-x1 root root8 Jan 1 00:21 bus.0 drwxr-xr-x1 root root8 Jan 1 00:21 settings drwxr-xr-x1 root root8 Jan 1 00:21 statistics drwxr-xr-x1 root root 30 Jan 1 00:21 structure drwxr-xr-x1 root root8 Jan 1 00:21 system drwxr-xr-x1 root root8 Jan 1 00:21 uncached I thought it doesn't work on routerboard. So I bought a wrap board ( http://www.pcengines.ch/alix2d2.htm ), which is x86 based and I'm trying on it to make it work. But the problem is the same :-( Of course I disabled the serial consol Is there anybody can help me, I don't know where to look for the rason of the failure ?! the --debug says when I start: *** root@drone:~# owfs --passive=/dev/ttyS0 /mnt/1w/ --8bit --debug CONNECT: owfs.c:main(123) fuse mount point: /mnt/1w/ CONNECT: ow_avahi_link.c:OW_Load_avahi_library(72) No Avahi support. Library libavahi-client couldn't be loaded CONNECT: ow_dnssd.c:OW_Load_dnssd_library(136) Zeroconf/Bonjour is disabled since dnssd library isn't found CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[] DEBUG: owlib.c:SetupTemperatureLimits(79) Globals temp limits 0C 100C (for simulated adapters) DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 0 OWFS DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 1 /mnt/1w/ DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 2 -o DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 3 direct_io DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 4 -f DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 5 -d DEBUG: owfs.c:main(152) fuse_mnt_opt=[(null)] DEBUG: owfs.c:main(154) fuse_open_opt=[(null)] FUSE library version: 2.8.3 nullpath_ok: 0 unique: 1, opcode: INIT (26), nodeid: 0, insize: 56 INIT: 7.13 flags=0x007b max_readahead=0x0002 INIT: 7.12 flags=0x0011 max_readahead=0x0002 max_write=0x0002 unique: 1, success, outsize: 40 *** When I try to list the mountpoint directory: **unique: 2, opcode: ACCESS (34), nodeid: 1, insize: 48 unique: 2, error: -38 (Function not implemented), outsize: 16 unique: 3, opcode: GETATTR (3), nodeid: 1, insize: 56 getattr / CALL: ow_fstat.c:FS_fstat(22) path=/ CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/] CALL: ow_fstat.c:FS_fstat_postparse(39) ATTRIBUTES path=/ DEBUG: ow_parsename.c:FS_ParsedName_destroy(54) / unique: 3, success, outsize: 120 unique: 4, opcode: OPENDIR (27), nodeid: 1, insize: 48 unique: 4, success, outsize: 32 unique: 5, opcode: READDIR (28), nodeid: 1, insize: 80 getdir[0] CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/] CALL: owfs_callback.c:FS_getdir(175) GETDIR path=/ DEBUG: ow_dir.c:FS_dir(63) path=/ CALL: ow_dir.c:FS_dir_both(98) path=/ DEBUG: ow_cache.c:Cache_Get_Dir(806) Looking for directory 00 00 00 00 00 00 00 00 DEBUG: ow_cache.c:Cache_Get_Common_Dir(819) Get from cache sn 00 00 00 00 00 00 00 00 pointer=0xb7766f34 extension=0 DEBUG: ow_cache.c:Cache_Get_Common_Dir(843) dir not found in cache DEBUG: ow_search.c:BUS_first(32) Start of directory path=/ device=00 00 00 00 00 00 00 00 DEBUG: ow_select.c:BUS_select(72) Selecting a path (and device) path=/ SN=00 00 00 00 00 00 00 00 last path=FF 00 00 00 00 00 00 00 DEBUG: ow_select.c:BUS_select(77) Clearing root branch DEBUG: ow_transaction.c:BUS_transaction_single(99) send = 0 DEBUG: ow_transaction.c:BUS_transaction_single(168) end = 0 DEBUG: ow_cache.c:Cache_Add_Dir(405) Adding duirectory for 00 00 00 00 00 00 00 00 elements=0 DEBUG: ow_cache.c:Cache_Add_Common(595) Add to cache sn 00 00 00 00 00 00 00 00 pointer=0xb7766f34 index=0 size=0 CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/bus.0] DEBUG: ow_parsename.c:FS_ParsedName_destroy(54) /bus.0 CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/uncached] DEBUG:
Re: [Owfs-developers] ds9097 on embedded boards
So you've already done a lot of debugging -- the fuse system works, and the hardware works on another system. Thus the problem is with serial port handling (hardware or kernel or maybe timing). digitemp http://www.digitemp.com/ has support for the DS9097E passive adapter and would be another test of the hardware. It shouldn't be a polarity issue, but it could be a voltage problem on the embedded board. The passive adapter steals power from the serial pins. Paul Alfille On Tue, Apr 3, 2012 at 1:27 PM, Kassai Istvan k...@zhnet.hu wrote: There are two files under the owfs mountpoint named shorts. One in the ./bus.0/interface/statistics/ and one in the ./uncached/bus.0/interface/statistics/ Both of them contains 0 2012-04-03 16:35 keltezéssel, Roberto Spadim írta: hum, check statistics if theres a short counter with value0 Em 3 de abril de 2012 10:46, Kassai Istvank...@zhnet.hu escreveu: Hi folks, I'm trying to make a working temperature logging device on embedded platform (because of consumption reason). I was already trying to prepare before, but haven't succeeded. It works on PC (But I don't want to let running a whole PC ) normally. So I dicided to move this simple thing to a routerboard 433AH. It didn't worked. only gives this directory structure: root@drone:/mnt/1w# ls -la drwxr-xr-x1 root root8 Jan 1 00:21 . drwxr-xr-x5 root root 1024 Jan 1 00:07 .. drwxr-xr-x1 root root8 Jan 1 00:21 bus.0 drwxr-xr-x1 root root8 Jan 1 00:21 settings drwxr-xr-x1 root root8 Jan 1 00:21 statistics drwxr-xr-x1 root root 30 Jan 1 00:21 structure drwxr-xr-x1 root root8 Jan 1 00:21 system drwxr-xr-x1 root root8 Jan 1 00:21 uncached I thought it doesn't work on routerboard. So I bought a wrap board ( http://www.pcengines.ch/alix2d2.htm ), which is x86 based and I'm trying on it to make it work. But the problem is the same :-( Of course I disabled the serial consol Is there anybody can help me, I don't know where to look for the rason of the failure ?! the --debug says when I start: *** root@drone:~# owfs --passive=/dev/ttyS0 /mnt/1w/ --8bit --debug CONNECT: owfs.c:main(123) fuse mount point: /mnt/1w/ CONNECT: ow_avahi_link.c:OW_Load_avahi_library(72) No Avahi support. Library libavahi-client couldn't be loaded CONNECT: ow_dnssd.c:OW_Load_dnssd_library(136) Zeroconf/Bonjour is disabled since dnssd library isn't found CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[] DEBUG: owlib.c:SetupTemperatureLimits(79) Globals temp limits 0C 100C (for simulated adapters) DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 0 OWFS DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 1 /mnt/1w/ DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 2 -o DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 3 direct_io DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 4 -f DEBUG: fuse_line.c:Fuse_add(82) Added FUSE option 5 -d DEBUG: owfs.c:main(152) fuse_mnt_opt=[(null)] DEBUG: owfs.c:main(154) fuse_open_opt=[(null)] FUSE library version: 2.8.3 nullpath_ok: 0 unique: 1, opcode: INIT (26), nodeid: 0, insize: 56 INIT: 7.13 flags=0x007b max_readahead=0x0002 INIT: 7.12 flags=0x0011 max_readahead=0x0002 max_write=0x0002 unique: 1, success, outsize: 40 *** When I try to list the mountpoint directory: **unique: 2, opcode: ACCESS (34), nodeid: 1, insize: 48 unique: 2, error: -38 (Function not implemented), outsize: 16 unique: 3, opcode: GETATTR (3), nodeid: 1, insize: 56 getattr / CALL: ow_fstat.c:FS_fstat(22) path=/ CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/] CALL: ow_fstat.c:FS_fstat_postparse(39) ATTRIBUTES path=/ DEBUG: ow_parsename.c:FS_ParsedName_destroy(54) / unique: 3, success, outsize: 120 unique: 4, opcode: OPENDIR (27), nodeid: 1, insize: 48 unique: 4, success, outsize: 32 unique: 5, opcode: READDIR (28), nodeid: 1, insize: 80 getdir[0] CALL: ow_parsename.c:FS_ParsedName_anywhere(90) path=[/] CALL: owfs_callback.c:FS_getdir(175) GETDIR path=/ DEBUG: ow_dir.c:FS_dir(63) path=/ CALL: ow_dir.c:FS_dir_both(98) path=/ DEBUG: ow_cache.c:Cache_Get_Dir(806) Looking for directory 00 00 00 00 00 00 00 00 DEBUG: ow_cache.c:Cache_Get_Common_Dir(819) Get from cache sn 00 00 00 00 00 00 00 00 pointer=0xb7766f34 extension=0 DEBUG: ow_cache.c:Cache_Get_Common_Dir(843) dir not found in cache DEBUG: ow_search.c:BUS_first(32) Start of directory path=/ device=00 00 00 00 00 00 00 00 DEBUG: ow_select.c:BUS_select(72) Selecting a path (and device) path=/ SN=00 00 00 00 00 00 00 00 last
Re: [Owfs-developers] ds9097 on embedded boards
2012-04-03 20:11 keltezéssel, Paul Alfille írta: So you've already done a lot of debugging -- the fuse system works, and the hardware works on another system. Thus the problem is with serial port handling (hardware or kernel or maybe timing). digitemp http://www.digitemp.com/ has support for the DS9097E passive adapter and would be another test of the hardware. It shouldn't be a polarity issue, but it could be a voltage problem on the embedded board. The passive adapter steals power from the serial pins. You mean it steals power for the adapter, or the sensor own? (I think for the sensor, cause the adapter has only passive parts) The sensor works in parasite mode. May the problem resolved by directly powering the sensor? Paul Alfille On Tue, Apr 3, 2012 at 1:27 PM, Kassai Istvan k...@zhnet.hu mailto:k...@zhnet.hu wrote: There are two files under the owfs mountpoint named shorts. One in the ./bus.0/interface/statistics/ and one in the ./uncached/bus.0/interface/statistics/ Both of them contains 0 -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] ds9097 on embedded boards
I assume that the serial port of the embedded system only provides 5V on its signal lines. If the DS9097 expects 12V and uses a voltage regulator to provide 5V to the bus, it will most probably fail. Can you measure voltage between 1wire and gnd pins on your adaptor? It should not be much less than 5 volts. best regards, Markus On Apr 3, Kassai Istvan k...@zhnet.hu wrote: 2012-04-03 20:11 keltezéssel, Paul Alfille írta: So you've already done a lot of debugging -- the fuse system works, and the hardware works on another system. Thus the problem is with serial port handling (hardware or kernel or maybe timing). digitemp http://www.digitemp.com/ has support for the DS9097E passive adapter and would be another test of the hardware. It shouldn't be a polarity issue, but it could be a voltage problem on the embedded board. The passive adapter steals power from the serial pins. You mean it steals power for the adapter, or the sensor own? (I think for the sensor, cause the adapter has only passive parts) The sensor works in parasite mode. May the problem resolved by directly powering the sensor? Paul Alfille On Tue, Apr 3, 2012 at 1:27 PM, Kassai Istvan k...@zhnet.hu mailto:k...@zhnet.hu wrote: There are two files under the owfs mountpoint named shorts. One in the ./bus.0/interface/statistics/ and one in the ./uncached/bus.0/interface/statistics/ Both of them contains 0 -- __/\ Markus Gaugusch \ /ASCII Ribbon Campaign markus(at)gaugusch.at X Against HTML Mail / \-- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] HA7E Adapter
I have an HA7E adapter that I would like to test, but owfs does not seem to recognise it. I am running owfs 2.8p13 installed from the deb repository. I seem to remember from somewhere that you had to select HA7E at compile time, is it included in the deb package? Is there something else I need to do? Thanks Mick -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] HA7E Adapter
Did you try --ha7e=/dev/ttyS0 or whatever your serial port is? Paul Alfille On Tue, Apr 3, 2012 at 3:37 PM, Mick Sulley m...@sulley.info wrote: I have an HA7E adapter that I would like to test, but owfs does not seem to recognise it. I am running owfs 2.8p13 installed from the deb repository. I seem to remember from somewhere that you had to select HA7E at compile time, is it included in the deb package? Is there something else I need to do? Thanks Mick -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
[Owfs-developers] android interface
hi guys, now that many companies developed many IDE to work with android (basic4android and others..), could anyone help me developing a interface to ow programs? what´s the idea? 1) app will work on ARM Eabi 4 compatible devices (i think it will cover 90% of android devices) 2) it will create a owserver process with a command line given at user interface (easier than selecting devices, etc...) and listen to a specific port XXX 3) it will have a checkbox to startup everytime device power on 4) it will never stop, if user close app it will run background 5) it will have a stop button, to close process 6) it will start owserver at background and monitor if it´s working, if not restart 7) it will have a watchdog restart timer, at X seconds restart owserver (to don´t have problem with usb devices and others common problems that we never know what happened and don´t want to lose time solving bugs) 6) it will have a option to run owhttpd process in port YYY, conecting to owserver at port XXX 7) it must have all needed files to run owserver and owhttpd 8) no rewrite of any owserver or owhttpd code 9) add a button to open owhttpd page in android webbrowser 10) it must work and be free eheheheh 11) since it´s a android device (linux) it will work with many interfaces... maybe we should allow just some master devices... like owserver, ds2480b (bluetooth, usb serial converter, or native serial), passive serial? usb? i think that´s all. maybe ow kernel module will not work, ahavi and others zeroconf and others libs maybe could be removed 12) be opensource and free at appstore? what you think? -- Roberto Spadim Spadim Technology / SPAEmpresarial -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problems in owfs2.p14 DS9490
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 03.04.2012 16:48, schrieb Roberto Spadim: hi, could you add a version information at debug output too? maybe at the start of ow program, just to us know what's the version... this could be easier to know what we are debugging There was no Debug-output in my post, the version is in the subject, but this feature is already in CVS AFAIK ;) I'd be happy to use it, but owfs is - sorry for direct speech - really very broken regarding the stock USB-adaptors for quite a while now, thats my issue, not in which version,, Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk97r14ACgkQaWRHV2kMuAJ9AgCgx+YQtaxL9y2dkKPpqYarIdfG b+UAoIIdB3utAPa3gLGM1TMEAZiXgUFI =mpVS -END PGP SIGNATURE- -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
Re: [Owfs-developers] Problems in owfs2.p14 DS9490
sorry i wrote wrong... could you make a patch that put ow version at debug output? :) Em 3 de abril de 2012 23:18, Michael Markstaller m...@elabnet.de escreveu: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 03.04.2012 16:48, schrieb Roberto Spadim: hi, could you add a version information at debug output too? maybe at the start of ow program, just to us know what's the version... this could be easier to know what we are debugging There was no Debug-output in my post, the version is in the subject, but this feature is already in CVS AFAIK ;) I'd be happy to use it, but owfs is - sorry for direct speech - really very broken regarding the stock USB-adaptors for quite a while now, thats my issue, not in which version,, Michael -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk97r14ACgkQaWRHV2kMuAJ9AgCgx+YQtaxL9y2dkKPpqYarIdfG b+UAoIIdB3utAPa3gLGM1TMEAZiXgUFI =mpVS -END PGP SIGNATURE- -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers -- Roberto Spadim Spadim Technology / SPAEmpresarial -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev___ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
