During this time-based contract, I worked on three avionics test benches.
Two for SAGEM (on the Mirage F1) and the third for Thalès.
The first SAGEM testbench consisted of validating a discrete-component concentrator electronics box. The main aim of this testbench was to apply different stimuli to the box’s inputs and outputs and ensure the proper operation of its RS422 interfaces. PXI architecture was chosen.
My work involved:
• Participating in the definition of testbench design and architecture.
• Finding equipment.
• Developing the utility APIs and VIs under LabVIEW as well as all of the LabVIEW FPGA.
• Developing all of the test automation part under TestStand.
• Creating specific test reports under TestStand.
• Drafting technical documents such as: Specifications, Design, User guide.
• Participating in testbench validation.
The second SAGEM project consisted of building a testbench to validate an electronics box interfacing with both navigation and attack systems (NAS) on a fighter aircraft and smart munitions.
This product used several communication modes such as the 1553 bus, the Digibus, RS422 and RS232 serial links, Ethernet and USB. It also had some discrete inputs/outputs.
The purpose of this tester, which was entirely developed under LabVIEW, was to validate proper data exchanges on the 1553 bus, digibus and RS422 link, as well as the proper I/O operation.
My work involved:
• Participating in the definition of software architecture.
• Finding equipment.
• Developing test software under LabVIEW.
• Drafting technical documents such as: Specifications, Design.
Lastly, the last testbench on which I worked involved the combination of two aircraft computer card testbenches into one and the automation of all test procedures under TestStand.
For this project, I was involved in:
• LabVIEW development.
• Development of automated test sequences under TestStand.
• Creation of specific test reports under TestStand.
My entire experience within the Motorola SPS group, which later became Freescale, was gained within the Tools team. The main objective of this department was to create software test tools for other teams to facilitate and expedite the testing of electronics cards for future telephones.
During this period, I essentially worked on two tools.
The aim of the first, PHI (Platform Hardware Integration), was to be a HOST and EMB multiplatform tool to validate connectivity and operation of Base Band and RF modules in the electronics card.
I was able to participate over the entire V-cycle of this team project (design, coding of high and low level VIs, tests, integration, deliveries and customer support).
The second project, on which I worked alone, was a test automation tool using the BB and RF test cases developed for the first tool to validate mass-produced HW platforms, in particular at the end of the production line. This tool, which was coded in TestStand and LabVIEW, was also a multiplatform solution, customizable through configuration files, and which generated its own test report. It could be installed on any PC using an executable.
This mission allowed me to create two end-to-end projects. The first working as part of a team and the second working alone developing my own specifications. I was able to actively participate in all project stages (design, development, documentation, support, integration, delivery and customer support). Thanks to the technical support provided, I always maintained contact with the other teams and the customer to continuously improve these tools.
Another highly interesting point was the possibility of working with international customer sites (Romania, India, USA…). I had to adapt to different working methodologies and I communicated in English on a daily basis.
My work involved:
• Participating in the definition of the framework for the PHI tool.
• Developing high- and low-level VIs under LabVIEW for BB and RF test cases (3 GPP standard).
• Developing multiplatform test automation tool under TestStand for mass validation (production line).
• Creating and modifying instrument drivers (GPIB, IVI).
• Performing configuration management under ClearCase.
• Delivery to customers in the form of an executable.
• Customer support (internal and external).
• Training our customers (in English).
• Drafting technical documents such as the User Manual, design, programmer’s guide… (in English)
Languages : LabVIEW, LabWindows/CVI, TestStand
System : Windows XP
Hardware : Control of measurement instruments via GPIB and IVI.
HOST/EMB communication via RS232 and USB.
Various : ClearCase configuration management tool
Modification management tool: DDTS, clearQuest
The aim of this time-based contract was to integrate Polyspace software into the development process of a programming team at Magneti-Marelli. The particularity of this software was its ability to test C or Ada code without performing unit tests. It checked, for example, that there was no redundant code, infinite loops, syntax errors…
My work involved:
• Automating as far as possible the source code tests regardless of the kernel and system used.
• Developing programs interfacing between the source code and the Polyspace software.
• Drafting all user documentation.
Languages : Linux, Perl
System : LINUX
Various : Polyspace code analysis software
The aim of this time-based contract was to develop a software tool for an anti-aircraft radar based on existing specifications.
This project consisted of two parts:
- An operational part that corresponded to the final software.
- Another part for the simulation of the different system components.
The goal was to check the proper exchange of data between the operational system and the components via Profibus and serial links.
My work involved:
• Checking specifications and returning any errors.
• Coding several modules for both parts of the project.
• Drafting technical documentation in compliance with the SPICE standard.
Languages : ISaGRAF
System : Windows NT, OS9
Hardware : Automatons and PEP cards, serial links.
Network : Profibus
Various : VSS configuration management tool
The aim of this time-based contract was to work within a team to maintain and develop generic testbench software for radar cards.
My work was essentially focused on:
• The development of ATEasy programs.
• The creation of drivers for components using the IEEE protocol.
• Drafting technical documentation in compliance with the SPICE standard.
Languages : ATEasy
System : Windows NT
Hardware : Control of measurement instruments via GPIB
Various : VSS configuration management tool
The aim of this short experience was to develop software with the twofold objective of managing PDF-format label printing for items coming off the production lines and the reading of these same labels to be able to check their content.
I worked alone on this project based on a minimal set of specifications and my work involved:
• Analysis and complete programming under LabWindows/CVI.
• Drafting a user guide.
Languages : LabWindows/CVI
System : Windows NT
Various : Use of a barcode reader
The aim of this fixed-price contract was to perform software development on testbenches for optical components mounted on a base.
This experience allowed me to take a central role for analysis, design, development and integration of the software developed on these testbenches.
In addition to the technical aspect, this experience was an opportunity to make use of my inter-personal skills. I paid regular visits to the customer site to validate software modifications applied, ensuring in advance the availability of the testbenches and persons requesting these changes to validate my work overall and setup configuration management.
My work on this project involved:
• Developing the different validation test phases for the optical components under LabWindows/CVI.
• Developing test automation under TestStand.
• Creating and modifying instrument drivers.
• Coordinating with the customer the implementation of the test, validation and integration of software modifications.
Languages : LabWindows/CVI, TestStand
System : Windows NT
Various : VSS configuration management tool