Overall Features

From the initial idea, we set out to create a VCU (Vehicle Control Unit) platform to allow integration and conversions builds as compatible as possible with various hardware such as BMS (Battery Management Systems), DC-DC Converters, Electric Water Pumps, Electric Cabin Heaters, Electric Power Steering, Electric Motors (primarily Tesla), and more. Although we cannot explicitly test our hardware and software for every possible variety, we included peripherals to allow as much flexibility as possible with a specific automotive-grade form factor. This list of controllable peripherals as of the current (near final if not final) revision includes:

  1. 3x CAN Modules at configurable baudrates
  2. 1x I2C for external communication with selectable 3.3V or 5V level shifting
  3. 1x SD-Card Slot for data logging or customized configuration
  4. 1x I2C EEPROM for storing customized configurations
  5. 8x General Purpose buffered 5V outputs
  6. 4x Open-Drain (4A Max/ea) outputs
  7. OPTIONAL 1x 802.11 b/g/n (WiFi) module for firmware updates and main VCU communication by the user
  8. OPTIONAL 1x USB Type-C programming and debugging connector

As we have not outsourced any engineering work, and have done all the hardware design, layout, and software in-house, we have established a VCU platform that is easy for us to readily push new updates to and provide component level support for.

Current State of VCU

As of writing this, there are still quite a few features the VCU does not yet support. However, customers will receive lifetime updates for the platform ordered to be manually updated via the integrated (optional) WiFi module/USB Type-C connector. With all the necessary hardware peripherals on-board, additional features can easily be added as they roll out to new firmware updates. Currently, the following is still on the roadmap that has taken a lower priority yet to be implemented:

  • EEPROM is currently unused
  • SD-Card reader is currently unused

There are other, more general planned features that are not hardware specific. We hope to keep close communications with customers for providing feedback and feature requests. As we may not have physical access to conduct testing of our VCU on differing platforms from our initial Chevy Volt BMS and Tesla Model S proof-of-concept, we will have to work closely with customers who opt-in to receive remote “beta” firmware builds with features, or customization, for their specific platforms.

The current WiFi module currently hosts a simple website allowing the user basic control such as:

  • Flashing both the VCU firmware and the WiFi firmware
  • Enabling/Disabling USB-based DFU (Direct Firmware Upgrade)
  • Enabling/Disabling USB-based VCOM (R232 Virtual COM Port)
  • Rebooting the VCU

Guides and Usage

Once we have fully tested the latest, finalized revision of our hardware, we plan to write up formal documentation of our best-guess coverage of all topics users may want to know about. Understanding that this will be an iterative process, we look forward to working with you in updating our documentation and support for this and future devices!

Feature Requests and Support

Alongside finalizing the VCU design, we are exploring ideas on how to establish quick, easy, and effective communication channels for both customers to connect with us, submit feature requests to be tracked as part of roadmap items, and fast responses on support issues (should any arise). If there are recommendations or preferences you, the reader, has or can make, please don’t hesitate to let us know either via e-mail or our social media links in our contact section of the website!