owlib does have support for that kind of device -- (multiple buses) -- The
DS2482-800 is a good example. It has one "port" and multiple buses. The
port gets locked for just the message (e.g. serial communication) and the
individual 1-wire bus and slave gets locked for the 1-wire "conversation".
Eac
I'm sorta gone. How can I help the transition?
Paul
On Tue, Jul 26, 2016 at 4:18 AM, Jan Kandziora wrote:
> Am 26.07.2016 um 08:36 schrieb Martin Patzak (GMX):
> > who else thinks the following should find it's way onto the owfs
> web-site?
> >
> Guys, face it
Is that family code 11 decimal or hex? Family 0x0B is a DS1985.
http://owfs.org/index.php?page=ds1985
On Tue, Jun 2, 2015 at 5:01 PM, Jerry Scharf wrote:
> Hi,
>
> I am helping someone reverse engineer some power supply tips that use
> 1-wire devices to code them . Most of them read fine (ds250
To expand on Colin's point, the files in owfs are created on the fly by the
program. They don't exist on disk. When you "read" a temperature, the
system makes it look like the file contains a number, but actually the
program reads data from the 1-wire bus to get the value.
The UNIX file system nee
So is the problem the parsing of the line in the config file?
On Wed, Jun 10, 2015 at 2:42 PM, Jerry Scharf <
sch...@lagunawayconsulting.com> wrote:
> Don't you hate it when someone replies to them selves on the list. I was
> trying to get them using the device variable in a config file. I
> coul
Are you talking about the "presence pulse" when the device is connected?
OWFS doesn't monitor that directly (it's possible some hubs might have
internal detection).
On Thu, Jun 11, 2015 at 11:09 AM, Howell, Larry (Contractor) <
larry.how...@stryker.com> wrote:
> Hi list,
>
>
>
> Our project is
The hub support is still in development. Which version do you have?
On Thu, Jun 11, 2015 at 3:53 PM, Lyle Giese wrote:
> On 6/11/2015 11:16 AM, Lyle Giese wrote:
> > I have a 'new' Hobby-Board 4 port master hub. It appears to be a
> > working unit. I connected it via USB to a OpenSuSE box and
Hi,
I wonder if the rate of reading is overwhelming the capacitor charging in
the circuit. The DS2438 humidity sensor design creates Vdd from the data
line, if I remember correctly.
Do the problems resolve if you delay readings by, say, 60 seconds
intervals? I doubt your humidity really changes t
listing you see at the top level.
Paul Alfille
On Fri, May 8, 2015 at 7:24 PM, Gary Fariss wrote:
> Hello...
>
> I have OWFS 3.1 installed on a Raspberry Pi 2 with Raspian Wheezy. I have
> a single DS2482-800 connected to --i2c=/dev/i2c-1:0 and several temp and
> PIO chips
Yes, plug and play (as you put it).
You can disconnect the devices at will, and plug them in whenever you want.
A caveat: so improve performance, the device list is kept around 2 minutes
or so, before scanning again (the scan can be slow on a large bus). You can
ask for the /uncached/ directory t
Just "make install" the new one.
Else, delete /opt/owfs
On Thu, Apr 2, 2015 at 5:13 AM, HRueck wrote:
> Thanks to Jan and Paul for the info!
>
> I installed via "make install".
> could you please advise how de-install properly without any corruptions?
>
> best regards, Herbert
>
>
>
> --
> View
I usually just build the new version on top of the old. That works as long
as you didn't install via package manager and direct source build, since
one usually installs in /usr/bin and the other in /opt/owfs/bin
The only other gotcha is that linux won't load the new shared library as
long as any o
I took the unusual step of 2 releases:
3.0p2 Adds minor changes to the K1WM Bus Master from Martin Rapavy for the
Kisler moification of the synthesized DS1WM Bus Master.
3.1p0 is a major change in linkage. We leave behind the legacy version of
libusb for the modern version. Libusb is used for the
ead". That is, reading means
> any previous output will be invalidated as it will no longer "supply" a
> high/low level.
>
> How about auxctrl and auxsense, to avoid mixup with other "power" entries
> (which indicates powered or parasite)?
>
>
> On 3
I love the idea, but not the names. In seems that one is read-only and one
write-only from the name.
How about auxpower and auxsense?
On Thu, Mar 12, 2015 at 12:37 PM, Johan Ström wrote:
> Oops, early send... Trying again, this time writing the full mail!
>
> The LINK adapter has an extra AUX
I assume we're talking about the DS2482-800 -- the 8 channel i2c-based bus
master.
The fact that a reboot doesn't fix the problem takes in issue out of owfs
(which should be entirely reset by a reboot) and to the hadware (which
might need a power cycle to fully reset).
The datasheet talks about a
OWFS Release Notes
3.0p1
Feb 27, 2015
New Features.
1. owhttpd supports "sparse arrays"
A. Based on feedback by Eugenio Torrini
B. Sparse arrays allow the file extension to have any value, e.g. a
password in the case of the DS1991
C. owhttpd now has an extension input field for sparse arr
#x27;t even have the datasheet pinouts correct in the code.
Paul Alfille
On Tue, Feb 24, 2015 at 7:17 AM, Paul Alfille
wrote:
> Just about done, but I'm not sure how to handle the clock divisor in the
> DS1WM. It needs the actual clock speed input to the DS1WM. Is that standard
>
>
> Thank you for your support.
>
> Best regards,
> Martin
> --
> *From:* Paul Alfille [paul.alfi...@gmail.com]
> *Sent:* Monday, February 23, 2015 7:18 PM
>
> *To:* owfs-developers
> *Subject:* Re: [Owfs-developers] Add support for additio
>
> As I said I expect the context of each call (like active channel, pointer
> to device memory map, etc.) to be stored in my master_uio structure.
> I suppose OWFS needs to know how to setup the context before calling
> functions from my module – could you please explain me how t
Writing slave code is quite easy, in fact. Most of the infrastructure is
built into macros.
Take a look at any similar slave e.g. modules/owlib/src/c/ow_2406.c
You add entries in the big structure near the top for the new properties,
include the name, type, length , read and write functions and p
ommand line / configuration
> file parameter.
>
>
>
> How does owfs treat channels? Do we need to pass number of channels as
> command line / configuration file parameter as well?
>
>
>
> Thanks,
> Martin
>
>
>
> *From:* Paul Alfille [mailto:paul.alfi...@
Do you map the 6 control registers to consecutive memory locations? Would
we pass that location in a command line option?
On Feb 19, 2015 12:16 PM, "Jan Kandziora" wrote:
> Am 19.02.2015 um 08:59 schrieb Martin Rapavy:
> > Hi Paul,
> >
> > thanks for briefing me on the architecture of OWFS. My ma
;discovery" to enumerate the 1-wire slaves. Often hardware
assisted.
4. Optional "Power bit".
You'll also need to add a command line configuration option. If you can
describe your bus master to me, I can easily write a rough draft that you
can test and perfect. (Or send me a sa
ors. They work great.
>
> Do I need to have the pioa and piob ports connected to have the files?
> I just wanted to try if I can see the device before soldering things to
> it.
>
> Do you need more information?
>
>
>
> Thank you for your work by the way!
> Sven
Wouldn't once per second be enough?
You can also partition the problem -- set up a separate 1-wire bus just for
the polling -- wouldn't be interfering with your sensors. Also these days,
just have a Raspberry Pi or something like that do the polling and 1-wire
work and use your main CPU for data c
Hi Daniel,
Gregg answered the more general philosophy of 1-wire architecture. Let me
address your questions narrowly.
All the 1-wire chips (well, almost all except the DS1821) have a unique ID
that can be queried by the 1-wire "discovery" protocol. When you ask for a
"directory listing" in OWFS i
I carefully diff-ed the DS2483 and DS2484 data sheets. There are no
substantive differences. The DS2483 seems to be a little fussier about
having Strong Pull-up (SPU) stopped before a reset.
Thus, I would have expected the DS2484 to work fine. Can you check your
hardware setup?
Paul
On Mon, Feb
Eugenio,
I looked at the code for the DS1991 and I think I'll rewrite it. I'll send
you some versions to test.
One thing that will change is how the password field is entered for each
read and write.
If the password is 0x1112131415161718 to read in subkey 1 you will read and
write to
subkey1/da
n the code something is done,
Did I answer your question?
Paul
On Wed, Feb 4, 2015 at 5:00 PM, Eric Baumann
wrote:
> Hi
>
> Thanks a lot for your replies :-)
>
> @ Paul Alfille:
> No, I haven't.
>
> It's just that I want to READ about it first.
> My question i
Don't read too much into the major number change, although I've been doing
some major updating.
This version is about being better on the Mac, and a better systemd and
launchd client.
OWFS Release Notes 3.0p0 Feb 2, 2015 New Features. 1. Monitor configuration
file changes A. Use operating system
Eric,
Have you actually tried the devices? I've worked with Hobbyboards to
support most of their devices.
Can you give name of the devices? I can give a more definitive answer then.
Paul
On Feb 2, 2015 5:56 PM, "Eric Baumann" wrote:
> Hi :-)
>
> I am new to OWFS.
>
> I just bought pretty much
Hi Sven,
I'll have to locate a DS 2413 to test, but there have been no recent
changes to the code.
Does your device have family code 3A?
Paul
On Mon, Jan 26, 2015 at 6:57 AM, Sven wrote:
> Hallo Mailinglist,
>
> I have problems with a DS2413 device.
> I do not have files like
>
> |-- PIO.A
>
ed I think). Many IDs are built in to OWFS but the
> > documentation on the devices and ID has always been a bit spotty. I can
> > help you figure it out (and improve OWFS) once we get to that stage.
> >
> > Basically the DS2438 measures a few voltages and temperature.
> >
es and temperature.
Paul Alfille
On Thu, Jan 22, 2015 at 9:11 PM, Peter Hollenbeck wrote:
> I have a LinkUSB and an MS-TV temperature and voltage sensor.
>
> http://localhost:2121/ shows:
>
> *10.67C6697351FF* <http://localhost:2121/10.67C6697351FF>
> *05.4AEC29CDBAAB* <ht
Hi Larry,
The owfs "--debug" option adds "-d" to the fuse command line to enable
debugging. I typically see the error messages intermixed.
One thing to look at is in the /statistics directory. Perhaps there is line
noise that is causing more retries and a delay.
Paul
On Wed, Jan 21, 2015 at 8:5
n –disable-zero?
> I will get on my build system (Based on µclib - buildroot) an fault, when
> i have set –disable-zero.
> The message is, that in ow_browse_monitor.c an fault is by Browse_detect
>
> Best regards,
> Roland
>
> *From:* Paul Alfille
> *Sent:* Tuesday, Janua
d, and an empty owfs/2.9p9 folder.
> As always, thanks for keeping this going
> Bruce
>
> *From:* Paul Alfille
> *Sent:* Tuesday, January 06, 2015 8:59 AM
> *To:* owfs-developers
> *Subject:* [Owfs-developers] New Release 2.9p9
>
> Minor improvement -- basical
, and I
presume that size has increased from 64k to 128k recently which is over
owfs's arbitrary internal limit.
I added a size limiter in the owfs read code and everything now works. A
new release 2.9p9 now includes the fix.
Thank you Markus and Stefano for finding and investigating this probl
s some internal limits.
We now trim the read request before processing.
Paul Alfille
--
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Med
I don't have the answer yet, but it happens only with cat or cp, not
less,head or tail.
It also happens only with owfs->owserver->bus, since owfs->bus is ok.
There must be something different in the tcp protocol handling. I'll
investigate further.
Paul
On Sun, Jan 4, 2015 at 1:20 PM, Jacob Josep
Have you tried another channel on the DS2482-800 for the long run? The 8
channels are electrically separate.
I assume you've looked at some of the resources for 1-wire bus topology,
like http://www.maximintegrated.com/en/app-notes/index.mvp/id/148
Paul
On Fri, Jan 2, 2015 at 10:08 AM, Jan Sennes
Hi. I'm sorry there build isn't working. Did you do the "./bootstrap,
./configure, make" sequence?
One of the messages:
configure.ac:52: warning: AM_INIT_AUTOMAKE: two- and three-arguments
forms are deprecated. For more info, see:
configure.ac:52:
Is benign. (For that matter, what type of idiots
Yes. Easystart is a convenience function. Otherwise there are a number of
steps needed in sequence to start a measurement and a risk of bricking the
device if the oscillator isn't started first. I'll admit I haven't looked
at the thermochrons in some years so testing would be wise (and feedback
wel
I think you have the right idea.
owexternal is a protocol to use non 1-wire devices as 1-wire slaves.
Obviously we can't use normal 1-wire reading, writing, IDs or selection.
Instead the device is described in a file with links to programs that do
the actual communication and return the result.
The DS2482 (i2c bus master) suggests that it can run at 3.3V level.
http://datasheets.maximintegrated.com/en/ds/DS2482-100.pdf
Paul
On Fri, Nov 21, 2014 at 4:53 PM, Jan Kandziora wrote:
> Am 21.11.2014 um 19:56 schrieb Jerry Scharf:
> > Hi,
> >
> > I am looking at using the MAX31850 chip for m
As Jan points out, the official source of 1-wire numbers is Maxim. In
general they reserve 0x00 to 0x80 and use the upper half of the family code
space for "special runs" and 3-rd party.
Some people have just chosen a number on their own -- Luis Swart took 0xFF
years ago and even proposed splittin
Hi Roland,
Maybe I can help you understand the process.
Say you want to run owfs, owserver and owhttpd with a USB device and
Fahrenheit temperature scale.
Purely from the command line you would run:
owserver -F -u -p 4304 # reads from USB, serves port 4304
owfs -F -m /var/temp/1wire -s 4304 # r
Well there's always the possibility that there is a wiring problem, but
also there could be two processes competing for the same resource.
Is owserver and owfs running at the same time? Your configuration file
would have them both grabbing the same serial devices and stepping on each
other.
If th
Can you tell me the type_number and version for the two devices? (Reading
from the owfs entries)? Both will show selected properties based on the
type number which Hobbyboards (and owfs) uses to distinguish the different
available sensors.
Paul
On Fri, Oct 24, 2014 at 10:57 PM, David Lazarou
wro
Sorry for the rapid releases, but some functional problems in the last two
releases were serious enough to need fixing promptly -- specifically with
the filesystem owfs.
-
OWFS 2.9p8
Release Notes
Oct 18, 2014
One Wire File System
www.owfs.org
New Features
1. Filesy
Sorry. Known bug in 2.9p7 with owfs. Fixed and new release later today.
Paul
On Oct 18, 2014 6:07 AM, "Thomas Zimmermann" wrote:
> Hi,
> I'm currently packaging owfs for openSUSE and got a bug report that in the
> package with systemd enabled owfs crashes as soon as one browses the
> /run/owfs
>
Thank you. I had overlooked that masking bit. Will be included in p8
Paul
On Fri, Oct 17, 2014 at 1:30 AM, Vincent Danjean
wrote:
> I forgot to add my personal repo to test new packages in the
> previous mail
>
> On 17/10/2014 07:21, Vincent Danjean wrote:
> > Hi
> >
> > On 17/10/2014 00:05
If you add /text to the path the result is easier to parse.
For that matter, owhttpd isn't the easiest way to get pure data (as opposed
to a nice display). The file system, shell utilities, ownet within your own
program all give pure text.
On Oct 14, 2014 4:25 PM, "somewire" wrote:
> Nevermind,
Hi Gregg,
Most of the development is done on 64-bit systems. Not slackware, though,
so your work and testing is appreciated.
As for extensive testing -- clearly the recent spate of bugs after the last
release shows it wasn't extensive enough.
Paul
On Fri, Oct 10, 2014 at 11:54 PM, Gregg Levine
l pkg-plist diff:
> https://github.com/stromnet/freebsd-ports/commit/27f00a6e436d224ea9940ed530280163fcaf5cdc#diff-3
> )
>
> In addition, they are not too informative.. For example:
>
> $ man configuration
> Name of an configuration file with more command line parameters
> $
>
>
Ok, that was embarrassing.
I hadn't tested building from a fresh directory the download file rather
than just packaging up the development directory with "make dist"
Basically I commented the "lint" stuff from the two Makefiles.
OWFS 2.9p7
Release Notes
Oct 8, 2014
Fix build problems, otherwis
OWFS 2.9p6
Release Notes
Oct 7, 2014
One Wire File System
www.owfs.org
New Features
1. HobbyBoards Masterhub
A. New 4-port hub
B. USB suport
C. Ethernet not yet implemented
D. Autodiscovery not yet implemented
2. New HobbyBoards Sensors
A. Updated Moisture Meter
B. Humidity
C. Barometer
3. Impro
Hi Stefano,
/sys/bus/usb-serial/devices doesn't seem to pick up ttyACM? devices, but
does discover some devices I missed.
Actually the two methods give quite different results on my machine:
#-tty2usb output = 6 devices--
paul@hz tty2usb-code$ ./tty2usb
List tty -> USB pairings
Hi Michael,
There are two possible uses for the usb<->tty mapping.
1. Discovery -- find a unique USB device (HobbyBoards, Eclo, etc) and then
find the tty port to use.
2. Tune a FTDI device when the /dev/tty port is passed to owfs.
You're right, of course. Probing an anonymous serial device is u
y for tty[A-Za-z]* (which
indicates a serial device)
3. Choose the longest path for a given tty device.
Paul
On Mon, Oct 6, 2014 at 3:47 AM, Colin Law wrote:
> On 6 October 2014 04:30, Paul Alfille wrote:
> > After all the discussion about serial and usb pairing, I created a new
>
and auto-scanning.
I'd really like testing and feedback. It's very easy to use --
make
sudo make install
ttyusb
Paul Alfille
--
Slashdot TV. Videos for Nerds. Stuff that Matters.
http://pubads.g.doubleclick
I've done over 100 DS18S20's (passive) on passive, active, Link and DS9490
successfully. It isn't fast, but then your temperature changes aren't that
fast.
On Wed, Oct 1, 2014 at 4:53 PM, Roberto Spadim
wrote:
> that what i stored here some years ago when testing ds1820 devices
> in other words
Ok, here is my code for mapping USB devices to tty devices. It's a script
and needs to be tested on various platforms.
---
#!/bin/sh
# find all directories with busnum (they are USB devices)
usbdirs=$(find /sys/devices -name "busnum" -printf "%h\n")
# look at ever
messages give any information.
Paul
On Sun, Sep 28, 2014 at 5:04 PM, Chris Green wrote:
> On Sun, Sep 28, 2014 at 11:43:32AM -0400, Paul Alfille wrote:
> >'dmesg' is the command that shows the system messages, including USB
> >plug/unplug.
> >'lsusb
'dmesg' is the command that shows the system messages, including USB
plug/unplug.
'lsusb' (if installed) will give a list of current USB devices.
On Sun, Sep 28, 2014 at 11:39 AM, Colin Law wrote:
> On 28 September 2014 15:00, Chris Green wrote:
> > I have a 1-wire installation which I am tryi
PBM01) -- 0403:6015 -- with UNIQUE product and manufacture ID
>
> Sorry for the delay. I'm still negotiating a sample for your.
>
> Thanks
> Dirk
>
> Am 23.09.2014 um 23:27 schrieb Paul Alfille:
>
> Ok, I did some testing of various USB 1-wire bus masters:
>
> LinkUS
perhaps I have an early version and the internal fields have
changed.
Paul Alfille
On Tue, Sep 23, 2014 at 3:40 PM, Johan Ström wrote:
> I'm all for auto-detection, when it is possible to do so reliably. As you
> mentioned in the other reply, randomly poking at stuff is neith
al devices is not just listing them, but
rather the danger of randomly poking at them to see if they are a
recognized 1-wire bus master. I don't know of any agreed safe way to do it.
That's why USB with identifying fields is better -- reading those fields is
safe.
Paul Alfille
On Mon, Sep
I notice in recent Linux (Fedora specifically) that USB devices get pretty
consistently listed by a reasonably consistent and recognizable name in
/dev/serial/by_id.
I haven't looked to closely at all the USB fields yet, but some devices
have unique identifiers rather than the generic USB/serial.
reads
> /28.xxx/power in ~77ms, vs 27ms with 1ms timeout.
>
>
> Regarding 0-baud, I think it's only done from serial_powercycle, not sure
> why though. Power-cycle adapters powered directly by the serial-port?
> Since I don't know the use of the code, I cannot reall
Thank you, Johan, for the detailed tests.
The idea of "slurp" was to collect any pending serial traffic and allow
communication with the bus master to be synchronized. I agree that matching
expected response exactly is optimal, but that supposes that you start from
a known clean state. I found in
Glad to hear there is a solution. I wonder if we can find a way to make
owfs handle USB problems more gracefully.
A description of getting owfs working on an embedded platform like the
WR703N would be great.
Paul
On Fri, Sep 5, 2014 at 6:23 AM, Colin Law wrote:
> Thanks for the suggestions, a
Thank you Hans-Frieder. And Stafano as well for his recent patch.
On Sat, Aug 23, 2014 at 6:21 AM, Stefano Miccoli wrote:
> For information only: the patch undoes a change introduced in
>
> commit 8af70c688c0d293ecb1e5d725b32f32f51d522fc
> Date: Fri Apr 11 14:54:57 2014 +
>
> If possible
Indeed, Robin Gilks endian corrections were in 2.9p3
Can you try a newer version and see if the problem persists?
Paul
On Thu, Aug 7, 2014 at 2:45 AM, Robin Gilks wrote:
>
> > Hi Paul,
> >
> >
> > On Wed, Aug 6, 2014 at 9:54 PM, Paul Alfille
> > wrote:
&g
Hi Akos,
Can you clarify? Do some combinations of platform and version work and some
not? Or do you have trouble in all circumstances.
Also, which fields are you setting and how are you testing? You can set the
state of the tri-state pin to conducting or non-conducting or sensing, but
the actual
The code does confirm that your device is found.
How about the simplest test,
root@PiDoor:~# owserver --fake=10 -p 4304 --error_level=9 --foreground
Just to make sure that the problem is the bus-master code.
Paul
On Fri, Jul 25, 2014 at 4:03 AM, Thomas Oeding
wrote:
> Hello all,
>
> i assemb
I've not written code structured this way, so I'd have to learn myself
> how to. I assume you are describing a process where the calling code
> creates a thread for each owfs read operation, carries the reads out and
> returns them to the calling function (or puts them where they
f OWFS and
just issue reads for each of your sensors in separate threads. Each will
return when done. They can run concurrently if the sensor is powered.
Paul Alfille
On Thu, Jul 10, 2014 at 2:09 PM, Colin Reese wrote:
> Hello,
>
> After talking with iButtonLink, it was brought to my a
We care! And thank you.
I'll review and apply the changes.
Paul
On Wed, Jul 9, 2014 at 9:55 AM, ppanish wrote:
> For anyone who cares,
>
> Attached is a new version of ow_1820.c with minor modifications to correct
> operation with the MAX31850 thermocouple sensor. I have checked operation
> w
might be reported by the system (dmesg).
I have a BBB and can try to see if I get the same errors if you describe
your setup a little more.
Paul Alfille
On Sat, Jul 5, 2014 at 8:32 PM, Loren Amelang wrote:
> My problem with 12-bit reads degenerating to half-degree steps seems to be
> hid
EDS
http://www.embeddeddatasystems.com/OW-ENV-TH--Temperature-Humidity-Sensor_p_168.html
iButtonLink: http://www.ibuttonlink.com/products/ms-th
CMCIEL:
http://www.cmciel.com/products-solutions/individual-products/relative-humidity-sensor-mrh001/
PCSensor: http://pcsensor.com/index.php?_a=product&pr
and systemd.
3. What's the best way to test and the monitor?
Paul
On Mon, Jun 9, 2014 at 7:01 AM, Tomasz Torcz wrote:
> On Thu, Jun 05, 2014 at 05:34:01PM -0400, Paul Alfille wrote:
> > Tomasz,
> >
> > I'm having trouble visualizing how the systemd triggering works. W
; we should be looking for one. If we are explicitly told which serial to use
> though, we can try to open it, but will get permission denied if that is
> the case (if I recall correct).
>
>
>
> On 23/06/14 14:39, Paul Alfille wrote:
>
> How about imbedding a list of known good vi
ULL
> (12Mbps) pwr=ON (44mA)
> bcdUSB = 0x0110
> iProduct = 0x0002
> iSerialNumber = 0x0003
>
> Not so much to go on.. the iProduct string is different, but I bet the
> chip is not exactly the same, and that any FT232R based design identifies
> itself as "FT232R USB
This is incredible work. Definitely will add to the master branch once the
final touches and test are done.
It's easy, using libusb, to read the vendor/product code. We do it for
DS9490R adapters now. Beyond vendor/product codes, there are many other USB
strings. One of them might be characteristi
The DS2438 is certainly supported and used in any number of devices
(humidity sensors, multifunction sensors from HobbyBoards and iButtonlink
among others).
he DS2436 is supported based on it's datasheet, but I can't recall if it's
been tested in real life. The command set is similar to the DS2438
4 at 1:50 PM, Jan Kandziora wrote:
>
>> Am 12.06.2014 12:38, schrieb Paul Alfille:
>> > So can we have the situation where owserver waits for both
>> >
>> > 1. the USB device (say) to be available
>> > 2. a request to come in
>> >
>> >
So can we have the situation where owserver waits for both
1. the USB device (say) to be available
2. a request to come in
and appear always available to the clients?
On Wed, Jun 11, 2014 at 7:59 AM, Jan Kandziora wrote:
> Am 11.06.2014 13:04, schrieb Paul Alfille:
> >
> &g
I think differences between the 2 ARM platforms are at a lower level than
owfs. owfs basically uses the kernel-supplied i2c drivers for DS2482-X
communication. My guess is that one platform is using a dedicated i2c port,
and the other is using bit-banging GPIO support.
Paul Alfille
On Wed, Jun
05, 2014 at 05:34:01PM -0400, Paul Alfille wrote:
> > Tomasz,
> >
> > I'm having trouble visualizing how the systemd triggering works. When a
> > program like owread tries to contact owserver, is owserver started? Is
> this
> > done by monitoring the typical ow
Tomasz,
I'm having trouble visualizing how the systemd triggering works. When a
program like owread tries to contact owserver, is owserver started? Is this
done by monitoring the typical owserver port (4304)? How about other
owserver friends?
If you don't mind describing the process more, or givi
Tomasz, would you use dbus for systemd? And would you send 1-wire data that
way or just program control.
Looking at dbus, it certainly looks like 1-wire data could map to it
easily. I'm just not sure if it would be useful.
Paul
On Tue, Jun 3, 2014 at 4:57 PM, Tomasz Torcz wrote:
> On Mon, Jun
Your changes were applied, Stefano.
Jan, I'd be happy to make any changes that ease package maintainer's work.
On Tue, Jun 3, 2014 at 9:08 AM, Stefano Miccoli wrote:
> No, I do not think: I addressed only problems on Darwin.
>
> BTW I tested my patch under the assumption that manpages are inst
I'll order one. I guess running 1-wire via one of the GPIO pins would be
the simplest solution. No mention of power source or budget that I could
find.
Paul
On Tue, May 27, 2014 at 12:20 PM, Colin Law wrote:
> This might make a nice wifi remote 1-wire server if it gets off the ground.
>
>
> ht
I like that name "owfsd" but the program is confusingly called just "owfs"
Paul
On Wed, May 7, 2014 at 12:27 AM, Roberto Spadim wrote:
> ops :P you are right, owfsd isn't running try starting it , you will need
> fuse filesystem support
>
>
> 2014-05-07 1:24 GMT-03:00 Eloy Paris :
>
> The owfs
es. This has to be done on all the forwarding nodes because the loop
> may not include the originating node. That is a far greater limit than hop
> count, IMO.
>
> jerry
>
>
> On 05/02/2014 08:38 AM, Paul Alfille wrote:
>
> Yes, I chose the second approach (hash of some relat
Thanks to quick testing by Stefano Miccoli and Johan Strom!
Release Notes owfs 2.9p5
5/2/2014
Fixes some show-stopper bugs in 2.9p4
Fixes:
1. Token creation problem from Stefano Miccoli
2. Select when no DS2409 (Microlan hub) present
Found by Johan Strom
Redacted release 2.9p4:
Release Note
The size is constant, the odds of duplication are vanishingly small and it
> discloses no information. You don't need anything secure, so 128 bit MD5 is
> fine and there may be even shorter ones. This requires having the crypto
> hash software available, which may be a challenge across
small bug in the new antiloop code
> (module/owserver/src/c/owserver.c) please see the attached patch.
>
> Stefano
>
>
>
>
> PS:
>
> in my opinion, instead of the MD5 hash of some process data, a UUID <
> http://en.wikipedia.org/wiki/Universally_unique_identifier>
1 - 100 of 2297 matches
Mail list logo
