With the help of William Farmer at iButtonLink.com, we now have support for the Link-Hub-E.
This is a Link adapter connected via ethernet. The syntax is the same as owserver: owfs -s 10.23.45.67:10001 /1wire Where the ethernet address of the Link-Hub-E and port are given. OWFS will be able to distinguish between owserver and Link-Hub-E. Note that owserver can accept multiple connections, Link-Hub-E cannot (but you can use owserver to multiplex it, just like any adapter. Some caveats: 1. Only limitted tested was done, to a Link-Hub-E at Bill's company. Reads, writes and directory listings all worked. I don't have one myself for testing. 2. I needed to introduce the concept of a network timeout (to distinguish between owserver and Link-Hub-E), and the timing is empiric. Long network latency will make the Link-Hub-E undetectable, and the default owserver will be assumed. 3. If the Link-Hub-E is unavailable at configuration time, owserver will be assumed. We may need to adjust this wit ha command line parameter. -- perhaps owfs -s 3001 /1wire will be either owserver (default) or Link-Hub-E if detectable owfs --LINKE 3001 /1wire will be Link-Hub-E only owfs --owserver 3001 /1wire will be owserver only But I'm open to suggestions. Paul Alfille ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
