Eric
They are truly in series. The LinkUSB light will come on dimly all the
time with a long cable with nothing attached to it and stay on all the
time dimly. The light should only be on when there is traffic on the
network.
Colin
Colin,
Are your devices truly connected in series or are
On 27 January 2014 23:33, Jim Lill j...@jimlill.com wrote:
Can the owfs directory and files be shared across a network?
Possibly, but instead I would recommend instead using owserver and
accessing the server across the network. That is what owserver is
for.
Colin
Owfs looks at all the bus masters and queries each of them (actually its a
little smarter and remembers locations). Owserver (even remote) is handled like
just another bus master. Only with better communication protocol (tcp) and
remote caching. Which us why I suggest remote owserver. Like an
Thank you for your precision!
I'll correct the calculation for the next release.
As a side note, I am told that the real precision of the A/D conversion is
8 bits, not 16, which probably is a larger source of error. I recall
discussions of trying to make a drop-in replacement for the DS2450 with
Hi,
In the talk about wireless connection, no one mentioned Dash7. I am
solving a different problem and looking at it Dash7 seems to be the
perfect solution. It has longer range, low power, message based
transmission and location ability. It seems like the ideal package for
remote sensors.
I just looked at dash7 -- 439MHz radio. Looks interesting, but its not yet
clear to me out how it would fit in.
I'm trying to download the protocol but how do you envision using dash7? As
communication from sensors directly, or as dash7-enabled bus masters?
Does dash7 have unique addresses for
It looks great, but where is the hardware?
On Tue, Jan 28, 2014 at 11:57 AM, Paul Alfille paul.alfi...@gmail.comwrote:
I just looked at dash7 -- 439MHz radio. Looks interesting, but its not yet
clear to me out how it would fit in.
I'm trying to download the protocol but how do you envision
I take it your microprocessor doesn't run linux. In that case, you want it
to look like a serial bus master.
There are 3 serial bus masters that I can remember off hand: the DS9097U,
the Link and the HA5. The later 2 use a much simplified serial data stream
(simple ascii), and I think are both
Is there a good reason why a micro can't emulate a serial bus master?
On Tue, Jan 28, 2014 at 12:12 PM, Paul Alfille paul.alfi...@gmail.comwrote:
I take it your microprocessor doesn't run linux. In that case, you want it
to look like a serial bus master.
There are 3 serial bus masters that
Sorry, reading your last sentence, you did address this. Why would you not
recommend trying this? Error-prone?
On Tue, Jan 28, 2014 at 12:12 PM, Paul Alfille paul.alfi...@gmail.comwrote:
I take it your microprocessor doesn't run linux. In that case, you want it
to look like a serial bus
Paul,
I was imagining it as a channel back from a remote bus master. Dash
supports 2 byte local net addressing and 8 byte unique addressing. It
was designed to play well with RFID, so I would assume that unique
addresses would be of that form. Since 1-wire is a master/slave
messaging system,
Very interesting.
You're right, we could just add it to owserver We'd just implement the
owserver messaging protocol, which is also message based.
Is there a trial platform? And what do the device addresses look like? (I'm
trying to think of the command line format).
Paul
On Tue, Jan 28, 2014
The emulated serial requires changing baud rates for each 1-wire
communication, and using a serial byte to send each 1-wire bit. Since most
computer UARTs have a pretty small buffer, the CPU does a lot of work
waiting for the serial data.
A microprocessor is great for low-level bit-banging, but
if anyone have the link to buy the hardware i could buy and leave a
virtual machine online to test
2014-01-28 Paul Alfille paul.alfi...@gmail.com:
Very interesting.
You're right, we could just add it to owserver We'd just implement the
owserver messaging protocol, which is also message
/)
i didn't tested this one, but they work like a multi drop network
(rs485)? for example, using one serial allow 10+ ow bus?
2014-01-28 Paul Alfille paul.alfi...@gmail.com:
The emulated serial requires changing baud rates for each 1-wire
communication, and using a serial byte to send each
hum found some nice links about dash7
http://www.fritz-hut.com/2013/01/04/home-automation-using-dash7/
http://sourceforge.net/projects/opentag/
http://www.ti.com/lsds/ti/microcontroller/16-bit_msp430/new-cc430.page?DCMP=CC430HQS=cc430
http://www.dash7.org/ (obvious)
anyone found some sensors
Understood. Thanks for the explanation.
On 1/28/2014 16:07, Paul Alfille wrote:
The emulated serial requires changing baud rates for each 1-wire
communication, and using a serial byte to send each 1-wire bit. Since
most computer UARTs have a pretty small buffer, the CPU does a lot of
work
Roberto,
It seems to be the problem that it all sounds great but there is very
little hardware out there. I was hoping some of you might have seen more
hardware.
This all started as a smart RFID tag system for the military. It seems
like it could be so much more, with the longer range, easy
18 matches
Mail list logo
