Am 15.02.2015 um 21:48 schrieb Colin Reese:
> Yes just run a micro controller non-stop and have it announce presence over a
> serial port.
>
No, USB. I made a simple software for doing this on a random ATtiny
processor with the help of the V-USB firmware.
http://vusb.wikidot.com/project:vusb
K
Very strange. The devices you see look like /sys entries from the operating
system. Nothing that owfs would generate.
What you should see is:
home/paul/1w/3A.F2FBE3467CC2/
├── address
├── alias
├── crc8
├── family
├── id
├── locator
├── PIO.A
├── PIO.ALL
├── PIO.B
├── PIO.BYTE
├── r_address
├── r_
And that's easy to do. I database everything immediately including device type
and other metadata and separate control scripts act on data, including device
presence.
If time response is important, you can insert the response functions into the
detect script as well. Read devices, check agains
I wasn't sure what Daniel wanted.
Well, I was hoping that someone would say, "Well, when your application
initializes, you register Subroutine X to be run as soon as something new
appears on the bus."
And then, when that sub gets called, you check the serial number of the new
thing, if it matc
Hello!
I wasn't sure what Daniel wanted. The more complicated explanation. Or
the overly simplified one. Or one that left our friend even more
confused.
The one presented is largely based on an explanation given to me by
one of the folks at Dallas Semiconductor shortly after the whole
business got
Yes just run a micro controller non-stop and have it announce presence over a
serial port.
C
> On Feb 15, 2015, at 12:37 PM, Paul Alfille wrote:
>
> 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'
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
Paul:
> Periodic polling is the best way.
So are you saying that if I have an iButton base on my network, I have to be
constantly running through a 1-Wire directory search and looking for the button?
So if I wanted to use this to open a door, and wanted reasonable response time
I’d have to be
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
Hello!
A good question. One I've asked myself countless times, before Paul
wrote his excellent tool set and realized there was a better way to
manage certain storage methods.
Let's say you own an iButton of the type who contains a DS2401
electronic serial number. Inserting it into the reader will
OK, I'm going to come across as really stunned here, but if I don't ask, I
won't learn.
I am accustomed to having devices -- mostly temperature sensors -- on my 1W
bus, getting a catalog of them by hand, and then entering the serial numbers
into a configuration file in my sofware, which then qu
Hi Paul,
sorry for the delay. Yes my device has family code 3A.
These are my devices:
cd /sys/bus/w1/devices/
pi@hauspi /sys/bus/w1/devices $ ls -l
insgesamt 0
lrwxrwxrwx 1 root root 0 Jan 12 20:18 28-061549ec ->
../../../devices/w1_bus_master1/28-061549ec
lrwxrwxrwx 1 root root 0 Jan 1
12 matches
Mail list logo
