1.10 Configuration

Example configuration without comments, further explanations below:

    OPT_OW='yes'                      # install OPT_OW (yes/no)
    OW_USER_SCRIPT=”                 # e.g. 'usr/local/bin/ow-user-script.sh'

    OW_OWFS='yes'                     # start owfs (yes/no)
    OW_OWFS_DEV='usb'                 # usb*, ttyS*, ip:port, etc.
    OW_OWFS_GROUP_N='4'                           # number of groups
    OW_OWFS_GROUP_1_NAME='1--Wire at USB'         # name of first group
    OW_OWFS_GROUP_1_PORT_N='2'                    # number of ports of device
    OW_OWFS_GROUP_1_PORT_1_ID='81.70D42A000000/ID'      # ID of device
    OW_OWFS_GROUP_1_PORT_1_ALIAS='ID'                   # alias of ID
    OW_OWFS_GROUP_1_PORT_2_ID='81.70D42A000000/Admin/*' # admin-access
    OW_OWFS_GROUP_1_PORT_2_ALIAS='Admin/'               # alias of admin

    OW_OWFS_GROUP_2_NAME='Heating'
    OW_OWFS_GROUP_2_PORT_N='7'
    OW_OWFS_GROUP_2_PORT_1_ID='3A.F6E401000000/PA'
    OW_OWFS_GROUP_2_PORT_1_ALIAS='1. circulation pump'
    OW_OWFS_GROUP_2_PORT_2_ID='3A.F6E401000000/PB'
    OW_OWFS_GROUP_2_PORT_2_ALIAS='2. charging pump'
    OW_OWFS_GROUP_2_PORT_3_ID='10.651BA9010800/temp'
    OW_OWFS_GROUP_2_PORT_3_ALIAS='4. Return temperature'
    OW_OWFS_GROUP_2_PORT_4_ID='10.DEF0A8010800/temp'
    OW_OWFS_GROUP_2_PORT_4_ALIAS='3. flow temperature'
    OW_OWFS_GROUP_2_PORT_5_ID='3A.F6E401000000/Admin/*'
    OW_OWFS_GROUP_2_PORT_5_ALIAS='Admin/Switch-'
    OW_OWFS_GROUP_2_PORT_6_ID='10.DEF0A8010800/Admin/*'
    OW_OWFS_GROUP_2_PORT_6_ALIAS='Admin/VLT-'
    OW_OWFS_GROUP_2_PORT_7_ID='10.651BA9010800/Admin/*'
    OW_OWFS_GROUP_2_PORT_7_ALIAS='Admin/RLT-'

    OW_OWFS_GROUP_3_NAME='Solar devices'
    OW_OWFS_GROUP_3_PORT_N='3'
    OW_OWFS_GROUP_3_PORT_1_ID='1C.7F6CF7040000/P0'
    OW_OWFS_GROUP_3_PORT_1_ALIAS='1. charging pump'
    OW_OWFS_GROUP_3_PORT_2_ID='1C.7F6CF7040000/P1'
    OW_OWFS_GROUP_3_PORT_2_ALIAS='2. valve'
    OW_OWFS_GROUP_3_PORT_3_ID='1C.7F6CF7040000/Admin/*'
    OW_OWFS_GROUP_3_PORT_3_ALIAS='Admin/Switch-'

    OW_OWSHELL='yes'
    OW_OWSHELL_RUN='yes'
    OW_OWSHELL_DEV='usb'
    OW_OWSHELL_PORT='127.0.0.1:4304'

    OW_OWHTTPD='yes'
    OW_OWHTTPD_RUN='yes'
    OW_OWHTTPD_DEV='127.0.0.1:4304'
    OW_OWHTTPD_PORT='8080'

The following variables have to be to configured in the file config/ow.txt:

OPT_OW

With the default setting OPT_OW='no', the package is not installed. Using OPT_OW='yes' activates the package.

OW_USER_SCRIPT

This variable defines the path and file name of an optional background control, with which, for example, the heating system can be controlled. Further details can be found in chapter 1.14.3.

OW_OWFS

OWFS provides easy access to the 1–wire bus via the fli4l web interface. By specifying OW_OWFS='yes' a file system in the default path '/var/run/ow' is generated using fuse. The 1–wire bus is depicted there. The directories created in the file system are sorted by Identnumbers (see Appendix A.2) of the chips. With the family code of the components a corresponding sortorder can easily be created.

OW_OWFS_DEV

The variable OW_OWFS_DEV defines the PC interface the 1–wire adapter is connected to.

PC interface	Variable set to	Example
serial	ttyS*	ttyS0 = COM1, ttyS1 = COM2
USB	ttyUSB*	ttyUSB1 = first USB adapter
	usb = first USB adapter
	usb3 = third USB adapter
I2C	i2c-[0-9]	i2c-0 = first I2C port
Simulation	fake	For using 'FAKE' and 'TESTER' modes set the variables OW_OWFS_FAKE or OW_OWFS_TESTER to valid family codes, see chapter 1.11

OW_OWFS_GROUP_N

The variable OW_OWFS_GROUP_N specifies the number of groups displayed in the browser where In- and Outputs belonging together i.e. for driving a solar device and the corresponding names for OW_OWFS_GROUP_NAME are defined.

OW_OWFS_GROUP_x_PORT_N OW_OWFS_GROUP_x_PORT_x_ID OW_OWFS__GROUP_x_PORT_x_ALIAS

The variable OW_OWFS_GROUP_x_PORT_N defines the number of ports for a group. With the two subsquent variables OW_OWFS_GROUP_x_PORT_x_ID and
OW_OWFS_GROUP_x_PORT_x_ALIAS you assign a name to the In- resp. Output of 1–wire components.

If you want to suppress display of certain data in the web interface, i.e. because the port of a component has not been established or after completion of the configuration the admin branch is no longer needed, you can prefix the name with an exclamation mark (!).

OW_OW_SHELL

Activation of the OWFS "server", for providing the OWFS-BUS simultaneously for multiple applications (OWFS and OWHTTPD). For using this no other application may be set to the direct interface of the adapter, but instead must be linked to the server.

OW_OW_SHELL_RUN

Should the Server service be started at boot time?

OW_OW_SHELL_DEV

The device the server accesses (hardware)

OW_OW_SHELL_PORT

IP-address and port the server uses. Only the localhost address 127.0.0.1 makes sense here. As a default port 4304 (OWFS port) should be used for the Server. This address is hardcoded into package RRDTool. If you want to collect values via RRDTool you may not change this setting.

OW_OWHTTPD

Activation of OWFS's own web server.

OW_OWHTTPD_RUN

Should the web server be started during system boot?

OW_OWHTTPD_READONLY

Should write access to the components be allowed in OWFS via the web server?

OW_OWHTTPD_DEV

Device, the web server accesses. In conclusion with OW_OWSHELL (Server) also a single device may be accessed here.

OW_OWHTTPD_PORT

HTTP port for the web server.

Configuration example:

    OW_OWFS_GROUP_x_PORT_x_ID='29.57D305000000/P6'
    OW_OWFS_GROUP_x_PORT_x_ALIAS='EA-Modul/!P6'        # Signal suppressed
    OW_OWFS_GROUP_x_PORT_x_ID='29.57D305000000/Admin/*'
    OW_OWFS_GROUP_x_PORT_x_ALIAS='EA-Modul/Admin/!'    # Admin path deactivated
                                                       # completely

A detailed description for the configuration of OWFS can be found in the appendix A.6 and here: http://owfs.org/index.php?page=owfs.

<<3310>>