s essential for
reliability. Having moved from breadboard to a PCB with slave on, I
added this to the network at the weekend and again had at least 50% data
errors, and it was an "oh no, not again" feeling. However as soon as I
connected the unused white/green at the master, it became 10
they would be ok if for each slave
that was created, the unique device ID was taken from a real part that
was destroyed or at least never released into the wild so that there
would never be a clash, or whether they simply don'
pi listings since
they went in, and these are even more insane.
Nick
--
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers wor
On 16/12/2011 01:08, Nathan Hurst wrote:
> On Thu, Dec 15, 2011 at 09:21:32PM +, Colin Law wrote:
>> On 15 December 2011 15:44, Nick wrote:
>>> ...
>>> After fiddling a little and getting nowhere, I brought in my laptop, LA and
>>> some other kit to the off
Hi Eloy
"Eloy Paris" wrote in message
news:4eea41df.7090...@chapus.net...
>
> I do find it very odd that things work perfectly when the LinkUSB is
> connected to a laptop but don't work when the LinkUSB is connected to
> another machine because the 1-Wire network is connected to the LinkUSB,
> n
for data and is fine as I said.
I would welcome any views about why the experiments made a difference, such
as different PC's, why laptop is fine and not PCs, connecting the LA earth
etc.
Nick
--
10 Tip
ire
works out fine for the 10 temp sensors we currently have.
Nick
--
10 Tips for Better Server Consolidation
Server virtualization is being driven by many needs.
But none more important than the need to reduce IT com
ks fine too.
So that would be my vote unless you need much larger storage, in which case
a laptop drive instead of SSD, or a separate NAS box.
Also, it uses x86 instruction set making it likely that pre-built
executables will run.
Good luck.
Nick
and where it was
expecting to receive read timeslots so that it could send back the ~CRC16.
The flowcharts on the datasheet show nicely what the device is supposed to
receive and send back.
Nick
--
All the data continuou
recommendation for a different memory oriented part to emulate then the
choice can easily be changed. It just needs to be a part that has about
8 bytes or so of writeable address space.
Nick
--
All the data continuously
I've been writing a small perl script to parse my 1-wire network giving just
the immediately useful values back.
One thing i have noticed is that the couplers are showing both branches are
live when i read them (cached or un-cached values), which the man pages say
is not allowed.
*"Is the branch
>> My current setup checks outdoor and greenhouse temp to determine
>> whether to turn on a 240VAC power switch to heat up (or cool down)
>> the greenhouse. owfs polls every 15 seconds?
> owfs never poll on itself !
If owfs never polls itself, how does the cached directory structure get
updated?
lt;<<<<<<<
|-- Office_Hub2
| |-- aux
| `-- main
|-- Office_Hub3
| |-- aux
| `-- main
|-- Test_DS1820_S
| `-- errata
|-- USB_Dongle2
`-- alarm <<<<<<<<<<<<<<<<<<<<<<<<<
`-- Test_DS1820_S
`--
ves a write error. In case
it's relevant, there are eleven powered 18b20's on the network with a
LinkUSB 1.4 driver. 2.8p4 appears to be the last good version.
hth.
Nick
--
What You Don't Know About Data C
ust fine.
>
> http://bytality.com/gallery/1-wire_setup/
>
> As far as 85°C, my temp collection script takes a series of readings and
> then tosses any that are outside a predefined distance from the average.
> Granted, my aquarium should never hit anywhere near 85°C, but it got rid
Here are my water proof sensors using copper pipe and HMA, they have worked
well so far.
http://kiwi-hacker.blogspot.com/2011/01/new-soil-temperature-sensors.html
On Wed, Mar 2, 2011 at 9:57 PM, Mick Sulley wrote:
> On Wed, 2011-03-02 at 09:18 -0600, Guil Barros wrote:
> > > Hhmmm. Interestin
I've found that you need to unmount the 1-wire mount point as well
below is my init script, which you can edit and run.
Rgds,
Nick.
#!/bin/sh
#
#
# owfs - init script
#
# v1.0 - Nov2010 - CrossN - Initial re
I am getting a steady amount of select errors on my long-ish micro lan.
I edited the owfs code to determine which select error i was actually
getting, it seems i am getting a lot of BUS_transaction_nolock errors on the
main branch of each of my couplers. No errors report on the aux branch
strange
Excellent, that has done it.
Can i ask why "bus.0" is in the path twice ? I hadn't noticed it before.
Best Regards,
On Tue, Feb 8, 2011 at 4:48 AM, Paul Alfille wrote:
> What's your topology? I.e., it's possible that
> $ cat /var/1wire/bus.0/bus.0/interface/statistics/select_errors ;echo
19 matches
Mail list logo
