EpAnemoKernel - Manual

Data acquisition Application for Static Wind Sensor Networks

Abootorabi@gmail.com

Introduction
EpAnemoKernel is industrial software designed for Real-time synchronized data acquisition from a network of Static Wind Sensors. This version is designed to gather data from TCP/IP protocol based networks. Every single Wind Sensor node in the system should have its own IP or if more than one node shares a same IP, then the combination of the IP and Network Port number should be unique for each node. EpAnemoKernel is able to automatically detect each sensor and its data stream depending on sensor specific ID entered in setting of the system. EpAnemoKernel is configured and designed as Server in TCP/IP protocol so each Wind sensor network adaptor must be configured as Client. In EpAnemoKernel Application three types of data acquisition is manipulated and ready to apply by user. These methods are Bulk Record, Manual Record and Trigger Auto Record. Also three different alarm levels are ready to be defined by user. Every Event is automatically recorded on system log, enabling technical user to detect clues to system halt, system exit and in the case they happen. A text box in the application dialog contains every single event happen in the current instance life cycle of the application.

General Setting

General setting Menu is divided into five major groups: Output file, Trigger, Record, Network and Warning/Alarm

Output File
Output directory is even entered or browsed there. Output directory is the address of main directory system output is written to. This address is then divided automatically by EpAnemoKernel to directories containing Year, Month and Day of the year. For example if today is the fifth February of year 2010 and main Output directory is browsed like C:\Documents and Settings\Epeck\Desktop\Record the address all records of the current day written to will be C:\Documents and Settings\Epeck\Desktop\Record\2010\February\05 Wednesday Folders are automatically created depending of the computers date and time Every output file name contains date and time of creation also type of data gathering the file is based on.

Trigger
Trigger group consists of four parameters dealt in system Auto-trigger function. Acquisition Frequency: Defined as the frequency system is set to synchronize together. This is the frequency Wind Sensors are set to. Absolute Trigger Level: Defined as the threshold system is set to automatically issue a record event under the category of absolute trigger. This parameter must be defined as Meters per Second (m/s) Record Before Trigger: Defined as time in seconds data is recorded before the point trigger is happened. Record After Trigger: Defined as time in seconds data is recorded after the point trigger is happened. In the following example Absolute Trigger Level is set in 10 (m/s). Time before Trigger is set to 30 seconds and Time after Trigger is also set to 30 seconds.

Record
The only member of record group is Bulk (Continuous) Record Enable check box. When Bulk Record is enabled every gathered data is recorded continuously to the current Continuous record file. When choosing this option bear in mind the size of output directory and allocate a proper disk space to output directory of the system

Network
As previously mentioned EpAnemoKernel is configured as Server in TCP/IP protocol. Thus the port clients should be waiting for must be declared in the application under category of Server Port Number. The other parameter is Wait for Network represents maximum of seconds application is waiting for data arrival from Ethernet convertor to the PC EpAnemoKernel is running on.

Warning / Alarm
Three Different Alarm levels are declarable in EpAnemoKernel application. These levels are defined as Pre-Warning, Warning and Alarm. When signal level exceeds each level a warning/Alarm trigger is issued by the application. The result is shown as lightening of a light in the EpAnemoKernel Dialog. Note: Level should be defined as Meters Per Second (m/s).

Sensor Setting

Sensor setting dialog contains technical data identifying each single sensor. Every sensor should be given a unique name and unique combination of IP and Port.

Sensor Name
User should feel free to grant any name to each sensor but it is recommended to give meaningful names to each Wind Sensor indicating its location and direction.

Sensor IP Address
Here IP of the Ethernet convertor used to convert sensor data to network pockets should be entered. This IP should be unique for any Ethernet convertor

Sensor Network Port Number

Port Number of each Sensor attached to each port of the Ethernet convertor should be given to the application. EpAnemoKernel uses a combination of IP and Network Port Number to recognize each data stream belongs to each sensor, so this combination must be unique for each sensor. Note: Sensor direction is important in true data gathering but there is no software adjustment for that. Sensor direction adjustment should be done in the sensor installation phase.

Note: Please bear in mind new setting would not take effect until next execution of the
application.

Output of the System

Output of the software in the form of tab delaminated text files being feed able to many of other analyzing software like Matlab, Excel and