Distribution:
Distributor ID: Debian
Description: Debian GNU/Linux 8.4 (jessie)
Release: 8.4
Codename: jessie
Description: Debian GNU/Linux 8.4 (jessie)
Release: 8.4
Codename: jessie
------
Debug of owread:
DEBUG: ow_tcp_read.c:(113) read: 24 - 0 = 24
DEBUG: from_client.c:(66) FromClient payload=10 size=65536 type=2 sg=0x10A offset=0
DEBUG: from_client.c:(74) FromClient (no servermessage) payload=10 size=65536 type=2 controlflags=0x10A offset=0
DEBUG: ow_tcp_read.c:(63) attempt 10 bytes Time: 10.000000 seconds
DEBUG: ow_tcp_read.c:(113) read: 10 - 0 = 10
DEBUG: handler.c:(153) START handler /uncached
CALL: data.c:(103) DataHandler: parse path=/uncached
DEBUG: ow_parseobject.c:(163) /uncached
CALL: ow_parsename.c:(104) path=[/uncached]
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^bus\.([[:digit:]]+)/?> compiled to 0xb7741ee0
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^settings/?> compiled to 0xb7741ec0
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^statistics/?> compiled to 0xb7741ea0
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^structure/?> compiled to 0xb7741e80
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^system/?> compiled to 0xb7741e60
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^interface/?> compiled to 0xb7741e40
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^text/?> compiled to 0xb7741e20
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^json/?> compiled to 0xb7741e00
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^uncached/?> compiled to 0xb7741de0
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^unaliased/?> compiled to 0xb7741dc0
DEBUG: ow_regex.c:(154) Not found
CALL: data.c:(144) Read message
DEBUG: read.c:(55) ReadHandler start
DEBUG: read.c:(61) ReadHandler: From Client sm->payload=10 sm->size=65536 sm->offset=0
DEBUG: read.c:(79) ReadHandler: call FS_read_postparse on /uncached
DEBUG: ow_read.c:(72) /uncached
DEBUG: read.c:(81) ReadHandler: FS_read_postparse read on /uncached return = -21
OWQ OneWireQuery structure of /uncached
OneWireQuery size=8 offset=0, extension=0
Byte buffer OneWireQuery buffer, length=8
--000: 00 00 00 00 00 00 00 00
<........>
Cleanup = 0006 OneWireQuery I=0 U=0 F=0 Y=0 D=Thu Jan 1 01:00:00 1970
DEBUG: from_client.c:(66) FromClient payload=10 size=65536 type=2 sg=0x10A offset=0
DEBUG: from_client.c:(74) FromClient (no servermessage) payload=10 size=65536 type=2 controlflags=0x10A offset=0
DEBUG: ow_tcp_read.c:(63) attempt 10 bytes Time: 10.000000 seconds
DEBUG: ow_tcp_read.c:(113) read: 10 - 0 = 10
DEBUG: handler.c:(153) START handler /uncached
CALL: data.c:(103) DataHandler: parse path=/uncached
DEBUG: ow_parseobject.c:(163) /uncached
CALL: ow_parsename.c:(104) path=[/uncached]
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^bus\.([[:digit:]]+)/?> compiled to 0xb7741ee0
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^settings/?> compiled to 0xb7741ec0
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^statistics/?> compiled to 0xb7741ea0
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^structure/?> compiled to 0xb7741e80
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^system/?> compiled to 0xb7741e60
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^interface/?> compiled to 0xb7741e40
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^text/?> compiled to 0xb7741e20
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^json/?> compiled to 0xb7741e00
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^uncached/?> compiled to 0xb7741de0
DEBUG: ow_regex.c:(74) Reg Ex _expression_ <^unaliased/?> compiled to 0xb7741dc0
DEBUG: ow_regex.c:(154) Not found
CALL: data.c:(144) Read message
DEBUG: read.c:(55) ReadHandler start
DEBUG: read.c:(61) ReadHandler: From Client sm->payload=10 sm->size=65536 sm->offset=0
DEBUG: read.c:(79) ReadHandler: call FS_read_postparse on /uncached
DEBUG: ow_read.c:(72) /uncached
DEBUG: read.c:(81) ReadHandler: FS_read_postparse read on /uncached return = -21
OWQ OneWireQuery structure of /uncached
OneWireQuery size=8 offset=0, extension=0
Byte buffer OneWireQuery buffer, length=8
--000: 00 00 00 00 00 00 00 00
<........>
Cleanup = 0006 OneWireQuery I=0 U=0 F=0 Y=0 D=Thu Jan 1 01:00:00 1970
--- OneWireQuery done
DEBUG: read.c:(86) ReadHandler: FS_read_postparse error -21
DEBUG: read.c:(100) ReadHandler: To Client cm->payload=0 cm->size=0 cm->offset=0
DEBUG: data.c:(146) Read message done value=(nil)
DEBUG: ow_parsename.c:(63) /uncached
DEBUG: data.c:(193) DataHandler: FS_ParsedName_destroy done
DEBUG: data.c:(207) DataHandler: cm.ret=-21
DEBUG: to_client.c:(76) payload=0 size=0, ret=-21, sg=0x10A offset=0
DEBUG: to_client.c:(85) No data
DEBUG: data.c:(226) Finished with client request
DEBUG: handler.c:(135) OWSERVER handler done
DEBUG: ow_net_server.c:(259) Normal completion.
DEBUG: read.c:(86) ReadHandler: FS_read_postparse error -21
DEBUG: read.c:(100) ReadHandler: To Client cm->payload=0 cm->size=0 cm->offset=0
DEBUG: data.c:(146) Read message done value=(nil)
DEBUG: ow_parsename.c:(63) /uncached
DEBUG: data.c:(193) DataHandler: FS_ParsedName_destroy done
DEBUG: data.c:(207) DataHandler: cm.ret=-21
DEBUG: to_client.c:(76) payload=0 size=0, ret=-21, sg=0x10A offset=0
DEBUG: to_client.c:(85) No data
DEBUG: data.c:(226) Finished with client request
DEBUG: handler.c:(135) OWSERVER handler done
DEBUG: ow_net_server.c:(259) Normal completion.
Gesendet: Freitag, 24. Juni 2016 um 15:03 Uhr
Von: "Jan Kandziora" <j...@gmx.de>
An: "OWFS (One-wire file system) discussion and help" <owfs-developers@lists.sourceforge.net>
Betreff: Re: [Owfs-developers] Communication to DS9097U not working
Von: "Jan Kandziora" <j...@gmx.de>
An: "OWFS (One-wire file system) discussion and help" <owfs-developers@lists.sourceforge.net>
Betreff: Re: [Owfs-developers] Communication to DS9097U not working
Am 24.06.2016 um 14:52 schrieb samuix:
> Hi,
> we have a "test" installation with a 1-Wire Adapter USB DS9490R (eService) and
> connected sensors constructed as all sensors have been read correctly.
> Now we have the "end installation" with 1-Wire bus coupler USB Pro, Isolated
> (eService) -> 1-Wire hub III DC (eService) -> i-wire bus -> sensor
> On the bus coupler, we have connected a owserver but no sensor is displayed.
> We have following trace:
>
https://www.eservice-online.de//media/pdf/Bauanleitung_1-Wire-Hub-II-AC%20V1.0.pdf
page 3 says that "1-Wire hub III DC (eService)" is a passive star
coupler rather than a onewire "hub". That means the stubs shouldn't be
longer than a few metres to avoid electrical problems.
Which distribution do you use?
Please test with owserver and owget as you need to trigger at least one
bus action to get a useful log output:
# /opt/owfs/bin/owserver --debug -d /dev/ttyUSB1
Other terminal window
$ /opt/owfs/bin/owread /uncached
What does the owserver log say?
Kind regards
Jan
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
> Hi,
> we have a "test" installation with a 1-Wire Adapter USB DS9490R (eService) and
> connected sensors constructed as all sensors have been read correctly.
> Now we have the "end installation" with 1-Wire bus coupler USB Pro, Isolated
> (eService) -> 1-Wire hub III DC (eService) -> i-wire bus -> sensor
> On the bus coupler, we have connected a owserver but no sensor is displayed.
> We have following trace:
>
https://www.eservice-online.de//media/pdf/Bauanleitung_1-Wire-Hub-II-AC%20V1.0.pdf
page 3 says that "1-Wire hub III DC (eService)" is a passive star
coupler rather than a onewire "hub". That means the stubs shouldn't be
longer than a few metres to avoid electrical problems.
Which distribution do you use?
Please test with owserver and owget as you need to trigger at least one
bus action to get a useful log output:
# /opt/owfs/bin/owserver --debug -d /dev/ttyUSB1
Other terminal window
$ /opt/owfs/bin/owread /uncached
What does the owserver log say?
Kind regards
Jan
------------------------------------------------------------------------------
Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
Francisco, CA to explore cutting-edge tech and listen to tech luminaries
present their vision of the future. This family event has something for
everyone, including kids. Get more information and register today.
http://sdm.link/attshape
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape
_______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
