How to use eservice LCD

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

How to use eservice LCD

Dr. Trigon
Hello

I bought an eservice LCD [1] but it does not work. Can somebody give me some advice what to do?

[1] https://www.eservice-online.de/shop/e-service-1-wire-bus/display-lcd/
Dr. Trigon
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: How to use eservice LCD

Jan Kandziora
Am 20.06.2016 um 07:39 schrieb Dr. Trigon:
> Hello
>
> I bought an eservice LCD [1] but it does not work. Can somebody give me some advice what to do?
>
> [1] https://www.eservice-online.de/shop/e-service-1-wire-bus/display-lcd/
> Dr. Trigon
>
That display isn't supported by the current version of owfs as it has its
DS2408 <-> KS0073 connections different from both the Maxim/Dallas and
the Hobby-Boards design.

According to

https://www.eservice-online.de/media/pdf/Bedienungsanleitung%20LCD%20Display%20163.pdf

section 5.1 (page 3), that display has

D4 on P0
D5 on P1
D6 on P2
D7 on P3
RS on P4

About P5, P6, P7 it says it has a button input and two backlight control
outputs. The datasheet has it confused but according to the PHP examples,
the table in section 5.1 is correct. So

Button on P5
Backlight control on P6, P7 (off, 50%, 100%, blinking)



We could add support but I've got no time for it. Johan? Anyone else?

Kind regards

        Jan





------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: How to use eservice LCD

Johan Ström-3
On 20/06/16 16:12, Jan Kandziora wrote:

> Am 20.06.2016 um 07:39 schrieb Dr. Trigon:
>> Hello
>>
>> I bought an eservice LCD [1] but it does not work. Can somebody give me some advice what to do?
>>
>> [1] https://www.eservice-online.de/shop/e-service-1-wire-bus/display-lcd/
>> Dr. Trigon
>>
> According to
>
> https://www.eservice-online.de/media/pdf/Bedienungsanleitung%20LCD%20Display%20163.pdf
> ...
>
>
> We could add support but I've got no time for it. Johan? Anyone else?

Seems pretty straight forward. Unfortunately I'm pretty swamped at the
moment too. Especially to do testing etc without access to a device.

Dr Trigon, are you familiar with building software/owfs manually,
checking out code with git etc? If so, we might do a quick patch and
reverse the bits just to try and see if it works. If that works fine, we
could try to find some time to add it properly.

------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: How to use eservice LCD

Dr. Trigon
In reply to this post by Dr. Trigon


>Message: 5
>Date: Tue, 21 Jun 2016 08:04:02 +0200
>From: Johan Str?m <[hidden email]>
>Subject: Re: [Owfs-developers] How to use eservice LCD
>To: "OWFS (One-wire file system) discussion and help"
> <[hidden email]>
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=windows-1252; format=flowed
>
>On 20/06/16 16:12, Jan Kandziora wrote:
>
>> Am 20.06.2016 um 07:39 schrieb Dr. Trigon:
>>> Hello
>>>
>>> I bought an eservice LCD [1] but it does not work. Can somebody give
>me some advice what to do?
>>>
>>> [1]
>https://www.eservice-online.de/shop/e-service-1-wire-bus/display-lcd/
>>> Dr. Trigon
>>>
>> According to
>>
>>
>https://www.eservice-online.de/media/pdf/Bedienungsanleitung%20LCD%20Display%20163.pdf
>> ...
>>
>>
>> We could add support but I've got no time for it. Johan? Anyone else?
>
>Seems pretty straight forward. Unfortunately I'm pretty swamped at the
>moment too. Especially to do testing etc without access to a device.
>
>Dr Trigon, are you familiar with building software/owfs manually,
>checking out code with git etc? If so, we might do a quick patch and
>reverse the bits just to try and see if it works. If that works fine,

Yes, sure - sounds perfect! Happy to test it!

(I tried to implement it myself but I am not familiar with the owfs source - don't know where to start. ;)

>we
>could try to find some time to add it properly.


That would be great!

Thanks a lot!


>------------------------------
>
>------------------------------------------------------------------------------
>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
>
>------------------------------
Dr. Trigon

------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: How to use eservice LCD

Dr. Trigon
In reply to this post by Dr. Trigon


>Message: 5
>Date: Tue, 21 Jun 2016 08:04:02 +0200
>From: Johan Str?m <[hidden email]>
>Subject: Re: [Owfs-developers] How to use eservice LCD
>To: "OWFS (One-wire file system) discussion and help"
> <[hidden email]>
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=windows-1252; format=flowed
>
>On 20/06/16 16:12, Jan Kandziora wrote:
>
>> Am 20.06.2016 um 07:39 schrieb Dr. Trigon:
>>> Hello
>>>
>>> I bought an eservice LCD [1] but it does not work. Can somebody give
>me some advice what to do?
>>>
>>> [1]
>https://www.eservice-online.de/shop/e-service-1-wire-bus/display-lcd/
>>> Dr. Trigon
>>>
>> According to
>>
>>
>https://www.eservice-online.de/media/pdf/Bedienungsanleitung%20LCD%20Display%20163.pdf
>> ...
>>
>>
>> We could add support but I've got no time for it. Johan? Anyone else?
>
>Seems pretty straight forward. Unfortunately I'm pretty swamped at the
>moment too. Especially to do testing etc without access to a device.
>
>Dr Trigon, are you familiar with building software/owfs manually,
>checking out code with git etc? If so, we might do a quick patch and
>reverse the bits just to try and see if it works. If that works fine,
>we
>could try to find some time to add it properly.

Any news on this? Patch for testing ready? ;)
Dr. Trigon

------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: How to use eservice LCD

samuix
Hi,
with the help of digitemp_DS9097U we found following:
 
In the module ow_ds9097u.c is a parameter missing, we modified a line and it seems to work.....
 
we patched the module locally: ow_ds9097u.c    row:594   :
// default PDSRC = 1.37Vus
RETURN_BAD_IF_BAD(DS2480_configuration_write(PARMSEL_SLEW, PARMSET_Slew1p37Vus, in)) ;
 
The value (PDSRC=1.37V/µs) is mentioned in the specification : http://pdfserv.maximintegrated.com/en/an/AN192.pdf
 
after make the owserver found the sensors :-)
/opt/owfs/bin/owget /uncached
/uncached/20.0AF6B7180000
/uncached/28.BCBDAE070000
/uncached/28.EAF2BF040000
/uncached/26.4964FB010000
/uncached/bus.0
/uncached/settings
/uncached/system
/uncached/statistics
/uncached/structure
/uncached/simultaneous
/uncached/alarm
 
 /opt/owfs/bin/owserver -d /dev/ttyUSB0 --debug
DEBUG MODE
libow version:
        3.1p1
  DEBUG: ow_daemon.c:(170) main thread id = 3074172672
  DEBUG: ow_inotify.c:(80) No configuration files to monitor
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd library isn't found
   CALL: ow_parsename.c:(104) path=[]
  DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock adapters)
  DEBUG: ow_ds9097U.c:(471) Attempt 0 of 3 to initialize the DS9097U
  DEBUG: ow_ds9097U.c:(565) Send the initial reset to the bus master.
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_net_server.c:(76) ServerAddr: [0.0.0.0] [4304]
  DEBUG: ow_tcp_read.c:(63) attempt 24 bytes Time: 10.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 24 - 0 = 24
  DEBUG: from_client.c:(66) FromClient payload=10 size=0 type=7 sg=0x10A offset=0
  DEBUG: from_client.c:(74) FromClient (no servermessage) payload=10 size=0 type=7 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 0xb774cf20
  DEBUG: ow_regex.c:(74) Reg Ex expression <^settings/?> compiled to 0xb774cf00
  DEBUG: ow_regex.c:(74) Reg Ex expression <^statistics/?> compiled to 0xb774cee0
  DEBUG: ow_regex.c:(74) Reg Ex expression <^structure/?> compiled to 0xb774cec0
  DEBUG: ow_regex.c:(74) Reg Ex expression <^system/?> compiled to 0xb774cea0
  DEBUG: ow_regex.c:(74) Reg Ex expression <^interface/?> compiled to 0xb774ce80
  DEBUG: ow_regex.c:(74) Reg Ex expression <^text/?> compiled to 0xb774ce60
  DEBUG: ow_regex.c:(74) Reg Ex expression <^json/?> compiled to 0xb774ce40
  DEBUG: ow_regex.c:(74) Reg Ex expression <^uncached/?> compiled to 0xb774ce20
  DEBUG: ow_regex.c:(74) Reg Ex expression <^unaliased/?> compiled to 0xb774ce00
  DEBUG: ow_regex.c:(154) Not found
   CALL: data.c:(163) Directory message (all at once)
  DEBUG: dirall.c:(66) OWSERVER Dir-All SpecifiedBus=0 path = /uncached
  DEBUG: ow_dir.c:(80) path=/uncached
   CALL: ow_dir.c:(104) path=/uncached
  DEBUG: ow_search.c:(32) Start of directory path=/uncached device=00 00 00 00 00 00 00 00
  DEBUG: ow_select.c:(70) Selecting a path (and device) path=/uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00
  DEBUG: ow_select.c:(81) Clearing root branch
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 2 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 2 - 0 = 2
  DEBUG: ow_transaction.c:(113) send = 0
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_transaction.c:(131) readin = 0
  DEBUG: ow_transaction.c:(208) end = 0
  DEBUG: ow_select.c:(247) No DS2409 microlan hub found at this level
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 16 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 16 - 0 = 16
  DEBUG: ow_ds9097U.c:(921) SN found: 20 0A F6 B7 18 00 00 62
  DEBUG: ow_search.c:(74) Device found: 20 0A F6 B7 18 00 00 62
  DEBUG: ow_cache.c:(546) Adding device location 20 0A F6 B7 18 00 00 62 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 20 0A F6 B7 18 00 00 62 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(546) Adding device location 20 0A F6 B7 18 00 00 62 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 20 0A F6 B7 18 00 00 62 pointer=0xb774d148 index=0 size=4
   CALL: ow_parsename.c:(104) path=[/uncached/20.0AF6B7180000]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(74) Reg Ex expression <^alarm?> compiled to 0xb774cd00
  DEBUG: ow_regex.c:(74) Reg Ex expression <^simultaneous/?> compiled to 0xb774cdc0
  DEBUG: ow_regex.c:(74) Reg Ex expression <^thermostat/?> compiled to 0xb774cda0
  DEBUG: ow_regex.c:(74) Reg Ex expression <^text/?> compiled to 0xb774cd80
  DEBUG: ow_regex.c:(74) Reg Ex expression <^json/?> compiled to 0xb774cd60
  DEBUG: ow_regex.c:(74) Reg Ex expression <^uncached/?> compiled to 0xb774cd40
  DEBUG: ow_regex.c:(74) Reg Ex expression <^unaliased/?> compiled to 0xb774cd20
  DEBUG: ow_regex.c:(74) Reg Ex expression <^([[:xdigit:]]{2})\.?([[:xdigit:]]{12})\.?([[:xdigit:]]{2}){0,1}$> compiled to 0xb774cf40
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><20.0AF6B7180000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><20><.0AF6B7180000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <20.><0AF6B7180000><>
  DEBUG: ow_cache.c:(912) Looking for device 20 0A F6 B7 18 00 00 62
  DEBUG: ow_cache.c:(1070) Search in cache sn 20 0A F6 B7 18 00 00 62 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(1086) Value found in cache. Remaining life: 120 seconds.
  DEBUG: ow_presence.c:(75) Found device on bus 0
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><20.0AF6B7180000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><20><.0AF6B7180000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <20.><0AF6B7180000><>
  DEBUG: ow_parsename.c:(63) /uncached/20.0AF6B7180000
  DEBUG: ow_select.c:(70) Selecting a path (and device) path=/uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00
  DEBUG: ow_select.c:(84) Continuing root branch
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 16 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 16 - 0 = 16
  DEBUG: ow_ds9097U.c:(921) SN found: 28 BC BD AE 07 00 00 01
  DEBUG: ow_search.c:(74) Device found: 28 BC BD AE 07 00 00 01
  DEBUG: ow_cache.c:(546) Adding device location 28 BC BD AE 07 00 00 01 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 28 BC BD AE 07 00 00 01 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(546) Adding device location 28 BC BD AE 07 00 00 01 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 28 BC BD AE 07 00 00 01 pointer=0xb774d148 index=0 size=4
   CALL: ow_parsename.c:(104) path=[/uncached/28.BCBDAE070000]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><28.BCBDAE070000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><28><.BCBDAE070000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <28.><BCBDAE070000><>
  DEBUG: ow_cache.c:(912) Looking for device 28 BC BD AE 07 00 00 01
  DEBUG: ow_cache.c:(1070) Search in cache sn 28 BC BD AE 07 00 00 01 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(1086) Value found in cache. Remaining life: 120 seconds.
  DEBUG: ow_presence.c:(75) Found device on bus 0
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><28.BCBDAE070000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><28><.BCBDAE070000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <28.><BCBDAE070000><>
  DEBUG: ow_parsename.c:(63) /uncached/28.BCBDAE070000
  DEBUG: ow_select.c:(70) Selecting a path (and device) path=/uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00
  DEBUG: ow_select.c:(84) Continuing root branch
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 16 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 16 - 0 = 16
  DEBUG: ow_ds9097U.c:(921) SN found: 28 EA F2 BF 04 00 00 48
  DEBUG: ow_search.c:(74) Device found: 28 EA F2 BF 04 00 00 48
  DEBUG: ow_cache.c:(546) Adding device location 28 EA F2 BF 04 00 00 48 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 28 EA F2 BF 04 00 00 48 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(546) Adding device location 28 EA F2 BF 04 00 00 48 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 28 EA F2 BF 04 00 00 48 pointer=0xb774d148 index=0 size=4
   CALL: ow_parsename.c:(104) path=[/uncached/28.EAF2BF040000]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><28.EAF2BF040000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><28><.EAF2BF040000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <28.><EAF2BF040000><>
  DEBUG: ow_cache.c:(912) Looking for device 28 EA F2 BF 04 00 00 48
  DEBUG: ow_cache.c:(1070) Search in cache sn 28 EA F2 BF 04 00 00 48 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(1086) Value found in cache. Remaining life: 120 seconds.
  DEBUG: ow_presence.c:(75) Found device on bus 0
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><28.EAF2BF040000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><28><.EAF2BF040000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <28.><EAF2BF040000><>
  DEBUG: ow_parsename.c:(63) /uncached/28.EAF2BF040000
  DEBUG: ow_select.c:(70) Selecting a path (and device) path=/uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00
  DEBUG: ow_select.c:(84) Continuing root branch
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 16 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 16 - 0 = 16
  DEBUG: ow_ds9097U.c:(921) SN found: 26 49 64 FB 01 00 00 C2
  DEBUG: ow_search.c:(74) Device found: 26 49 64 FB 01 00 00 C2
  DEBUG: ow_cache.c:(546) Adding device location 26 49 64 FB 01 00 00 C2 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 26 49 64 FB 01 00 00 C2 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(546) Adding device location 26 49 64 FB 01 00 00 C2 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 26 49 64 FB 01 00 00 C2 pointer=0xb774d148 index=0 size=4
   CALL: ow_parsename.c:(104) path=[/uncached/26.4964FB010000]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><26.4964FB010000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><26><.4964FB010000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <26.><4964FB010000><>
  DEBUG: ow_cache.c:(912) Looking for device 26 49 64 FB 01 00 00 C2
  DEBUG: ow_cache.c:(1070) Search in cache sn 26 49 64 FB 01 00 00 C2 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(1086) Value found in cache. Remaining life: 120 seconds.
  DEBUG: ow_presence.c:(75) Found device on bus 0
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><26.4964FB010000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><26><.4964FB010000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <26.><4964FB010000><>
  DEBUG: ow_parsename.c:(63) /uncached/26.4964FB010000
  DEBUG: ow_cache.c:(478) Adding directory for 00 00 00 00 00 00 00 00 elements=4
  DEBUG: ow_cache.c:(635) Add to cache sn 00 00 00 00 00 00 00 00 pointer=0xb774d150 index=0 size=32
   CALL: ow_parsename.c:(104) path=[/uncached/bus.0]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->5 found <><bus.0><>
  DEBUG: ow_regex.c:(201) 1: 4->5 found <bus.><0><>
  DEBUG: ow_regex.c:(74) Reg Ex expression <^/bus\.[[:digit:]]+/?> compiled to 0xb774cde0
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_parsename.c:(63) /uncached/bus.0
   CALL: ow_parsename.c:(104) path=[/uncached/settings]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_parsename.c:(63) /uncached/settings
   CALL: ow_parsename.c:(104) path=[/uncached/system]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_parsename.c:(63) /uncached/system
   CALL: ow_parsename.c:(104) path=[/uncached/statistics]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_parsename.c:(63) /uncached/statistics
   CALL: ow_parsename.c:(104) path=[/uncached/structure]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_parsename.c:(63) /uncached/structure
   CALL: ow_parsename.c:(104) path=[/uncached/simultaneous]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_parsename.c:(63) /uncached/simultaneous
   CALL: ow_parsename.c:(104) path=[/uncached/alarm]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_parsename.c:(63) /uncached/alarm
  DEBUG: ow_dir.c:(199) ret=0
  DEBUG: ow_parsename.c:(63) /uncached
  DEBUG: data.c:(193) DataHandler: FS_ParsedName_destroy done
  DEBUG: data.c:(207) DataHandler: cm.ret=0
  DEBUG: to_client.c:(76) payload=236 size=235, ret=0, sg=0x10A offset=49158
  DEBUG: data.c:(226) Finished with client request
  DEBUG: handler.c:(135) OWSERVER handler done
  DEBUG: ow_net_server.c:(259) Normal completion.
 
 
 
 
Gesendet: Montag, 27. Juni 2016 um 18:06 Uhr
Von: "Dr. Trigon" <[hidden email]>
An: [hidden email]
Betreff: Re: [Owfs-developers] How to use eservice LCD


>Message: 5
>Date: Tue, 21 Jun 2016 08:04:02 +0200
>From: Johan Str?m <[hidden email]>
>Subject: Re: [Owfs-developers] How to use eservice LCD
>To: "OWFS (One-wire file system) discussion and help"
> <[hidden email]>
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=windows-1252; format=flowed
>
>On 20/06/16 16:12, Jan Kandziora wrote:
>
>> Am 20.06.2016 um 07:39 schrieb Dr. Trigon:
>>> Hello
>>>
>>> I bought an eservice LCD [1] but it does not work. Can somebody give
>me some advice what to do?
>>>
>>> [1]
>https://www.eservice-online.de/shop/e-service-1-wire-bus/display-lcd/
>>> Dr. Trigon
>>>
>> According to
>>
>>
>https://www.eservice-online.de/media/pdf/Bedienungsanleitung%20LCD%20Display%20163.pdf
>> ...
>>
>>
>> We could add support but I've got no time for it. Johan? Anyone else?
>
>Seems pretty straight forward. Unfortunately I'm pretty swamped at the
>moment too. Especially to do testing etc without access to a device.
>
>Dr Trigon, are you familiar with building software/owfs manually,
>checking out code with git etc? If so, we might do a quick patch and
>reverse the bits just to try and see if it works. If that works fine,
>we
>could try to find some time to add it properly.

Any news on this? Patch for testing ready? ;)
Dr. Trigon

------------------------------------------------------------------------------
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
[hidden email]
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: How to use eservice LCD

samuix
Sorry the response was regarding: "Communication to DS9097U not working"
mixed the emails up.... sorry
 
Gesendet: Montag, 27. Juni 2016 um 18:40 Uhr
Von: samuix <[hidden email]>
An: [hidden email]
Betreff: Re: [Owfs-developers] How to use eservice LCD
Hi,
with the help of digitemp_DS9097U we found following:
 
In the module ow_ds9097u.c is a parameter missing, we modified a line and it seems to work.....
 
we patched the module locally: ow_ds9097u.c    row:594   :
// default PDSRC = 1.37Vus
RETURN_BAD_IF_BAD(DS2480_configuration_write(PARMSEL_SLEW, PARMSET_Slew1p37Vus, in)) ;
 
The value (PDSRC=1.37V/µs) is mentioned in the specification : http://pdfserv.maximintegrated.com/en/an/AN192.pdf
 
after make the owserver found the sensors :-)
/opt/owfs/bin/owget /uncached
/uncached/20.0AF6B7180000
/uncached/28.BCBDAE070000
/uncached/28.EAF2BF040000
/uncached/26.4964FB010000
/uncached/bus.0
/uncached/settings
/uncached/system
/uncached/statistics
/uncached/structure
/uncached/simultaneous
/uncached/alarm
 
 /opt/owfs/bin/owserver -d /dev/ttyUSB0 --debug
DEBUG MODE
libow version:
        3.1p1
  DEBUG: ow_daemon.c:(170) main thread id = 3074172672
  DEBUG: ow_inotify.c:(80) No configuration files to monitor
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd library isn't found
   CALL: ow_parsename.c:(104) path=[]
  DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock adapters)
  DEBUG: ow_ds9097U.c:(471) Attempt 0 of 3 to initialize the DS9097U
  DEBUG: ow_ds9097U.c:(565) Send the initial reset to the bus master.
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_net_server.c:(76) ServerAddr: [0.0.0.0] [4304]
  DEBUG: ow_tcp_read.c:(63) attempt 24 bytes Time: 10.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 24 - 0 = 24
  DEBUG: from_client.c:(66) FromClient payload=10 size=0 type=7 sg=0x10A offset=0
  DEBUG: from_client.c:(74) FromClient (no servermessage) payload=10 size=0 type=7 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 0xb774cf20
  DEBUG: ow_regex.c:(74) Reg Ex expression <^settings/?> compiled to 0xb774cf00
  DEBUG: ow_regex.c:(74) Reg Ex expression <^statistics/?> compiled to 0xb774cee0
  DEBUG: ow_regex.c:(74) Reg Ex expression <^structure/?> compiled to 0xb774cec0
  DEBUG: ow_regex.c:(74) Reg Ex expression <^system/?> compiled to 0xb774cea0
  DEBUG: ow_regex.c:(74) Reg Ex expression <^interface/?> compiled to 0xb774ce80
  DEBUG: ow_regex.c:(74) Reg Ex expression <^text/?> compiled to 0xb774ce60
  DEBUG: ow_regex.c:(74) Reg Ex expression <^json/?> compiled to 0xb774ce40
  DEBUG: ow_regex.c:(74) Reg Ex expression <^uncached/?> compiled to 0xb774ce20
  DEBUG: ow_regex.c:(74) Reg Ex expression <^unaliased/?> compiled to 0xb774ce00
  DEBUG: ow_regex.c:(154) Not found
   CALL: data.c:(163) Directory message (all at once)
  DEBUG: dirall.c:(66) OWSERVER Dir-All SpecifiedBus=0 path = /uncached
  DEBUG: ow_dir.c:(80) path=/uncached
   CALL: ow_dir.c:(104) path=/uncached
  DEBUG: ow_search.c:(32) Start of directory path=/uncached device=00 00 00 00 00 00 00 00
  DEBUG: ow_select.c:(70) Selecting a path (and device) path=/uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00
  DEBUG: ow_select.c:(81) Clearing root branch
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 2 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 2 - 0 = 2
  DEBUG: ow_transaction.c:(113) send = 0
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_transaction.c:(131) readin = 0
  DEBUG: ow_transaction.c:(208) end = 0
  DEBUG: ow_select.c:(247) No DS2409 microlan hub found at this level
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 16 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 16 - 0 = 16
  DEBUG: ow_ds9097U.c:(921) SN found: 20 0A F6 B7 18 00 00 62
  DEBUG: ow_search.c:(74) Device found: 20 0A F6 B7 18 00 00 62
  DEBUG: ow_cache.c:(546) Adding device location 20 0A F6 B7 18 00 00 62 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 20 0A F6 B7 18 00 00 62 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(546) Adding device location 20 0A F6 B7 18 00 00 62 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 20 0A F6 B7 18 00 00 62 pointer=0xb774d148 index=0 size=4
   CALL: ow_parsename.c:(104) path=[/uncached/20.0AF6B7180000]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(74) Reg Ex expression <^alarm?> compiled to 0xb774cd00
  DEBUG: ow_regex.c:(74) Reg Ex expression <^simultaneous/?> compiled to 0xb774cdc0
  DEBUG: ow_regex.c:(74) Reg Ex expression <^thermostat/?> compiled to 0xb774cda0
  DEBUG: ow_regex.c:(74) Reg Ex expression <^text/?> compiled to 0xb774cd80
  DEBUG: ow_regex.c:(74) Reg Ex expression <^json/?> compiled to 0xb774cd60
  DEBUG: ow_regex.c:(74) Reg Ex expression <^uncached/?> compiled to 0xb774cd40
  DEBUG: ow_regex.c:(74) Reg Ex expression <^unaliased/?> compiled to 0xb774cd20
  DEBUG: ow_regex.c:(74) Reg Ex expression <^([[:xdigit:]]{2})\.?([[:xdigit:]]{12})\.?([[:xdigit:]]{2}){0,1}$> compiled to 0xb774cf40
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><20.0AF6B7180000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><20><.0AF6B7180000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <20.><0AF6B7180000><>
  DEBUG: ow_cache.c:(912) Looking for device 20 0A F6 B7 18 00 00 62
  DEBUG: ow_cache.c:(1070) Search in cache sn 20 0A F6 B7 18 00 00 62 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(1086) Value found in cache. Remaining life: 120 seconds.
  DEBUG: ow_presence.c:(75) Found device on bus 0
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><20.0AF6B7180000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><20><.0AF6B7180000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <20.><0AF6B7180000><>
  DEBUG: ow_parsename.c:(63) /uncached/20.0AF6B7180000
  DEBUG: ow_select.c:(70) Selecting a path (and device) path=/uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00
  DEBUG: ow_select.c:(84) Continuing root branch
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 16 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 16 - 0 = 16
  DEBUG: ow_ds9097U.c:(921) SN found: 28 BC BD AE 07 00 00 01
  DEBUG: ow_search.c:(74) Device found: 28 BC BD AE 07 00 00 01
  DEBUG: ow_cache.c:(546) Adding device location 28 BC BD AE 07 00 00 01 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 28 BC BD AE 07 00 00 01 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(546) Adding device location 28 BC BD AE 07 00 00 01 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 28 BC BD AE 07 00 00 01 pointer=0xb774d148 index=0 size=4
   CALL: ow_parsename.c:(104) path=[/uncached/28.BCBDAE070000]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><28.BCBDAE070000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><28><.BCBDAE070000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <28.><BCBDAE070000><>
  DEBUG: ow_cache.c:(912) Looking for device 28 BC BD AE 07 00 00 01
  DEBUG: ow_cache.c:(1070) Search in cache sn 28 BC BD AE 07 00 00 01 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(1086) Value found in cache. Remaining life: 120 seconds.
  DEBUG: ow_presence.c:(75) Found device on bus 0
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><28.BCBDAE070000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><28><.BCBDAE070000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <28.><BCBDAE070000><>
  DEBUG: ow_parsename.c:(63) /uncached/28.BCBDAE070000
  DEBUG: ow_select.c:(70) Selecting a path (and device) path=/uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00
  DEBUG: ow_select.c:(84) Continuing root branch
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 16 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 16 - 0 = 16
  DEBUG: ow_ds9097U.c:(921) SN found: 28 EA F2 BF 04 00 00 48
  DEBUG: ow_search.c:(74) Device found: 28 EA F2 BF 04 00 00 48
  DEBUG: ow_cache.c:(546) Adding device location 28 EA F2 BF 04 00 00 48 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 28 EA F2 BF 04 00 00 48 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(546) Adding device location 28 EA F2 BF 04 00 00 48 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 28 EA F2 BF 04 00 00 48 pointer=0xb774d148 index=0 size=4
   CALL: ow_parsename.c:(104) path=[/uncached/28.EAF2BF040000]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><28.EAF2BF040000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><28><.EAF2BF040000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <28.><EAF2BF040000><>
  DEBUG: ow_cache.c:(912) Looking for device 28 EA F2 BF 04 00 00 48
  DEBUG: ow_cache.c:(1070) Search in cache sn 28 EA F2 BF 04 00 00 48 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(1086) Value found in cache. Remaining life: 120 seconds.
  DEBUG: ow_presence.c:(75) Found device on bus 0
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><28.EAF2BF040000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><28><.EAF2BF040000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <28.><EAF2BF040000><>
  DEBUG: ow_parsename.c:(63) /uncached/28.EAF2BF040000
  DEBUG: ow_select.c:(70) Selecting a path (and device) path=/uncached SN=00 00 00 00 00 00 00 00 last path=00 00 00 00 00 00 00 00
  DEBUG: ow_select.c:(84) Continuing root branch
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
  DEBUG: ow_tcp_read.c:(63) attempt 16 bytes Time: 5.000000 seconds
  DEBUG: ow_tcp_read.c:(113) read: 16 - 0 = 16
  DEBUG: ow_ds9097U.c:(921) SN found: 26 49 64 FB 01 00 00 C2
  DEBUG: ow_search.c:(74) Device found: 26 49 64 FB 01 00 00 C2
  DEBUG: ow_cache.c:(546) Adding device location 26 49 64 FB 01 00 00 C2 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 26 49 64 FB 01 00 00 C2 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(546) Adding device location 26 49 64 FB 01 00 00 C2 bus=0
  DEBUG: ow_cache.c:(635) Add to cache sn 26 49 64 FB 01 00 00 C2 pointer=0xb774d148 index=0 size=4
   CALL: ow_parsename.c:(104) path=[/uncached/26.4964FB010000]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><26.4964FB010000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><26><.4964FB010000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <26.><4964FB010000><>
  DEBUG: ow_cache.c:(912) Looking for device 26 49 64 FB 01 00 00 C2
  DEBUG: ow_cache.c:(1070) Search in cache sn 26 49 64 FB 01 00 00 C2 pointer=0xb774d148 index=0 size=4
  DEBUG: ow_cache.c:(1086) Value found in cache. Remaining life: 120 seconds.
  DEBUG: ow_presence.c:(75) Found device on bus 0
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->15 found <><26.4964FB010000><>
  DEBUG: ow_regex.c:(201) 1: 0->2 found <><26><.4964FB010000>
  DEBUG: ow_regex.c:(201) 2: 3->15 found <26.><4964FB010000><>
  DEBUG: ow_parsename.c:(63) /uncached/26.4964FB010000
  DEBUG: ow_cache.c:(478) Adding directory for 00 00 00 00 00 00 00 00 elements=4
  DEBUG: ow_cache.c:(635) Add to cache sn 00 00 00 00 00 00 00 00 pointer=0xb774d150 index=0 size=32
   CALL: ow_parsename.c:(104) path=[/uncached/bus.0]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(201) 0: 0->5 found <><bus.0><>
  DEBUG: ow_regex.c:(201) 1: 4->5 found <bus.><0><>
  DEBUG: ow_regex.c:(74) Reg Ex expression <^/bus\.[[:digit:]]+/?> compiled to 0xb774cde0
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_parsename.c:(63) /uncached/bus.0
   CALL: ow_parsename.c:(104) path=[/uncached/settings]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_parsename.c:(63) /uncached/settings
   CALL: ow_parsename.c:(104) path=[/uncached/system]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_parsename.c:(63) /uncached/system
   CALL: ow_parsename.c:(104) path=[/uncached/statistics]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_parsename.c:(63) /uncached/statistics
   CALL: ow_parsename.c:(104) path=[/uncached/structure]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_parsename.c:(63) /uncached/structure
   CALL: ow_parsename.c:(104) path=[/uncached/simultaneous]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_parsename.c:(63) /uncached/simultaneous
   CALL: ow_parsename.c:(104) path=[/uncached/alarm]
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_regex.c:(154) Not found
  DEBUG: ow_parsename.c:(63) /uncached/alarm
  DEBUG: ow_dir.c:(199) ret=0
  DEBUG: ow_parsename.c:(63) /uncached
  DEBUG: data.c:(193) DataHandler: FS_ParsedName_destroy done
  DEBUG: data.c:(207) DataHandler: cm.ret=0
  DEBUG: to_client.c:(76) payload=236 size=235, ret=0, sg=0x10A offset=49158
  DEBUG: data.c:(226) Finished with client request
  DEBUG: handler.c:(135) OWSERVER handler done
  DEBUG: ow_net_server.c:(259) Normal completion.
 
 
 
 
Gesendet: Montag, 27. Juni 2016 um 18:06 Uhr
Von: "Dr. Trigon" <[hidden email]>
An: [hidden email]
Betreff: Re: [Owfs-developers] How to use eservice LCD


>Message: 5
>Date: Tue, 21 Jun 2016 08:04:02 +0200
>From: Johan Str?m <[hidden email]>
>Subject: Re: [Owfs-developers] How to use eservice LCD
>To: "OWFS (One-wire file system) discussion and help"
> <[hidden email]>
>Message-ID: <[hidden email]>
>Content-Type: text/plain; charset=windows-1252; format=flowed
>
>On 20/06/16 16:12, Jan Kandziora wrote:
>
>> Am 20.06.2016 um 07:39 schrieb Dr. Trigon:
>>> Hello
>>>
>>> I bought an eservice LCD [1] but it does not work. Can somebody give
>me some advice what to do?
>>>
>>> [1]
>https://www.eservice-online.de/shop/e-service-1-wire-bus/display-lcd/
>>> Dr. Trigon
>>>
>> According to
>>
>>
>https://www.eservice-online.de/media/pdf/Bedienungsanleitung%20LCD%20Display%20163.pdf
>> ...
>>
>>
>> We could add support but I've got no time for it. Johan? Anyone else?
>
>Seems pretty straight forward. Unfortunately I'm pretty swamped at the
>moment too. Especially to do testing etc without access to a device.
>
>Dr Trigon, are you familiar with building software/owfs manually,
>checking out code with git etc? If so, we might do a quick patch and
>reverse the bits just to try and see if it works. If that works fine,
>we
>could try to find some time to add it properly.

Any news on this? Patch for testing ready? ;)
Dr. Trigon

------------------------------------------------------------------------------
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
[hidden email]
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 [hidden email] 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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: How to use eservice LCD

Jan Kandziora
In reply to this post by Johan Ström-3
Am 21.06.2016 um 08:04 schrieb Johan Ström:

> On 20/06/16 16:12, Jan Kandziora wrote:
>
>> Am 20.06.2016 um 07:39 schrieb Dr. Trigon:
>>> Hello
>>>
>>> I bought an eservice LCD [1] but it does not work. Can somebody give me some advice what to do?
>>>
>>> [1] https://www.eservice-online.de/shop/e-service-1-wire-bus/display-lcd/
>>> Dr. Trigon
>>>
>> According to
>>
>> https://www.eservice-online.de/media/pdf/Bedienungsanleitung%20LCD%20Display%20163.pdf
>> ...
>>
>>
>> We could add support but I've got no time for it. Johan? Anyone else?
>
> Seems pretty straight forward. Unfortunately I'm pretty swamped at the
> moment too. Especially to do testing etc without access to a device.
>
Johan, lean back if you are still swamped. I prepared a test board and
work on a patch.

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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: How to use eservice LCD

Jan Kandziora
In reply to this post by Dr. Trigon
Am 27.06.2016 um 18:06 schrieb Dr. Trigon:
>
> Any news on this? Patch for testing ready? ;)
>
A quick&dirty patch is appended. I have tested it myself with a DS2408
plus HD44780 LCD connected as described in the eservice documentation.

Don't forget to install automake and pkgconfig. Use the current git
archive clone as your base.

$ git clone git://git.code.sf.net/p/owfs/code owfs-code
$ cd owfs-code
$ ./bootstrap
$ ./configure

$ patch -p1 <../eservice_lcd.diff

$ make ; sudo make install


Test with:

# /opt/owfs/bin/owserver --debug -u

and in another terminal window:

$ /opt/owfs/bin/owwrite /<your DS2408 address>/strobe 1
$ /opt/owfs/bin/owwrite /<your DS2408 address>/LCD_H/clear 1
$ /opt/owfs/bin/owwrite /<your DS2408 address>/LCD_H/message "Foobar"

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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

eservice_lcd.diff (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: How to use eservice LCD

Dr. Trigon
In reply to this post by Dr. Trigon
>>> Any news on this? Patch for testing ready? ;)
>>>
>>A quick&dirty patch is appended. I have tested it myself with a DS2408
>>plus HD44780 LCD connected as described in the eservice documentation.
>>
>>Don't forget to install automake and pkgconfig. Use the current git
>>archive clone as your base.
>>
>>$ git clone git://git.code.sf.net/p/owfs/code owfs-code
>>$ cd owfs-code
>>$ ./bootstrap
>>$ ./configure
>>
>>$ patch -p1 <../eservice_lcd.diff
>>
>>$ make ; sudo make install
>>
>>
>>Test with:
>>
>># /opt/owfs/bin/owserver --debug -u
>>
>>and in another terminal window:
>>
>>$ /opt/owfs/bin/owwrite /<your DS2408 address>/strobe 1
>>$ /opt/owfs/bin/owwrite /<your DS2408 address>/LCD_H/clear 1
>>$ /opt/owfs/bin/owwrite /<your DS2408 address>/LCD_H/message "Foobar"

Hello Jan

So here is what I did:

$ git clone git://git.code.sf.net/p/owfs/code owfs-code
$ cd owfs-code/
~/owfs-code$ ./bootstrap
~/owfs-code$ ./configure
(get patch from https://sourceforge.net/p/owfs/mailman/owfs-developers/?viewmonth=201606&viewday=28)
~/owfs-code$ patch -p1 < eservice_lcd.diff
~/owfs-code$ make
~/owfs-code$ nano owfs.conf
(copy content from my wiki)
~/owfs-code$ module/owserver/src/c/owserver -c ~/owfs-code/owfs.conf --debug -u
(in another window)
~/owfs-code$ module/owhttpd/src/c/owhttpd -c ~/owfs-code/owfs.conf
(check localhost:2121 to find device -> 29.2F7214000000)
~/owfs-code$ module/owshell/src/c/owwrite /29.2F7214000000/strobe 1
~/owfs-code$ module/owshell/src/c/owwrite /29.2F7214000000/LCD_H/clear 1
~/owfs-code$ module/owshell/src/c/owwrite /29.2F7214000000/LCD_H/message "Foobar"
(copy output of 1st/debug window for maillist then quit app)
~/owfs-code$ sudo killall lt-owfs lt-owhttpd lt-owserver

When I connect the device the background led switches on shortly and the off. The colored led is off too.
After the clear command the background led switches on and stays on, the colored led switches on too (in red state I think - not sure anymore).
No text appears after the message command...
Any idea what's the issue? I'll send the server output as text file attachement in another mail - otherwise the list does not let it through.

Dr. Trigon
------------------------------------------------------------------------------
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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: How to use eservice LCD

Dr. Trigon
In reply to this post by Dr. Trigon

Dr. Trigon
------------------------------------------------------------------------------

_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

owfs-debug-log (57K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: How to use eservice LCD

Jan Kandziora
In reply to this post by Dr. Trigon
Am 02.07.2016 um 15:08 schrieb Dr. Trigon:

>
> $ git clone git://git.code.sf.net/p/owfs/code owfs-code
> $ cd owfs-code/
> ~/owfs-code$ ./bootstrap
> ~/owfs-code$ ./configure
> (get patch from https://sourceforge.net/p/owfs/mailman/owfs-developers/?viewmonth=201606&viewday=28)
> ~/owfs-code$ patch -p1 < eservice_lcd.diff
> ~/owfs-code$ make
> ~/owfs-code$ nano owfs.conf
> (copy content from my wiki)
> ~/owfs-code$ module/owserver/src/c/owserver -c ~/owfs-code/owfs.conf --debug -u
>
Uhhh, no. -c ~/owfs-code/owfs.conf and -u may be mutually exclusive.
You haven't listed what is inside ~/owfs-code/owfs.conf.

Does your user have sufficient rights to access the host adaptor?
Because you don't start owserver as root.


> (in another window)
> ~/owfs-code$ module/owhttpd/src/c/owhttpd -c ~/owfs-code/owfs.conf
> (check localhost:2121 to find device -> 29.2F7214000000)
>
Same here with the config. You don't need this program for testing. If
you want to check for the device id, use

$ module/owshell/src/c/owdir /uncached


> ~/owfs-code$ module/owshell/src/c/owwrite /29.2F7214000000/strobe 1
> ~/owfs-code$ module/owshell/src/c/owwrite /29.2F7214000000/LCD_H/clear 1
> ~/owfs-code$ module/owshell/src/c/owwrite /29.2F7214000000/LCD_H/message "Foobar"
> (copy output of 1st/debug window for maillist then quit app)
>
I'd like to see that log.


> ~/owfs-code$ sudo killall lt-owfs lt-owhttpd lt-owserver
>
You should have killed all these programs *before* starting anything
new. When you use the --debug switch on owserver it stays in the
foreground and you can terminate it with Ctrl-C. The owshell programs
aren't daemons at all.

Please try again, cleanly.

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
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers