eHouse Home Automation . High level programming using Windows – eHouse software package.
eHouse Automation Additionally, the software can be , Programs using ” overlay ” running parallel to the Home Automation – Software .
Programming examples are in Delphi 5 (Pascal), to be able to use the free version of this software already for amateurs and for home.
Professionals and Developers , can of course use the newer and richer Licensed version or rewrite examples to other programming languages ââlike C++ , C# etc .
High level programming for eHouse system involves the creation of home control software without interfering with the transmission protocols and communication drivers using existing software eHouse . This will ensure correct operation of such a solution , even in the event of major changes in transmission protocols and transmission medium.
EHouse software package (application eHouse.exe) provides, inter alia:
- External monitoring applications that interact with the system (in the directory configuration “%EHOUSE_DIR\exec\” ) Especially KillEhouse.exe
- Updates the data and status outputs , sensors values measured all the electronic controllers
- Creates a text log directory “%EHOUSE_DIR%\Logs\”
- Creates a file-tags included inputs and outputs according to the names assigned to the configuration for controllers , Outputs , Inputs, Sensors , etc
- Periodically checks the queue of events to be sent to the controllers “%EHOUSE_DIR%\Emails\” in text file format
Application (KillEhouse.exe) to:
- monitoring other applications eHouse system (configuration directory “%EHOUSE_DIR\killexec\” )
- Force application restart for timeout , suspension , lack of response by the programmed time
- KillEhouse application can be monitored by “eHouse.Exe” , to ensure continuous operation of the system under the supervision of eHouse PC
Application Monitoring , maintaining stability and continuity software
eHouse software package is built to monitor the performance of all applications and continuity of communication with controllers – Watch Dog Timer (WDT).
The configuration files for the WatchDogTimer (WDT) must have a “.runs” to be read by applications eHouse.
File format ” *.runs ” for eHouse.Exe and KillEhouse.exe applications is as follows:
Example for eHouse.exe to check for updates to the data – Home Automation Controllers called “Salon” :
– – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
e-House Manager Application name in Task Manager windows (TaskManager)
eHouse.exe File name. It must be in the directory “%EHOUSE_DIR\bin\”
/ Ne / nr / nt / nd The parameters on the command line application
100000 Maximum life
120 Maximum inactivity time applications
c:\e-House\logs\salon.txt Checked the file name (change the recording date – indicating proper operation of the application)
Empty – future use
Empty – future use
Empty – future use
Empty – future use
Empty – future use
Empty – future use
Empty – future use
Empty – future use
Empty – future use
Posting events to eHouse system microprocessor controllers – run the command
Main system events for each controller are exported to the directory “%EHOUSE_DIR\AllEvents\” formatted text files.
Event to run is stored in a text file, simply copy it to the system event queue of eHouse.exe , or directory ” %EHOUSE_DIR\emails\” .
Filename events in this directory for information, the name of the Home Automation Controller or device and the name of the event .
This name is generated by replacing the Polish regional basic ASCII characters and is only relevant information .
The file extension must be “.run” that it was captured from the event queue after copying . File content can not be changed , because it has a specific format, and the vicious record of events , they will be removed or cause unstable system . It is best to copy the event file rather than create it themselves in the event queue directory .
Contents of the file is as follows: Salon ; Lighting Central 2 Where Salon – RoomManager controller name – to
Home Automation – Light Controller and
Home Automation – Room Heat Controller for room
Lighting Central 2
The separator between the device name and the name of the event is a semicolon and a space ” ; ”
Other examples of file contents:
Salon ; IR (Video – REW)
// Start events of learned IR code to send the VCR to rewind
Salon ; Program 2
// Run number 2 driver living
It is a very simple way to start the basic events for drivers by simply copying .
Running more complex events is to create a file with the following format (direct events):
Secu ; At home (Day) Name as above, but only for the information displayed in the log
blank lines
blank lines
blank lines
blank lines
blank lines
blank lines
blank lines
blank lines
Direct Event Do not change this file
Event Marker direct
2 address h driver
1 empty l driver
252 event code
99 argument 1 event
255 argument 2 events
255 argument 3 events
255 argument 4 events
255 argument 5 events
255 argument 6 events
255 argument 7 events
The numbers are written in decimal format. Descriptions indicated in red .
Event List mode “Direct Event” located in a directory such as “%EHOUSE_DIR%\Mobile\”.
The files with the extension “.TXT” is the name of the event , and in “.DXT” direct event code – hexadecimal code .
Create events in the queue should be done as soon as possible , so as not to interfere with the normal operation of the application and testing eHouse not read to the end of the saved file.