My criticue fucusses not to my bussiness but rather to physical/electrical
properties and principles of 1-wire which never was designed as long or
middle range network.
Would you like to discuss with phisic ?
There is no software which is able to change a car into a space ship.
As I wrote I have
Thank you for the file.
I agree about the problem with long runs and complex wiring topologies. I
was just pointing out that some of these problems can be overcome with
OWFS's ability to aggregate many bus masters over a TCP network seamlessly.
What software do you use with your systems? Are
For what it's worth I was repairing voltage supply on HP DV6000 laptop
and noticed that there were 2 maxim chips. At least one was in the power
management area. There was also mention of 1 wire bus use.
Paul Alfille wrote:
Zapinio, I think your critique focusses on your own business. 1-wire
Hi zapinio,
Regarding protocol property, maybe proposing alternate slave is discussable.
As you, I simply note that 1-wire offer is slowly going out.
My offer is not an competing product to Maxim-Dallas, It is more a
complementary solution to existing standard products.
I agree for your remarks
Zapinio, I think your critique focusses on your own business. 1-wire has a
lot to offer. Further, I don't know of a system similar to OWFS that
provides a simple layer between the hardware and a consistent interface for
programming and design
The best choice of technology depends on the specifics
On Fri, 5 Mar 2010, zapinio wrote:
It can be used for free ONLY for slaves of Dallas origin. It is patented and
selling of third party slaves was (is?) not accepted by Dallas/Maxim.
Those patents must be close to expiring by now?
notes about reliability agreed.
njh
This is a long response with lots of technical stuff.
For the casual reader, here is the short version:
I propose:
* memory-map based interface
* pre-defined 'drivers' for different functionality
* keep driver interfaces as close to uC hardware implementation as possible
* drivers can and should
On Wed, Feb 24, 2010 at 4:15 AM, nufan_...@comcast.net wrote:
OWFS typically presents all of the possible functions of a device in the
directory for that device, eg take my DS2780: It has a high-sensitivity ADC
which can be used to measure tiny voltages. Those tiny voltages can also be
Ah, ok I was not aware of that
How do you feel about the mini driver (per functionality) concept?
Owfs is probably already built in a somewhat similar manner for other
devices (temp. sensors perhaps)
-tmk
On Feb 24, 2010, at 3:28 AM, Paul Alfille paul.alfi...@gmail.com
wrote:
On Wed,
On 24 February 2010 09:15, nufan_...@comcast.net wrote:
For the casual reader, here is the short version:
I propose:
* memory-map based interface
* pre-defined 'drivers' for different functionality
* keep driver interfaces as close to uC hardware implementation as possible
* drivers can and
Give me some time and I'll work on a draft spec.
Just confirming, you saw my mini spec at the end of that last email, right?
-tmk
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself.
Hi,
I come from a different world, that of communications protocols, so I
have a different bias. I understand and agree with your desire to expose
as much as possible from a device designer's point of view. I am more
from the system designer side and want to have things be the most
consistent
On 24 February 2010 17:31, nufan_...@comcast.net wrote:
Give me some time and I'll work on a draft spec.
Just confirming, you saw my mini spec at the end of that last email, right?
Yup and liked it a lot! :)
Take care,
Ben
On Wed, Feb 24, 2010 at 12:45 PM, Jerry Scharf
sch...@lagunawayconsulting.com wrote:
I think we need to look into loadable drivers for OWserver/OWFS. [I can
imagine smoke coming out of Paul's ears.] Once drivers become complex,
this is the next step of being able to load, unload and update
I've been thinking about this issue off and on for a couple years now,
and I like a large part of what I see so far, but also want to throw
in some thoughts.
After reading some details on the BAE chip as well as talking to some
embedded designers and thinking about applications, I envisioned
I agree with most of this. After discussing this with a friend, we
came to the conclusion that most uC implementations will support only
what is actually implemented in their ROM image, and little else, so
exposing all the functions is probably not helpful, but is still
possible if
On Tue, 23 Feb 2010 nufan_...@comcast.net wrote:
Anyone have other suggestions for functionality?
Integrator, DAC, bidirectional counter ('quadrature').
What sort of integration are you talking about here? voltage sampling? sounds
interesting
Yep, take a sample every x ms and add to a
Sorry to be blunt, but this is exactly what I want to avoid.
Just because you are implementing your DAC in one form doesn't mean that
others will. We need to have a common model that allows OWFS to present
a rational access model to differing implementations of the same
functionality. That's
Power injection. Although which scheme to use is unclear.
http://owfs.org/index.php?page=wiring-standards
Paul Alfille
On Tue, Feb 23, 2010 at 4:02 AM, njh n...@njhurst.com wrote:
So are there any shortcomings of existing adapters which would be worth
addressing?
Hi Pascal,
Thanks for this awful chip - i just ordered a free (thanks again) demo
board ...
What are your plans for availability - lets say if i want to use this
device for a commercial application - are the chips still available in,
lets say, 10 years ?!?!
thanks a lot,
marcus.
Hi marcus,
Availlability: I really don't have a cristal globe to tell the future, even
less over 10 years...
But if for any reason I would stop this activity, I will pass the relay to
someone else, or even open source the project...
My short planning is to propose alternate board based on the
On 22 February 2010 15:22, Pascal Baerten pascal.baer...@gmail.com wrote:
But if for any reason I would stop this activity, I will pass the relay to
someone else, or even open source the project...
I'm a newcomer to 1-wire and was a bit disappointed to see the DS2423
phased out and joined this
I am writing a 1 wire slave library for the AVR series of
microcontrollers.
That should allow you to do all the stuff you want.
Hooking into OWFS might be a little tricky if everyone implements
their own functionality though.
If a standard set of functionalities can be agreed on, (counter,
I have a few thoughts on this.
First, I would love to see a model for DAC as well as PWM for output. A
simple two double byte model with a 16 bit set for signed output and 16
bits for log gain. Clearly there is nothing that you are going to hook
to a 1-wire bus that is capable of this kind of
We've intermittently worked on this. I have one student who has made
the beginnings of PIC code for OW slave interface, although has
implemented very few of the commands so far.
I also have some C code intended for compiling for the Atmel to
implement the timings and raw read/write for slave
On Feb 22, 2010 11:25 AM, tmk nufan_...@comcast.net wrote:
Off topic:
I have also considered making a complete clone of the DS2490 (usb to 1
wire master) on an AVR chip. $30 is too much for a USB - 1wire adapter!
An ATTiny chip should be able to handle it no problem
Would this be interesting?
On Mon, 22 Feb 2010, tmk wrote:
If a standard set of functionalities can be agreed on, (counter, pwm,
tri state pio, temp sensor, ADC, memory access), then almost anything
could be done
Anyone have other suggestions for functionality?
Integrator, DAC, bidirectional counter ('quadrature').
On Mon, 22 Feb 2010, Pascal Baerten wrote:
I like open source concept, it is just not easy to keep a business model
compatible with it...
I for one will buy a premade unit even if I could make it myself if it
comes on a nice pcb. If it's open source and I can modify it, I'm even
likely to
On 22 February 2010 18:33, Paul Alfille paul.alfi...@gmail.com wrote:
It's fine to stay on this list. The discussion is welcome, in fact.
That's great news - many thanks!
There's definitely a place for a generic protocol for a device that
tells the master the capabilities of each of it's I/O
On 22 February 2010 21:54, Pascal Baerten pascal.baer...@gmail.com wrote:
My target is indeed versatility and I think we share the same objective.
I like the BAE0910 a lot and can't wait to get my hands on one! :)
Ben
I also have some C code intended for compiling for the Atmel to
implement the timings and raw read/write for slave devices on the OW
bus. This hasn't been tested at all yet.
Sounds like i'm a bit farther along then
In any case, I may be able to get someone on this over the summer.
feel
First, I would love to see a model for DAC as well as PWM for output.
Well, i view DAC as primarily a hardware interface to either PWM or PIO
features. The chips themselves (at least AVR) do not directly support DAC, but
you can either do PWM with a Resitor+capacitor smoother, or a R2R
Hi Pascal.
Might be a stupid question since I'm not a hardware guy but would this
chip be suitable for my project to try and read by central heating meter
which has an optical serial (RS232) interface? Could you fit in a simple
RS232 stack on the chip or should/could you run the code on the
Hello Johan,
Not a stupid question. I should say that I've similar need for my wood
pellets boiler who accepts rs232 connexion. However, the BAE0910 has no uart
pin available.
Emulating uart communication on a PIO is feasible for tx, but rx is not
reliable with polling, even at 2400 bps.
I plan
Hi Paul, is version 2.7p29 available ?
-Original Message-
From: Pascal Baerten [mailto:pascal.baer...@gmail.com]
Sent: Tuesday, February 02, 2010 10:17 AM
To: OWFS (One-wire file system) discussion and help
Subject: [Owfs-developers] Announcement for a new 1-wire slave device
BAE0910
-wire file system) discussion and help
*Subject:* [Owfs-developers] Announcement for a new 1-wire slave device
BAE0910
Hi,
I'm pleased to announce the BAE0910, a new multifunction 1-wire slave
device!
Functions such pulse width modulation and embedded logic are now possible
on your 1-wire
system) discussion and help
Subject: [Owfs-developers] Announcement for a new 1-wire slave device
BAE0910
Hi,
I'm pleased to announce the BAE0910, a new multifunction 1-wire slave
device!
Functions such pulse width modulation and embedded logic are now possible on
your 1-wire network.
The BAE0910
Hi,
I'm pleased to announce the BAE0910, a new multifunction 1-wire slave
device!
Functions such pulse width modulation and embedded logic are now possible on
your 1-wire network.
The BAE0910 was the missing link of most 1-wire projects.
Main features:
- 1-wire compatible
- up to four PWM
38 matches
Mail list logo
