Show Posts
1
Users / Re: Dallas Semiconductor 1-Wire Questions
« on: January 28, 2010, 05:02:25 am »
To all - so many questions... I have no coding skills and not much useful experience with Linux. please bear that in mind all...
Please do not take this as me being nasty or a - insert colorful metaphor -. I am simply trying to assess the state of LMCE and whether I am appropriate for it - if you get my meaning. Is there no archival data available aid in recovering the loss of the driver? This kind of 'disappearance' suggests this project exists on the brink of calamity. What am I missing? This also suggests interest in 1 wire is almost non-existent in the LMCE community. To me, that means I would be more on my own than I would like to be. As I see it 1-wire is a very powerful and flexible technology that would draw interest to LMCE and so would not be easily 'dropped' - perhaps it wasn't easy... Sorry if this is an excessively simplistic question/observation.
Again, I am asking because I am totally unable to assess this on my own - what is meant by driver in the MCE context? I ask because there is this thing called FUSE (user file system I guess) now in the kernel (?) and this thing called OWFS (One Wire File System) and optionally OWHTTPD etc. I had OWFS/OWHTTPD working alongside MisterHouse on ubuntu 6.? as I recall and owfs had built in support for most, if not all of the available 1-wire chips at the time. I had some problems with Misterhouse that derailed me at that time. Also, MH seemed to be stagnant then and It doesn't seem to have improved since. None of it was all that difficult to get going - it couldn't be, if I did it! Anyway, OWFS provided both flat and tree file structure (I think) that reflected the one wire devices connected to the host beginning at the configured mount point. It gave at least some control over most aspects of the management of the 1-wire net but didn't need to be hand cranked to get useful info to and from devices. I don't know how LMCE handled 1-wire before, or if it still does - just not the usb dongle. Again, ignorance speaking here, but it seems like it would be not so difficult to add OWFS to LMCE. What would then be needed is code to scan the directory tree(s) - multiple 1-wire interfaces to discover what devices are connected, and code to allow proper interaction with the various device types available (driver?). One thing that might require a little bit of extra smart code might be reading the branches of a 1-wire tree. I don't recall just how that worked. There was the possibility of using a 1-wire part to isolate branches to limit the effects of capacitance and thus permit larger nets and more reliable comms. without needing more host interfaces etc.
So:
Does LMCE support 1-wire at all now? I still see Dallas Semi and the USB host adapter in child device setup...
What host interfaces are supported?
Does LMCE use OWFS? (Where is it mounted?)
If it doesn't use OWFS, was OWFS considered and rejected? Why?
Any illumination would be appreciated.
Assuming I can get the rest of what I need working in the short term on my dinosaur, I would be willing to do some testing of beta code to help get 1-wire USB going again... I have 2 of the USB host interfaces, and can deploy nearly a dozen temperature sensors within 6 weeks or so. Once that part works I would add some discrete I/O points - perhaps 8 for starters.
To Trentend:
If your remarks were to me, I have a WRT610N that I would use more or less as you describe (dd-wrt etc. etc.) but there, I get no basic functions working without writing my own code. Basic stuff to me is things like turn on the outside lights (some controlled by 1-wire outputs) if the driveway sensors sense incoming traffic and it is dark and play a sound if the time is right. Turn off the outside lights if it is sunrise and there was an override on. Otherwise, turn them off 20 minutes (randomize) after the last outside door in the area is closed or driveway sensors indicate departure. Another example - when you hear x10 code A1on send B all lights on and turn on output at 1-wire address (address) etc.
Gotta go.
I do hope LMCE will work for me and that I will be able to contribute something here eventually.
Quote
soooo....write a new driver....we have a considerable architecture for it....either C++ or Ruby...take your pick.
Please do not take this as me being nasty or a - insert colorful metaphor -. I am simply trying to assess the state of LMCE and whether I am appropriate for it - if you get my meaning. Is there no archival data available aid in recovering the loss of the driver? This kind of 'disappearance' suggests this project exists on the brink of calamity. What am I missing? This also suggests interest in 1 wire is almost non-existent in the LMCE community. To me, that means I would be more on my own than I would like to be. As I see it 1-wire is a very powerful and flexible technology that would draw interest to LMCE and so would not be easily 'dropped' - perhaps it wasn't easy... Sorry if this is an excessively simplistic question/observation.
Again, I am asking because I am totally unable to assess this on my own - what is meant by driver in the MCE context? I ask because there is this thing called FUSE (user file system I guess) now in the kernel (?) and this thing called OWFS (One Wire File System) and optionally OWHTTPD etc. I had OWFS/OWHTTPD working alongside MisterHouse on ubuntu 6.? as I recall and owfs had built in support for most, if not all of the available 1-wire chips at the time. I had some problems with Misterhouse that derailed me at that time. Also, MH seemed to be stagnant then and It doesn't seem to have improved since. None of it was all that difficult to get going - it couldn't be, if I did it! Anyway, OWFS provided both flat and tree file structure (I think) that reflected the one wire devices connected to the host beginning at the configured mount point. It gave at least some control over most aspects of the management of the 1-wire net but didn't need to be hand cranked to get useful info to and from devices. I don't know how LMCE handled 1-wire before, or if it still does - just not the usb dongle. Again, ignorance speaking here, but it seems like it would be not so difficult to add OWFS to LMCE. What would then be needed is code to scan the directory tree(s) - multiple 1-wire interfaces to discover what devices are connected, and code to allow proper interaction with the various device types available (driver?). One thing that might require a little bit of extra smart code might be reading the branches of a 1-wire tree. I don't recall just how that worked. There was the possibility of using a 1-wire part to isolate branches to limit the effects of capacitance and thus permit larger nets and more reliable comms. without needing more host interfaces etc.
So:
Does LMCE support 1-wire at all now? I still see Dallas Semi and the USB host adapter in child device setup...
What host interfaces are supported?
Does LMCE use OWFS? (Where is it mounted?)
If it doesn't use OWFS, was OWFS considered and rejected? Why?
Any illumination would be appreciated.
Assuming I can get the rest of what I need working in the short term on my dinosaur, I would be willing to do some testing of beta code to help get 1-wire USB going again... I have 2 of the USB host interfaces, and can deploy nearly a dozen temperature sensors within 6 weeks or so. Once that part works I would add some discrete I/O points - perhaps 8 for starters.
To Trentend:
If your remarks were to me, I have a WRT610N that I would use more or less as you describe (dd-wrt etc. etc.) but there, I get no basic functions working without writing my own code. Basic stuff to me is things like turn on the outside lights (some controlled by 1-wire outputs) if the driveway sensors sense incoming traffic and it is dark and play a sound if the time is right. Turn off the outside lights if it is sunrise and there was an override on. Otherwise, turn them off 20 minutes (randomize) after the last outside door in the area is closed or driveway sensors indicate departure. Another example - when you hear x10 code A1on send B all lights on and turn on output at 1-wire address (address) etc.
Gotta go.
I do hope LMCE will work for me and that I will be able to contribute something here eventually.
