Projects
Home / Projects
Development and Maintenance of Central Tools
.NET Framework 1.1, .NET Framework 2.0, ASP.NET, C#
Porting/Customizing CE 4.2 OS on ViaCEPC ETX board
.NET Framework 2.0, C#
Design and Development of OPC Server for Controller used in Building automation.
Off Shore Development
.Visual C++, Windows NT
Eliga developed two OPC servers. Both the servers are used for collecting real-time data from the controllers. These OPC Server are based an OPC (OLE for Process Control) Data Access 2.03 standard. This software is used for gathering the plant floor data being collected by two types of controllers and the same data being made available to other third party OPC clients.
These OPC Servers allows third-party OPC-based client applications to access data in AC and Infinity controllers through an Ethernet network.
From an OPC-compatible client application, you can:
Runs on Familiar Windows NT/2000 Operating Systems over Ethernet TCP/IP
Simulator
VC++, WIN - NT
The software simulates controller Public APIs.Using this software a process control server can communicate with any number of simulated controllers and subcontrollers and supply data to a process control client
Eliga Modbus OPC Server
Off Shore Development
Windows NT,VC++
Eliga Modbus OPC Server (also called BMOS) is developed for providing the facility to monitor any Modbus compatible devices. Eliga Modbus OPC Server provides connectivity to Modbus compatible devices using both Modbus TCP and RS-232 Serial communication. The server runs as a stand-alone executable on Windows NT & Windows 2000. The Server supports both local and remote operation, so it can be run on a local machine or any computer on your network. Devices and OPC Server Tags can be configured using our Explorer style Configurator application or you can import Tag database from CSV (Comma Separated Values) format.
BORB Server
Off Shore Development
Windows NT,VC++
Eliga ORB is developed for OPC client applications that use redundant OPC servers to achieve the highest degree of communication reliability. It works like a pass-through OPC server between the OPC client applications and the OPC primary and standby servers. The client, instead of connecting to the OPC server directly, connects to the Eliga ORB, which in turn connects to the primary and standby OPC servers, thus providing the server redundancy. As the OPC standard does not address the redundancy issues inherently, Eliga ORB provides the same. Eliga ORB allows the OPC-Enabled applications to use two OPC servers. As such the top-level application does not need to be aware of the standby OPC server. It simply connects to the Eliga ORB and the Eliga ORB handles the OPC server's communication, redundancy and other aspects. The Eliga ORB achieves this by registering with COM and intercepting calls to the OPC Server. When ORB detects that the primary OPC server fails, it immediately switches to the Standby OPC server and continues passing data along. Therefore, the top-level application is not even aware that a failure occurred. The Eliga ORB supports both local and remote operation, so it can be run on a local machine or any computer on your network.
OPCDA Server for XBS System
Off Shore Development
C++, VC++, COM/DCOM, Windows NT 4.0
The project is to develop an OPC Data Access server for the client's control system. The Server developed as per OPCDA Custom Interface 2.04 standard, so that any OPC standard client can communicate with the server and access the points in the client's control system. The server is ATL COM enabled MFC application. The OPC DA Server gets the points from client's control system and manages those points and updates the client.
WAP enabled OPC client
Off Shore Development
VC++, SQL server, Nokia server
Eliga has developed OPC-WAP Client product wherein the data can be obtained from any OPC Data Access Server and
In addition to data monitoring, the user can set the value from the Cells phone and this value will be sent to the OPC Server for updating the controller.
Additionally, the user can specify the alarm limits for the items and on exceeding the limits
The interface to a telephone is through the Dialogic card D21H with Springware-2 software -System Release Version 5.0 for Windows. Some of the APIs used are dx_open, dx_deltones, dx_sethook, dx_clrcap, dx_dial, dx_playwav, dx_close, dx_stopch etc.