|
| Communication |
|
|
| Advanced
Automobile Control System |
| Development and testing of a real-time
micro-controller based Advanced Automobile control system for Ford Motor Company. Involved
in developing software to control various subsystems of the Automobile engine ( Air, Fuel
Injection, Spark Ignition, Catalytic converter, HEGO, EGR,OBD-2 related software). |
|
| Multi-Bus
Avionics Systems Configuration |
| Has facilities to define system configuration,
Remote Terminal (RT) characteristics, create messages, define signals, categories and
create schedules. |
|
| Generation
of Avionics Software Requirements Specification |
| The documents were generated using CASE tools with
extensive interaction with users and as per Software Engineering Standards. |
|
| Definition
and Verification of Interface Control Documents (ICDs) |
| Definition and verification of data elements for
the various Remote Terminals. This involves definition of signal types, categories,
conversion factors, units for all data elements etc. |
|
| Emulation
of Avionics Subsystems |
| Functional emulation of more than 15 Remote
Terminals for verification of Bus Controller (BC) Software. The emulation also involved
error injection, message history, status display etc. The RTs were emulated on a 386/486
IBM AT using PC- compatible 1553B boards using touch-sensitive screens for display. Some
of the important RTs emulated were: |
 |
|
MFK ( Multi-function Keyboard ) |
|
|
MPRU ( Mission Preparation and Retrieval Unit ) |
|
|
SGU ( Symbol Generator Unit ) |
|
|
EEMS ( Electronic Engine Monitoring System ) |
|
|
ECS ( Environment Control System ) |
|
|
DHMS ( Digital Hydraulic Monitoring System ) |
|
|
DFMS ( Digital Fuel Monitoring System ) |
|
|
FSP ( Function Selection Panel ) |
|
|
|
|
| Development
of Bus Controller Validation Test Plan |
| Test plan for more than 100 tests as per SAE
standards were developed which include electrical, protocol, error injection and hardware
dependent tests. |
|
| Testing
of Embedded Avionics Software |
| A separate team was established to do a code-walk
and develop test plans and procedures and write test programs to test the Avionics
application software at the module level. |
|
| Interactive
Software Packages for RT, BC and Monitor |
| This package helps in configuring the PC-based
1553B board to function as an RT, BC or Monitor and exercises all the features
interactively. Multiple boards can be exercised simultaneously on a single PC. The 1553B
board on the target can also be exercised through the RS-422 link. |
|
| Device
Drivers for RT, BC and Monitor for PC Compatible 1553B Based Boards. |
| Has more than 100 functions for exercising the
board in BC, RT and Monitor modes and gives excellent support for interrupt handling. |
|
| Design
of Bus Controller Software. |
| Transacts and controls message transfers in major
frames of 160 ms having 8 minor frames of 20 ms each. Extensive error handling is done and
conditions such as BUSY and SERVICE REQUEST are handled efficiently. Controls three buses
simultaneously. |
|
| Design
and Development of Bus Controller Scheduler Tools |
| The package helps to define and create the data
structures for the schedules used by the Bus Controller software for managing multiple
buses. |
|
| Message
Analysis software and 1553B Bus Monitoring tools. |
| Has features to get 1553B characteristics like: |
|
|
Bus load in % - peak, RT-wise, message-type-wise |
|
|
Unique messages on the bus |
|
|
Message periodicity |
|
|
Multi-Bus message frame capture |
|
|
Display of all status words |
|
|
Bus idle time display |
|
|
Display of message count - error, no error |
|
|
|
|
| Message
Trigger and Capture Package |
| Facility to capture messages based on triggers and
filter conditions in real-time |
|
| Real-Time
Symbolic and Graphic Message Analysis Package |
| Extensive analysis of captured messages using the
Avionics Data Base and also in real-time. Provides graphical analysis in real-time. |
|
| Development
of Operational Flight Program |
| All functions such as initialization, navigation,
handling cabin input, display synthesis, data loading/retrieval etc. are implemented. |
|
| Sensor
Modelling through GPIB |
| Generation of sensor data to 1553B sensor
equipment's through GPIB. The data is generated periodically as specified and sent to the
instruments. |
|
| Design
and Development of Automated Bus Controller Validation Test Plan Software based on SAE
standards |
| This is an automated test equipment software
package that tests the functional capability of the Bus Controller hardware and its
compliance to the MIL-STD-1553B standards with regard to protocol, electrical
characteristics and noise rejection test. The software runs on an IBM AT and is connected
to the target through RS-422 and to the SBA-100V instrument through GPIB. The SBA-100V is
programmed and messages are transacted on the target and the post-execution results from
the target and the SBA are captured and analyzed to certify pass/fail. The package is
highly menu-driven and generates a detailed test report. |
|
| Development
of ATE Software for Testing of Avionics Hardware |
| The package tests various avionics hardware like
display systems, power supplies etc. using the PC-based ATE hardware. The test instruments
include Multimeter, Signal Generator, Data Generator, Electronic load and Frequency
counter connected through GPIB and BurrBrown cards. |
|
| Development
of Hardware Test Suite |
| Development of test vectors for various hardware
chips. |
|
| GPIB-based
Device Driver for SBA-100V 1553B Test Equipment |
| General purpose driver developed for MS-DOS
environment for monitoring automated test software and other 1553B based applications
using the SBA-100V instrument. |
|
| Design
and Development of SLATE - Symbolic Language for Automated Testing of Equipments (similar
to ATLAS) |
| A symbolic language that reduces software
development efforts involved in testing equipments. SLATE has language constructs that
facilitate instrument programming. The instrument can be programmed without having to know
all the low level details (which are taken care of by SLATE). |
|
| Integrated
Test Suite (ITS) |
| This system consists of about 30 tests each for
approximately 20 instruments. A number of instruments are used to generate data and
measure the output. The interface allows building test sets from a global pool of tests,
restarting/stopping a test(s), looping, logging of data to be used as input at a later
time etc. The instruments are connected through the GPIB and BurrBrown interfaces. |
|