ed help from the devs ... PPUL ;)))
regards,
marcus.
>
> Servus,
> Martin
>
>
> On 07/25/17 12:32, Marcus Priesch wrote:
>> Hello Martin,
>>
>>
>>> ... /same lines//repeat a while/
>>> DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.
Hello Martin,
> ... /same lines//repeat a while/
> DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.00 seconds
> DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
> DEBUG: ow_tcp_read.c:(63) attempt 1 bytes Time: 1.00 seconds
> DEBUG: ow_tcp_read.c:(113) read: 1 - 0 = 1
> DEBUG:
Dear All,
i just read the wohle thread, well there are of course thousand ways to
make sensors wireless ;)
According to 6lowpan, i would like to mention the Open Source Domotics
Group where i am member ;)
Basically the OSD-Groups aims to provide open and standards compliant
domotic solutions.
THE 3rd-party python owfs wrapper ... ;)
http://priesch.co.at/pyowfs
regards,
mexx.
ps: sorry, couldn't resist ;)
On 2013-12-10 07:07, m...@box.li wrote:
You can check the 1wire plugin of smarthome.py
Regards
Am 10.12.2013 00:49 schrieb Colin Reese colin.re...@gmail.com:
kicks owserver out. I do not know the syntax, but you should make
owpython access owserver on port 4303 too.
... -s serverIP:4304
regards,
marcus.
--
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid
Dear List,
i wonder if anyone has ever played around with this device:
http://cel-mar.pl/en/addressable_rs485rs422_1wire_m401wa.htm
or even had success in using it with owfs ...
it basically has a DS2480B behind a microcontroller which handles
the communication (and adressing of the
Dear all,
i just submitted a new version of pyowfs which introduces caching to
speed up searching on larger 1wire trees ...
results to .get are cached (which is also used by .find
the timeout can be set in pyowfs.libcapi.CACHE_MAX_AGE and defaults to
30 seconds.
when issuing a .put the cached
why not one of those ?!?
http://www.fuchs-shop.com/download/MultiSensor_Manual_V091028.pdf
this page is from germany but you should be able to get these anywhere else ...
regards,
marcus
Peter Hollenbeck pwhb...@gmail.com schrieb:
I don't really understand why that works, but I could
Hi,
you could also try pyowfs ... would be interesting if it works on win32
though ;)
regards,
marcus.
On 2013-05-27 11:03, Nitish Jha wrote:
Hi
i tried using the ownet interface but i get this error when i try to get
a list of the devices. (I m using the fake devices option in owserver)
Hello Joe,
thanks for your interest in pyowfs ;)
the .get() and .put() methods can only access attributes of a sensor
object (the leaves in the tree). To access a specific Sensor by id you
have to use the .find() method of the connection. Obviously you should
also check if the sensor actually
now 23:20).
--
Regards
Joe P.
On 18/04/13 22:18, Marcus Priesch wrote:
Hello Joe,
thanks for your interest in pyowfs ;)
the .get() and .put() methods can only access attributes of a sensor
object (the leaves in the tree). To access a specific Sensor by id
you
have to use the .find
Hello Attila,
you could also try http://priesch.co.at/pyowfs
with it it should be possible to get any entry
in the owfs tree ...
interesting though that the 8bit value gets calculated differently ...
i also fiddled around with the ds2450 some day and found out that anything
below 8bit is
upgraded from an old debian to ubuntu precise, the bad value
was something like 80degres.
It is now 0 degres, and this triggers my HVAC.
I need a way to detect a wrong value.
None would be ok for me.
On Tue, Sep 18, 2012 at 7:54 PM, Marcus Priesch mar...@priesch.priv.at
wrote:
res
Hello Sophana,
i dont know if it would help the gil issue, but you could try pyowfs
(easy_install pyowfs) wihich basically is a ctypes wrapper around
libow.
starting a owserver instance and then talking via different pyowfs
Connections (one in each thread) to the owserver should not block the
Made my wrapper to its capi, and it looks MUCH better.
Threads seem responsive again.
Hey, glad to hear that ;)
Are there exceptions thrown when a sensor read goes wrong?
according to libcapi.py's get and put:
def get (self, path) :
buf_p = ctypes.POINTER (ctypes.c_char) ()
and send it, it get back to not marked...
maybe a problem with owhttp url parsing algorithm???
2011/12/21 Marcus Priesch mar...@priesch.priv.at:
Hi Guys,
i have a netgear router (WNDR3700v2 running OpenWRT Backfire
10.03.1
Hello William,
Am Dienstag, den 15.03.2011, 17:27 -1000 schrieb William Brown:
Should owserver and owhttpd be displayed in the System Monitor app
(gnome-system-monitor) in Ubuntu? Mine are not and I would like them
too. Any suggestions.
yes, they should - try displaying all processes ...
Hi There,
Am Samstag, den 05.02.2011, 01:10 + schrieb Mick Sulley:
My sensors are powered, the temperature sensors are a mix of DS18B20 and
DS18S20, I just used DS1820 as a generic term.
Is there a way to use simultaneous conversion with pyowfs?
import pyowfs
c =
I think the solution should be that the user has to convert the message
form whatever charset she uses to the charset needed by the lcd - and
definitely *NOT* support all available charsets in owfs !!!
anyhow - if the user isnt aware of different charsets - she would also
not know what message_*
Hi Mick,
+ you could take a look at the dmesg output for any errors on your
serial port
+ try reloading the serial modules (ist it usb-serial?)
+ are you using owserver - and connecting remotely ? - then restarting
owserver could also help
+ other things would involve tyring owhttpd and
Hi Rob,
i have a custom board with *one* ds2406 (with 1kb eprom) and some other
1wire components (2450 adc, 2408 pio) - to identify such a board with
its companion devices, i store the 1wire ids of the companion devices
into the ds2406' memory (alongside with some other info like pio
Hi Paul,
thanks for the new release - although beeing a bit late with my email, i
get the following when compiling under gentoo:
libtool: compile: i486-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I.
-I../../../../src/include -I../include -fexceptions -Wall -W -Wundef
-Wshadow -Wpointer-arith -Wcast-qual
Am Donnerstag, den 13.01.2011, 11:35 -0900 schrieb Joshua J. Kugler:
On Thursday 13 January 2011, Marcus Priesch elucidated thus:
Hi Paul,
thanks for the new release - although beeing a bit late with my
email, i get the following when compiling under gentoo:
libtool: compile: i486-pc
Am Donnerstag, den 13.01.2011, 14:06 -0900 schrieb Joshua J. Kugler:
On Thursday 13 January 2011, Marcus Priesch elucidated thus:
hmmm ... what has bash to do with all this ? - the semicolon *is*
missing in the source ... i added a patch to my gentoo ebuild and now
everything is fine
Am Sonntag, den 12.12.2010, 19:59 -0700 schrieb AGSCalabrese:
I would very much like to see a touch interface . even if it is a single
contact touch.
Next best would be rotary knobs to set values
or rotate and click ;)
and ... rotate with latching - i dont know the exact verb - its
Hi Paul,
+ in my application i am using pyowfs ...
+ inside pyowfs i load the libowcapi via ctypes ...
but if i have two adapters connected, initialisation of a newly imported
libowcapi resets all other libowcapi instances to the same
interface ... which is definitely not what i want ... :(
Hi Paul,
thanks for your answer ...
Am Montag, den 13.12.2010, 14:25 -0500 schrieb Paul Alfille:
A single instance of libowcapi can bind to any number of 1-wire
adapters.
yes, but only on startup - you cant add/delete adapters (at least
usb-serial ones - afaik ?!?)
I don't know of
Am Montag, den 13.12.2010, 09:43 -0900 schrieb Joshua J. Kugler:
There is also OW Python where you can access your sensors directly with
Python, instead of reading off the file system.
import ow
ow.init(val) # where val is 'u' for USB, or the server address
sensor =
Hi Wil,
Am Montag, den 08.11.2010, 02:06 -1000 schrieb William Brown:
Since upgrading to Ubuntu 10.04 I have had the following problem using
rs232 to usb serial adapter (HL-340).
so you are not using a LinkUSB ... maybe things are different for this
kind of adapter ... what 1w-master are you
Dear all,
i found an endless loop in the Slurp function (ow_slurp.c) ...
reproduceable simply by unplugging the LinkUSB when owfs is using the
device - also when there is no traffic ...
adding these lines at the end solves it for me ...
if (ignore_result == 0) {
Hi Rob,
this sounds like a great idea !
do you mind implementing this as a standalone owfs diagnose tool ?!?!
as i think it would be much easier to implement it (or at least start
building up a prototype) in something more high level to web-apps than C
currently is (e.g. python) besides this -
) serial port: /dev/ttyUSB0
On 10/28/2010 04:18 AM, Marcus Priesch wrote:
Hi there,
also LinuUSB detection and communication is currently not working
out-of-the box ... i posted a patch for 2.8p2.
it is related to enabling rts/cts handshake - but maybe this is
dependent on the kernel
Am Freitag, den 29.10.2010, 01:30 -1000 schrieb William Brown:
It looks like the patch has been applied in 2.8p2 or did I miss
something?
no, the lines you posted are ok - take a look at the patch - the changes
are in owfs-2.8p2/module/owlib/src/c/ow_link.c:
only use flow_hard and flush buffer
Hi there,
also LinuUSB detection and communication is currently not working
out-of-the box ... i posted a patch for 2.8p2.
it is related to enabling rts/cts handshake - but maybe this is
dependent on the kernel version running (and the ftdi driver) ?!?! - for
me it only works when i enable
Hi Mick,
great to here from you again ;)
Traceback (most recent call last):
File ./list_all.py, line 194, in module
init_1_wire() # initialise the 1-wire network and get the sensor
id's
File ./list_all.py, line 43, in init_1_wire
for s in connection.find () :
File
Dear List,
i finally debugged why the LINK isnt working - in --LINK mode ...
on current ubuntu :
p...@pr-laptop:~$ uname -a
Linux pr-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 16 19:48:22 UTC 2010
i686 GNU/Linux
two things:
1.) it definitely needs RTS turned on !
2.) upon sending a
Hi Guys,
i just found one ;) - at least i think the behaviour should be
different ...
i have a system with either ds2490 or LinkUSB ...
so i want autoprobing (ds2490 missing, LinkUSB plugged in):
import ow
ow.init (u)
Traceback (most recent call last):
File stdin, line 1, in module
Oh, sorry, i missed the most important part:
owfs-2.8p2 on gentoo 2.6.24.7, python 2.5.4 ...
but i doubt it makes a difference ... ;)
regards,
marcus.
--
Start uncovering the many advantages of virtual appliances
Hi Mick,
i just digged in my sources ... ;)
you need to set PIO.A to 0 (or 1?) to cunduct the output (it's open
drain afaik) and set PIO.A to 1 (or 0?) to release the output ...
latch, flipflop and sensed are all for reading the inputs and detecting
if there have been and edges there ...
to
Hi Joshua,
Am Freitag, den 17.09.2010, 12:25 -0800 schrieb Joshua J. Kugler:
On Friday 17 September 2010, Marcus Priesch elucidated thus:
there is a new version which fixes this - are you sure you are
using the latest ?!?!
I'm using 0.1.4.
ok, that sound fine - could you
Am Montag, den 20.09.2010, 10:35 +0200 schrieb Ghislain FOURNIER:
and you have to put the device into VAD measuring mode
how to put the device into VAD measuring mode.
as stated by paul this should not be needed ... sorry for that ...
regards,
marcus.
Hi Joshua,
Am Donnerstag, den 16.09.2010, 22:05 -0800 schrieb Joshua J. Kugler:
One of them was with ctypes, which didn't want to find my libowcapi.so
in /usr/local/lib (even though ldconfig -p confirmed it was known).
there is a new version which fixes this - are you sure you are using the
Am Freitag, den 17.09.2010, 10:15 -0800 schrieb Joshua J. Kugler:
On Friday 17 September 2010, Marcus Priesch elucidated thus:
Hi Joshua,
Am Donnerstag, den 16.09.2010, 22:05 -0800 schrieb Joshua J. Kugler:
One of them was with ctypes, which didn't want to find my
libowcapi.so in /usr
Hi,
just a qiuck look over the datasheet and your schematics:
i am not sure if you need to put Vsens- to ground ?
and you have to put the device into VAD measuring mode ... however i am
not sure how to do this via owfs ...
maybe this helps ...
gegards,
marcus.
Am Mittwoch, den 15.09.2010,
.
Am Mittwoch, den 15.09.2010, 11:19 -0400 schrieb Paul Alfille:
Yes. I found the LinkUSB has problems with hardware handshaking. When
stable, the next version of owfs will work consistently with the
LinkUSB. (At least with extensive tests on my platform).
On Wed, Sep 15, 2010 at 2:46 AM, Marcus
it displays all devices, i
am now using it in ds2490 emulation ...
stay tuned,
m.
Am Donnerstag, den 16.09.2010, 13:59 -0400 schrieb Eloy Paris:
Hi Marcus,
On 09/16/2010 07:13 AM, Marcus Priesch wrote:
Hi Paul,
thanks for your answer, i have tested both with and without hw
handshaking
Dear List,
i just wanted to replace my DS9490 with a LinkUSB - which is working
fine on other systems ...
however, i updated owfs to 2.8_p2, but it still does not work:
- i have the /dev/ttyUSB0 device
- the permissions are correct
- when i connect with minicom, the communication works
Hi Guys (and Dolls) ;)
i am running owfs in a couple of installations:
my home heating system - couple of ds1820's and ds2406's connected to a
mixed star/bus topology (~20-40 meters) connected via ds9490B,
controlled by a cron job running every minute reading temperature values
through owpython
Hi,
Am Dienstag, den 10.08.2010, 18:58 +0200 schrieb Petr Jakeš:
I don't think pyowfs is intended to be used that way. Sounds
like you
need something different.
Hmmm... thanks for the hint.
maybe I can just mount the OWFS and go through
Hi Paul,
thanks for your words ...
Am Mittwoch, den 11.08.2010, 07:15 -0400 schrieb Paul Alfille:
I suspect that pyowfs does an initial scan when you first connect,
nope, it doesnt ...
when you call find () it internally calls iter_sensors () which in turn
calls libcapi's OW_get with the
Hi Petr,
To solve the problem, I have owfs mounted and I am reading the devices
from its file structure right now. It looks it is a bit faster with
the passive RS232 adapter. Because of that I can not provide feedback
right now.
But what you propose looks exactly what I wanted, when I
Hi,
You could try pyowfs instead - it uses the owfs libs (namely owcapi)
directly - but is in no means compatible to the original python
bindings ... but overcomes some of their limitations ... ;)
read more at:
http://priesch.co.at/pyowfs
install by:
easy_install pyowfs
this
there is a better way to
achieve this?
#! /usr/bin/env python
# Filename pyowfs_test1.py
# based up the code from Marcus Priesch
from pyowfs import Connection
import sys
class Sensor (object) :
id = None
def __init__ (self, connection):
self.conn = connection
12, 2010 at 5:32 PM, Marcus Priesch mar...@priesch.priv.at
wrote:
Hi Paul,
if it *really* is more platform independent, then go ahead with the
003 literals ...
however, from DBus i get thos numbers as integers ... and i dont see a
point why it would make sense to have them
Hi mick, dear all,
new version 0.1.3 just uploaded to pypi ;)
as i only tested it briefly i hope it works also for you ;)
if not, please tell me!
regards thanks for using it!
marcus.
--
Hi Paul,
if it *really* is more platform independent, then go ahead with the
003 literals ...
however, from DBus i get thos numbers as integers ... and i dont see a
point why it would make sense to have them as strings ... what is more
recents libusb's behaviour in this regard ?!?!
however
Hi Paul,
i did another test with two 2490 adapters ... i get the following when
both adapters are connected :
open...@openwis-desktop:~$ lshal | grep ^udi | grep 2490
udi = '/org/freedesktop/Hal/devices/usb_device_4fa_2490_noserial_0'
udi =
Hi Paul,
Am Donnerstag, den 06.05.2010, 21:26 -0400 schrieb Paul Alfille:
On Thu, May 6, 2010 at 3:49 AM, Marcus Priesch mar...@priesch.priv.at wrote:
so using bus.n sounds feasible, but is this numbering consistent through
(un)plugging various adapters ?!?!
i would expect following
Hi Paul, thanks for your detailed answer !
Am Dienstag, den 04.05.2010, 17:51 -0400 schrieb Paul Alfille:
On Tue, May 4, 2010 at 3:25 PM, Marcus Priesch mar...@priesch.priv.at wrote:
but in the case of owfs - with multiple usb adapters - i would have:
n interfaces - n sensors
and i can
Hi paul, dear list ;)
as i am currently in duty of defining a general purpose sensor library
and i want to incorportate owfs - i have a question for specifying the
usb adaptor to use ...
but, let me first explain some internals ...
my sensorlib utilizes dbus/hal to query for interfaces
Hi Steinar, Hi Paul,
[...]
so I use an external watchdog to restart owserver when it dies.
[..]
Do you have any example code for this? Forking is no problem, we already fork
for entering background. I'm a little wary of signal handling, and how well
this
will work on all platforms
Hi mick,
this means that the find () method didnt find anything ... i assume your
id is wrong ... see pascals post on that:
I guess this would do better:
s = root.find (id=10.0D54A9010800)[0]
even if only one element is returned, the find returns a list, the [0]
at the end indicate that you
Hi mick,
i just tried 2.7p34 and it works again with pyowfs ... thanks paul !!!
i also tried searching the bus for a sensor specified by id ... the
correct syntax is:
c.find (id=7F922100)
without the familiy code - so your try should have worked ... maybe you
had wrong id ?!?!
you
Hi mick,
congratulations at the first place !!!
Am Dienstag, den 06.04.2010, 21:15 +0100 schrieb Mick Sulley:
Hi,
Thanks to the help from Marcus and Pascal I am now able to read sensors
on my network. Now the next question -
I can run
root = Connection (/dev/ttyD1)
s = root.find
Hi Mick,
Am Dienstag, den 06.04.2010, 22:36 +0100 schrieb Mick Sulley:
Hi Marcus,
Tried your code, needed a colon at the end of
def __init__ (connection)
but now I get
Traceback (most recent call last):
File ./pyowfs_test3.py, line 22, in module
room = LivingRoom
Am Sonntag, den 28.03.2010, 23:56 +0200 schrieb Pascal Baerten:
I don't know pyowfs, but I guess:
s=root.find(type=DS18S20)[0]
and read the properties specific to the DS18S20 sensor with
print s.get(temperature)
thanks pascal, perfectly right ;)
regards,
marcus.
Hi paul,
i just tested pyowfs with p33 and it still crashes ... also the example
provided in owcapi (the C one) crashes with a double free ...
is there a another proper way to report this (e.g. a bugtracker) besides
this list - so that it doesnt get forgotten ... ?!?!
regards,
marcus.
Hi Mick,
congratulations !!!
however it would be very interesting why the LD_LIBRARY_PATH thing didnt
work for you ...
regards,
marcus.
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for
Hi Mick,
it should look in /usr/lib, /usr/local/lib all paths configured
in /etc/ld.so.conf and in the paths configured in LD_LIBRARY_PATH -
seperated by colon
you could try to symlink in /usr/local/lib or install owfs
to /usr/local/lib - the default i think when you dont specify a --prefix
to
Hi Mick,
are you sure a libowcapi.so can be found in /opt/owfs/lib ?
i just tried a fresh install with the following commands and it worked
(at least i was able to initialise the usb adapter i have here)
p...@mexx-desktop:~$ mkdir tmp
p...@mexx-desktop:~$ cd tmp
p...@mexx-desktop:~/tmp$ tar
Dear pyowfs users,
i just found out that pyowfs is not working for owfs versions 2.7p29.
when using p30 or p32 (p31 not tested) pyowfs terminates with a
segfault. p28 and p29 are tested and working ok.
paul, have you changed anything libowcapi related - i didnt find
anything in owcapi.h ?!?!
well, further investigations reveal that the example for libowcapi
access is also not working in p30, but working in p28 ... does it get
tested before release ;)
details on pastebin:
p30: http://pastebin.org/118517
p28: http://pastebin.org/118519
have fun,
marcus
Hi Mick,
sorry for beeing lazy the last days, but fortunately i now have a
solution for you ...
after testing out a fresh compile and install from both owfs and pyowfs
i also was not able to specify the path to the .so files ...
i now have fixed this behaviour inside pyowfs (now using
//usr/lib/python2.6/distutils.core
so it is still looking in /var/mail
Any ideas? I am passed the limit of my knowledge in this area so any
help would be appreciated.
Thanks
Mick
On Thu, 2010-03-11 at 13:24 +0100, Marcus Priesch wrote:
Hi Mick,
Am Mittwoch, den 10.03.2010, 21
Hi Mick,
great success by now !
Am Sonntag, den 14.03.2010, 19:42 + schrieb Mick Sulley:
Hi Marcus,
OK it seems to install now, now to the next problem!
Following the example code from your web page
from pyowfs import Connection
root = Connection (/dev/ttyD1)
Traceback (most
you point me in the right
direction please?
Thanks
Mick
On Wed, 2010-03-10 at 20:20 +0100, Marcus Priesch wrote:
and not to forget ...
4) http://priesch.co.at/pyowfs - a simple (and more complete) wrapper
around owcapi ...
have fun,
marcus
and not to forget ...
4) http://priesch.co.at/pyowfs - a simple (and more complete) wrapper
around owcapi ...
have fun,
marcus.
Am Dienstag, den 09.03.2010, 20:26 -0500 schrieb Paul Alfille:
There are 3 ways to use python and OWFS.
1. run the FUSE virtual filesystem (program owfs) and
Hi Pascal,
Thanks for this awful chip - i just ordered a free (thanks again) demo
board ...
What are your plans for availability - lets say if i want to use this
device for a commercial application - are the chips still available in,
lets say, 10 years ?!?!
thanks a lot,
marcus.
Hello Paul,
Am Sonntag, den 27.12.2009, 21:25 -0500 schrieb Paul Alfille:
Very nice.
I see you used owcapi, which should be a very stable interface.
i hope so ;)
but, determining the .so to be loaded sounds tricky ... in the ubuntu
packages announced here some time ago there is no
Dear List,
i am using owpython in my project. i have a ds2406 (switch with eprom
memory) where i store configuration information - until now, the
information stored in there had no NULL character, so there was no
problem reading the contents back ;)
but, however now i am short in time and my
Am Montag, den 19.10.2009, 18:35 -0400 schrieb Paul Alfille:
I love a patch!
Does it correct your hardware problem?
definitely it improves the situation !
i am now running with 1,8,3 for slewrate, w1l, dso set in my pathon app
as i mentioned some postings ago.
i am able to communicate with
Hi paul,
i was off-duty for the past few days, checked your change today, but no
luck at all ...
according to debug message from USB_Control_Msg the values now get
transferred after changing them - i see this as a huge part of the patch
- but the values set are always the start up (==default)
Dear Paul, dear list,
i finally came up with a patch (against current HEAD) which doesn't
overwrite the changed settings with the default ones ...
please review and merge into HEAD - as i am not 100% sure if the call to
DS9490_SetFlexParameters () is in the correct place ... ;)
thanks,
marcus.
be
strongly suspicious of hardware problems when adding new
chips.
Paul Alfille
On Mon, Oct 12, 2009 at 5:08 PM, Marcus Priesch
mar...@priesch.priv.at wrote:
Dear owfs-developers
Thanks for the answer !
paul, is it possible to modify these settings from within python ?!?!
if not, then i'll have to rewrite my 1wire stuff ...
regards,
marcus.
Am Dienstag, den 13.10.2009, 14:03 -0400 schrieb Paul Alfille:
I'll look a little closer, but it appears we're overwriting those
Yup,
i found it already ...
import ow
ow.init (u)
ow.owfs_get (/bus.0/interface/settings/usb/datasampleoffset)
' 7'
ow.owfs_put (/bus.0/interface/settings/usb/datasampleoffset,8)
0
ow.owfs_get (/bus.0/interface/settings/usb/datasampleoffset)
' 8'
that should do it ;)
Dear owfs-developers ...
thanks for the great work, i am using owfs for quite some years for my
heating controller and it works perfectly !!!
although currently i have some difficulties ... which i was not able to
get rid of and thats the reason why i am posting here ...
in my current project
87 matches
Mail list logo
