Development

M1 Build Tab

M1 Build software

M1 Build is an Integrated Development Environment (IDE) for authoring M1 firmware to run on a range of M1 products. Its purpose is to facilitate M1 developers to quickly create customised M1 firmware by managing and automating the code creation, leaving the developer to focus on strategy.

M1 Build is available to download from the MoTeC website at any time, but it can only be used to create a functional Package when used in conjunction with an M1 Build Key and a M1 Development ECU.

M1 Build features:

  • Dedicated IDE development environment with hardware description for M1 products
  • Tree structure to represent logical subsystems and define naming of calibration and data (channel) items
  • Calibration items from a single value through to tabular data with three axes
  • Floating Point data for arithmetic calculations
  • Customisable enumerated data types allow meaningful names to represent system states
  • End user help and documentation can be added to describe the firmware operation
  • Sophisticated security definition to manage secured groups of items and manage higher level operations
  • Two tier user management to cater for simple through to complex security management
  • Secure Licence system with industry standard encryption and private key cryptography to protect intellectual property
  • Fast one-click firmware build (via the integrated compiler)
  • Automatic generation of firmware description and Package assembly for M1 Tune
  • Immediate code execution for testing (via integration with M1 Tune to send firmware to the ECU)
  • 'c' like script syntax for programming the application logic
  • Selectable execution rates from 1000Hz down to 1Hz
  • Automatic execution scheduling via dependency analysis
  • Library of common functions to reduce script length and complexity
  • Automatic management of stateful library functions to minimise complexity
  • Pre-defined modules for common subsystems ranging from Sensors through to Throttle Servo, Camshaft Phasing and many more
  • Access to low level components if required, such as analogue inputs and fuel and ignition outputs, for maximum flexibility when developing custom strategies

Security

The M1 development model includes a highly sophisticated security model that ensures you are always in full control. Security features of the M1 environment include:

  • Fine grain control of end user access to the finished Package. Users can see/modify only as much or as little of the Package as is designed in by the developer.
  • Hardware and software is hardware-locked, based on the industry standard private key cryptography. This ensures that the development always remains secure.
  • Individualised licensing of ECUs, ensuring that only the intended ECUs can be loaded with your Package.

Documentation Suite

There is a comprehensive suite of reference documentation, including the following manuals:

M1 Tune User Manual

The M1 Tune User Guide is a training document intended for all users of the MoTeC M1 product.

This guide contains detailed instructions on how to use the M1 Tune software, explaining all of its features and functions. Features of this manual include:

  • Software installation and ECU connection details
  • M1 Tune workflows
  • Package content and usage
  • Workbook and Worksheet usage and customisation
  • Using M1 Tune to configure M1 ECUs
  • Logging setup and retrieval
  • Dyno tuning with M1 Tune
  • M1 Tune data migration
  • Security

M1 Build User Manual

This manual guides developers through the Build software and explains how each part of the software works, and how to use its features. The M1 Build User Manual covers these topics:

  • Descriptions of menus
  • Administration of Projects
  • Editing Project components
  • Script editing
  • Managing data types
  • Defining properties
  • Compare Projects
  • Security setup
  • Help setup

M1 Development Manual

This manual assists developers with the use of M1 Build and can be described as a programmer's reference. Please note, there is a level of assumed knowledge. Topics include:

  • Description of the M1 System
  • Overview about components, methods and modules
  • How to use data types
  • Quantities and base units
  • Script syntax
  • Description of provided modules and library functions
  • Usage of security options
  • Scheduling
  • Sample Project

M1 ECU Hardware Tech Note

  • ECU types
  • Detailed description of hardware options
  • Detailed specifications of input and output hardware pins
  • Hardware communication options