On 07.08.2017 21:43, Johan Ström wrote:
> Don't remember from the top of my head, but you will need to
> chown/chgrp some node in /dev/usb/something for that particular user.
> Not sure if that was ever documented properly..
There are lots of examples on the net how to write an udev rule which
doe
Hi,
> Am 06.08.2017 um 18:52 schrieb Michael Hughes:
>> I am using the ow C API to read all of my Dallas 1-Wire devices.
>> I do a OW_init("/dev/cuao0"). I then go in to a loop and use
>> OW_get to read each device. I use the following line to read the
>> voltages:
>>
>> OW_get( "/uncached/1F.49
On 09.08.2017 19:46, Martin Patzak (GMX) wrote:
> SUBSYSTEMS=="usb", ATTRS{manufacturer}=="FTDI",
> ATTRS{product}=="FT232R USB UART", ATTRS{serial}=="A800bXHr",
> GROUP="owsrv", MODE="0664", SYMLINK+="LinkUSB"
For me this works perfectly (a) without the symlink (b) with an
additional DRIVER==
Hello,
>
> (b) with an additional DRIVER=="USB" condition.
>
This is nonsense; the "USB" needs to be lowercase and the field is named
DRIVERS. Sorry about that.
--
-- Matthias Urlichs
signature.asc
Description: OpenPGP digital signature
On 24.09.2017 12:38, Mick Sulley wrote:
> Any suggestions on how I can find out what is causing this.
When I had this problem, the root cause was a flaky power supply.
Get a cap-rail-mounted adjustable 5V power supply (e.g. from Meanwell).
Connect the Pi, then carefully adjust the voltage up to 5
On 25.09.2017 10:32, Mick Sulley wrote:
> Matthias, I have just looked through the Meanwell site but cannot see
> any that are adjustable (may have missed it there are a lot there),
> can you tell me which one you used please?
https://www.trcelectronics.com/mean-well-din-rail-power-supply-mdr-20
-
On 16.11.2017 11:56, FireWorker wrote:
> i must differentiate on witch DS9490 Adapter a I-Button is connectet
There is a DS2401 in every DS9490. You distinguish the buses by the
serial number of the 81.X device you find on each bus.
> What must i do that the first DS9490 allways connect to Bus.
On 17.12.2017 00:19, Stefano Miccoli wrote:
> Unfortunately owpython (the swig bindings) is not under active
> development.
I'd go a step further and remove them from the next release.
--
-- Matthias Urlichs
--
Check o
On 17.12.2017 17:45, Gregg Levine wrote:
> Of course the merely obvious question is why the swig bindings are not
> under active development.
Because they're mosty useless, IMHO. In any sort off production
environment I want a way to access the actual bus and check which data
is actually out there
On 05.03.2018 11:15, Stefano Miccoli wrote:
> In my opinion it should be time to migrate the principal OWFS repo from SF to
> GH.
Seconded. SF is not going to get better, long-term.
--
-- Matthias Urlichs
--
Check out
On 08.04.2018 10:12, Johan Ström wrote:
> I have taken the liberty to make the move.
Great, and thanks for adding me.
I have taken the opportunity to start removing the obsolete SVN tags
from owfs's files. There are still a couple of $Release$ and $Date$ tags
which need to be replace or removed,
Hi,
I'm writing a new high-level asynchronous Python library to talk to
owserver.
It features multiple persistent server connections, transparent support
for DS2409 couplers, automatic retries when he server is busy or the
connection breaks, object-oriented design, auto-generating accessor
method
On 04.09.2018 20:37, Loren Amelang wrote:
> I have a single bus with ten parasitic 18B20s spread along close to 100' of
> cable
Wow. Frankly I wouldn't even dream of doing that without a 5V wire.
My basement bus would have required close to twice that lenght if I had
run it as a single straight
On 05.09.2018 07:45, Jan Kandziora wrote:
> So my advice from pratice is basing all the automatical mechanisms on
> a logical abstraction of a whole peripheral, with the Onewire stuff
> being only a part of a bigger picture.
My main goal with this library is that the instance representing a slave
d
On 05.09.2018 11:00, Jan Kandziora wrote:
> Yes, exactly. But that's what a clever designed library can assist the
> application programmer. By requiring him to think about the logical
> abstraction of a whole device first, not just a Onewire slave.
Well, I can't help with "requiring".
But once t
On 21.10.18 10:20, Martin Patzak wrote:
> Do you meen a switch like e.g. a DS2408?
>
> How do I issue an ON command with timeout?
There is no off-the-shelf 1wire component that does this. You'll either
have to implement it yourself using AVR or STM32 slave code, or use
external components that re
On 11.04.19 22:25, Johan Ström wrote:
> I don't mind sponsoring the cost for a year just to avoid thinking
> about this now (so community can focus on the page) but in the long
> run the community needs to decide if and how we want to handle it.
I'm already sponsoring a bunch of domains (open-end)
On 01.05.19 10:38, Nico Bouthoorn via Owfs-developers wrote:
> Who owns the domains now?, it looks like it has nothing todo with owfs
> anymore.
Owch. Typical domain grabbing idiocy. We should have transferred it
before it expired. :-(
Reasonable registrars block new registrations for a time to
On 25/05/2019 09:25, Colin Reese wrote:
porting the C and python bindings?
There are perfectly working python-only bindings for OWFS. Porting any
bindings of libow[net] is a heap of work and won't get you anything.
--
-- Matthias Urlichs
___
Owf
On 19.06.19 09:39, Jan Kandziora wrote:
> The 1W host has to supply current to the 1W line to power all the
> parasitic powered slave devices.
Well, the solution is to not parasitically power anything.
Of course you can't do that with DS2401 switches or iButtons, but the
other 1wire ICs have Vcc
On 19.06.19 13:03, Mick Sulley wrote:
> Yes all of my sensors are powered.
In that case, my next step would be to replace the "hot" sensor.
For added peace-of-mind, I'd also add a small capacitor (100nF or so)
between Vcc and GND.
--
-- mit freundlichen Grüßen
--
-- Matthias Urlichs
___
On 29.08.19 09:50, Nico Bouthoorn via Owfs-developers wrote:
> Many years ago I built a snow depth sensor based on the LP-THS
> temperature/humidity board, but it has now had a failure. I do have
> some spare parts, including the DS2409 which apparently had failed on
> the board
This might be a s
On 09.10.19 22:44, Mick Sulley wrote:
> I can get around this by appending .decode('utf-8) and .encode('utf-8)
> to the read and write functions
That's the idea. Separating strings and bytes was necessary because it
ultimately caused too many interesting hard-to-debug problems …
--
-- Matthias U
On 26.10.19 12:53, Mick Sulley wrote:
> Question - is it good practice to always install packages like this as
> root?
On Linux, best practice is to not use "pip" if the distribution already
has a package for whatever you need. Debian: "sudo apt install
python3-ownet" (or the GUI equivalent).
--
Hi,
> Debian: "sudo apt install python3-ownet" (or the GUI equivalent).
Having just done that …
(a) the module is named "ownet" not "pyownet"
(b) This module doesn't work with python3. Like, at all. I have created
https://github.com/owfs/owfs/pull/44 to (barely) fix that, and I sent a
bug repor
25 matches
Mail list logo
