OWFS and the newer 4-Channel Hub from HobbyBoards

davygravy
2014-02-01
2014-02-08
  • davygravy

    davygravy - 2014-02-01

    Greetings,

    How does one go about controlling the HobbyBoards 1-Wire 4 Channel Hub using (only) OWFS?

    I've recently replace my old/dying 6-Channel Hub from Hobby Boards w/ the newer 4-Channel Hub. This replacement no longer uses the DS2409/microlan, and instead uses a newer (proprietary?) chip that I'm unable to positively identify at this point, except that it may be from Embedded Data Systems. ( referring to this http://sourceforge.net/projects/owfs/files/owfs/2.8p18/readme.txt/download ).

    The OWFS.org site shows this: http://owfs.org/index.php?page=4-channel-hub
    … and in particular, mentions :

    The controls for the 2-channel Hub are very simple:
    To read or write status:

    EF.1234323424/hub/branch.0
    EF.1234323424/hub/branch.1
    EF.1234323424/hub/branch.2
    EF.1234323424/hub/branch.3
    EF.1234323424/hub/branch.ALL # a comma separated list of branch status
    EF.1234323424/hub/branch.BYTE # binary number of the status (15=all on, 2=only branch.1 on)

    To me this seems to imply some sort of directory structure in the owfs mount.

    I see, on the other hand,

    root@pogoweather:/mnt/1wire# ls -R EF.123420150000/ -ln
    EF.123420150000/:
    total 0
    -r--r--r-- 1 0 0 16 Dec 31 1969 address
    -rw-rw-rw- 1 0 0 256 Dec 31 1969 alias
    -r--r--r-- 1 0 0 2 Dec 31 1969 crc8
    -r--r--r-- 1 0 0 2 Dec 31 1969 family
    -r--r--r-- 1 0 0 12 Dec 31 1969 id
    -r--r--r-- 1 0 0 16 Dec 31 1969 locator
    -r--r--r-- 1 0 0 16 Dec 31 1969 r_address
    -r--r--r-- 1 0 0 12 Dec 31 1969 r_id
    -r--r--r-- 1 0 0 16 Dec 31 1969 r_locator
    -r--r--r-- 1 0 0 32 Dec 31 1969 type
    -r--r--r-- 1 0 0 12 Jan 28 12:19 type_number
    -r--r--r-- 1 0 0 5 Jan 28 12:19 version

    Can the hub only be controlled w/ proprietary (non-open source) software, or is there something that I'm failing to do in my config that would make the ID-Address/hub directory visible to me?

    Thank you in advance,

    Dave Purdy

    PS: I'm not interested in non-open source. I am aware of the ows package from Axiris.eu, but it is unfortunately non-open source, from my inquires.

     
  • Paul Alfille

    Paul Alfille - 2014-02-01

    What does type number show?

     
  • davygravy

    davygravy - 2014-02-01
    root@pogoweather:/mnt/1wire/EF.209F20150000# cat type_number ; echo
               5
    
     
  • Paul Alfille

    Paul Alfille - 2014-02-04

    Well that's correct.

    Can you run with --debug and grep for "Checking visibility" ?

    Also, try accessing the /hub/ properties "blindly". Might work.

    I have the UVI sensor and will check to see if it still works properly.

    Paul

     
  • davygravy

    davygravy - 2014-02-06

    Paul,

    Thank you for the reply, it is much appreciated.

    A 5 minute or so snippet of debug is at the pastebin link below in case you might find it illuminating somehow.
    http://pastebin.com/0DP8DyNm

    Notably, the string "visibility" (regardless of case) seem to not be present in the debug output.

    I can find no such directory called hub in any (super)directory anywhere...

    My /etc/owfs.conf is shown below inline.

    Dave

    root@pogoweather:/etc# cat owfs.conf
    # Sample configuration file for the OWFS suite for Debian GNU/Linux.
    #
    #
    # This is the main OWFS configuration file. You should read the
    # owfs.conf(5) manual page in order to understand the options listed
    # here.
    
    ######################## SOURCES ########################
    #
    # With this setup, any client (but owserver) uses owserver on the
    # local machine...
    ! server: server = localhost:4304
    #
    # ...and owserver uses the real hardware, by default fake devices
    # This part must be changed on real installation
    #server: FAKE = DS18S20,DS2405
    #
    USB device: DS9490
    server: usb = all
    #
    # Serial port: DS9097
    #server: device = /dev/ttyS1
    #
    # owserver tcp address
    #server: server = 192.168.10.1:3131
    #
    # random simulated device
    #server: FAKE = DS18S20,DS2405
    #
    ######################### OWFS ##########################
    #
    #--debug
    #--error_level=3
    #--foreground
    
    mountpoint = /mnt/1wire
    allow_other
    
    Fahrenheit
    timeout_usb = 10
    timeout_volatile = 90
    zero
    
    #
    ####################### OWHTTPD #########################
    
    http: port = 2121
    
    ####################### OWFTPD ##########################
    
    ftp: port = 2120
    
    ####################### OWSERVER ########################
    
    server: port = localhost:4304
    
     
  • davygravy

    davygravy - 2014-02-07

    from the email reply you sent me, Paul...

    Hi Davy,

    I looked briefly at your debug output. It seems that you have an EF.209F201500, but i could see that you tried to list it's contents.

    Paul

    I'm not understanding what you are saying...

    Reading your reply, it seems to me that you are saying that the cause of me not being able to not being able to see the contents of the directory was my attempt to ... uhmmm... see the contents of the directory...

    Is there some other way to determine the contents of the directory to see what is there...?

    Or is the /hub/ directory located elsewhere?

    TIA,

    Dave

     
    Last edit: davygravy 2014-02-07
  • davygravy

    davygravy - 2014-02-08

    OK, I found the problem. From the changelog, support was added with 2.8p18.

    Incredibly, Debian ships the older 2.8p15. It seems odd that they would let 2 years go by without updating the owfs suite/packages w/ current source.

    I compiled my own using the 2.9p1 source and now I see:

    root@pogoweather:/mnt/1wire# ls EF.209F20150000/
    address alias crc8 family hub id locator r_address r_id r_locator type type_number version
    root@pogoweather:/mnt/1wire# cd EF.209F20150000/
    root@pogoweather:/mnt/1wire/EF.209F20150000# ls
    address alias crc8 family hub id locator r_address r_id r_locator type type_number version
    root@pogoweather:/mnt/1wire/EF.209F20150000# cd hub/
    root@pogoweather:/mnt/1wire/EF.209F20150000/hub# ls
    branch.0 branch.2 branch.ALL short.0 short.2 short.ALL
    branch.1 branch.3 branch.BYTE short.1 short.3 short.BYTE
    root@pogoweather:/mnt/1wire/EF.209F20150000/hub# cat branch.ALL
    1,1,1,1root@pogoweather:/mnt/1wire/EF.209F20150000/hub# cat branch.BYTE
    15root@pogoweather:/mnt/1wire/EF.209F20150000/hub#

    Mystery solved, Paul. Thanks for you patience.

    I've confirmed that the directory appears in the OWFS as it should, and read from & write to the files works as expected.

    Dave

     
    Last edit: davygravy 2014-02-08

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks