Re: [Owfs-developers] owfs.org is down

I'm happy to chip in to keep the domain. I can also secondary dns & email. Where is the mailing list hosted? That probably needs to live somewhere too... On 12 April 2019 3:45:49 am AEST, "Johan Ström" wrote: >Personally I'm voting for a technical solution such as described in

Re: [Owfs-developers] Suggestions of Microcontrollers for 1-wire use.

or using a readonly root filesystem - Buildroot & OpenWRT are both good choices to build this. -- Alastair D'Silva mob: 0423 762 819 skype: alastair_dsilva Twitter: @EvilDeece blog: http://alastair.d-silva.org On Thu, 2019-02-21 at 23:54 +0100, Stefano Miccoli via Owfs-develo

Re: [Owfs-developers] Reliability and Robustness of the DS2482-100 or DS2482-800

7/02/2019 22:13, Alastair D'Silva wrote: >> The series resistance within a DS9503 should be sufficient, I hope. >It's worth using these anyway, for ESD protection. >> > > >___ >Owfs-developers mailing list >Owfs-developers@lists.s

Re: [Owfs-developers] Reliability and Robustness of the DS2482-100 or DS2482-800

The series resistance within a DS9503 should be sufficient, I hope. It's worth using these anyway, for ESD protection. -- Alastair D'Silva mob: 0423 762 819 skype: alastair_dsilva msn: alast...@d-silva.org blog: http://alastair.d-silva.orgTwitter: @EvilDeece > -Origi

Re: [Owfs-developers] Howto configure --i2c=ALL:ALL into config file

Yup, here’s what I use: ! server: server = localhost:4304 server: i2c = /dev/i2c-0:18 owfs: mountpoint = /1wire owfs: allow_other http: port = 2121 ftp: port = 2120 server: port = localhost:4304 -- Alastair D'Silva mob: 0423 762 819 skype: alastair_dsilva msn: alast

Re: [Owfs-developers] Many-port bus master

On Thu, 2018-11-15 at 11:19 +0100, Stefano Miccoli via Owfs-developers wrote: > > On 15 Nov 2018, at 08:27, Alastair D'Silva > > wrote: > > > > > > One question, my code has C99isms, which are fine for modern > > compilers as they default to C99. Older comp

Re: [Owfs-developers] Many-port bus master

default to C90. I can fix this in 2 ways: Easy way: add std=c99 to CFLAGS to force C99 mode Hard(er) way: Remove C99isms from the code. It's not that hard, but it will result in some vars getting a larger scope than they need. -- Alastair D'Silva mob: 0423 762 819 skype: alastair_dsilva msn: alast...

Re: [Owfs-developers] Many-port bus master

Owfs-developers] Many-port bus master > > Am 01.08.2017 um 16:01 schrieb Alastair D'Silva: > > Hi folks, > > > > I'm currently designing an open-hardware 32 port 1wire bus master for > > part of my home automation system, and would like your input. > > > >

Re: [Owfs-developers] Arduino yun as wifi 1wire master

For my pool solar controller, I use an HLK-RM04 module running OpenWRT and a USB9097 1 wire master. If I was doing it again, I would an Orange Pi Zero or simlar to reduce the cost. From: Dr. Trigon [mailto:dr.tri...@surfeu.ch] Sent: Saturday, 22 July 2017 8:25 PM To:

Re: [Owfs-developers] Arduino yun as wifi 1wire master

the eaves (normally made from fibreboard) to drop the cable outside. From: Alastair D'Silva [mailto:alast...@d-silva.org] Sent: Saturday, 22 July 2017 9:02 PM To: 'OWFS (One-wire file system) discussion and help' <owfs-developers@lists.sourceforge.net> Subject: RE: [Owfs-developers] A

Re: [Owfs-developers] Unsupported 1-wire device

entations, such as hiding unavailable directory entries. Incidentally, I've chosen family code FE for my gear, so you may want to pick something different :) -- Alastair D'Silva mob: 0423 762 819 skype: alastair_dsilva msn: alast...@d-silva.org blog: ht

Re: [Owfs-developers] Fine-tune timing against disappearing slaves

One thing I am doing is dropping a low going pulse onto another GPIO pin in my slave implementations, and hooking that up to the logic analyser as well as the 1wire line. That way, I can tell if a pulse originated from my slave implementation, or elsewhere on the bus. From: Sven Giermann

Re: [Owfs-developers] New device driver - write function not being called

> -Original Message- > From: Alastair D'Silva [mailto:alast...@d-silva.org] > Sent: Thursday, 16 February 2017 7:02 PM > To: 'OWFS (One-wire file system) discussion and help' develop...@lists.sourceforge.net> > Subject: Re: [Owfs-developers] New device driver - write

Re: [Owfs-developers] New device driver - write function not being called

g > called > > Am 15.02.2017 um 12:54 schrieb Alastair D'Silva: > > > > Command: > > > > echo "5,10,15,20,300" > /mnt/1wire/FE.DECEA5EDBEEF/channel0 > > -bash: echo: write error: Invalid argument > > > Is your parse_rgbw_stri

[Owfs-developers] New device driver - write function not being called

5EDBEEF/channel0 Extension 0 Gives result -22 DEBUG: ow_write.c:(437) Write a non-array element /FE.DECEA5EDBEEF/channel0 DEBUG: ow_cache.c:(1362) Delete from cache sn FE DE CE A5 ED BE EF E5 in=0x7ff3f1d10f40 index=0 DEBUG: ow_write.c:(495) Write /FE.DECEA5EDBEEF/channel0 Extension 0 Gives

Re: [Owfs-developers] Hiding incompatible device variants

> Am 10.02.2017 um 22:04 schrieb Alastair D'Silva: > > Hi folks, > > > > I've written a 1Wire slave implementation for ARM (which I will be > > open sourcing), in order to implement some functionality that does not > > exist in the 1Wire world (multichannel RGBW con

[Owfs-developers] Hiding incompatible device variants

specific struct, and potentially alter the visibility of the files so that only the relevant content is visible to the user. Could you please advise whether I am on the right track, or if there is a better solution? Cheers, -- Alastair D'Silva mob: 0423 762 819 skype: alastair_dsilva msn