owfs-developers — Developer's list for OWFS

[Owfs-developers] Simultaneous not working

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

Running v3.2p3 on Raspberry Pi,  I have set up some DS18B20 sensors on a 
test system, all of them are powered, but simultaneous does not seem to 
be working

The code is below, when I run it the first loop takes 16 seconds then it 
loops at 3 seconds for a while, then a 16 second etc. so it looks like 
it does slow individual conversions, then uses cached values until they 
expire, then another slow individual conversion, etc.  Have I got 
something wrong here?

Thanks

Mick

#!/usr/bin/python3

# sensor_read.py

import pyownet
import time

def main():
     owp = pyownet.protocol.proxy()
     while True:
         start = time.time()
         owp.write('/simultaneous/temperature', b'1')
         time.sleep(1)
         print('start of sensor_read.py')
         sen_lst = ['Solar_Pnl_1A', 'Solar_Pnl_2A','Solar_Pnl_1B', 
'Pool_Sol_X', 'Pool_CH_X', 'DHW_Mid_Top', 'DHW_Mid_Btm', 
'DHW_Top','Temp5', 'Temp19', 'Temp20','Temp21', 'Temp22', 'Temp23', 
'Temp25', 'Temp26', 'Temp27', 'Temp29',  'Temp30']
         prop_lst =  ['/type', '/power', '/latesttemp']
         for p in prop_lst:
             print('%s  ' %p,  end = '')
         print('')
         for sen in sen_lst:
             print('\n%s ' %sen, end = '')
             for prop in prop_lst:
                 try:
                     print('%s  ' %(owp.read('/uncached/' + sen + 
prop).decode()),  end = '')
                 except:
                     print('failed! ',    end = '')
         endt = time.time() - start
         print('\nTime = %f' %endt)

if __name__ == "__main__":
     main()

Re: [Owfs-developers] DS2423 question

[<br...@va...>]

Arent they for ESD protection?
 
Bruce
-----Original Message-----
From: "Gregg Levine" <gre...@gm...>
Sent: Tuesday, June 23, 2020 10:24am
To: "owfs-developers owfs" <owf...@li...>
Subject: [Owfs-developers] DS2423 question



Hello!
On a page inside appnote AN3845 from Maxim back when they were still
making the DS2423 parts, the schematic shown includes a pair of
Schottky diodes, they were the BAT54 series. Also a pull-down resistor
of 1Meg.

Now I can certainly grok the reasoning behind the pull-down resistor
for the part to work properly, but what about the dual diodes? The
other problem is that these are of the small outline style, which
means they are available as surface mount styles. (They might be
available in the standard mountable rather than a surface mount style.
I've not checked further.)
-----
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

[Owfs-developers] DS2423 question

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

Hello!
On a page inside appnote AN3845 from Maxim back when they were still
making the DS2423 parts, the schematic shown includes a pair of
Schottky diodes, they were the BAT54 series. Also a pull-down resistor
of 1Meg.

Now I can certainly grok the reasoning behind the pull-down resistor
for the part to work properly, but what about the dual diodes? The
other problem is that these are of the small outline style, which
means they are available as surface mount styles. (They might be
available in the standard mountable rather than a surface mount style.
I've not checked further.)
-----
Gregg C Levine gre...@gm...
"This signature fought the Time Wars, time and again."

Re: [Owfs-developers] Bugfixed release not the one for download?

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

Am 23.06.20 um 00:15 schrieb Gregg Levine:
> Hello!
> Okay group, I'll defer to all of you on this. Something else, do any
> of you know who does the packaging for Debian?
>
Vincent Danjean <vda...@de...>

You can find out such things on the official Debian packages documentation:

https://packages.debian.org/en/sid/owfs

Kind regards

	Jan

Re: [Owfs-developers] Bugfixed release not the one for download?

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

Hello!
Okay group, I'll defer to all of you on this. Something else, do any
of you know who does the packaging for Debian? And that for the
Raspberry Pi families? I ask because I read over of the series of
messages on making things work on one and the problems related there,
resemble some of the reasons why I do build from source, instead of
using preexisting packages.
-----
Gregg C Levine gre...@gm...
"This signature fought the Time Wars, time and again."

On Mon, Jun 22, 2020 at 4:59 PM Stefano Miccoli via Owfs-developers
<owf...@li...> wrote:
>
> There are a number of open pull requests and issues; I think we should first sort these out before thinking abut releasing a new version.
>
> Stefano
>
> On 22 Jun 2020, at 22:10, Jan Kandziora <jj...@gm...> wrote:
>
> Am 22.06.20 um 18:27 schrieb Gregg Levine:
>
>
> I decided to check to see if the project page for OWFS had anything
> new, that is newer than the OWFS-3.2P2 one that I'm busy building.
> The release device from the page wanted to send me the previous
> release. Since I'm still down as an admin I decided to see if I could
> change things to reflect that version. I decided against it because I
> did not want to break any of the pages on the site.
>
> Last release was October 2018, so yes, we should have a new version.
>
> I do some test compiles at the moment and found warnings and bugs.
>
> Kind regards
>
> Jan
>
>
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Bugfixed release not the one for download?

[Stefano M. <mo...@ic...>]

There are a number of open pull requests and issues; I think we should first sort these out before thinking abut releasing a new version.

Stefano

> On 22 Jun 2020, at 22:10, Jan Kandziora <jj...@gm...> wrote:
> 
> Am 22.06.20 um 18:27 schrieb Gregg Levine:
>> 
>> I decided to check to see if the project page for OWFS had anything
>> new, that is newer than the OWFS-3.2P2 one that I'm busy building.
>> The release device from the page wanted to send me the previous
>> release. Since I'm still down as an admin I decided to see if I could
>> change things to reflect that version. I decided against it because I
>> did not want to break any of the pages on the site.
>> 
> Last release was October 2018, so yes, we should have a new version.
> 
> I do some test compiles at the moment and found warnings and bugs.
> 
> Kind regards
> 
> 	Jan
> 
> 
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Bugfixed release not the one for download?

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

Am 22.06.20 um 18:27 schrieb Gregg Levine:
>
> I decided to check to see if the project page for OWFS had anything
> new, that is newer than the OWFS-3.2P2 one that I'm busy building.
> The release device from the page wanted to send me the previous
> release. Since I'm still down as an admin I decided to see if I could
> change things to reflect that version. I decided against it because I
> did not want to break any of the pages on the site.
>
Last release was October 2018, so yes, we should have a new version.

I do some test compiles at the moment and found warnings and bugs.

Kind regards

	Jan

[Owfs-developers] Bugfixed release not the one for download?

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

Hello!
As with everyone during this time, I'm busily exploring a project or
three. In this case I decided to spin up one from either last year or
two years ago, concerning OWFS and using one of the 3.2 releases on a
Raspberry Pi.

I decided to check to see if the project page for OWFS had anything
new, that is newer than the OWFS-3.2P2 one that I'm busy building.
The release device from the page wanted to send me the previous
release. Since I'm still down as an admin I decided to see if I could
change things to reflect that version. I decided against it because I
did not want to break any of the pages on the site.

About that project. That will be discussed in a separate message.
-----
Gregg C Levine gre...@gm...
"This signature fought the Time Wars, time and again."

Re: [Owfs-developers] Balena.io & OWFS

[Stefano M. <mo...@ic...>]

> On 16 May 2020, at 12:49, Stefano Miccoli via Owfs-developers <owf...@li...> wrote:
> 
> The python code could also be improved a little bit, shortly I will post a gist with some corrections.
> 

Please, see at https://gist.github.com/miccoli/5a6fcb400e13a22873863df6d3b48c02 <https://gist.github.com/miccoli/5a6fcb400e13a22873863df6d3b48c02> for a refactored python3 script.

Here my modifications:

- no need to perform °C -> °F conversion explicitly, just query owserver with the appropriate flag, see https://pyownet.readthedocs.io/en/latest/protocol.html#pyownet.protocol.FLG_TEMP_F <https://pyownet.readthedocs.io/en/latest/protocol.html#pyownet.protocol.FLG_TEMP_F>

- temperature conversion is cached in owserver; since you are reading in a tight busy loop, better to use uncached values, and force temperature conversion at each read (supposing there is a single process querying the owserver)
https://pyownet.readthedocs.io/en/latest/protocol.html#pyownet.protocol.FLG_UNCACHED <https://pyownet.readthedocs.io/en/latest/protocol.html#pyownet.protocol.FLG_UNCACHED>

- since you are in a tight busy loop, use a persistent connection
https://pyownet.readthedocs.io/en/latest/protocol.html#persistent-vs-non-persistent-proxy-objects <https://pyownet.readthedocs.io/en/latest/protocol.html#persistent-vs-non-persistent-proxy-objects>

- better error handling

regards,

Stefano

Re: [Owfs-developers] Balena.io & OWFS

[Stefano M. <mo...@ic...>]

I don’t think that the problem is in pyownet, but of course, since I’m the author of that package I’m biased. (In Neapolitan language there is a saying: "Ogne scarrafone è bello a mamma soja”)

'pyownet.protocol.ConnError: [Errno 111] Connection refused’ usually  means that there is no ‘owserver’ listening al port 4304, or, less likely, that there is a firewall preventing the python process to access port 4304.

Since you installed also ow-shell, just issue an “owdir” command before calling the python program, just to check if observer is listening and the sensors are there.

The python code could also be improved a little bit, shortly I will post a gist with some corrections.

Stefano

> On 16 May 2020, at 01:59, Greg Pronko <gr...@L2...> wrote:
> 
> Hi All,
>  
> I am new to the mailing list and am hoping someone out there might be able to help us.  We are currently working on a set of devices for monitoring endangered animal habitats and we need to try to read multiple 1wire temp sensor readings via RPI3. Specifically I am hoping to find someone with experience using OWFS on the Balena.io <http://balena.io/> platform and Docker templates.  I am looking for an example of OWFS measuring 1wire thermocouples via i2c hat running on Balena.io <http://balena.io/> via a Dockerfile? The key here is to get it to work on Balena via a Dockerfile.template with i2c enabled as that is how we will manage fleets of these devices.
>  
> For those of you who aren’t familiar with Balena.io <http://balena.io/> it used to be called Resin.io <http://resin.io/> until a few years ago.  Balena is a great fleet management and deployment platform for managing multiple IOT devices. We use it for many RPI implementations.  I highly recommend taking a few hours to learn how to deploy a device on their platform as once you start using it you won’t go back.  But my biggest hope is for one of you experts at OWFS to deploy OWFS via Balena onto a RPI3 with an i2c 1-wire hat so that you can share a solution on how to properly build a Dockerfile and python file for it that works.  I have been trying to figure it out for days and getting nowhere.  I am trying to use pyownet which might be part of my problem but I don’t have to use that if you can think of a better way to do this. I would also like to stick to Python3 as Balena is dropping support for Python2 soon.
>  
> I am sure Balena will be adopted by folks more and more moving forward so solving this would be a great investment in furthering the 1wire and owfs platform to be deployed in fleets.  In this situation, it is also going towards a good cause of helping endangered animals.
>  
> Below is my dockerfile & python code which I just can’t get to work properly. I continue to get this error: pyownet.protocol.ConnError: [Errno 111] Connection refused
>  
> This is the i2c device I am using: https://www.abelectronics.co.uk/kb/article/3/owfs-with-i2c-support-on-raspberry-pi <https://www.abelectronics.co.uk/kb/article/3/owfs-with-i2c-support-on-raspberry-pi>
>  
> Thanks so much,
>  
> Greg
>  
> ----------------------------------------
> DOCKERFILE CODE BELOW
> ----------------------------------------
> FROM balenalib/raspberrypi3-python:3.7.6 
>  
> ENV DEBIAN_FRONTEND=noninteractive
> ENV DEBCONF_NOWARNINGS yes
>  
> RUN     apt-get update -y; \
>         apt-get upgrade -y; \
>         apt-get clean all
>  
> RUN sudo apt-get update -y;\
>         apt-get install -qy apt-utils \
>         python3-pip \
>         python3 \ 
>         libtool \
>         python3-dev \
>         python3-smbus\
>         libtool \
>         rpi-update \
>         raspi-config \
>         owfs \
>         owserver \
>         ow-shell \
>         python-ow \
>         python3-rpi.gpio \
>         && apt-get clean && rm -rf /var/lib/apt/lists/*
>  
> RUN sudo pip3 install setuptools --upgrade
>  
> RUN sudo pip3 install --upgrade pip
>  
> RUN sudo pip3 install pyownet
>  
> RUN sed -i '20i\server: device=/dev/i2c-1' /etc/owfs.conf
> RUN sed -i 's/^server: FAKE = DS18S20,DS2405/#server: FAKE = DS18S20,DS2405/' /etc/owfs.conf
> RUN sed -i 's/^ftp: port = 2120/#ftp: port = 2120/' /etc/owfs.conf
>  
> COPY . ./
>  
> ENV INITSYSTEM on 
>  
> CMD modprobe i2c-dev && owserver -d /dev/i2c-
> CMD ["python3", "1wire_temp_test.py"]
>  
> ----------------------------------------
> PYTHON CODE BELOW
> ----------------------------------------
> import time
> from pyownet import protocol
>  
> temp_type = 'F'
> tc_1_mac = 'FF8AD3641402'  ### This is obviously my thermocouple so enter your own mac address here ###
>  
> owproxy = protocol.proxy(host="localhost", port=4304)
> sensor_file_1 = '/28.' + tc_1_mac + '/temperature'
>  
> def main():
>                 while True:
>                                 try:
>                                                 thetext = owproxy.read(sensor_file_1)
>                                                 heater_temp_1 = round((float(thetext[2:])*(9/5)+32),2)
>                                                 print ('SENSOR #1 =', heater_temp_1, temp_type)
>                                 except IOError:
>                                                 print ('SENSOR #1 READ FAIL')
>                                 time.sleep(10)
>                                 
> if __name__ == '__main__':
>                 main()
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li... <mailto:Owf...@li...>
> https://lists.sourceforge.net/lists/listinfo/owfs-developers <https://lists.sourceforge.net/lists/listinfo/owfs-developers>

Re: [Owfs-developers] Balena.io & OWFS

[Henrik Ö. <tr...@gm...>]

I have used this image for years:
https://hub.docker.com/r/smarthomerocks/owserver
However I have stripped away all unnecessary stuff just to keep the image
small and simple (only owserver available, no python or C bindings).
Maybe there is something in there that you could use.

Best regards, Henrik

Den lör 16 maj 2020 kl 06:32 skrev Greg Pronko <gr...@l2...>:

> Hi All,
>
>
>
> I am new to the mailing list and am hoping someone out there might be able
> to help us.  We are currently working on a set of devices for monitoring
> endangered animal habitats and we need to try to read multiple 1wire temp
> sensor readings via RPI3. Specifically I am hoping to find someone with
> experience using OWFS on the Balena.io platform and Docker templates.  I am
> looking for an example of OWFS measuring 1wire thermocouples via i2c hat
> running on Balena.io via a Dockerfile? The key here is to get it to work on
> Balena via a Dockerfile.template with i2c enabled as that is how we will
> manage fleets of these devices.
>
>
>
> For those of you who aren’t familiar with Balena.io it used to be called
> Resin.io until a few years ago.  Balena is a great fleet management and
> deployment platform for managing multiple IOT devices. We use it for many
> RPI implementations.  I highly recommend taking a few hours to learn how to
> deploy a device on their platform as once you start using it you won’t go
> back.  But my biggest hope is for one of you experts at OWFS to deploy OWFS
> via Balena onto a RPI3 with an i2c 1-wire hat so that you can share a
> solution on how to properly build a Dockerfile and python file for it that
> works.  I have been trying to figure it out for days and getting nowhere.
> I am trying to use pyownet which might be part of my problem but I don’t
> have to use that if you can think of a better way to do this. I would also
> like to stick to Python3 as Balena is dropping support for Python2 soon.
>
>
>
> I am sure Balena will be adopted by folks more and more moving forward so
> solving this would be a great investment in furthering the 1wire and owfs
> platform to be deployed in fleets.  In this situation, it is also going
> towards a good cause of helping endangered animals.
>
>
>
> Below is my dockerfile & python code which I just can’t get to work
> properly. I continue to get this error: pyownet.protocol.ConnError: [Errno
> 111] Connection refused
>
>
>
> This is the i2c device I am using:
> https://www.abelectronics.co.uk/kb/article/3/owfs-with-i2c-support-on-raspberry-pi
>
>
>
> Thanks so much,
>
>
>
> Greg
>
>
>
> ----------------------------------------
>
> DOCKERFILE CODE BELOW
>
> ----------------------------------------
>
> FROM balenalib/raspberrypi3-python:3.7.6
>
>
>
> ENV DEBIAN_FRONTEND=noninteractive
>
> ENV DEBCONF_NOWARNINGS yes
>
>
>
> RUN     apt-get update -y; \
>
>         apt-get upgrade -y; \
>
>         apt-get clean all
>
>
>
> RUN sudo apt-get update -y;\
>
>         apt-get install -qy apt-utils \
>
>         python3-pip \
>
>         python3 \
>
>         libtool \
>
>         python3-dev \
>
>         python3-smbus\
>
>         libtool \
>
>         rpi-update \
>
>         raspi-config \
>
>         owfs \
>
>         owserver \
>
>         ow-shell \
>
>         python-ow \
>
>         python3-rpi.gpio \
>
>         && apt-get clean && rm -rf /var/lib/apt/lists/*
>
>
>
> RUN sudo pip3 install setuptools --upgrade
>
>
>
> RUN sudo pip3 install --upgrade pip
>
>
>
> RUN sudo pip3 install pyownet
>
>
>
> RUN sed -i '20i\server: device=/dev/i2c-1' /etc/owfs.conf
>
> RUN sed -i 's/^server: FAKE = DS18S20,DS2405/#server: FAKE =
> DS18S20,DS2405/' /etc/owfs.conf
>
> RUN sed -i 's/^ftp: port = 2120/#ftp: port = 2120/' /etc/owfs.conf
>
>
>
> COPY . ./
>
>
>
> ENV INITSYSTEM on
>
>
>
> CMD modprobe i2c-dev && owserver -d /dev/i2c-
>
> CMD ["python3", "1wire_temp_test.py"]
>
>
>
> ----------------------------------------
>
> PYTHON CODE BELOW
>
> ----------------------------------------
>
> import time
>
> from pyownet import protocol
>
>
>
> temp_type = 'F'
>
> tc_1_mac = 'FF8AD3641402'  ### This is obviously my thermocouple so enter
> your own mac address here ###
>
>
>
> owproxy = protocol.proxy(host="localhost", port=4304)
>
> sensor_file_1 = '/28.' + tc_1_mac + '/temperature'
>
>
>
> def main():
>
>                 while True:
>
>                                 try:
>
>                                                 thetext =
> owproxy.read(sensor_file_1)
>
>                                                 heater_temp_1 =
> round((float(thetext[2:])*(9/5)+32),2)
>
>                                                 print ('SENSOR #1 =',
> heater_temp_1, temp_type)
>
>                                 except IOError:
>
>                                                 print ('SENSOR #1 READ
> FAIL')
>
>                                 time.sleep(10)
>
>
>
> if __name__ == '__main__':
>
>                 main()
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>

[Owfs-developers] Balena.io & OWFS

[Greg P. <gr...@L2...>]

Hi All,

I am new to the mailing list and am hoping someone out there might be able to help us.  We are currently working on a set of devices for monitoring endangered animal habitats and we need to try to read multiple 1wire temp sensor readings via RPI3. Specifically I am hoping to find someone with experience using OWFS on the Balena.io platform and Docker templates.  I am looking for an example of OWFS measuring 1wire thermocouples via i2c hat running on Balena.io via a Dockerfile? The key here is to get it to work on Balena via a Dockerfile.template with i2c enabled as that is how we will manage fleets of these devices.

For those of you who aren't familiar with Balena.io it used to be called Resin.io until a few years ago.  Balena is a great fleet management and deployment platform for managing multiple IOT devices. We use it for many RPI implementations.  I highly recommend taking a few hours to learn how to deploy a device on their platform as once you start using it you won't go back.  But my biggest hope is for one of you experts at OWFS to deploy OWFS via Balena onto a RPI3 with an i2c 1-wire hat so that you can share a solution on how to properly build a Dockerfile and python file for it that works.  I have been trying to figure it out for days and getting nowhere.  I am trying to use pyownet which might be part of my problem but I don't have to use that if you can think of a better way to do this. I would also like to stick to Python3 as Balena is dropping support for Python2 soon.

I am sure Balena will be adopted by folks more and more moving forward so solving this would be a great investment in furthering the 1wire and owfs platform to be deployed in fleets.  In this situation, it is also going towards a good cause of helping endangered animals.

Below is my dockerfile & python code which I just can't get to work properly. I continue to get this error: pyownet.protocol.ConnError: [Errno 111] Connection refused

This is the i2c device I am using: https://www.abelectronics.co.uk/kb/article/3/owfs-with-i2c-support-on-raspberry-pi

Thanks so much,

Greg

----------------------------------------
DOCKERFILE CODE BELOW
----------------------------------------
FROM balenalib/raspberrypi3-python:3.7.6

ENV DEBIAN_FRONTEND=noninteractive
ENV DEBCONF_NOWARNINGS yes

RUN     apt-get update -y; \
        apt-get upgrade -y; \
        apt-get clean all

RUN sudo apt-get update -y;\
        apt-get install -qy apt-utils \
        python3-pip \
        python3 \
        libtool \
        python3-dev \
        python3-smbus\
        libtool \
        rpi-update \
        raspi-config \
        owfs \
        owserver \
        ow-shell \
        python-ow \
        python3-rpi.gpio \
        && apt-get clean && rm -rf /var/lib/apt/lists/*

RUN sudo pip3 install setuptools --upgrade

RUN sudo pip3 install --upgrade pip

RUN sudo pip3 install pyownet

RUN sed -i '20i\server: device=/dev/i2c-1' /etc/owfs.conf
RUN sed -i 's/^server: FAKE = DS18S20,DS2405/#server: FAKE = DS18S20,DS2405/' /etc/owfs.conf
RUN sed -i 's/^ftp: port = 2120/#ftp: port = 2120/' /etc/owfs.conf

COPY . ./

ENV INITSYSTEM on

CMD modprobe i2c-dev && owserver -d /dev/i2c-
CMD ["python3", "1wire_temp_test.py"]

----------------------------------------
PYTHON CODE BELOW
----------------------------------------
import time
from pyownet import protocol

temp_type = 'F'
tc_1_mac = 'FF8AD3641402'  ### This is obviously my thermocouple so enter your own mac address here ###

owproxy = protocol.proxy(host="localhost", port=4304)
sensor_file_1 = '/28.' + tc_1_mac + '/temperature'

def main():
                while True:
                                try:
                                                thetext = owproxy.read(sensor_file_1)
                                                heater_temp_1 = round((float(thetext[2:])*(9/5)+32),2)
                                                print ('SENSOR #1 =', heater_temp_1, temp_type)
                                except IOError:
                                                print ('SENSOR #1 READ FAIL')
                                time.sleep(10)

if __name__ == '__main__':
                main()

Re: [Owfs-developers] Caching for I/O modules

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

Thanks Jan.

On 09/05/2020 20:14, Jan Kandziora wrote:
> Am 09.05.20 um 14:42 schrieb Mick Sulley:
>> I understand how caching works for temperature sensors, use of
>> simultaneous etc, but how do I/O modules work in that respect?
>>
>> I am particularly interested in DS2413. Is there any difference between
>> "owwrite /TestIO/PIO.A 1" and "owwrite /uncached/TestIO/PIO.A 1",
>>
> They both write to the chip. No difference.
>
>
>> similarly with reading, is it safer to use "owread
>> /uncached/TestIO/PIO.A" rather than "owread /TestIO/PIO.A"
>>
> Only reading /uncached will give you the current value the chip read
> each time. The cached one may be seconds old, depending on when you read
> it from the chip last time.
>
>> and is there
>> a performance hit?
>>
> Reading a cached value does not introduce any bus transfer.
>
> Kind regards
>
> 	Jan
>
>
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Caching for I/O modules

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

Am 09.05.20 um 14:42 schrieb Mick Sulley:
> I understand how caching works for temperature sensors, use of
> simultaneous etc, but how do I/O modules work in that respect?
>
> I am particularly interested in DS2413. Is there any difference between
> "owwrite /TestIO/PIO.A 1" and "owwrite /uncached/TestIO/PIO.A 1",
>
They both write to the chip. No difference.


> similarly with reading, is it safer to use "owread
> /uncached/TestIO/PIO.A" rather than "owread /TestIO/PIO.A"
>
Only reading /uncached will give you the current value the chip read
each time. The cached one may be seconds old, depending on when you read
it from the chip last time.

> and is there
> a performance hit?
>
Reading a cached value does not introduce any bus transfer.

Kind regards

	Jan

[Owfs-developers] Caching for I/O modules

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

I understand how caching works for temperature sensors, use of 
simultaneous etc, but how do I/O modules work in that respect?

I am particularly interested in DS2413. Is there any difference between 
"owwrite /TestIO/PIO.A 1" and "owwrite /uncached/TestIO/PIO.A 1", 
similarly with reading, is it safer to use "owread 
/uncached/TestIO/PIO.A" rather than "owread /TestIO/PIO.A" and is there 
a performance hit?

Thanks

Mick

Re: [Owfs-developers] Protocol Error Starting owserver

[Dennis P. <da...@be...>]

*Hi Jan,**
**
**Sorry, I thought I included that.*

# Sample configuration file for the OWFS suite for Debian GNU/Linux.
#
#
# This is the main OWFS configuration file. You should read the
# owfs.conf(5) manual page in order to understand the options listed
# here.

######################## SOURCES ########################
#
# With this setup, any client (but owserver) uses owserver on the
# local machine...
! server: server = localhost:4304
#
# ...and owserver uses the real hardware, by default fake devices
# This part must be changed on real installation
#server: FAKE = DS18S20,DS2405
#
# USB device: DS9490
server: device = /dev/ic2-1
#
# Serial port: DS9097
#server: device = /dev/ttyS1
server: device = /dev/ttyAMA0
#
# owserver tcp address
#server: server = 192.168.10.1:3131
#
# random simulated device
#server: FAKE = DS18S20,DS2405
#
######################### OWFS ##########################
#
mountpoint = /mnt/1wire
allow_other
#
####################### OWHTTPD #########################

http: port = 2121

####################### OWFTPD ##########################

ftp: port = 2120

####################### OWSERVER ########################

server: port = localhost:4304


On 5/5/2020 6:38 PM, Jan Kandziora wrote:
> Am 05.05.20 um 21:17 schrieb Dennis Putnam:
>> *Hi Jan,** ** **Here is the requested info:*
>>
>> *systemctl show owserver.service|grep ExecStart*
>>
>> ExecStart={ path=/usr/bin/owserver ; argv[]=/usr/bin/owserver -c
>> /etc/owfs.conf ; ignore_errors=no ; start_time=[Mon 2020-05-04
>> 17:17:17 EDT] ; stop_time=[Mon 2020-05-04 17:17:17 EDT] ; pid=485 ;
>> code=exited ; status=0 }
>>
> That means owserver reads /etc/owfs.conf for its configuration
> options. As I wrote, we also need to see the contents of that file.
>
>
>
>> *I'm not sure how to tell what adapter I'm using (not a hardware
>> guy) but I think I was told it is DS2480 as the busmaster and the
>> device is DS2413.*
>>
> You must find out for sure which busmaster you use, and if it is
> indeed a DS2480, at which RS232 port it is connected. The Raspi's
> internal one? Or one on an USB-RS232 adapter?
>
>
>
>
>> *cat /boot/config.txt*
>> # Uncomment some or all of these to enable the optional hardware
>> interfaces dtparam=i2c_arm=on
>>
> I²C is enabled which may mean the host might use an DS2482
> hostadapter. W1 on GPIO is not enabled so it can't be that hostadapter.
>
> Kind regards
>
> 	Jan
>
>
>
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Protocol Error Starting owserver

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

Am 05.05.20 um 21:17 schrieb Dennis Putnam:
> *Hi Jan,** ** **Here is the requested info:*
>
> *systemctl show owserver.service|grep ExecStart*
>
> ExecStart={ path=/usr/bin/owserver ; argv[]=/usr/bin/owserver -c
> /etc/owfs.conf ; ignore_errors=no ; start_time=[Mon 2020-05-04
> 17:17:17 EDT] ; stop_time=[Mon 2020-05-04 17:17:17 EDT] ; pid=485 ;
> code=exited ; status=0 }
>
That means owserver reads /etc/owfs.conf for its configuration
options. As I wrote, we also need to see the contents of that file.



> *I'm not sure how to tell what adapter I'm using (not a hardware
> guy) but I think I was told it is DS2480 as the busmaster and the
> device is DS2413.*
>
You must find out for sure which busmaster you use, and if it is
indeed a DS2480, at which RS232 port it is connected. The Raspi's
internal one? Or one on an USB-RS232 adapter?




> *cat /boot/config.txt*
>>
> # Uncomment some or all of these to enable the optional hardware
> interfaces dtparam=i2c_arm=on
>
I²C is enabled which may mean the host might use an DS2482
hostadapter. W1 on GPIO is not enabled so it can't be that hostadapter.

Kind regards

	Jan

Re: [Owfs-developers] Protocol Error Starting owserver

[Dennis P. <da...@be...>]

*Hi Jan,**
**
**Here is the requested info:*

*systemctl show owserver.service|grep ExecStart*

ExecStart={ path=/usr/bin/owserver ; argv[]=/usr/bin/owserver -c
/etc/owfs.conf ; ignore_errors=no ; start_time=[Mon 2020-05-04 17:17:17
EDT] ; stop_time=[Mon 2020-05-04 17:17:17 EDT] ; pid=485 ; code=exited ;
status=0 }

*I'm not sure how to tell what adapter I'm using (not a hardware guy)
but I think I was told it is DS2480 as the busmaster and the device is
DS2413.*

*cat /boot/config.txt*

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if
console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's
size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio
work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference,
blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
#dtoverlay=w1-gpio,gpiopin=20

# NOOBS Auto-generated Settings:
#hdmi_force_hotplug=1

On 5/3/2020 9:52 PM, Jan Kandziora wrote:
> Am 03.05.20 um 23:55 schrieb Dennis Putnam:
>> I've installed owfs on my Pi4 but cannot start owserver. I get the
>> following in journalctl:
>>
>> -- Defined-By: systemd -- Support: https://www.debian.org/support
>>
>> [...]
>>
> That log is not too helpful. We need the output of
>
> $ systemctl show owserver.service|grep ExecStart
> $ cat /etc/owfs.conf
>
> Also, we need to know what Onewire hostadapter you use. Is it the
> bitbanging host on GPIO4? Is it an I²C connected DS2482 or similar? If
> yes, also show us
>
> $ cat /boot/config.txt
>
> Kind regards
>
> 	Jan
>
>
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Protocol Error Starting owserver

[Dennis P. <da...@be...>]

Hi Alex,

I don't see anything like that. The /etc/init.d/owserver specifies the
right config file and I don't see any port specified.

On 5/3/2020 10:43 PM, Mail Lists wrote:
> Hi Dennis,
>
> I’ve just been through all this myself a few days ago and I did a
> bunch of different things to get owserver, owhttpd server and PHP /
> Python network / api bindings to work. I had to build from source to
> fix an issue with the specific 1-Wire chips I use.
>
> I think you’ll find it might be an issue with the user that the
> service is being started as and having permission to bind to a TCP
> port < 1024.
>
> Also I noticed that the command line for the owserver config in the
> service definition seemed to default to using:
>
> -w 1 (from memory) for the in-kernel bit-bashed 1-Wire support.
>
> I changed this to be: -c /etc/owfs.conf so that it picked up all its
> settings from the config file
>
> Check those things and see if it makes a difference else come back
> here with some more questions and I can check my RPi 4 at help after work
>
> HTH
>
> Alex Shepherd
>
>
>  
>
>
>> On 4/05/2020, at 9:55 AM, Dennis Putnam <da...@be...
>> <mailto:da...@be...>> wrote:
>>
>> I've installed owfs on my Pi4 but cannot start owserver. I get the
>> following in journalctl:
>>
>> -- Defined-By: systemd
>> -- Support: https://www.debian.org/support
>> -- 
>> -- A stop job for unit owserver.service has finished.
>> -- 
>> -- The job identifier is 1564 and the job result is done.
>> May 03 10:58:37 raspberrypi systemd[1]: owserver.service: Start
>> request repeated too quickly.
>> May 03 10:58:37 raspberrypi systemd[1]: owserver.service:*Failed with
>> result 'protocol'.*
>> -- Subject: Unit failed
>> -- Defined-By: systemd
>> -- Support: https://www.debian.org/support
>> -- 
>> -- The unit owserver.service has entered the 'failed' state with
>> result 'protocol'.
>> May 03 10:58:37 raspberrypi systemd[1]: Failed to start Backend
>> server for 1-wire control.
>> -- Subject: A start job for unit owserver.service has failed
>> -- Defined-By: systemd
>> -- Support: https://www.debian.org/support
>> -- 
>> -- A start job for unit owserver.service has finished with a failure.
>> -- 
>> -- The job identifier is 1564 and the job result is failed.
>> May 03 10:58:51 raspberrypi sudo[1632]:       pi : TTY=pts/0 ;
>> PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -xe
>> May 03 10:58:51 raspberrypi sudo[1632]: pam_unix(sudo:session):
>> session opened for user root by (uid=0)
>>
>> I have not idea what that means. Can someone help me get owserver
>> started? TIA.
>> _______________________________________________
>> Owfs-developers mailing list
>> Owf...@li...
>> <mailto:Owf...@li...>
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
>
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Protocol Error Starting owserver

[Mail L. <li...@aj...>]

Hi Dennis,

I’ve just been through all this myself a few days ago and I did a bunch of different things to get owserver, owhttpd server and PHP / Python network / api bindings to work. I had to build from source to fix an issue with the specific 1-Wire chips I use.

I think you’ll find it might be an issue with the user that the service is being started as and having permission to bind to a TCP port < 1024.

Also I noticed that the command line for the owserver config in the service definition seemed to default to using:

	-w 1 (from memory) for the in-kernel bit-bashed 1-Wire support.

I changed this to be: -c /etc/owfs.conf so that it picked up all its settings from the config file

Check those things and see if it makes a difference else come back here with some more questions and I can check my RPi 4 at help after work

HTH

Alex Shepherd


 


> On 4/05/2020, at 9:55 AM, Dennis Putnam <da...@be...> wrote:
> 
> I've installed owfs on my Pi4 but cannot start owserver. I get the following in journalctl:
> 
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support <https://www.debian.org/support>
> -- 
> -- A stop job for unit owserver.service has finished.
> -- 
> -- The job identifier is 1564 and the job result is done.
> May 03 10:58:37 raspberrypi systemd[1]: owserver.service: Start request repeated too quickly.
> May 03 10:58:37 raspberrypi systemd[1]: owserver.service: Failed with result 'protocol'.
> -- Subject: Unit failed
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support <https://www.debian.org/support>
> -- 
> -- The unit owserver.service has entered the 'failed' state with result 'protocol'.
> May 03 10:58:37 raspberrypi systemd[1]: Failed to start Backend server for 1-wire control.
> -- Subject: A start job for unit owserver.service has failed
> -- Defined-By: systemd
> -- Support: https://www.debian.org/support <https://www.debian.org/support>
> -- 
> -- A start job for unit owserver.service has finished with a failure.
> -- 
> -- The job identifier is 1564 and the job result is failed.
> May 03 10:58:51 raspberrypi sudo[1632]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -xe
> May 03 10:58:51 raspberrypi sudo[1632]: pam_unix(sudo:session): session opened for user root by (uid=0)
> 
> I have not idea what that means. Can someone help me get owserver started? TIA.
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Protocol Error Starting owserver

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

Am 03.05.20 um 23:55 schrieb Dennis Putnam:
> I've installed owfs on my Pi4 but cannot start owserver. I get the
> following in journalctl:
>
> -- Defined-By: systemd -- Support: https://www.debian.org/support
>
> [...]
>
That log is not too helpful. We need the output of

$ systemctl show owserver.service|grep ExecStart
$ cat /etc/owfs.conf

Also, we need to know what Onewire hostadapter you use. Is it the
bitbanging host on GPIO4? Is it an I²C connected DS2482 or similar? If
yes, also show us

$ cat /boot/config.txt

Kind regards

	Jan

[Owfs-developers] Protocol Error Starting owserver

[Dennis P. <da...@be...>]

I've installed owfs on my Pi4 but cannot start owserver. I get the
following in journalctl:

-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit owserver.service has finished.
-- 
-- The job identifier is 1564 and the job result is done.
May 03 10:58:37 raspberrypi systemd[1]: owserver.service: Start request
repeated too quickly.
May 03 10:58:37 raspberrypi systemd[1]: owserver.service:*Failed with
result 'protocol'.*
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit owserver.service has entered the 'failed' state with result
'protocol'.
May 03 10:58:37 raspberrypi systemd[1]: Failed to start Backend server
for 1-wire control.
-- Subject: A start job for unit owserver.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit owserver.service has finished with a failure.
-- 
-- The job identifier is 1564 and the job result is failed.
May 03 10:58:51 raspberrypi sudo[1632]:       pi : TTY=pts/0 ;
PWD=/home/pi ; USER=root ; COMMAND=/bin/journalctl -xe
May 03 10:58:51 raspberrypi sudo[1632]: pam_unix(sudo:session): session
opened for user root by (uid=0)

I have not idea what that means. Can someone help me get owserver
started? TIA.

Re: [Owfs-developers] Surplus Items

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

How about £40 for the 3 DS9097Us ?

On 27/04/2020 20:09, Michael Hughes wrote:
> On Mon, 27 Apr 2020 19:22:53 +0100
> Mick Sulley <mi...@su...> wrote:
>
>> Greeting.  I have just had a very overdue tidy up and as a result I
>> have some items which are surplus to requirements.
>>
>> 2 X Hobbyboards 8 channel I/O v2.0  (I have soft copy of the
>> schematic and user manual)
>> 2 X Maxim DS9097U-009   Universal 1-Wire COM Port Adapter (with id
>> chip) 1 X Maxim DS9097U-S09   Universal 1-Wire COM Port Adapter
>> (without id chip) 1 X Embedded Data Systems HA7E   ASCII 1-Wire Host
>> Adapter 3 X Embedded Data Systems D2P    2 Channel Digital I/O 1-Wire
>> Card (solder connections)
>> 3 X Embedded Data Systems D2PC    2 Channel Digital I/O 1-Wire Card
>> (screw terminals)
>>
>> All are used but I believe that they are in working order.
>>
>> I intend to put them all on eBay but thought I would offer them here
>> first.  Anyone interested?
>>
>> Mick
> How much do you want for the DS9097Us (all 3)?
>
>

Re: [Owfs-developers] Surplus Items

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

On Mon, 27 Apr 2020 19:22:53 +0100
Mick Sulley <mi...@su...> wrote:

> Greeting.  I have just had a very overdue tidy up and as a result I
> have some items which are surplus to requirements.
> 
> 2 X Hobbyboards 8 channel I/O v2.0  (I have soft copy of the
> schematic and user manual)
> 2 X Maxim DS9097U-009   Universal 1-Wire COM Port Adapter (with id
> chip) 1 X Maxim DS9097U-S09   Universal 1-Wire COM Port Adapter
> (without id chip) 1 X Embedded Data Systems HA7E   ASCII 1-Wire Host
> Adapter 3 X Embedded Data Systems D2P    2 Channel Digital I/O 1-Wire
> Card (solder connections)
> 3 X Embedded Data Systems D2PC    2 Channel Digital I/O 1-Wire Card 
> (screw terminals)
> 
> All are used but I believe that they are in working order.
> 
> I intend to put them all on eBay but thought I would offer them here 
> first.  Anyone interested?
> 
> Mick

How much do you want for the DS9097Us (all 3)?


-- 
Michael D Hughes                            Loghome living is the best!

Mi...@Th...

Re: [Owfs-developers] Surplus Items

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

Hello!
Yes me. What's involved?
-----
Gregg C Levine gre...@gm...
"This signature fought the Time Wars, time and again."

On Mon, Apr 27, 2020 at 2:23 PM Mick Sulley <mi...@su...> wrote:
>
> Greeting.  I have just had a very overdue tidy up and as a result I have
> some items which are surplus to requirements.
>
> 2 X Hobbyboards 8 channel I/O v2.0  (I have soft copy of the schematic
> and user manual)
> 2 X Maxim DS9097U-009   Universal 1-Wire COM Port Adapter (with id chip)
> 1 X Maxim DS9097U-S09   Universal 1-Wire COM Port Adapter (without id chip)
> 1 X Embedded Data Systems HA7E   ASCII 1-Wire Host Adapter
> 3 X Embedded Data Systems D2P    2 Channel Digital I/O 1-Wire Card
> (solder connections)
> 3 X Embedded Data Systems D2PC    2 Channel Digital I/O 1-Wire Card
> (screw terminals)
>
> All are used but I believe that they are in working order.
>
> I intend to put them all on eBay but thought I would offer them here
> first.  Anyone interested?
>
> Mick
>
>
>
> _______________________________________________
> Owfs-developers mailing list
> Owf...@li...
> https://lists.sourceforge.net/lists/listinfo/owfs-developers