Re: [Owfs-developers] Protocol Error Starting owserver

2020-05-06 Thread Dennis Putnam 
*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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers



signature.asc
Description: OpenPGP digital signature
___
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Protocol Error Starting owserver

2020-05-05 Thread Jan Kandziora 
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Protocol Error Starting owserver

2020-05-05 Thread 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 }

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



signature.asc
Description: OpenPGP digital signature
___
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Protocol Error Starting owserver

2020-05-05 Thread Dennis Putnam 
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 > > 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
>> [email protected]
>> 
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
>
> ___
> Owfs-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers



signature.asc
Description: OpenPGP digital signature
___
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Protocol Error Starting owserver

2020-05-03 Thread Mail Lists 
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  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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

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

Re: [Owfs-developers] Protocol Error Starting owserver

2020-05-03 Thread Jan Kandziora 
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers