SUMMARY

• Over 7 years of experience in Automotive and Electronic Industry.
• Extensive experience in Embedded Software Development for 8 bit, 16bit and 32 bit microcontrollers in C language.
• Worked on Powertrain Controller module for software verification and validation. Prepared and presented technical reports.
• Involved in Development, execution, and verification of control system requirement and algorithm.
• Good Understanding and experience of testing in HIL environment.
• Designed validation test procedure for different simple and complex I/Os.
• Good Working knowledge of AutomationDesk and ControlDesk.
• Worked with engine calibration functionality and OBD. Experienced with control systems.
• Extensively worked on CAN, J1939 and KWP2000 protocols. Developed and designed Low Level driver using 32 bit Microcontroller with ARM Architecture.
• Exiensively worked on bootloader, Tool chain setup, advanced programming technique.
• Experienced in working with Low Level Control Processing (Interrupts, Timers, Digital I/Os), serial communication protocols (RS232, I2C, SPI).
• Embedded hardware design responsibilities include schematic capture and circuit design & analysis for embedded 8bit processor. Worked on DC motor software design.
• Worked on in-circuit emulators / target system debuggers.
• Experienced in working with wireless technology like GSM, GPS, RF link.
• Worked closely with ASIC developers on new products definition and implementation.
• Implementation and testing experience in Instrumental cluster for Ford Motor Industry using Star 12 Processor. Good experience with Vector tools.
• Worked on Embedded Linux a Real Time operating system for porting Web server with Object Oriented design.
• Performed Project management activity, participated in software review meetings and CCB meetings.
• Excellent Communication Skills and worked closely with different cross functional group.
• Experienced in QA Roles such as CMMI ver 1.2 Software Standard Implementations.

Assembly language (AT89c51), C, C++.

Microcontroller

32 bit - MPC 55xx (Motorola).
32 bit - ARM7TDMI-LPC2292 (PHILIPS).
16 bit – 68HC12 (Motorola-Star12).
8bit – 89c51 (Atmel).

Cross Compiler

IAR -2.44B, TD3, Keil C.

Tools

CANalyser – Capl Programming, CANgen, EESE diagnostic tool, Matlab/Simulink, Wincal, PowerCAL, Lauterbach-Debugging and measurement, Dspace, INCA, power probe, PiAutoSim, CANcaseXL, Diab data, Autobob, Telelogic Doors, Tornado IDE, ClearQuest, IAR Embedded Workbench, Microsoft Visio, Rational Rose, Microsoft office tools.

Protocols

I2C, CAN, J1939, GMLAN, RS232, SPI.

Operating Systems:

VxWorks5.4, Unix Internals, FNOS (Ford Network Operating System), Ford Kernel, Windows 9x.

Configuration Management Tool

Clear Case, VSS.

Coding Standards

MISRA C Compliance.

PROFESSIONAL EXPERIENCE

1. Confidential,Farmington Hills, MI
Nov2009 to Till Date

The Vehicle diagnostic tester is intended for deployment and Implementation of Diagnostics commands using KWP2000 protocol. And used to diagnose bus communication for Invehicle network.

Responsibilities:

• Worked on KWP2000 protocol for diagnostic communication.
• Designed Initial and detailed requirement using waterfall model.
• Prepared low level and high level design to establish communication using KWP2000 protocol.
• Developed Integration test plan for KWP2000 protocol communication interface.
• Proactive in debugging both low-level and high-level implementation Issues.
• Worked with code debugging at instruction level using JTAG
• Worked to design, development, test, and maintenance of real-time application.
• Prepared and delivered technical presentation.

Environment:
C language, Manual Test bench environment with Atmel ARM9 board, power Supply and Inbuild J-tag debugger. IAR Embedded Workbench to setup build and debugging.

2. Confidential,Auburn Hills, MI
Apr2008 to Nov2009

General Motors G30 and G32 is a functional component of the Powertrain Gasoline Controls subsystem which combines one or more micro-processors, powertrain component interfaces, vehicle component interfaces. It allows GMPT control algorithms to operate automobile powertrain elements for Engine Specification (engine and/or transmission and/or hybrid drive unit).
Responsibilities:

• Worked extensively on I/Os and Secondary processor functionality with FMEA and DVP&R process. Worked with Matlab/Simulink.
• Analyzed and good working knowledge of closed loop control algorithms (Spark Control, Motor Control), Flash programming, Serial Communication Drivers (CAN) and Memory Management (MMU, DMA).
• Utilized software engineering process in Analysis, Software Design, Code, and Functional Verification.
• Worked with GM operating systems, interrupt handling and communication drivers.
• Worked with pre-emptive multi-tasking environment, with good knowledge of related key issues in CPU Utilization, Memory Management.
• Analyzed requirement, schematics extensively to design software and test procedure.
• Analyzed and modified test software as per designed test procedure.
• Worked extensively on pulse input, frequency input, secondary processor task manager, DC motor Controller output, Spark control output, Nonvolatile Bootcode memory, Serial Communication by implementation and designing validation test procedure.
• Worked for implementation of Cylinder deactivation output.
• Designed and implemented Battery independent non volatile data memory.
• Executed automated Test scripts with INCA hooked on to ECU.
• Execute Manual test procedure on the automated bench environment. Used C Programming to develop software.

Environment:
Automated Test bench with Engine controller Module, dSPACE Automation Desk (hardware-in-loop), dSPACE Control Desk, INCA, Lauterbach, Power Cal, Matlab/Simulink, power probe, AutoBOB, Diab data Cross compiler, Agilent Oscilloscope. Used MPC55xx microcontroller.

A. Confidential,

1. Hydrive – Canada/ Dearborn Electronics India - WIHL System
Dec 2006 to Mar 2008

The Hy-Drive WIHL system is intended for deployment into the next generation of self-adaptive HGS (Hydrogen Generating System) for Hybrid Electric Vehicle. WIHL system consist of two units, In-Cab Interface Unit (IIU) and a HGS Interface Unit (HIU), to constitute a Module Pair
Features:
IIU: The purpose of the IIU is to fetch required data from the J-Bus and transmit this data to the HIU at defined periodicity.
HIU: The purpose of the HIU is to act as the wireless interface between the IIU and the HGS processor. It communicates with the IIU via the RF link and receives data that is then transmitted to the HGS via an RS232 link.

Responsibilities:

• Worked extensively on CAN, J1939 protocol.
• Designed Initial and detailed requirement using iterative model.
• Prepared low level and high level design to establish communication between In-Cab Interface unit and Vehicle bus (J1939-Bus).
• Developed Integration test plan for J1939 (TP BAM) and used Capl programming.
• Developed C code to establish Communication between In-cab Interface unit (IIU) and Vehicle bus (J1939-Bus).
• Developed C code to establish Communication between In-cab Interface unit (IIU) and HIU using RF link.
• Developed C code for On Board Diagnostics. Worked on Bootloader.
• Reviewed code to verify communication between HGS, HIU, IIU, WAN interface and display interface using defined message frame.
• Involved in complete product development life cycle (Including project Estimation and Planning) with process compliance. Worked with telelogic doors.
• Generated IPSR (Internal Project Status Report) for project tracking with Estimation. Technical leadership to review software architecture.
• Extensively involved in plan for risk management activity. Participated in CCB and software review meetings.
• Involved in Estimation and metrics council meetings to review respective reports.
• Responsible for the overall QA and product development activities.
• Used Embedded C for programming.

Environment:
Manual Test bench with IIU, HIU, Power Supply and Inbuilt J-tag debugger.
IAR Embedded Workbench to setup build and debugging, CANcaseXL, Agilent Oscilloscope. Used LPC2292 microcontroller.

2. Confidential,
July2004 to Dec2006
Software Engineer

The Instrument Cluster is the ignition node and interfaces with the vehicle and external modules through a combination of hardwired signals and networked messages. The P356 IC has Four variants namely Diesel, gasoline, RPO and BASE.
Features:
Network: FNOS (MSCAN, HSCAN, and Gateway between them)
Diagnostics: Ford CAN Generic v2003.0
Responsibilities:

• Developed application using C for Display, tire pressure monitoring, diagnostics and Telltales with MISRA compliance.
• Developed integration test cases for Display, Diagnostics, telltales and chimes features.
• Developed unit test cases for diagnostics and Telltales and executed on manual bench environment using Lauterbach debugger.
• Executed Integration test cases on manual bench environment and log defects to help development team. Worked on bootloader.
• Developed unit test cases for Diagnostic and Telltales.
• Extensively used Capl scripting for Testing.
• Analyzed FNOS (Ford Network Operating system) to understand communication of MSCAN, HSCAN and gateway between them and generate FNOS code through CANgen.
• Worked for Requirement management activity.
• Code walk through for gauge implementation with cluster.

Environment:
Manual Test bench environment with CANcaseXL, CANalyser, Agilent Oscilloscope, Lauterbach - debugging and measurement, IAR, Clear case, ClearQuest, Instrumental Cluster and Power Supply. Used Star12 68HC12 microcontroller.

3. Confidential,
Jan2004 to June2004

The main purpose of GPECII is to control the Engine and transmission function.
Responsibilities:

• Analyzed requirement with the schematic provided at component level.
• Developed functional test procedure for Simple and complex I/Os by considering requirement with respect to the automated environment.
• Converted all the Functional Test Procedure into script in VC++ Platform. Used Matlab / Simulink.
• Created comprehensive test plans, collect and analyze technical data to understand system behavior and propose improvements
• Created and validate system level requirements for control systems including specification of electrical interfaces (sensors, actuators), functionality and diagnostics.
• Involved in building harness with core microcontroller.
• Executed all functional test cases on automated environment.

Environment:
Automated Test bench environment with PiAutosim, Autobob, Matlab /Simulink, CANcaseXL, CANalyser, Lauterbach debugger used MPC5554 microcontroller.

B. Confidential,

1. Porting a webserver using Embedded Linux to PPC403GCX.
Sep 2003 to Dec 2003

This project is aimed at to develop a web-based diagnosis program using a 403 Evaluation board to drive the Medical Instrument.
Responsibilities:

• Worked for design and Implementation activity to bring up the board for diagnosis.
• Worked extensively with POSIX threads, TCP/IP socket programming.
• Developed software using C ++programming.

Environment:
Embedded Linux, IBM PowerPC 403EVB.

2. Confidential,
Apr2003 to Sep 2003
Software Developer

This project is aimed at to design and to implement AT commands for SMS service on Smart GSM modem for trainer kit with UART on Atmel 89C51 as a core. And it aims to interface with LCD (Liquid Crystal Display), ADC (Analog to Digital converter) with Timer interface, RTC (Real Time Clock) and EEPROM. Established communication between RTC, EEPROM and 89c51 using I2C protocol. Worked with Orcad for Hardware layout and design
Environment:
Keil cross compiler, 89c51 hardware board and GSM modem.