Yes currently I have one sensor without an alias and get -
control@pi-f ~ $ cat /var/1-wire/mnt/28.BE27BC04/alias
control@pi-f ~ $
Mick
On 11/12/13 10:10, Top-Dog wrote:
> It's the latest (v2.9) I believe. I only got it about two weeks ago from
> sourceforge. I'm running it on a BeagleBone B
It's the latest (v2.9) I believe. I only got it about two weeks ago from
sourceforge. I'm running it on a BeagleBone Black that has Linux Debian as
the OS. There may be something wrong with the alias stuff on my platform,
because when I try and use the .alias attribute without any
assigned alias I
Itis a plain text doc, current version is called "sensor_list6.3"
Which version of owfs are you running? I seem to remember there was a
problem with alias in the past, but it was quite a while back.
Also what OS are you running?
Cheers
Mick
On 10/12/13 22:02, Top-Dog wrote:
> What file type d
What file type do you use? I find that if I don't give the file and extension
it doesn't work, but if I give it a .txt extension I get '\r' tags on the
end. E.g.
>>> a.alias
'USB_One_Wire\r'
>>> a,b=ow.Sensor("/").sensorList()
>>> a
")nsor("/USB_One_Wire
>>> b
Sensor("/DevMem")
I can use 'strip'
I have been using aliases for a long time. You need to add
-a "PathToAliasFile" to your command where you call owfs, owhttpd, etc
where your alias file has entries for each device
e.g.
10.A209A9010800 = LoungeTemp
10.1C5BA9010800 = KitchenTemp
On 10/12/13 01:56, Top-Dog wrote:
> I'm pretty sur
I'm pretty sure something is up with the alias and pages attributes. I can't
make them work properly or at all. Has anyone actually tried them? Would you
be able to explain what you did to make it work?
And, how do the pages work? The DS2431, which I'm using, has 4 pages but I
can only seem to wr
Am 09.12.2013 22:13, schrieb Top-Dog:
>
> And on the side, I can't open the file 'list' (at /settings/alias/list)
> using sftp, but when I try ssh'ing into it I can open the file in nano (but
> it's empty) and when I try to write to it I get 'Error: Operation not
> supported".
>
This may be becau
Converting names to IP addresses happens as part of what the lower level
system libraries do when a connection in requested.
There are two ways to get this to work. I am assuming you are running
this on some form of *nix type system. There is a file called /etc/hosts
to which you can add names
On 9 December 2013 21:13, Top-Dog wrote:
> Thanks! That's what I was looking for, so I needed to replace ow.init('u')
> with ow.init('-s serverIP:4304'), so that it accesses owserver instead of
> the hardware directly. I've seen from looking around that some guys have set
> their servers up to hav
Thanks! That's what I was looking for, so I needed to replace ow.init('u')
with ow.init('-s serverIP:4304'), so that it accesses owserver instead of
the hardware directly. I've seen from looking around that some guys have set
their servers up to have a custom name instead of the IP address, how do
> 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 hyb
Hi,
I have no python exposure, but I think I got it.
Think in layers.
Layer0 is the hw.
Layer1 is owserver, the -u means it will access the usb device directly
In Layer2 you have several components side by side.
- owfs will create the filesystem representation. -s serverIP:4304
causes it to a
For aliases see
http://owfs.org/index.php?page=alias-improved
On 09/12/13 02:20, Top-Dog wrote:
> Thanks, I think I have some understanding about how this works now, but I
> still can't make it work for me. I still have the same original problem
> where if I want to do something like sensor.type
Thanks, I think I have some understanding about how this works now, but I
still can't make it work for me. I still have the same original problem
where if I want to do something like sensor.type or
ow.Sensor("/").sensorList() I need to have the USB device initialised
(inside of python) and the only
Am 07.12.2013 23:22, schrieb Top-Dog:
> OK... but how do I read and write to an EEPROM page file if I can't access
> the file structure of the 'sensor'?
>
You still don't understand. Owlib just offers a "file" *representation*
of the devices of the bus. The owfs tool presents this file
representa
OK... but how do I read and write to an EEPROM page file if I can't access
the file structure of the 'sensor'?
I'll probably need more owfs 'packages' because I want to put the file
structure online (so use owhttpd, and owserver) and then use owpython to
handle the read/writing and IDing the conn
Am 05.12.2013 21:08, schrieb Top-Dog:
> Thanks for the explanations. I'm still a bit confused about how I'm meant to
> use the python api though. If I don't mount the file system with 'sudo
> /opt/owfs/bin/owfs --allow_other -u /root/EEPROM.../' then when I go
> straight to python and do the us
On 04.12.2013 23:54, Top-Dog wrote:
> I have noticed that the only way (maybe?) to recover functionality if the
> file system is lost is to physically unplug/plug the USB adapter. Also, I've
> done a few more tests and it almost seems random as to where/when the 1-wire
> devices will detach themsel
Ok. Thanks that should help me out a bit.
These are the results I get in python at the moment:
>>> b
Sensor("/2D.C1E79A01")
>>> b.type
'DS2431'
>>> b.entryList()
['address', 'alias', 'crc8', 'family', 'id', 'locator', 'memory', 'pages',
'r_address', 'r_id', 'r_locator', 'type']
>>> b.pages
Tr
It defines aliases for your sensors. You create a file with entries like
10.A209A9010800=LoungeTemp
10.1C5BA9010800=KitchenTemp
Then when you look at the directory structure it uses LoungeTemp instead
of 10.A209A9010800, so it is easier to read and a bit more user
friendly. Yo
Mick Sulley wrote
> owserver -p 4304 --nozero --i2c=/dev/i2c-0:ALL
> owfs -s localhost:4304 -a alias_file -m /var/1-wire/mnt --allow_other
Hi Mick, what does the '-a alias_file' bit do? I get: DEFAULT:
ow_alias.c:(34) [No such file or directory] Cannot process alias file
alias_file when I try and
I use python to parse the files as well, but would prefer the
object-oriented approach I've seen in the owpython implementation. From
what I can tell, using the python would require nothing but the source, and
possibly an install using python-setuptools if one wanted to invoke it from
anywhere. I w
Hi
I use owfs with Python as well. I am not an expert on either, but in my
code I start owfserver first then start owfs like this -
owserver -p 4304 --nozero --i2c=/dev/i2c-0:ALL
owfs -s localhost:4304 -a alias_file -m /var/1-wire/mnt --allow_other
so owserver talks to the 1-wire network and
Thanks for the explanations. I'm still a bit confused about how I'm meant to
use the python api though. If I don't mount the file system with 'sudo
/opt/owfs/bin/owfs --allow_other -u /root/EEPROM.../' then when I go
straight to python and do the usual set up:
import ow
ow.init('u')
The file s
Am 05.12.2013 01:30, schrieb Top-Dog:
> Hi Jan,
>
> I have these entries in the directory /etc/modprobe.d/:
> blacklist ds2490
> blacklist ds2490r
>
Good.
> What do you mean by 'one' owlib instance? Do you mean that every time I call
> ow.init('u') in python I create a new instance even if I e
Hi Jan,
I have these entries in the directory /etc/modprobe.d/:
blacklist ds2490
blacklist ds2490r
blacklist wire
blacklist cn
What do you mean by 'one' owlib instance? Do you mean that every time I call
ow.init('u') in python I create a new instance even if I exit python an
restart it (plus use
I have noticed that the only way (maybe?) to recover functionality if the
file system is lost is to physically unplug/plug the USB adapter. Also, I've
done a few more tests and it almost seems random as to where/when the 1-wire
devices will detach themselves.
--
View this message in context:
ht
Am 04.12.2013 23:12, schrieb Top-Dog:
>
> I have also observed in other cases that the file
> system disappears immediately after ow.init('u') is called.
>
Access to the onewire hardware is usually limited to *one* owlib
intance. When you have two or more, use owserver for the actual hardware
conne
Why is the owpython source not downloadable? I wish I'd known about it and
would be happy to contribute. First I need to download it...
On Wed, Dec 4, 2013 at 2:12 PM, Top-Dog wrote:
> Hi,
> I'm pretty new to the owfs and have been trying to get it working properly
> but have run into some issu
Hi,
I'm pretty new to the owfs and have been trying to get it working properly
but have run into some issues. Basically my device (DS2431) and USB adapter
(DS9490r) will disconnect and disappear from the 1-wire file system mount
point. I'm using the python api (http://owfs.sourceforge.net/owpython.
On 11/02/2013 10:10 AM, Guy COLIN wrote:
> Hi Colin,
>
> sounds like hardware problem.
> Does the USB us master disapear also? i.e. no more 81.xx in the devices
> listing. Or only the temp sensors disapear?
I have been having this same issue intermittently. Mine sometimes come
back on its ow
I think it must have been a connection issue that varied with
temperature or humidity. I jiggled the connections last time and
repositioned them and it's been fine ever since. I've been meaning to
get some better RJ12 splitters anyway.
C
On 11/3/2013 04:18, Guy COLIN wrote:
> Hello,
>
> I have
Hello,
I have 3 Raspberry Pi(Raspbian) with owfs
2 with i2c to 1wire : running 24/7 no stability problem
1 was on serial to 1wire from January to september running 24/7 : no
stability problem
1 is on USB to 1wire, it's my test platform it's not running 24/7 but also no
stability problem even wh
Interesting. I've had no reliability issues with the ds9490r (on Linux anyway)
prior. My plan was to try disconnect reconnect of the ds9490r and then swap out
sensors, but it decided it wanted to run for another day without problems. I
avoided this is the first place because it's inside of an en
Instead of rebooting, if you unplug the DS9490 and plug it back in, then
restart OWFS? Does it recover then?
I moved away from the the USB DS9490 because of unreliable operation. It would
just quit working. Now that was a while ago and on a different kernel and
architecture, so take it for wha
Hi Colin,
sounds like hardware problem.
Does the USB us master disapear also? i.e. no more 81.xx in the devices
listing. Or only the temp sensors disapear?
--
Guy
--
Android is increasing in popularity, but the
Oh also, I ran cat on all files in stats/errors and got nothing but zeroes.
C
On 11/1/2013 21:53, Colin Reese wrote:
> Hello all,
>
> I have an RPi that up until now has been faithfully reading multiple
> DS18B20s on a DS9490Rs for months on end. The devices have taken to
> disappearing after one
Hello all,
I have an RPi that up until now has been faithfully reading multiple
DS18B20s on a DS9490Rs for months on end. The devices have taken to
disappearing after one to several hours. This is what I have:
The bus is still present as bus.0
Killing owfs and restarting does not bring the devi
38 matches
Mail list logo
