>So if you check the bus.x contents after startup, and select the mapping you >like, it should stay consistent for that run of OWFS.
Seems i need to mount it twice.. The setup of system must be easy: 1. I set in config one "known" 1W device, it must be a +5V sensor with led. I specify how much lines are used and their functionality. known_device=12.12345AB0000 hvac_line=yes 2. Run the initialisation script which find all connected adapters and ask to connect the "known device" to $hvac_line. The conformity between $hvac_line and adapter registers in config: hvac_adapter=81.12345AB0000 Same for other defined lines. 3. i2c power management must be ready. It switches all GPIO of all IO chip's to find the right one for current line. We got this in config now: hvac_power="/dev/i2c/chip1/gpio1" Same for other lines. Power management can be done and with DS2408. 4. Connect the 1W buses to PSU (hub) out. Run hvac initialisation script. It will ask for temperature device $incoming_air and wait until somebody touch it by finger: incoming_air=10.12345AB0000 Same for other parts and 1W lines. Now i have different configs for independent "lowlevel" owfs scripts and a main config where adapters and lines are set. No crosstalks are allowed - 1 owfs process per task. I can use this config for setting up after boot. But after that all 1W lowlevel scripts run separately and check for devices present independently. When something fails, its goes on according the rules (may be just a replament?). I want to have owfs process for hvac mounted on /mnt/1wire/hvac. I dont use in config and in code usb ports or something. Does it means that i need to mount it twice? Or there is (will be) a feature to mount by adapter's ID? Errors with more than 4 adapters doesnt annoy me, i will use in one owfs process maximum 2. The communication between 15 "owfses" :) will be made by "highlevel" application. And more high-level will be linux-mce on separete server. 15 owfses is exactly what i need, because pulling all nets when something fails is unsecure in my case. Any "unique ID" device can be emulated by microcontroller and read from "failed" deattached device. >When the first master is taken down and the second activated, the bus will be >in an undefined state, and all the devices will need to be initialized. In >general that isn't an issue with 1-wire devices, except perhaps for some of >your PIO controls. I hope any undesirable switchings will not occur? >My impression is that the wiring is transparent to owfs. We really don't see >anything on the other side of the Bus Master, except throug the master. If you >can conceive of out-of-band control, I'd be happy to consider adding it. With 2 optocouplers before one DS2490 will be possible to connect one adapter to 2 usb ports and use master's config on slave PC. Why not? i2c + owfs seems to be powerful, but i2c over usb is very new and untested. 1W without +5V becomes unstable, especially switches. It could be possible to control 1W PSU by i2c and use i2c in some situations, may be even in same cable. Also technical difficulties with patching 1W trunk exists. I think this is complex trouble. All application notes based on single master adapter and DS2409 are out of date. I know only bash and electronic hardware, thus have no ideas how to wire correctly. Russian company Elin has a lot of experience in 1-wire, i am gotta ask them. All my software solutions will be GPL, and hardware too (with schemes and boards). I try to make it cheap and reliable. ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
