pdxostc/rvi_v2x_firmware

Firmware for V2X Board

rvi_v2x_firmware

Description

This repo contains the firmware source and design files for the JLR OSTC V2X project, an open source hardware device equipped with

• CAN/OBD2 interface
• 2G/3G/GPS/GSM modem
• Accelerometer

This project, and its associated firmware and hardware, are under ongoing development through the joint efforts of

• Jaguar Land Rover Open Software Technology Center (https://github.com/PDXostc) and the
• GENIVI Alliance (https://github.com/GENIVI)

Hardware repo can be found at https://github.com/PDXostc/rvi_v2x_hardware.

At the time of writing, current firmware version 0.2 intended to be used with the hardware 2.1 release.

Usage profile suggests pairing with a RaspberryPi host with RVI node installed, for telemetry preprocessing and automated control. Suggested host software is located with the GENIVI Smart Cities pilot project yocto layer and GENIVI Smart Cities application. Use of this software is not required for operation, but can provide a certain reference implementation.

Installation

Please see the V2X_SetupGuide.md for instructions on correctly setting up the project in the Atmel environment and with the Atmel Software Framework.

Tips for use in the field can be found in the Support Manual, located in this repo.

Tools in use:

• Atmel Studio 7 - Primary software IDE
• AVR Dragon - in-circuit programmer and debugger
• FOXIT - PDF printer and viewer
• V2X development hardware, OSTC prototype device

Contributors

Primary contact: [email protected]

Primary Development by Jesse Banks - [email protected].

Other Contributions from UCSD ECE191 Students Jaguar Land Rover OSTC - Portland, Oregon 2015-2016.

Additional development and 0.2.0 release by Steve Miller - [email protected]

Additional development and 0.3.0-0.3.1 release by Jesse Banks and Lilli Szafranski - [email protected]

Contributions and feedback are most welcome! Please use the Github issue tracking system for bugs and suggestions. Please feel free to fork this repo and send a merge request if you'd like to make an improvement or fix.

rvi_v2x_firmware's Issues

cgps query should also check for gps enable, and start if necessary

In certain startup cases, the at+cgps=1 seems to be missed. Because we rely on this feature, the driver should check for gps enabled at+cgps? OK as well as asking for gps information, via at+cgpsinfo. The driver should enable gps if it is needed at runtime post start up.

CMD menu, VXCA Can execute eeprom string works on alternating uses.

It appears that the the EEPROM playback function works successfully in alternating attempts when replaying this string while the can bus is active.

To recreate

vxcsATSP0, ATMA,
vxca
CAN>:ATSP0
CAN>:OK
CAN>:ATMA
CAN>:SEARCHING...
CAN>:02
...
CAN>:02
CAN>:BUFFER FULL
vxca
CAN>:ERROR: EEPROM sequence fail
vxca
CAN>:ATSP0
... repeat.

5v power usage should also start 4v

In upcoming Rev 2.0, hardware tolerances for power supplies and operational profile means that if the 5v rail is engaged (with expected use of the ELM/STN or HOST supply), so should the 4v rail be enabled. Failure to do so can result in insufficient supply and loss of communication with board. Automating this at the driver level could prevent operator error.

Driver should set SIMCOM chip to GPS auto start

Our use cases rely on gps functionality being active on start, so SIMCOM gps should start automatically.
The driver should send the command AT+CGPSAUTO=1, to ensure this. Future versions might provide the option to control this functionality.