Adrien Martin

Development of a fuel cell management system in a startup environment. System composed of a controller (ECU), a data logger (DCU), a cell voltage acquisition system (CVM), and various sensors and actuators.

My activity quickly focused on the CVMs: requirements specification, monitoring of a post-production prototype made by an external provider, development of the project roadmap with consideration for the complete ecosystem (development, CI, and validation testing), and definition of the SW architecture.

Additionally, I was able to contribute to the entire chain. Configuration of all sensors and actuators on each prototype, development and configuration on the ECU, and finally, specification and identification of prototype solutions for a DCU prototype.

Exciting mission - abruptly ended due to serious medical reasons.

Activities:

Project – setup, specification & architecture of CVMs

- Project management, planning for project and SW activities (HW responsibility of the HW team)

- System specifications, software specifications, SW architecture

- Quality & Safety study for ASIL A compliance

- Consideration of automated testing ecosystem

- Monitoring of the next generation CVMs POC in subcontracting with validation acceptance through functional tests

Development – embedded software on ECU and subsystems

- Real-time FW development of a CAN to CAN-FD interface (C language)

- Definition and implementation of an AUTOSAR architecture for the CVM SW

- Addition of functionality (safety and sensor) on the ECU

Testing – configuration, testing & integration of new sensors and actuators

- Configuration and integration of all sensors and actuators on each prototype

- Configuration and functional analysis of equipped CVMs on the first prototypes

Environment: C, CAN, CAN-FD, SPC5, Simulink, logic analyzers, FreeRTOS, Jenkins, git, ADBMS (ADC), PID controller, Autosar, ASIL A

Project: Software design and development of an energy meter solution for electric vehicle charging. My contribution covered all parts of the product in close collaboration with the hardware team and the testing team throughout all development phases of the product up to validation by European market certification bodies.

Team size: 2-3 developers

System Interfaces:

IN: Ethernet, physical quantity measurements (adc), supply voltages (adc), NvRam

OUT: Ethernet, screen, LEDs, NvRam

Objectives:

- Develop a first prototype that incorporates the main aspects of the software architecture

- Develop the application software components

- Analyze and fix HW & SW bugs

Activities:

Environment – setup (as a team)

- Project setup and work environment: requirements/specifications, functional and software architecture, tools

Development – of robust embedded software in C

- Familiarization with the ST/FreeRTOS environment and initial prototype on a Nucleo board

- Testing of the HW boards from the first run and porting of the RTOS environment

- Development and integration of the ADS driver for retrieving business data and redesign of the data processing functional component (including optimization)

- Integration of the Oryx TCP/IP library and functional development of the REST API

- Development of the NvRam driver and implementation of the data storage logic for system configuration and status

- Development of numerous components (ntp localtime, power monitoring, memory dump, PVTPT test module, etc.)

- Real-time analysis and optimization (via asynchronous service on UART)

- Debugging: identification, correction, SW-HW analysis

Environment: C, STM32, logic analyzers, Wireshark, NvRam, SPI, ADC, REST API, TCP/IP & UDP (Oryx/Cyclone), FreeRTOS, Jenkins, git, Segger JTrace, NTP

Project: Development of a graphical application for traffic management for several major cities (Paris, Lyon, Toulouse, etc.). The system is centered around a real-time server that interfaces all field data (statuses, alarms, events) with the applications used by municipal operators. I am responsible for the development and maintenance of the cartographic management tool, which allows visualization and control of all field objects (traffic lights, counting loops, display panels, links, zones, etc.). Other tasks: C++ software maintenance on other tools (real-time server, configuration, logbook, etc.). Objectives:

• Provide a common and configurable software component for all clients.

• Eliminate obsolete technologies, use recent and promising technologies.

• Implement continuous integration as a pilot project.

• Optimize user (client) experience. Activities: Development – of a multi-process graphical application using Qt in C++

• Modular application to adapt to client specificities (while maintaining a common base for all clients).

• Clear interfacing: MQTT for field data, serial TCP for command transmission.

• Graphical redesign of the application in collaboration with an UX Designer. Continuous integration – Git referent for the service. Pilot project for continuous integration.

• GitLab for source management, Jenkins for continuous integration with Octopus for automatic deployment on test machines and at the client's site.

• Training teams on the use of Git continuous integration tools. Environment: Qt (QtCreator), C++, MQTT, TCP, Git, SVN, Jenkins, Octopus