Re: [Owfs-developers] owfs on Raspberry Buster

2019-09-19 Thread Robert Lagus 
Ok! - my value hasn't changed between Rpi,2b,3b&4b...

Is there anything else I can do to troubleshoot this issue?

[image: Linkedin]  *Robert Lagus*

+358 (0)40 662 44 99

rob...@lagus.net



On Thu, 19 Sep 2019 at 13:09, Mick Sulley  wrote:

> The value and position in the grid depends, I think, on the actual adapter
> it detects.
>
> e.g. on a system with a Sheepwalk RPi2 I see
>
>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
> 10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- --
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 70: -- -- -- -- -- -- -- --
>
> on a system with a Sheepwalk RPi3 I see
>
>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
> 10: -- -- -- -- -- -- -- -- -- -- -- -- 1c -- -- --
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 70: -- -- -- -- -- -- -- --
>
> Both work fine.
>
>
> On 19/09/2019 10:56, Robert Lagus wrote:
>
> Resending, the last got stuck due to an attached image:
>
> robban@sniff:~$ *sudo i2cdetect -y 1*
>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
> 10: -- -- -- -- -- -- -- -- -- -- -- 1b -- -- -- --
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 70: -- -- -- -- -- -- -- --
>
> *sudo i2cdetect -r 1*
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c-1 using receive byte commands.
> I will probe address range 0x03-0x77.
> Continue? [Y/n]
>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
> 10: -- -- -- -- -- -- -- -- -- -- -- 1b -- -- -- --
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 70: -- -- -- -- -- -- -- --
>
> So it's the same value using -r & -y, I don't know if that's good or bad?
> I have always only seen 1b, and nothing else when using -y as in guide I
> was following previously (before Buster install).
>
> robban@sniff:~$ *sudo i2cdetect -r 2*
> [sudo] password for robban:
> Error: Could not open file `/dev/i2c-2' or `/dev/i2c/2': No such file or
> directory
> 1 robban@sniff:~$ *sudo i2cdetect -r 3*
> Error: Could not open file `/dev/i2c-3' or `/dev/i2c/3': No such file or
> directory
> 1 robban@sniff:~$ *sudo i2cdetect -F 1*
> Functionalities implemented by /dev/i2c-1:
> I2C  yes
> SMBus Quick Command  yes
> SMBus Send Byte  yes
> SMBus Receive Byte   yes
> SMBus Write Byte yes
> SMBus Read Byte  yes
> SMBus Write Word yes
> SMBus Read Word  yes
> SMBus Process Call   yes
> SMBus Block Writeyes
> SMBus Block Read no
> SMBus Block Process Call no
> SMBus PECyes
> I2C Block Write  yes
> I2C Block Read   yes
> robban@sniff:~$ *sudo i2cdetect -l*
> i2c-1   i2c bcm2835 I2C adapter I2C adapter
>
>
> [image: Linkedin]  *Robert Lagus*
>
> +358 (0)40 662 44 99
>
> rob...@lagus.net
>
>
>
> On Wed, 18 Sep 2019 at 19:51, Nico Bouthoorn via Owfs-developers <
> owfs-developers@lists.sourceforge.net> wrote:
>
>> Can you see the ds2482 device on the i2c bus like?:
>>
>> i2cdetect -r 1 ( 2 or 3)
>> WARNING! This program can confuse your I2C bus, cause data loss and worse!
>> I will probe file /dev/i2c-1 using read byte commands.
>> I will probe address range 0x03-0x77.
>> Continue? [Y/n]
>>   0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>> 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
>> 10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- --
>> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 70: -- -- -- -- -- -- -- --
>>
>>
>> You

Re: [Owfs-developers] owfs on Raspberry Buster

2019-09-19 Thread Mick Sulley 
The value and position in the grid depends, I think, on the actual 
adapter it detects.


e.g. on a system with a Sheepwalk RPi2 I see

 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:  -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

on a system with a Sheepwalk RPi3 I see

 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:  -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- 1c -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Both work fine.


On 19/09/2019 10:56, Robert Lagus wrote:

Resending, the last got stuck due to an attached image:

robban@sniff:~$ *sudo i2cdetect -y 1*
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- 1b -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

*sudo i2cdetect -r 1*
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1 using receive byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- 1b -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

So it's the same value using -r & -y, I don't know if that's good or bad?
I have always only seen 1b, and nothing else when using -y as in guide 
I was following previously (before Buster install).


robban@sniff:~$ *sudo i2cdetect -r 2*
[sudo] password for robban:
Error: Could not open file `/dev/i2c-2' or `/dev/i2c/2': No such file 
or directory

1 robban@sniff:~$ *sudo i2cdetect -r 3*
Error: Could not open file `/dev/i2c-3' or `/dev/i2c/3': No such file 
or directory

1 robban@sniff:~$ *sudo i2cdetect -F 1*
Functionalities implemented by /dev/i2c-1:
I2C                              yes
SMBus Quick Command              yes
SMBus Send Byte                  yes
SMBus Receive Byte               yes
SMBus Write Byte                 yes
SMBus Read Byte                  yes
SMBus Write Word                 yes
SMBus Read Word                  yes
SMBus Process Call               yes
SMBus Block Write                yes
SMBus Block Read                 no
SMBus Block Process Call         no
SMBus PEC                        yes
I2C Block Write                  yes
I2C Block Read                   yes
robban@sniff:~$ *sudo i2cdetect -l*
i2c-1   i2c             bcm2835 I2C adapter     I2C adapter


Linkedin  *Robert Lagus*
+358 (0)40 662 44 99
rob...@lagus.net  


On Wed, 18 Sep 2019 at 19:51, Nico Bouthoorn via Owfs-developers 
> wrote:


Can you see the ds2482 device on the i2c bus like?:

i2cdetect -r 1 ( 2 or 3)
WARNING! This program can confuse your I2C bus, cause data loss
and worse!
I will probe file /dev/i2c-1 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n]
      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --


You have to see the 18 for i2c device 0   etc


Nico

Mick Sulley wrote:
> I am having trouble getting owfs to work on Raspbian Buster.  I
have posted on the Pi forum
>
>

https://www.raspberrypi.org/forums/viewtopic.php?f=28=251702=1536228#p1536228
>
> Someone said they had the same problem but no suggestions to fix
it, so I wonder if anyone here can give me a clue.
>
> I have just done a

Re: [Owfs-developers] owfs on Raspberry Buster

2019-09-19 Thread Robert Lagus 
Resending, the last got stuck due to an attached image:

robban@sniff:~$ *sudo i2cdetect -y 1*
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:  -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- 1b -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

*sudo i2cdetect -r 1*
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1 using receive byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n]
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:  -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- 1b -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

So it's the same value using -r & -y, I don't know if that's good or bad?
I have always only seen 1b, and nothing else when using -y as in guide I
was following previously (before Buster install).

robban@sniff:~$ *sudo i2cdetect -r 2*
[sudo] password for robban:
Error: Could not open file `/dev/i2c-2' or `/dev/i2c/2': No such file or
directory
1 robban@sniff:~$ *sudo i2cdetect -r 3*
Error: Could not open file `/dev/i2c-3' or `/dev/i2c/3': No such file or
directory
1 robban@sniff:~$ *sudo i2cdetect -F 1*
Functionalities implemented by /dev/i2c-1:
I2C  yes
SMBus Quick Command  yes
SMBus Send Byte  yes
SMBus Receive Byte   yes
SMBus Write Byte yes
SMBus Read Byte  yes
SMBus Write Word yes
SMBus Read Word  yes
SMBus Process Call   yes
SMBus Block Writeyes
SMBus Block Read no
SMBus Block Process Call no
SMBus PECyes
I2C Block Write  yes
I2C Block Read   yes
robban@sniff:~$ *sudo i2cdetect -l*
i2c-1   i2c bcm2835 I2C adapter I2C adapter


[image: Linkedin]  *Robert Lagus*

+358 (0)40 662 44 99

rob...@lagus.net



On Wed, 18 Sep 2019 at 19:51, Nico Bouthoorn via Owfs-developers <
owfs-developers@lists.sourceforge.net> wrote:

> Can you see the ds2482 device on the i2c bus like?:
>
> i2cdetect -r 1 ( 2 or 3)
> WARNING! This program can confuse your I2C bus, cause data loss and worse!
> I will probe file /dev/i2c-1 using read byte commands.
> I will probe address range 0x03-0x77.
> Continue? [Y/n]
>   0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
> 10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- --
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 70: -- -- -- -- -- -- -- --
>
>
> You have to see the 18 for i2c device 0   etc
>
>
> Nico
>
> Mick Sulley wrote:
> > I am having trouble getting owfs to work on Raspbian Buster.  I have
> posted on the Pi forum
> >
> >
> https://www.raspberrypi.org/forums/viewtopic.php?f=28=251702=1536228#p1536228
> >
> > Someone said they had the same problem but no suggestions to fix it, so
> I wonder if anyone here can give me a clue.
> >
> > I have just done a fresh install of Buster and updated. I ran
> raspi-config and enabled 1-wire and i2c.
> > I have installed owserver ow-shell
> > At first it worked, I could see devices with owdir, but it has stopped
> working, owdir returns nothing
> > I have run "sudo systemctl enable owserver.service"
> > but I see -
> >
> > |pi@pi-solar-old:~ $ sudo systemctl status owserver.service ●
> owserver.service - Backend server for 1-wire control Loaded: loaded
> (/lib/systemd/system/owserver.service; enabled; vendor preset: enabled)
> Active: failed (Result: protocol) since Fri 2019-09-13 21:47:16 BST; 48s
> ago Docs: man:owserver(1) Main PID: 493 (code=exited, status=0/SUCCESS) Sep
> 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Service
> RestartSec=100ms expired, scheduling Sep 13 21:47:16 pi-solar-old
> systemd[1]: owserver.service: Scheduled restart job, restart counter is at
> Sep 13 21:47:16 pi-solar-old systemd[1]: Stopped Backend server for 1-wire
> control. Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Start
> request repeated too quickly. Sep 13 21:47:16 pi-solar-old systemd[1]:
> owserver.service: Failed with result 'protocol'. Sep 13 21:47:16
> pi-solar-old

Re: [Owfs-developers] owfs on Raspberry Buster

2019-09-18 Thread Nico Bouthoorn via Owfs-developers 

Can you see the ds2482 device on the i2c bus like?:

i2cdetect -r 1 ( 2 or 3)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n]
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:  -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- 18 -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --


You have to see the 18 for i2c device 0   etc


Nico

Mick Sulley wrote:

I am having trouble getting owfs to work on Raspbian Buster.  I have posted on 
the Pi forum

https://www.raspberrypi.org/forums/viewtopic.php?f=28=251702=1536228#p1536228

Someone said they had the same problem but no suggestions to fix it, so I 
wonder if anyone here can give me a clue.

I have just done a fresh install of Buster and updated. I ran raspi-config and 
enabled 1-wire and i2c.
I have installed owserver ow-shell
At first it worked, I could see devices with owdir, but it has stopped working, 
owdir returns nothing
I have run "sudo systemctl enable owserver.service"
but I see -

|pi@pi-solar-old:~ $ sudo systemctl status owserver.service ● owserver.service 
- Backend server for 1-wire control Loaded: loaded 
(/lib/systemd/system/owserver.service; enabled; vendor preset: enabled) Active: 
failed (Result: protocol) since Fri 2019-09-13 21:47:16 BST; 48s ago Docs: 
man:owserver(1) Main PID: 493 (code=exited, status=0/SUCCESS) Sep 13 21:47:16 
pi-solar-old systemd[1]: owserver.service: Service RestartSec=100ms expired, 
scheduling Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Scheduled 
restart job, restart counter is at Sep 13 21:47:16 pi-solar-old systemd[1]: 
Stopped Backend server for 1-wire control. Sep 13 21:47:16 pi-solar-old 
systemd[1]: owserver.service: Start request repeated too quickly. Sep 13 
21:47:16 pi-solar-old systemd[1]: owserver.service: Failed with result 
'protocol'. Sep 13 21:47:16 pi-solar-old systemd[1]: Failed to start Backend 
server for 1-wire control. pi@pi-solar-old:~ $ |||

|I have tried disable, enable, restart for the service, I have removed and 
reinstalled owserver and ow-shell but nothing helps.|

|Any ideas?
|





___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers



--
0623391101


___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] owfs on Raspberry Buster

2019-09-18 Thread Robert Lagus 
Okay, I understand that Buster install is a bit wonky...
I don't really understand why mine is so troublesome.

I have tried to load the right modules but it seems it's hard to get
anything right now..

*/etc/modprobe.d/raspi-blacklist.conf * - empty

*lsmod | grep i2c*
i2c_bcm270816384  0
i2c_dev20480  0
i2c_bcm283516384  0

*owfs.conf* - server: device=/dev/i2c-1

*sudo /usr/bin/owserver -c /etc/owfs.conf --debug*
DEBUG MODE
libow version:
3.2p3
  DEBUG: ow_daemon.c:(170) main thread id = 3070111472
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd library
isn't found
   CALL: ow_parsename.c:(174) path=[]
  DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock
adapters)
  DEBUG: ow_regex.c:(24) Reg Ex expression <^$> compiled to 0xb6fa860c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^all$> compiled to 0xb6fa862c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^scan$> compiled to 0xb6fa864c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^\*$> compiled to 0xb6fa866c
  DEBUG: ow_regex.c:(24) Reg Ex expression
<^[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}$>
compiled to 0xb6fa868c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^-?[[:digit:]]+$> compiled to
0xb6fa86ac
]*$> compiled to 0xb6fa86ccg Ex expression <^ *([^ ]+)[
]*$> compiled to 0xb6fa86ecg Ex expression <^ *([^ ]+) *: *([^ ]+)[
]*$> compiled to 0xb6fa870cg Ex expression <^ *([^ ]+) *: *([^ ]+) *: *([^
]+)[
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(100) 0: 0->10 found <><>
  DEBUG: ow_regex.c:(100) 1: 0->10 found <><>
  DEBUG: ow_parse_address.c:(87) Text 
  DEBUG: ow_parse_address.c:(142) First 
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 18
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 18 cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 19
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 19 cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1A
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1A cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1B
  DEBUG: ow_ds2482.c:(516) ok
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1B cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1C
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1C cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1D
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1D cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1E
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1E cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1F
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1F cannot be
reset. Not a DS2482.
  DEBUG: ow_com_close.c:(42) Unimplemented!!!
CONNECT: owlib.c:(145) Cannot detect an i2c DS2482-x00 on /dev/i2c-1
DEFAULT: owlib.c:(52) No valid 1-wire buses found
  DEBUG: ow_exit.c:(17) Exit code = 1
   CALL: ow_lib_close.c:(21) Starting Library cleanup
   CALL: ow_lib_stop.c:(22) Clear Cache
  DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out data)
  DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.
  DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out data)
  DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.
   CALL: ow_lib_stop.c:(24) Closing input devices
   CALL: ow_lib_stop.c:(26) Closing output devices
   CALL: ow_lib_close.c:(42) Finished Library cleanup
  DEBUG: ow_lib_close.c:(50) Libraries closed


So, is it strange or did I not load the right modules?
the i2c module card I have attached to my raspberry is:
https://en.m.nu/adapters-network-managment/r-pi-i2c-1wire-expansion-module-v11

Let me know your thoughts!
I'm dying to get this network up and working again.
//Robert

[image: Linkedin]  *Robert Lagus*

+358 (0)40 662 44 99

rob...@lagus.net



On Tue, 17 Sep 2019 at 23:31, Stefano Miccoli via Owfs-developers <
owfs-developers@lists.sourceforge.net> wrote:

>
>
> On 17 Sep 2019, at 14:35, Robert Lagus  wrote:
>
> I tried to start the ofserver with:
> *sudo systemctl restart owserver*
> Job for owserver.service failed because the service did not take the steps
> required by its unit configuration.
> See "systemctl status owserver.service" and "journalctl -xe" for details.
>
>
> You have two independent problems:
>
> 1) the ds2482 is not found by owserver. You should first debug this
> problem starting owserver manually:
> sudo /usr/bin/owserver -c /etc/owfs.conf --debug
>
> 2) the owserver.service unit file on buster is problematic.
>
>
> I cannot give you advice on 1), but I have

Re: [Owfs-developers] owfs on Raspberry Buster

2019-09-17 Thread Stefano Miccoli via Owfs-developers 


> On 17 Sep 2019, at 14:35, Robert Lagus  wrote:
> 
> I tried to start the ofserver with: 
> sudo systemctl restart owserver
> Job for owserver.service failed because the service did not take the steps 
> required by its unit configuration.
> See "systemctl status owserver.service" and "journalctl -xe" for details.
> 

You have two independent problems: 

1) the ds2482 is not found by owserver. You should first debug this problem 
starting owserver manually: 
sudo /usr/bin/owserver -c /etc/owfs.conf --debug

2) the owserver.service unit file on buster is problematic.


I cannot give you advice on 1), but I have solved 2) with a drop-in unit 
configuration file. I run owserver on an headless server with the following 
configuration.

$ sudo systemctl cat owserver.service
# /lib/systemd/system/owserver.service
[Unit]
Description=Backend server for 1-wire control
Documentation=man:owserver(1)

[Service]
Type=notify
NotifyAccess=all
ExecStart=/usr/bin/owserver -c /etc/owfs.conf
Restart=on-failure
#User=Debian-ow
#Group=Debian-ow

[Install]
WantedBy=multi-user.target
Also=owserver.socket

# /etc/systemd/system/owserver.service.d/override.conf
[Service]
User=Debian-ow
Group=Debian-ow
ExecStart=
ExecStart=/usr/bin/owserver -c /etc/owfs.conf --foreground

[Install]
Also=


A long story short. 

/lib/systemd/system/owserver.service is the system file shipped with Buster, 
and it did not work for me out of the box.
/etc/systemd/system/owserver.service.d/override.conf is an override file, that 
you create with `sudo systemctl edit owserver.service`.

My changes with respect to the shipped configuration.

1) Do not run the server as root. I use an USB adapter, and I wrote a couple of 
udev rules to change the ttyUSBxx group to Debian-ow and symlink it to a 
persistent /dev node. Skip this if you plan to run owserver with root 
privileges. (I’m not sure, but I think that root privileges are necessary to 
access the i2c bus.)

2) Add the the --foreground option to the owserver command. This is crucial for 
starting owserver under systemctl without socket activation.

3) Disable socket activation. I expect the owserver service to start at boot, 
before that the first client connects, so socket activation is not needed. I 
found that in edge conditions socket activation may interfere with the correct 
startup, therefore I prefer to disable it.


Bye

S.



___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] owfs on Raspberry Buster

2019-09-17 Thread Jan Kandziora 
Am 17.09.19 um 20:58 schrieb Robert Lagus:
> That worked!  I changed to "server: w1"- And owserver starts, however...
> I'm not seeing any sensors:
> *owdir*
> /bus.0
> /uncached
> /settings
> /system
> /statistics
> /structure
>
> Is this a result of using the module from userspace and not accessing it
> directly on the i2c bus?
>
As soon you use the --w1 option to owserver (or the w1 config option),
it doesn't care if there is any onewire hardware connected. That's now
the task of the kernel. What you are seeing there is a blank listing.
That one /bus.0 is the owserver itself.

Please check if the ds2482 module is loaded. If it is loaded and there
are slaves connected to the DS2482, they should appear at
/sys/bus/w1/devices. You don't need to run owserver for checking that.

Kind regards

Jan


___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] owfs on Raspberry Buster

2019-09-17 Thread Robert Lagus 
That worked!  I changed to "server: w1"- And owserver starts, however...
I'm not seeing any sensors:
*owdir*
/bus.0
/uncached
/settings
/system
/statistics
/structure

Is this a result of using the module from userspace and not accessing it
directly on the i2c bus?

While I run "owdir" in one terminal the log output shows this:

sudo /usr/bin/owserver -c /etc/owfs.conf --debug >> owserver.log
  DEBUG: ow_daemon.c:(170) main thread id = 3069947632
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd library
isn't found
   CALL: ow_parsename.c:(174) path=[]
  DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock
adapters)
  DEBUG: ow_w1_list.c:(53) Sending w1 bus master list message
  DEBUG: ow_net_server.c:(76) ServerAddr: [localhost] [4304]
  DEBUG: ow_w1_send.c:(131) Netlink send -
  DEBUG: ow_w1_send.c:(142) NETLINK sent seq=1
  DEBUG: ow_w1_dispatch.c:(172) Dispatch loop
  DEBUG: ow_w1_parse.c:(112) Wait to peek at message
  DEBUG: ow_tcp_read.c:(63) attempt 24 bytes Time: 10.00 seconds
  DEBUG: ow_tcp_read.c:(113) read: 24 - 0 = 24
  DEBUG: from_client.c:(65) FromClient payload=2 size=0 type=7 sg=0x10A
offset=0
  DEBUG: from_client.c:(73) FromClient (no servermessage) payload=2 size=0
type=7 controlflags=0x10A offset=0
  DEBUG: ow_tcp_read.c:(63) attempt 2 bytes Time: 10.00 seconds
  DEBUG: ow_tcp_read.c:(113) read: 2 - 0 = 2
  DEBUG: handler.c:(152) START handler /
   CALL: data.c:(103) DataHandler: parse path=/
  DEBUG: ow_parseobject.c:(163) /
   CALL: ow_parsename.c:(174) path=[/]
   CALL: data.c:(163) Directory message (all at once)
  DEBUG: dirall.c:(65) OWSERVER Dir-All SpecifiedBus=0 path = /
  DEBUG: ow_dir.c:(80) path=/
   CALL: ow_dir.c:(104) path=/
  DEBUG: ow_cache.c:(853) Looking for directory 00 00 00 00 00 00 00 00
  DEBUG: ow_cache.c:(866) Get from cache sn 00 00 00 00 00 00 00 00
pointer=0xb6f80bb8 extension=0
  DEBUG: ow_cache.c:(895) Dir not found in cache
   CALL: ow_parsename.c:(174) path=[/bus.0]
  DEBUG: ow_regex.c:(24) Reg Ex expression <^bus\.([[:digit:]]+)/?>
compiled to 0xb6f8073c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^settings/?> compiled to
0xb6f8075c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^statistics/?> compiled to
0xb6f8077c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^structure/?> compiled to
0xb6f8079c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^system/?> compiled to
0xb6f807bc
  DEBUG: ow_regex.c:(24) Reg Ex expression <^interface/?> compiled to
0xb6f807dc
  DEBUG: ow_regex.c:(24) Reg Ex expression <^text/?> compiled to 0xb6f807fc
  DEBUG: ow_regex.c:(24) Reg Ex expression <^json/?> compiled to 0xb6f8081c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^uncached/?> compiled to
0xb6f8083c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^unaliased/?> compiled to
0xb6f8085c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^alarm?> compiled to 0xb6f8087c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^simultaneous/?> compiled to
0xb6f8089c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^thermostat/?> compiled to
0xb6f808bc
  DEBUG: ow_regex.c:(24) Reg Ex expression <^/bus\.[[:digit:]]+/?> compiled
to 0xb6f808dc
  DEBUG: ow_regex.c:(24) Reg Ex expression <\.> compiled to 0xb6f808fc
  DEBUG: ow_regex.c:(24) Reg Ex expression <\.all$> compiled to 0xb6f8091c
  DEBUG: ow_regex.c:(24) Reg Ex expression <\.byte$> compiled to 0xb6f8093c
  DEBUG: ow_regex.c:(24) Reg Ex expression <\.[[:digit:]]+$> compiled to
0xb6f8095c
  DEBUG: ow_regex.c:(24) Reg Ex expression <\.[[:alpha:]]$> compiled to
0xb6f8097c
  DEBUG: ow_regex.c:(100) 0: 0->5 found <><>
  DEBUG: ow_regex.c:(100) 1: 4->5 found <0><>
  DEBUG: ow_regex.c:(100) 0: 0->6 found <><>
  DEBUG: ow_regex.c:(24) Reg Ex expression
<^([[:xdigit:]]{2})\.?([[:xdigit:]]{12})\.?([[:xdigit:]]{2}){0,1}$>
compiled to 0xb6f809a0
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_parsename.c:(133) /bus.0
   CALL: ow_parsename.c:(174) path=[/uncached]
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_parsename.c:(133) /uncached
   CALL: ow_parsename.c:(174) path=[/settings]
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_parsename.c:(133) /settings
   CALL: ow_parsename.c:(174) path=[/system]
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_parsename.c:(133) /system
   CALL: ow_parsename.c:(174) path=[/statistics]
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_parsename.c:(133) /statistics
   CALL: ow_parsename.c:(174) path=[/structure]
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_parsename.c:(133) /structure
  DEBUG: ow_dir.c:(199) ret=0
  DEBUG: ow_parsename.c:(133) /
  DEBUG: data.c:(193) DataHandler: FS_ParsedName_destroy done

Re: [Owfs-developers] owfs on Raspberry Buster

2019-09-17 Thread Jan Kandziora 
Am 17.09.19 um 08:52 schrieb Robert Lagus:
>
> *ofws.conf:*
> ! server: server = localhost:4304
> server: i2c = /dev/i2c-1
>
Please check if you have the ds2482 kernel module loaded.

What you are doing here is accessing the ds2482 directly from user
space. This is ok, but it creates a mess on the I²C bus if the ds2482
module is loaded, as that module access the ds2482 at the same time.

So either unload and blacklist that module, or change the owfs.conf line to

server: w1

This makes owserver use the kernel modules instead of accessing the I²C
hardware by itself.

Kind regards

Jan


___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] owfs on Raspberry Buster

2019-09-17 Thread Robert Lagus 
Hi, Thanks for your email!

I changed to your proposed owfs.conf with the same error messages:

*sudo /usr/bin/owserver -c /etc/owfs.conf --debug*
DEBUG MODE
libow version:
3.2p3
  DEBUG: ow_daemon.c:(170) main thread id = 3069234928
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd library
isn't found
   CALL: ow_parsename.c:(174) path=[]
  DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock
adapters)
  DEBUG: ow_regex.c:(24) Reg Ex expression <^$> compiled to 0xb6ed260c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^all$> compiled to 0xb6ed262c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^scan$> compiled to 0xb6ed264c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^\*$> compiled to 0xb6ed266c
  DEBUG: ow_regex.c:(24) Reg Ex expression
<^[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}$>
compiled to 0xb6ed268c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^-?[[:digit:]]+$> compiled to
0xb6ed26ac
]*$> compiled to 0xb6ed26ccg Ex expression <^ *([^ ]+)[
]*$> compiled to 0xb6ed26ecg Ex expression <^ *([^ ]+) *: *([^ ]+)[
]*$> compiled to 0xb6ed270cg Ex expression <^ *([^ ]+) *: *([^ ]+) *: *([^
]+)[
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(100) 0: 0->10 found <><>
  DEBUG: ow_regex.c:(100) 1: 0->10 found <><>
  DEBUG: ow_parse_address.c:(87) Text 
  DEBUG: ow_parse_address.c:(142) First 
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 18
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 18 cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 19
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 19 cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1A
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1A cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1B
  DEBUG: ow_ds2482.c:(516) ok
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1B cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1C
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1C cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1D
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1D cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1E
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1E cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1F
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1F cannot be
reset. Not a DS2482.
  DEBUG: ow_com_close.c:(42) Unimplemented!!!
CONNECT: owlib.c:(145) Cannot detect an i2c DS2482-x00 on /dev/i2c-1
DEFAULT: owlib.c:(52) No valid 1-wire buses found
  DEBUG: ow_exit.c:(17) Exit code = 1
   CALL: ow_lib_close.c:(21) Starting Library cleanup
   CALL: ow_lib_stop.c:(22) Clear Cache
  DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out data)
  DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.
  DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out data)
  DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.
   CALL: ow_lib_stop.c:(24) Closing input devices
   CALL: ow_lib_stop.c:(26) Closing output devices
   CALL: ow_lib_close.c:(42) Finished Library cleanup
  DEBUG: ow_lib_close.c:(50) Libraries closed

*systemctl status owserver*
● owserver.service - Backend server for 1-wire control
   Loaded: loaded (/lib/systemd/system/owserver.service; disabled; vendor
preset: enabled)
   Active: failed (Result: protocol) since Tue 2019-09-17 09:32:09 EEST; 5h
53min ago
 Docs: man:owserver(1)
  Process: 24451 ExecStart=/usr/bin/owserver -c /etc/owfs.conf
(code=exited, status=0/SUCCESS)
 Main PID: 24451 (code=exited, status=0/SUCCESS)

*sudo systemctl enable owserver*
Synchronizing state of owserver.service with SysV service script with
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable owserver
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "UTF-8",
LC_TERMINAL = "iTerm2",
LANG = "en_GB.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_GB.UTF-8").
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "UTF-8",
LC_TERMINAL = "iTerm2",
LANG = "en_GB.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_GB.UTF-8").
Created symlink
/etc/systemd/system/multi-user.target.wants/owserver.service →
/lib/systemd/system/owserver.service.
Created

Re: [Owfs-developers] owfs on Raspberry Buster

2019-09-17 Thread Mick Sulley 

In owfs.conf I have

server: device=/dev/i2c-1
rather than "server: i2c = /dev/i2c-1"  don't know if that is sigificant.

What do you see with

systemctl status owserver

If that shows an error you could try

sudo systemctl enable owserver

or

sudo systemctl restart owserver

also look in /var/logs/syslog  there may be owserver messages in there


On 17/09/2019 07:52, Robert Lagus wrote:

I have a very similar problem.
Rpi4 & Buster.

After Micks emails, I did try to remove & purge my ow-shell and 
owserver, the only thing that starts is the fake sensors.
I have not been able to access my sensors on my Buster install, I 
don't understand what's wrong and how I can get it working again.


I did have a thunder strike that grilled my Raspberry Pi (3?) but the 
1wire board and the RPI is brand new.


Does anyone have any ideas how I can access my sensors again?

*ls /dev/i2c**
/dev/i2c-1

*ofws.conf:*
! server: server = localhost:4304
server: i2c = /dev/i2c-1
http: port = 2121
ftp: port = 2120
server: port = localhost:4304

*sudo /usr/bin/owserver -c /etc/owfs.conf --debug*
DEBUG MODE
libow version:
        3.2p3
  DEBUG: ow_daemon.c:(170) main thread id = 3069411056
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd 
library isn't found

   CALL: ow_parsename.c:(174) path=[]
  DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock 
adapters)

  DEBUG: ow_regex.c:(24) Reg Ex expression <^$> compiled to 0xb6efd60c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^all$> compiled to 0xb6efd62c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^scan$> compiled to 0xb6efd64c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^\*$> compiled to 0xb6efd66c
  DEBUG: ow_regex.c:(24) Reg Ex expression 
<^[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}$> 
compiled to 0xb6efd68c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^-?[[:digit:]]+$> compiled 
to 0xb6efd6ac

]*$> compiled to 0xb6efd6ccg Ex expression <^ *([^ ]+)[
]*$> compiled to 0xb6efd6ecg Ex expression <^ *([^ ]+) *: *([^ ]+)[
]*$> compiled to 0xb6efd70cg Ex expression <^ *([^ ]+) *: *([^ ]+) *: 
*([^ ]+)[

  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(100) 0: 0->10 found <><>
  DEBUG: ow_regex.c:(100) 1: 0->10 found <><>
  DEBUG: ow_parse_address.c:(87) Text 
  DEBUG: ow_parse_address.c:(142) First 
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 18
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 18 cannot 
be reset. Not a DS2482.

CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 19
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 19 cannot 
be reset. Not a DS2482.

CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1A
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1A cannot 
be reset. Not a DS2482.

CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1B
  DEBUG: ow_ds2482.c:(516) ok
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1B cannot 
be reset. Not a DS2482.

CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1C
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1C cannot 
be reset. Not a DS2482.

CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1D
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1D cannot 
be reset. Not a DS2482.

CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1E
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1E cannot 
be reset. Not a DS2482.

CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1F
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1F cannot 
be reset. Not a DS2482.

  DEBUG: ow_com_close.c:(42) Unimplemented!!!
CONNECT: owlib.c:(145) Cannot detect an i2c DS2482-x00 on /dev/i2c-1
DEFAULT: owlib.c:(52) No valid 1-wire buses found
  DEBUG: ow_exit.c:(17) Exit code = 1
   CALL: ow_lib_close.c:(21) Starting Library cleanup
   CALL: ow_lib_stop.c:(22) Clear Cache
  DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out data)
  DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.
  DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out data)
  DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.
   CALL: ow_lib_stop.c:(24) Closing input devices
   CALL: ow_lib_stop.c:(26) Closing output devices
   CALL: ow_lib_close.c:(42) Finished Library cleanup
  DEBUG: ow_lib_close.c:(50) Libraries closed

I'm able to see the i2c device:
sudo i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- 1b -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --


I had it working on my last install with a Rpi3 with this conf:
(cropping commented lines)

! server: server = localhost:4304
server: i2c = ALL:ALL
http: port = 2121
ftp: port = 2120
server: port = localhost:4304

Any ideas

Re: [Owfs-developers] owfs on Raspberry Buster

2019-09-17 Thread Robert Lagus 
I have a very similar problem.
Rpi4 & Buster.

After Micks emails, I did try to remove & purge my ow-shell and owserver,
the only thing that starts is the fake sensors.
I have not been able to access my sensors on my Buster install, I don't
understand what's wrong and how I can get it working again.

I did have a thunder strike that grilled my Raspberry Pi (3?) but the 1wire
board and the RPI is brand new.

Does anyone have any ideas how I can access my sensors again?

*ls /dev/i2c**
/dev/i2c-1

*ofws.conf:*
! server: server = localhost:4304
server: i2c = /dev/i2c-1
http: port = 2121
ftp: port = 2120
server: port = localhost:4304

*sudo /usr/bin/owserver -c /etc/owfs.conf --debug*
DEBUG MODE
libow version:
3.2p3
  DEBUG: ow_daemon.c:(170) main thread id = 3069411056
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd library
isn't found
   CALL: ow_parsename.c:(174) path=[]
  DEBUG: owlib.c:(77) Global temp limit 0C to 100C (for fake and mock
adapters)
  DEBUG: ow_regex.c:(24) Reg Ex expression <^$> compiled to 0xb6efd60c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^all$> compiled to 0xb6efd62c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^scan$> compiled to 0xb6efd64c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^\*$> compiled to 0xb6efd66c
  DEBUG: ow_regex.c:(24) Reg Ex expression
<^[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}$>
compiled to 0xb6efd68c
  DEBUG: ow_regex.c:(24) Reg Ex expression <^-?[[:digit:]]+$> compiled to
0xb6efd6ac
]*$> compiled to 0xb6efd6ccg Ex expression <^ *([^ ]+)[
]*$> compiled to 0xb6efd6ecg Ex expression <^ *([^ ]+) *: *([^ ]+)[
]*$> compiled to 0xb6efd70cg Ex expression <^ *([^ ]+) *: *([^ ]+) *: *([^
]+)[
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(53) Not found
  DEBUG: ow_regex.c:(100) 0: 0->10 found <><>
  DEBUG: ow_regex.c:(100) 1: 0->10 found <><>
  DEBUG: ow_parse_address.c:(87) Text 
  DEBUG: ow_parse_address.c:(142) First 
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 18
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 18 cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 19
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 19 cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1A
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1A cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1B
  DEBUG: ow_ds2482.c:(516) ok
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1B cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1C
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1C cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1D
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1D cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1E
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1E cannot be
reset. Not a DS2482.
CONNECT: ow_ds2482.c:(396) Found an i2c device at /dev/i2c-1 address 1F
CONNECT: ow_ds2482.c:(422) i2c device at /dev/i2c-1 address 1F cannot be
reset. Not a DS2482.
  DEBUG: ow_com_close.c:(42) Unimplemented!!!
CONNECT: owlib.c:(145) Cannot detect an i2c DS2482-x00 on /dev/i2c-1
DEFAULT: owlib.c:(52) No valid 1-wire buses found
  DEBUG: ow_exit.c:(17) Exit code = 1
   CALL: ow_lib_close.c:(21) Starting Library cleanup
   CALL: ow_lib_stop.c:(22) Clear Cache
  DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out data)
  DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.
  DEBUG: ow_cache.c:(295) Flipping cache tree (purging timed-out data)
  DEBUG: ow_cache.c:(313) flip cache. tdestroy() will be called.
   CALL: ow_lib_stop.c:(24) Closing input devices
   CALL: ow_lib_stop.c:(26) Closing output devices
   CALL: ow_lib_close.c:(42) Finished Library cleanup
  DEBUG: ow_lib_close.c:(50) Libraries closed

I'm able to see the i2c device:
sudo i2cdetect -y 1
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:  -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- 1b -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --


I had it working on my last install with a Rpi3 with this conf:
(cropping commented lines)

! server: server = localhost:4304
server: i2c = ALL:ALL
http: port = 2121
ftp: port = 2120
server: port = localhost:4304

Any ideas are welcome!
Thanks!

[image: Linkedin]  *Robert Lagus*

+358 (0)40 662 44 99

rob...@lagus.net



On Sun, 15 Sep 2019 at 21:08, Mick Sulley  wrote:

> Many thanks Colin.
>
> The log had many lines like
>
> Sep 15 18:01:27 pi-solar-old kernel: [ 3631.364529] w1_master_driver
> w1_bus_master1: Attaching one wire slave 00.a200 crc 13
> Sep 15 18:01:27 pi-solar-old kernel: [

Re: [Owfs-developers] owfs on Raspberry Buster

2019-09-15 Thread Mick Sulley 

Many thanks Colin.

The log had many lines like

Sep 15 18:01:27 pi-solar-old kernel: [ 3631.364529] w1_master_driver 
w1_bus_master1: Attaching one wire slave 00.a200 crc 13
Sep 15 18:01:27 pi-solar-old kernel: [ 3631.383280] w1_master_driver 
w1_bus_master1: Family 0 for 00.a200.13 is not registered.


After a bit of head scratching I looked at /etc/owfs.config and that did 
not make much sense, so I deleted it and created a new one.  It is now 
working!


What I don't understand is how owfs.conf gets created in the first 
place.  I uninstalled and purged owserver and ow-shell, but owfs.conf 
was still there so I deleted it.  I then reinstalled but it didn't 
create owfs.conf, don't understand why.


Anyway, now I can get back to testing :)

Mick

On 15/09/2019 16:57, Colin Law wrote:
Check in the owserver log (likely /var/log/syslog) to see if it is 
showing errors.


Colin

On Sun, 15 Sep 2019, 12:08 Mick Sulley, > wrote:


I am having trouble getting owfs to work on Raspbian Buster.  I
have posted on the Pi forum


https://www.raspberrypi.org/forums/viewtopic.php?f=28=251702=1536228#p1536228

Someone said they had the same problem but no suggestions to fix
it, so I wonder if anyone here can give me a clue.

I have just done a fresh install of Buster and updated. I ran
raspi-config and enabled 1-wire and i2c.
I have installed owserver ow-shell
At first it worked, I could see devices with owdir, but it has
stopped working, owdir returns nothing
I have run "sudo systemctl enable owserver.service"
but I see -

|pi@pi-solar-old:~ $ sudo systemctl status owserver.service ●
owserver.service - Backend server for 1-wire control Loaded:
loaded (/lib/systemd/system/owserver.service; enabled; vendor
preset: enabled) Active: failed (Result: protocol) since Fri
2019-09-13 21:47:16 BST; 48s ago Docs: man:owserver(1) Main PID:
493 (code=exited, status=0/SUCCESS) Sep 13 21:47:16 pi-solar-old
systemd[1]: owserver.service: Service RestartSec=100ms expired,
scheduling Sep 13 21:47:16 pi-solar-old systemd[1]:
owserver.service: Scheduled restart job, restart counter is at Sep
13 21:47:16 pi-solar-old systemd[1]: Stopped Backend server for
1-wire control. Sep 13 21:47:16 pi-solar-old systemd[1]:
owserver.service: Start request repeated too quickly. Sep 13
21:47:16 pi-solar-old systemd[1]: owserver.service: Failed with
result 'protocol'. Sep 13 21:47:16 pi-solar-old systemd[1]: Failed
to start Backend server for 1-wire control. pi@pi-solar-old:~ $ |||

|I have tried disable, enable, restart for the service, I have
removed and reinstalled owserver and ow-shell but nothing helps.|

|Any ideas?
|

___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/owfs-developers



___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] owfs on Raspberry Buster

2019-09-15 Thread Colin Law 
Check in the owserver log (likely /var/log/syslog) to see if it is showing
errors.

Colin

On Sun, 15 Sep 2019, 12:08 Mick Sulley,  wrote:

> I am having trouble getting owfs to work on Raspbian Buster.  I have
> posted on the Pi forum
>
>
> https://www.raspberrypi.org/forums/viewtopic.php?f=28=251702=1536228#p1536228
>
> Someone said they had the same problem but no suggestions to fix it, so I
> wonder if anyone here can give me a clue.
>
> I have just done a fresh install of Buster and updated. I ran raspi-config
> and enabled 1-wire and i2c.
> I have installed owserver ow-shell
> At first it worked, I could see devices with owdir, but it has stopped
> working, owdir returns nothing
> I have run "sudo systemctl enable owserver.service"
> but I see -
>
> pi@pi-solar-old:~ $ sudo systemctl status owserver.service
> ● owserver.service - Backend server for 1-wire control
>Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor 
> preset: enabled)
>Active: failed (Result: protocol) since Fri 2019-09-13 21:47:16 BST; 48s 
> ago
>  Docs: man:owserver(1)
>  Main PID: 493 (code=exited, status=0/SUCCESS)
>
> Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Service 
> RestartSec=100ms expired, scheduling
> Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Scheduled restart 
> job, restart counter is at
> Sep 13 21:47:16 pi-solar-old systemd[1]: Stopped Backend server for 1-wire 
> control.
> Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Start request 
> repeated too quickly.
> Sep 13 21:47:16 pi-solar-old systemd[1]: owserver.service: Failed with result 
> 'protocol'.
> Sep 13 21:47:16 pi-solar-old systemd[1]: Failed to start Backend server for 
> 1-wire control.
> pi@pi-solar-old:~ $
>
> I have tried disable, enable, restart for the service, I have removed and
> reinstalled owserver and ow-shell but nothing helps.
>
> Any ideas?
>
> ___
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers