OHAS concept (old)

I'm old

At a central point on the Internet, like www.vscp.org, there are links to information about:

• tested and available services for a typical “house owner”.
• approved nodes.
• required nodes for a specified service in a defined country.

In your Home Application Network (HAN) you need a simple box connected with Linux, a Web-server, Mysql and Perl. On that platform this prototype of the “High End Node” (HAN) may be installed.

The installation is very simple. All you need to do, is to make two directories, move some files (no compiling) and give proper rights. It is all done on the webserver.

Move the files high_end_node.html and intro.html to the document root (like htdocs).

Make a directory hen_images in the same place (like htdocs) and copy all files from the dir hen_images in the download.

Make a directory high_end_node in the dir where you may run scripts (like cgi-bin) and copy all files from the dir high_end_node in the download.

Make sure your directories and files have the right to run.

Make a link to the hen somewhere in your document root (like /high_end_node.html).

Test the link and make sure you get access to the menue in the left frame with Info and Config.

Try to Import a Node, or a Service, from the menu. (If you change your mind it is easy to delete the service/node from the Config submenu).

Try to change the name etc. in the Config submenue. Make sure to hit “save” when you want to update the configuration. (Have a look at the file node.xml in the directory high_end_node after your imports & changes).

You have to tell a Service what Nodes & Objects it should be connected to. This is called Links in the Config for the Service.

1. - Import the Nodes you want, or make sure they are there already.

2. - Click on each Node in the Config submenu and check what index it has.

3. - Take a note with the index for each Node and Object.

4. - Click on the Service in the Config submenu and register the Node and Object in each Link.

Please note: A Service may be connected to many Nodes and a Node may be used by many Servicies.

The Operation submenue gives you three possibilities.

• Map (Now) Default

Current values

• Time (Future)

Setting future events. With a start- and end-time you may register a event (setting a value for an object) at certain intervals. The idea is to change alarm levels at certain times of the day, switch lamps on/off etc.

• History (Past)

The values for all objects related to a Service may stored in mySQL at preset intervals. It will also be possible to store certain events (like alarms).

Parameters for all above is set/changed in the Config submenu. You may also use your own pictures/drawings in the Map part of the Operation submenu. Take a picture of your house, save it as a xx.jpg in the dir htdocs/hen_images, register the name of the file in the Config submenu for that Service and you have your own version. Each Service may have one or more images. If you have more than one image, you can link them together and click your way around the house. All decimal values are set in a “normal” way, using decimal-comma (not decimal-point..).

The BackEnd is talking to the canald (TCP-server) and the following parameters has to be set in back_end_com.pl before you can start the BackEnd.

• # TCP-server (canald)
• my $vscp_host = “192.168.0.10”; # Set your address for VSCP server here (canald)
• my $vscp_port = “1681”; # Set port used by VSCP TCP-server (canald)
• my $vscp_user = ””; # Set username for TCP/IP i/f of VSCP daemon
• my $vscp_pass = ””; # Set password for TCP/IP i/f of VSCP daemon

The BackEnd is also calculating dummy teperatures (dummy nodes), checking values with alarm limits, ordering switches to be set over the network, handling the database by creating tables and inserting values in Mysql etc.

Start the BackEnd from cgi-bin/high_end_node/ with something like

• >./back_end_com.pl &
• >./back_end_node.pl &

Your dummy Nodes will work from now on. Messages are published in the VSCP-world over Canald.

To get some real action, all you need to do is to install some real nodes and make sure to import and configure the corresponding definitions with the Import and Config submenus. Please note that the GUID has to be registered for each VSCP-node in the Config submenu.

Go back