Has anybody used Jerry Scharf's python script recently?
I changed the import psycopg to import psycopg2
and ow.init to /dev/ttyUSB0.
The script runs but doesn't read any sensors.
outputs "sensors read = 0 " on each loop.
Any ideas out there?
Perhaps Jerry could provide insight if he is out there?
Am 03.02.2016 um 19:59 schrieb Dean Waldow:
>
> I don’t think libusb-1.0 is standard in el capitan but I believe
> MacPorts has that in their ports. The main issue may be the location
> of the libs from MacPorts versus the where owfs expects to find
> them?
>
./configure looks at all places where
Thanks Jan!
>> I am curious if owfs should be able to be installed on OSX? It seems
>> that it is intended to be installed on OSX from what I have read
>> onine perhaps with the exception of the fuse file system.
>>
> Besides owfs and core owlib, all programs use plain TCP sockets, so they
> sho
Am 03.02.2016 um 19:20 schrieb Radoslav Chovan:
> Hi,
> this is my current owshell.h
>
> #define OWSHELL_H
> #include
> #include
> #include
> #include "config.h"
> #include "owfs_config.h"
>
> I have run again configure and compile.
>
> I see same error:
>
> [...]
>
In that case, our configu
Hi,
this is my current owshell.h
#define OWSHELL_H
#include
#include
#include
#include "config.h"
#include "owfs_config.h"
I have run again configure and compile.
I see same error:
make[4]: Entering directory '/home/wsdadm/owfs-3.1p1/module/owshell/src/c'
gcc -DHAVE_CONFIG_H -I. -I../../../.
Am 03.02.2016 um 18:36 schrieb Dean Waldow:
>
> I am curious if owfs should be able to be installed on OSX? It seems
> that it is intended to be installed on OSX from what I have read
> onine perhaps with the exception of the fuse file system.
>
Besides owfs and core owlib, all programs use plain
Greetings,
I hope this is not too much of a newbie question and this list may be more
focused on development only...
I have used owfs in the past on redhat and centos but would really like to put
owfs on an OSX box. About a month ago, I spent a fair bit of time trying to
compile / install ow
Am 03.02.2016 um 17:44 schrieb Stefano Miccoli:
>
>> On 03 Feb 2016, at 16:29, Jan Kandziora wrote:
>>
>> Ah, yes, documentation is sparse. But I don't think manpages help much,
>> being scattered is their nature.
>
> I suggested a man page because it is the only documentation that is bundled
>
> On 03 Feb 2016, at 16:29, Jan Kandziora wrote:
>
> Ah, yes, documentation is sparse. But I don't think manpages help much,
> being scattered is their nature.
I suggested a man page because it is the only documentation that is bundled
with the SW itself.
> I'm up to write a recipe book with
Am 03.02.2016 um 09:53 schrieb Stefano Miccoli:
> OK I agree… mine was a misguided suggestion (due to the lack of
> understanding of what a write to /simultaneous/temperature actually
> does.)
>
> If I got it right, everything boils down to these points.
>
> - By simultaneous conversion, we mean
Agreed. My code sets simultaneous after reading all the values, then
carries on doing all its control stuff, then when it gets back to
reading again all the values are there. Having a simultaneous block
would just introduce a delay for no benefit.
On 03/02/16 07:00, Johan Ström wrote:
+1, I'
OK I agree… mine was a misguided suggestion (due to the lack of understanding
of what a write to /simultaneous/temperature actually does.)
If I got it right, everything boils down to these points.
- By simultaneous conversion, we mean a broadcast that tells all sensors to
start a temperature co
12 matches
Mail list logo
