Thanks for the suggestions, Martin. I'll be eager to hear any more ideas
you have after you can check your home system. In the meantime, I'll check
about ftdi drivers...
On Mon, Jun 10, 2013 at 2:03 PM, Martin Patzak (GMX)
<[email protected]>wrote:
> I am running successfully and without hitches (like there were in the
> beginning, that is summer last year) for 4 months continously (without
> reboot) my home heating system, but I am not home now, so I cannot check my
> settings.
>
> I do faintly remember, that I had to install some driver for ftdi, I am
> not sure if this is still required. If you can wait for the weekend, I can
> check my setup and config and give further help,
>
> Martin
>
> P.S. read some comments I made below...
>
>
> On 06/10/2013 02:36 PM, Mark Phillips wrote:
>
> Thanks for the quick responses. I am running everything as root, I have
> created the mount point directory, and I am using --foreground, but
> owserver still exits immediately with no output.
>
> Specifically, here's my /etc/owfs.conf (with comments removed to keep
> this message shorter):
>
> error_print = 2
>
> error_level = 9
>
> ! server: server = localhost:4304
> server: usb = all
> mountpoint = /mnt/1wire
> allow_other
> http: port = 2121
> ftp: port = 2120
> server: port = localhost:4304
>
>
> And here's my mount point directory:
>
> root@raspberrypi:~/ow# ls -ld /mnt/1wire
> drwxr-xr-x 2 root root 4096 Jun 9 22:53 /mnt/1wire
>
> to run owfs without sudo, you should make the 1wire directory your user
> and group
>
>
> When I run owserver with the following command, it exits immediately
> with no output.
>
> root@raspberrypi:~/ow# owserver --foreground --error_print=2
> --error_level=9 -c /etc/owfs.conf
> root@raspberrypi:~/ow#
>
>
> I've also checked the log files in /var/log (syslog, messages), and
> there are no owserver-related messages in them.
>
> yeah, I think I was wrong earlier, when I thought foreground is doing the
> trick - foreground is only not disconnecting from the terminal... sorry
>
>
> In case it's relevant, here are the messages that show up in
> /var/log/kern.log when I first plug the LinkUSB into one of the Pi's USB
> ports, showing that system is recognizing the LinkUSB:
>
> Jun 10 08:26:53 raspberrypi kernel: [ 1531.321917] usb 1-1.3: USB
> disconnect, device number 4
> Jun 10 08:26:53 raspberrypi kernel: [ 1531.322438] ftdi_sio ttyUSB0:
> FTDI USB Serial Device converter now disconnected from ttyUSB0
> Jun 10 08:26:53 raspberrypi kernel: [ 1531.322518] ftdi_sio 1-1.3:1.0:
> device disconnected
> Jun 10 08:27:02 raspberrypi kernel: [ 1540.775083] usb 1-1.3: new
> full-speed USB device number 5 using dwc_otg
> Jun 10 08:27:02 raspberrypi kernel: [ 1540.883165] usb 1-1.3: New USB
> device found, idVendor=0403, idProduct=6001
> Jun 10 08:27:02 raspberrypi kernel: [ 1540.883197] usb 1-1.3: New USB
> device strings: Mfr=1, Product=2, SerialNumber=3
> Jun 10 08:27:02 raspberrypi kernel: [ 1540.883215] usb 1-1.3: Product:
> FT232R USB UART
> Jun 10 08:27:02 raspberrypi kernel: [ 1540.883227] usb 1-1.3:
> Manufacturer: FTDI
> Jun 10 08:27:02 raspberrypi kernel: [ 1540.883239] usb 1-1.3:
> SerialNumber: A900Y1QD
> Jun 10 08:27:02 raspberrypi kernel: [ 1540.899470] ftdi_sio 1-1.3:1.0:
> FTDI USB Serial Device converter detected
> Jun 10 08:27:02 raspberrypi kernel: [ 1540.899637] usb 1-1.3: Detected
> FT232RL
> Jun 10 08:27:02 raspberrypi kernel: [ 1540.899655] usb 1-1.3: Number
> of endpoints 2
> Jun 10 08:27:02 raspberrypi kernel: [ 1540.899670] usb 1-1.3: Endpoint
> 1 MaxPacketSize 64
> Jun 10 08:27:02 raspberrypi kernel: [ 1540.899683] usb 1-1.3: Endpoint
> 2 MaxPacketSize 64
> Jun 10 08:27:02 raspberrypi kernel: [ 1540.899696] usb 1-1.3: Setting
> MaxPacketSize 64
> Jun 10 08:27:02 raspberrypi kernel: [ 1540.900858] usb 1-1.3: FTDI USB
> Serial Device converter now attached to ttyUSB0
>
> again, I can check that on the weekend
>
>
> Interestingly, if I change the line "server: usb = all" in
> /etc/owfs.conf to "server: FAKE = DS18S20,DS2405", the owserver command
> above does not exit --- the process seems to run, but I still get no output
> on stdout, stderr, or in the log files.
>
> Also, when I run owserver with "--help", it does print the help message,
> which shows that the owserver program is definitely installed and runable:
>
> root@raspberrypi:~/ow# owserver --help
> 1-WIRE access programs by Paul H Alfille and others.
>
> Syntax: owserver [options] device clientport
>
> Help resources:
> owserver --help This page
> owserver --help=device Bus master device options
> owserver --help=error List of error return codes
> owserver --help=program Program services (mountpoint, port)
> owserver --help=cache Cache and communication timing
> owserver --help=job Job control and debugging
> owserver --help=temperature Temperature scale and device format
> options
>
> man owserver man page for this program
> and man pages for individual 1-wire devices e.g. 'man DS2409'
>
> Copyright 2003-8 GPLv2 by Paul Alfille. See http://www.owfs.org for
> support, downloads
>
>
> Do you have any additional suggestions about what could be wrong? I
> don't understand why I am not seeing any error output at all.
>
> Thanks again!
>
> --Mark
>
>
>
>
> On Mon, Jun 10, 2013 at 5:55 AM, Martin Patzak (GMX) <[email protected]
> > wrote:
>
>> error messages go to syslog, unless you specify --foreground (I hope
>> its written right, check the man page please), in which case you get all
>> message directly to the terminal and the terminal stays connected to the
>> daemon.
>> error-level=9 delivers a LOT of messages! Try a lower number like 2 or 3
>> to get the essential messages.
>>
>> Martin
>>
>>
>> On 06/10/2013 05:53 AM, Mark Phillips wrote:
>>
>> Hi,
>>
>> I'm new to owfs and am trying to use it with a LinkUSB and two
>> temperature sensors on a Raspberry Pi. I've gotten the owfs package
>> installed via "apt-get install owfs", and I edited /etc/owfs.conf according
>> to some examples I've found on the web. But when I try to run either owfs
>> or owserver, both programs terminate with no error messages. I've tried
>> setting error_level=9 in /etc/owfs.conf, and also passing "--error_level=9"
>> on the command line, to no avail.
>>
>> Can someone give me a tip as to how I can get owserver/owfs to give me
>> some error output so that I can get some clues as to what is going wrong?
>>
>> Thanks!
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> How ServiceNow helps IT people transform IT departments:
>> 1. A cloud service to automate IT design, transition and operations
>> 2. Dashboards that offer high-level views of enterprise services
>> 3. A single system of record for all IT
>> processeshttp://p.sf.net/sfu/servicenow-d2d-j
>>
>>
>>
>> _______________________________________________
>> Owfs-developers mailing
>> [email protected]https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>>
>>
>> ------------------------------------------------------------------------------
>> How ServiceNow helps IT people transform IT departments:
>> 1. A cloud service to automate IT design, transition and operations
>> 2. Dashboards that offer high-level views of enterprise services
>> 3. A single system of record for all IT processes
>> http://p.sf.net/sfu/servicenow-d2d-j
>> _______________________________________________
>> Owfs-developers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
>>
>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT
> processeshttp://p.sf.net/sfu/servicenow-d2d-j
>
>
>
> _______________________________________________
> Owfs-developers mailing
> [email protected]https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Owfs-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
