owfs-developers — Developer's list for OWFS

[Owfs-developers] [SPAM] Re: Local and remote from C

[Jan K. <jj...@gm...>]

Am 05.04.25 um 15:12 schrieb Michael Hughes via Owfs-developers:
> Is there a way using the C library to open both a connection to a local
> RS-232 1-Wire interface and a TCP connection(s)?
>
Do you mean owcapi? Yes.

Use both the -d and the -s option in the string that you pass to
OW_init() or OW_init_args().

Kind regards

	Jan

[Owfs-developers] Local and remote from C

[Michael H. <ow...@th...>]

Is there a way using the C library to open both a connection to a local
RS-232 1-Wire interface and a TCP connection(s)?

-- 
Michael

[Owfs-developers] Where are we on releases?

[Gregg L. <gre...@gm...>]

Hello!
We've been very quiet lately. So I am wondering of course on releases?
Such as this one: Do we have any new ones scheduled?
-----
Gregg C Levine gre...@gm...
"This signature was still fighting the timewars, Time and again."

Re: [Owfs-developers] Anyone up for porting to TCL9?

[Tomasz T. <to...@pi...>]

On Mon, Mar 03, 2025 at 03:13:18PM +0100, Jan Kandziora wrote:
> Am 27.02.25 um 08:48 schrieb Tomasz Torcz:
> > Hi,
> > 
> >    Tcl recently released version 9. Code needs some porting.
> > Tcl parts of owfs work with Tcl 8.6, but failed when Fedora moved to
> > tcl9.
> > 
> >    Is anyone able to do the porting?  I do not know this part of owfs at
> > all. Fedora package can use tcl8 compatibility packages for few years,
> > but it would be safer to get just get tcl9 compatibility.
> > 
> Tomasz,
> 
> 
> I have an interest in having that ported and I’m likely able to but I
> don’t know when I can setup a Tcl-9 development environment. As OpenSUSE
> Tumbleweed is still at Tcl-8.6 only and I would like to avoid extra
> hoops as setting up Fedora inside a container.


 Hey Jan,

  Don't worry, it's not urgent. Fedora packages are currently broken,
due to errors in tcl8-compat packages (https://bugzilla.redhat.com/show_bug.cgi?id=2346957).
In worst case, I'll disable tcl parts of owfs temporarily.

  Nevertheless, looking forward for Tcl9 to be included in Tumbleweed :)

-- 
Tomasz Torcz               There exists no separation between gods and men:
to...@pi...       one blends softly casual into the other.  — Frank Herbert

Re: [Owfs-developers] Anyone up for porting to TCL9?

[Tomasz T. <to...@pi...>]

On Thu, Feb 27, 2025 at 08:48:25AM +0100, Tomasz Torcz wrote:
>   The porting guide is linked from 

  Sorry, wrong link. Correct is https://www.tcl-lang.org/software/tcltk/9.0.html

-- 
Tomasz Torcz               RIP is irrevelant. Spoofing is futile.
to...@pi...     Your routes will be aggreggated. – Alex Yuriev

[Owfs-developers] Anyone up for porting to TCL9?

[Tomasz T. <to...@pi...>]

Hi,

  Tcl recently released version 9. Code needs some porting.
Tcl parts of owfs work with Tcl 8.6, but failed when Fedora moved to
tcl9.

  Is anyone able to do the porting?  I do not know this part of owfs at
all. Fedora package can use tcl8 compatibility packages for few years,
but it would be safer to get just get tcl9 compatibility.

  The porting guide is linked from owfs-developers owfs <owf...@li...>

-- 
Tomasz Torcz               RIP is irrevelant. Spoofing is futile.
to...@pi...     Your routes will be aggreggated. – Alex Yuriev

Re: [Owfs-developers] Adafruit has introduced an I2C to One-Wire module

[Gregg L. <gre...@gm...>]

Hello!
A hasty P.S, to my earlier posting, This is a DS2484, not one of the
other two that I was originally looking at, and indeed mentioned on
the original Dot Org pages that we are busily migrating. The next
question is one of, has anyone tried that chip out using existing
software? Debian has the 3.2p4 and the 3.2p3 releases. And of course
the Source Forge pages are lagging.
-----
Gregg C Levine gre...@gm...
"This signature fought the Time Wars, time and again."

On Fri, Jul 5, 2024 at 5:35 PM Gregg Levine <gre...@gm...> wrote:
>
> Hello!
> Adafruit has gone and done something amazing, they've introduced a
> module that connects the One-Wire bus to the I2C bus. Here,
> https://tinyurl.com/ada5976 .
>
> So far the learn pages do not show anything regarding our efforts.
> -----
> Gregg C Levine gre...@gm...
> "This signature fought the Time Wars, time and again."

Re: [Owfs-developers] Adafruit has introduced an I2C to One-Wire module

[Paul E. <re...@re...>]

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">I’ve been selling something that does exactly the same thing in the UK since 2010 :)<div><br></div><div>This is the current version:<br><div><br></div><div><div style="display: block;" class=""><a href="https://www.sheepwalkelectronics.co.uk/product_info.php?products_id=73&amp;osCsid=cgmk6frce5p0v2vtcrqv90kj27">https://www.sheepwalkelectronics.co.uk/product_info.php?products_id=73</a><br></div></div><div><br id="lineBreakAtBeginningOfSignature"><div dir="ltr">Paul Everett</div><div dir="ltr"><br><blockquote type="cite">On 5 Jul 2024, at 22:36, Gregg Levine &lt;gre...@gm...&gt; wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><span>Hello!</span><br><span>Adafruit has gone and done something amazing, they've introduced a</span><br><span>module that connects the One-Wire bus to the I2C bus. Here,</span><br><span>https://tinyurl.com/ada5976 .</span><br><span></span><br><span>So far the learn pages do not show anything regarding our efforts.</span><br><span>-----</span><br><span>Gregg C Levine gre...@gm...</span><br><span>"This signature fought the Time Wars, time and again."</span><br><span></span><br><span></span><br><span>_______________________________________________</span><br><span>Owfs-developers mailing list</span><br><span>Owf...@li...</span><br><span>https://lists.sourceforge.net/lists/listinfo/owfs-developers</span><br></div></blockquote></div></div></body></html>

[Owfs-developers] Adafruit has introduced an I2C to One-Wire module

[Gregg L. <gre...@gm...>]

Hello!
Adafruit has gone and done something amazing, they've introduced a
module that connects the One-Wire bus to the I2C bus. Here,
https://tinyurl.com/ada5976 .

So far the learn pages do not show anything regarding our efforts.
-----
Gregg C Levine gre...@gm...
"This signature fought the Time Wars, time and again."

[Owfs-developers] Owhttpd works on a PiZero2W

[Gregg L. <gre...@gm...>]

Hello!
I just assembled a second DS2436 pod and connected the battery pack
that the PiZero2W uses for power via Powerboost 1000C from Adafruit
for power, and the program told what the battery voltage was, and the
room temp as well.

I also for this second one included a Time-In-A-Can device, in this
case it holds a DS2415 one, it confirms the time of day as well.

Some of you are wondering why I am doing this, there are two parts of
obvious to this, the merely obvious is that I needed to confirm for
myself that it works, and the incredibly obvious was one of, I can't
recall if anyone had gotten these two or just the DS2436 part to work
with these programs and on this platform.
-----
Gregg C Levine gre...@gm...
"This signature fought the Time Wars, time and again."

[Owfs-developers] Owhttpd works on a Raspberry Pi Zero

[Gregg L. <gre...@gm...>]

Hello!
This list is too quiet so I thought I'd post my latest and greatest
project. That of installing the owfs programs on a Raspberry Pi Zero.

Currently I have a traditional serial adapter plugged into an FTDI
based serial adapter with the DE9 connector. Basically the program is
reporting the power running to a boost device from Adafruit at 3.68
(It shows 4.7 unloaded.) and the room temperature at 24C on a DS2436.
-----
Gregg C Levine gre...@gm...
"This signature fought the Time Wars, time and again."

Re: [Owfs-developers] Raspberry Pi busmaster GPIO connector

[Jan K. <jj...@gm...>]

Am 02.04.24 um 06:16 schrieb Gregg Levine:
> Hello! I've a new project taking shape at the moment. And it involves
> making use of OWFS on the Raspberry Pi, a Pi Zero Wifi WH device in
> fact. And I recalled that when I enabled the GPIO settings such as
> the Serial port there, and typically the I2C settings, I would see
> but not enable the one for One-Wire. Now the question is one of which
> GPIO one that the system selected. The website makes a reference to
> someone's work, but does not provide references.
>
The bitbanging onewire host works with GPIO4 (pin 7 on the 40-pin
connector) by default on the Raspberry Pi. Use

	dtoverlay=w1-gpio

in /boot/config.txt. You can also select a different GPIO with

	dtoverlay=w1-gpio,gpiopin=4

with 4 being the GPIO you want. (Note those are called "gpiopin" but
it's not the pin numbers on the 40-pin connector but the GPIO numbers.)

The additional option pullup=1 may be used to enable the high-side
transistor of the GPIO for a strong pullup during some operations.

Note that the Raspberry Pi is a 3.3V device, so that Onewire is going to
be a 3.3V Onewire. You have to wire a 1.5kΩ resistor to +3.3V to make it
work correctly. If you need a 5V Onewire instead, use a level shifter as
this one:

|
|        +5V ----.           ,-----+---- +3.3V
|                |           |     |
|                \         G |     \
|                /      –––––'     /
|                \    ––– – –––    \
|                |     |  ^  |     |
| 5V bus line ---+-----'  '--+-----+---- 3.3V bus line
|                      D     S
|


The transistor is a small signal N-channel enhancement mode MOSFET, e.g.
a 2N7000, BS170 or MMBF170. The +5V pullup must be around 2.7kΩ.

Kind regards

	Jan

Re: [Owfs-developers] Raspberry Pi busmaster GPIO connector

[Gregg L. <gre...@gm...>]

Hello!
I returned this to the list, because I wanted everyone else to
comment. Right now I'm busily creating my ideas. Your gadget, which I
see is for sale from a good company, is a good idea, but I'm looking
at this from the perspective of how Adafruit suggested it originally.
Also I've enabled composite video output on the one I'm using today,
and was using earlier to perfect the ideas behind composite video out
from these devices. Now that's something worth writing about,
elsewhere.

Consider this, the original company developed a part for "smart
battery packs", that's the direction I'm going in for this job.
-----
Gregg C Levine gre...@gm...
"This signature fought the Time Wars, time and again."

On Tue, Apr 2, 2024 at 8:14 AM Nico Bouthoorn <ni...@cu...> wrote:
>
> Hi,
>
> Do you have something like this? https://fstab.nl/Raspberry-Pi-zero
>
> my docs, this is working at my place.
>
> Succes,
>
> Nico
>
>
> On 4/2/24 06:16, Gregg Levine wrote:
> > Hello!
> > I've a new project taking shape at the moment. And it involves making
> > use of OWFS on the Raspberry Pi, a Pi Zero Wifi WH device in fact. And
> > I recalled that when I enabled the GPIO settings such as the Serial
> > port there, and typically the I2C settings, I would see but not enable
> > the one for One-Wire. Now the question is one of which GPIO one that
> > the system selected. The website makes a reference to someone's work,
> > but does not provide references.
> > -----
> > Gregg C Levine gre...@gm...
> > "This signature fought the Time Wars, time and again."
> >
> >
> > _______________________________________________
> > Owfs-developers mailing list
> > Owf...@li...
> > https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
> --
> 0623391101
>

[Owfs-developers] Raspberry Pi busmaster GPIO connector

[Gregg L. <gre...@gm...>]

Hello!
I've a new project taking shape at the moment. And it involves making
use of OWFS on the Raspberry Pi, a Pi Zero Wifi WH device in fact. And
I recalled that when I enabled the GPIO settings such as the Serial
port there, and typically the I2C settings, I would see but not enable
the one for One-Wire. Now the question is one of which GPIO one that
the system selected. The website makes a reference to someone's work,
but does not provide references.
-----
Gregg C Levine gre...@gm...
"This signature fought the Time Wars, time and again."

[Owfs-developers] Connection to more then one server

[Michael H. <ow...@th...>]

From the C API, can you connect to more than one owserver?

-- 
Michael

[Owfs-developers] Surplus Devices

[Mick S. <mi...@su...>]

Hi People,

I have some bits that are of no further use to me and wonder if they may 
be of use to anyone else.

Qty 1 Embedded Data Systems HA7E serial to 1-wire adapter

Qty 2 DS9097U Dallas Maxim Universal 1-Wire COM Port Adapter

Qty 3 Hobby-boards 8 channel I/O Board

All believed to be in working order.  I am in the UK.  Anyone interested?

Cheers

Mick

Re: [Owfs-developers] How to find 1-wire device names?

[Chris G. <cl...@is...>]

On Sun, May 08, 2022 at 01:50:01PM +0100, Mick Sulley wrote:
> If you have ow-shell installed then owdir should show all the devices on the
> network
> 
Well I didn't have ow-shell installed but I have now, just what I
needed, thank you!

-- 
Chris Green

Re: [Owfs-developers] How to find 1-wire device names?

[Mick S. <mi...@su...>]

If you have ow-shell installed then owdir should show all the devices on 
the network

Mick

On 08/05/2022 13:11, Chris Green wrote:
> I seem to have lost a couple of 1-wire devices, they were working a
> while ago but now don't seem to be appearing.  I've tried re-running
> owfs but that has done no good.
>
> Is there some sort of debugging mode available and/or a way to list
> devices on the 1-wire bus?
>

[Owfs-developers] How to find 1-wire device names?

[Chris G. <cl...@is...>]

I seem to have lost a couple of 1-wire devices, they were working a
while ago but now don't seem to be appearing.  I've tried re-running
owfs but that has done no good.

Is there some sort of debugging mode available and/or a way to list
devices on the 1-wire bus?

-- 
Chris Green

Re: [Owfs-developers] owfs and BitBang

[Gregg L. <gre...@gm...>]

Hello!
How'd you wire yours? He's got a strange view of that device. Well
mostly as the ones I would use are all parasitic powered, which was of
course not driven by a VCC3 line someplace. And the line he chose
could be used for One-Wire communications via OWFS, as it's
documented, someplace.
-----
Gregg C Levine gre...@gm...
"This signature fought the Time Wars, time and again."

On Tue, Mar 29, 2022 at 6:38 PM Mick Sulley <mi...@su...> wrote:
>
> I have just set up a Pi zero with a temp sensor following this -
>
> https://www.circuitbasics.com/raspberry-pi-ds18b20-temperature-sensor-tutorial/
>
> It works OK but I am wondering if I can use the owfs modules with this?
> If so what do I set as the server in /etc/owfs.conf
>
> I don't see anything in the docs
>
> Thanks
>
> Mick
>
>
>
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

[Owfs-developers] owfs and BitBang

[Mick S. <mi...@su...>]

I have just set up a Pi zero with a temp sensor following this -

https://www.circuitbasics.com/raspberry-pi-ds18b20-temperature-sensor-tutorial/

It works OK but I am wondering if I can use the owfs modules with this?  
If so what do I set as the server in /etc/owfs.conf

I don't see anything in the docs

Thanks

Mick

Re: [Owfs-developers] owserver issue with kernel 5.10

[Rainer D. <ml...@bo...>]

Hi,

unfortunately, I cannot repro the issue right now. Not sure what happened. I 
will follow-up if it comes back...

Rainer

Am Mittwoch, 29. Dezember 2021, 18:21:38 CET schrieb Rainer Dorsch via Owfs-
developers:
> Hi,
> 
> I have an elabnet professional bus master (PBM) on Debian server (armhf,
> cubox-i). After upgrading from Debian 10 to Debian 11 owserver does not work
> anymore. If I boot the Debian 11 system with the older kernel 4.19.0 from
> Debian 10, owserver works again.
> 
> Is there any kernel dependency which I need to take care of when switching
> from Kernel 4.19 to 5.10?
> 
> Here are some logs:
> 
> Kernel 5.10.0:
> ==============
> rd@home:~$ owget /
> /bus.1
> /uncached
> /settings
> /system
> /statistics
> /structure
> rd@home:~$
> 
> rd@home:~$ systemctl status owserver
> ● owserver.service - Backend server for 1-wire control
>      Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor
> preset: enabled)
>      Active: active (running) since Wed 2021-12-29 16:09:20 CET; 1h 21min
> ago TriggeredBy: ● owserver.socket
>        Docs: man:owserver(1)
>    Main PID: 419 (owserver)
>       Tasks: 4 (limit: 4729)
>      Memory: 1.4M
>         CPU: 3min 42.672s
>      CGroup: /system.slice/owserver.service
>              └─419 /usr/bin/owserver --foreground -c /etc/owfs.conf
> 
> Dec 29 16:08:58 home systemd[1]: Starting Backend server for 1-wire
> control... Dec 29 16:08:58 home owserver[419]: DEFAULT: ow_opt.c:(780)
> systemd mode -- ignore foreground request
> Dec 29 16:08:58 home owserver[419]: DEFAULT: ow_opt.c:(670) systemd mode --
> ignore 'p' option
> Dec 29 16:09:04 home owserver[419]: DEFAULT: ow_elabnet.c:(145) PBM
> detection error
> Dec 29 16:09:14 home owserver[419]: DEFAULT: ow_elabnet.c:(145) PBM
> detection error
> Dec 29 16:09:20 home owserver[419]: DEFAULT: ow_elabnet.c:(145) PBM
> detection error
> Dec 29 16:09:20 home owserver[419]: DEFAULT: owlib.c:(208) Cannot open USB
> bus master
> Dec 29 16:09:20 home systemd[1]: Started Backend server for 1-wire control.
> rd@home:~$
> 
> Restart owserver:
> 
> Dec 29 17:31:35 home systemd[1]: Stopping Backend server for 1-wire
> control... Dec 29 17:31:35 home systemd[1]: owserver.service: Succeeded.
> Dec 29 17:31:35 home systemd[1]: Stopped Backend server for 1-wire control.
> Dec 29 17:31:35 home systemd[1]: owserver.service: Consumed 3min 43.935s CPU
> time.
> Dec 29 17:31:35 home systemd[1]: Starting Backend server for 1-wire
> control... Dec 29 17:31:35 home owserver[20717]: DEFAULT: ow_opt.c:(780)
> systemd mode -- ignore foreground request
> Dec 29 17:31:35 home owserver[20717]: DEFAULT: ow_opt.c:(670) systemd mode
> -- ignore 'p' option
> Dec 29 17:31:40 home owserver[20717]: DEFAULT: ow_elabnet.c:(145) PBM
> detection error
> Dec 29 17:31:41 home owserver[20717]: DEFAULT: owlib.c:(208) Cannot open USB
> bus master
> Dec 29 17:31:41 home systemd[1]: Started Backend server for 1-wire control.
> 
> Kernel 4.19-0:
> ==============
> 
> rd@home:~$ owget /
> /2D.8967C0120000
> /2D.F075C0120000
> /2D.FD6AC0120000
> /3A.C31626000000
> /3A.EDE537000000
> /3A.791426000000
> /3A.E98A25000000
> /3A.D11626000000
> /3A.51991C000000
> /3A.C16238000000
> /3A.017325000000
> /3A.1E2B26000000
> /3A.821626000000
> /3A.2CE537000000
> /3A.541826000000
> /3A.84DA37000000
> /3A.202A26000000
> /28.FF2741801604
> /28.FFF144801604
> /28.FFA666801603
> /28.FFA620841603
> /28.FFB843801604
> /bus.4
> /bus.3
> /bus.2
> /bus.1
> /uncached
> /settings
> /system
> /statistics
> /structure
> /simultaneous
> /alarm
> rd@home:~$
> 
> rd@home:~$ systemctl status owserver
> ● owserver.service - Backend server for 1-wire control
>      Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor
> preset: enabled)
>      Active: active (running) since Wed 2021-12-29 17:46:54 CET; 6min ago
> TriggeredBy: ● owserver.socket
>        Docs: man:owserver(1)
>    Main PID: 360 (owserver)
>       Tasks: 8 (limit: 4739)
>      Memory: 2.3M
>         CPU: 8.231s
>      CGroup: /system.slice/owserver.service
>              └─360 /usr/bin/owserver --foreground -c /etc/owfs.conf
> 
> Dec 29 17:46:49 home systemd[1]: Starting Backend server for 1-wire
> control... Dec 29 17:46:49 home owserver[360]: DEFAULT: ow_opt.c:(780)
> systemd mode -- ignore foreground request
> Dec 29 17:46:49 home owserver[360]: DEFAULT: ow_opt.c:(670) systemd mode --
> ignore 'p' option
> Dec 29 17:46:54 home owserver[360]: DEFAULT: ow_elabnet.c:(145) PBM
> detection error
> Dec 29 17:46:54 home owserver[360]: DEFAULT: owlib.c:(208) Cannot open USB
> bus master
> Dec 29 17:46:54 home systemd[1]: Started Backend server for 1-wire control.
> rd@home:~$
> 
> 
> Are three any additional useful logs?
> 
> Thanks
> Rainer


-- 
Rainer Dorsch
http://bokomoko.de/

[Owfs-developers] owserver issue with kernel 5.10

[Rainer D. <ml...@bo...>]

Hi,

I have an elabnet professional bus master (PBM) on Debian server (armhf, 
cubox-i). After upgrading from Debian 10 to Debian 11 owserver does not work 
anymore. If I boot the Debian 11 system with the older kernel 4.19.0 from 
Debian 10, owserver works again.

Is there any kernel dependency which I need to take care of when switching 
from Kernel 4.19 to 5.10?

Here are some logs:

Kernel 5.10.0:
==============
rd@home:~$ owget /
/bus.1
/uncached
/settings
/system
/statistics
/structure
rd@home:~$

rd@home:~$ systemctl status owserver
● owserver.service - Backend server for 1-wire control
     Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor 
preset: enabled)
     Active: active (running) since Wed 2021-12-29 16:09:20 CET; 1h 21min ago
TriggeredBy: ● owserver.socket
       Docs: man:owserver(1)
   Main PID: 419 (owserver)
      Tasks: 4 (limit: 4729)
     Memory: 1.4M
        CPU: 3min 42.672s
     CGroup: /system.slice/owserver.service
             └─419 /usr/bin/owserver --foreground -c /etc/owfs.conf

Dec 29 16:08:58 home systemd[1]: Starting Backend server for 1-wire control...
Dec 29 16:08:58 home owserver[419]: DEFAULT: ow_opt.c:(780) systemd mode -- 
ignore foreground request
Dec 29 16:08:58 home owserver[419]: DEFAULT: ow_opt.c:(670) systemd mode -- 
ignore 'p' option
Dec 29 16:09:04 home owserver[419]: DEFAULT: ow_elabnet.c:(145) PBM detection 
error
Dec 29 16:09:14 home owserver[419]: DEFAULT: ow_elabnet.c:(145) PBM detection 
error
Dec 29 16:09:20 home owserver[419]: DEFAULT: ow_elabnet.c:(145) PBM detection 
error
Dec 29 16:09:20 home owserver[419]: DEFAULT: owlib.c:(208) Cannot open USB bus 
master
Dec 29 16:09:20 home systemd[1]: Started Backend server for 1-wire control.
rd@home:~$

Restart owserver:

Dec 29 17:31:35 home systemd[1]: Stopping Backend server for 1-wire control...
Dec 29 17:31:35 home systemd[1]: owserver.service: Succeeded.
Dec 29 17:31:35 home systemd[1]: Stopped Backend server for 1-wire control.
Dec 29 17:31:35 home systemd[1]: owserver.service: Consumed 3min 43.935s CPU 
time.
Dec 29 17:31:35 home systemd[1]: Starting Backend server for 1-wire control...
Dec 29 17:31:35 home owserver[20717]: DEFAULT: ow_opt.c:(780) systemd mode -- 
ignore foreground request
Dec 29 17:31:35 home owserver[20717]: DEFAULT: ow_opt.c:(670) systemd mode -- 
ignore 'p' option
Dec 29 17:31:40 home owserver[20717]: DEFAULT: ow_elabnet.c:(145) PBM 
detection error
Dec 29 17:31:41 home owserver[20717]: DEFAULT: owlib.c:(208) Cannot open USB 
bus master
Dec 29 17:31:41 home systemd[1]: Started Backend server for 1-wire control.

Kernel 4.19-0:
==============

rd@home:~$ owget /
/2D.8967C0120000
/2D.F075C0120000
/2D.FD6AC0120000
/3A.C31626000000
/3A.EDE537000000
/3A.791426000000
/3A.E98A25000000
/3A.D11626000000
/3A.51991C000000
/3A.C16238000000
/3A.017325000000
/3A.1E2B26000000
/3A.821626000000
/3A.2CE537000000
/3A.541826000000
/3A.84DA37000000
/3A.202A26000000
/28.FF2741801604
/28.FFF144801604
/28.FFA666801603
/28.FFA620841603
/28.FFB843801604
/bus.4
/bus.3
/bus.2
/bus.1
/uncached
/settings
/system
/statistics
/structure
/simultaneous
/alarm
rd@home:~$

rd@home:~$ systemctl status owserver
● owserver.service - Backend server for 1-wire control
     Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor 
preset: enabled)
     Active: active (running) since Wed 2021-12-29 17:46:54 CET; 6min ago
TriggeredBy: ● owserver.socket
       Docs: man:owserver(1)
   Main PID: 360 (owserver)
      Tasks: 8 (limit: 4739)
     Memory: 2.3M
        CPU: 8.231s
     CGroup: /system.slice/owserver.service
             └─360 /usr/bin/owserver --foreground -c /etc/owfs.conf

Dec 29 17:46:49 home systemd[1]: Starting Backend server for 1-wire control...
Dec 29 17:46:49 home owserver[360]: DEFAULT: ow_opt.c:(780) systemd mode -- 
ignore foreground request
Dec 29 17:46:49 home owserver[360]: DEFAULT: ow_opt.c:(670) systemd mode -- 
ignore 'p' option
Dec 29 17:46:54 home owserver[360]: DEFAULT: ow_elabnet.c:(145) PBM detection 
error
Dec 29 17:46:54 home owserver[360]: DEFAULT: owlib.c:(208) Cannot open USB bus 
master
Dec 29 17:46:54 home systemd[1]: Started Backend server for 1-wire control.
rd@home:~$


Are three any additional useful logs?

Thanks
Rainer


-- 
Rainer Dorsch
http://bokomoko.de/

Re: [Owfs-developers] OWFS 3.2P4 will build on Raspberry Pi

[<han...@at...>]

Hello!
Thank you confirming that. I do not plan on using the kernel driver for the functions. 
--
Gregg Levine han...@at...
"They were in the wrong place at the wrong time. Naturally they became heroes." Princess Leia

-----Original Message-----
From: Jan Kandziora <jj...@gm...> 
Sent: Saturday, October 24, 2020 5:37 PM
To: OWFS (One-wire file system) discussion and help <owf...@li...>
Subject: Re: [Owfs-developers] OWFS 3.2P4 will build on Raspberry Pi

Am 24.10.20 um 06:31 schrieb han...@at...:
>
> Right now I'm working with Maxim to make arrangements to send a pair of
> DS2484 devices, and then a pair of DS28E17 devices as well. (I might have
> those.)
>
Be aware the DS28E17 is a 3.3V only device. It's not 5V tolerant. At
first it appears to be but you will fry it instantly if a 5V onewire is
connected while the power is disconnected.


> We know from earlier discussions that the Pi will work to talk to a device
> that uses the I2C methods. But what about those two?
>
The DS28E17 is only supported by the kernel driver. So you need to use
it with one of the Onewire host adapters that is supported by the
kernel. OWFS isn't involved but may be run in parallel with the --w1
option, or independently on other host adapters.

Do not use both the ds2482 kernel driver and the --i2c option of OWFS on
the same I²C Onewire hostadapter. This meant concurrent access on the
DS2484 chip and leads to all kind of tricky malfunctions.

Kind regards

	Jan


_______________________________________________
Owfs-developers mailing list
Owf...@li...
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] OWFS 3.2P4 will build on Raspberry Pi

[Jan K. <jj...@gm...>]

Am 24.10.20 um 06:31 schrieb han...@at...:
>
> Right now I'm working with Maxim to make arrangements to send a pair of
> DS2484 devices, and then a pair of DS28E17 devices as well. (I might have
> those.)
>
Be aware the DS28E17 is a 3.3V only device. It's not 5V tolerant. At
first it appears to be but you will fry it instantly if a 5V onewire is
connected while the power is disconnected.


> We know from earlier discussions that the Pi will work to talk to a device
> that uses the I2C methods. But what about those two?
>
The DS28E17 is only supported by the kernel driver. So you need to use
it with one of the Onewire host adapters that is supported by the
kernel. OWFS isn't involved but may be run in parallel with the --w1
option, or independently on other host adapters.

Do not use both the ds2482 kernel driver and the --i2c option of OWFS on
the same I²C Onewire hostadapter. This meant concurrent access on the
DS2484 chip and leads to all kind of tricky malfunctions.

Kind regards

	Jan