M1 Build is, simply put, a revolution in engine management customisation. No longer are you restricted to merely modifying the parameters made available via a tuning application.

By investigating and experimenting with their own control strategies and developing their own intellectual property, customers can gain a distinct performance advantage and stay ahead of their opposition.

M1 Build customises the functionality of the ECU, providing an unprecedented level of control. It allows the user to add Tables, Parameters and Channels and to enter ‘Script’ that defines how the ECU operates. The Script is a ‘C’ like programming language that enables entry of logic, calculations and algorithms.

If a new strategy is required to give you the competitive edge, then an M1 Development ECU is ideal for you.

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.

• 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
• DBC file import feature that defines the structure of the CAN messages and signals and simplifies the CAN scripts

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.

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

There are webinars on M1 Build under "M1 ECU including plugins" on our Training Webinars page.

An M1 Development ECU is the same as any other M1 ECU, but it has been loaded with an M1 Development Licence. A Development ECU must be purchased for a developer to be able to build a Package and test it. The M1 Development Licence prepares the M1 ECU to accept Packages with a correlating M1 Build Key, which is supplied by MoTeC.

One M1 Build Key can be used to write firmware for many M1 Development ECUs. Therefore, when a developer purchases additional M1 Development ECUs, they will each get an M1 Development Licence which correlates with the developer's M1 Build Key.

M1 Development ECUs can be used for in-house development, or sold as tailored ECUs to customers.

Using this model, a developer could buy additional M1 Development ECUs to sell to customers. The developer would write a Package for the customer and push the new code into the customer's ECU at any time.

If the end customer wanted to do their own development they would need to purchase their own M1 Development Licence and M1 ECU.

MoTeC's M1 Development ECU gives you complete control.

Do you want to develop your own control strategies or customise an existing M1 Package? Do you need a special feature written for your application? Or maybe you want to develop your own targeted M1 Packages and on-sell MoTeC ECUs to others around the world?

MoTeC's M1 Development ECU is the solution, allowing customers to step outside the limits of off-the-shelf engine management and create custom firmware using M1 Build.

If you are experienced at writing code you may be able to do it yourself, or you can engage the services of an expert to do it for you.

What is required to create custom M1 Firmware:

• An M1 ECU - Any model can become an M1 Development ECU when the M1 Development Licence is loaded. This can be purchased from your dealer.
• M1 Development Licence - A Licence that enables the ECU to accept firmware from a matching Build Licence. This can be purchased from your dealer.
• M1 Build Key - This is generated automatically and ensures that firmware compiled by a Developer matches their M1 Development Licence. There is no charge for this.
• M1 Build Software - A powerful tool to customise an M1 Project then compile into an M1 Package. This software assumes reasonable knowledge of code writing; MoTeC does not offer training in this field. There is no charge for this software.
  This combination of hardware, software and licencing provides the flexibility for developers to create unique and powerful strategies while ensuring the protection of their intellectual property and securing against the unauthorised use of firmware.

HOW IT WORKS

Onselling M1 ECU's
Anyone can now make M1 ECUs part of their business by developing their own personalised firmware and onselling this to customers as a Partner Package.
Partner Packages are created using an M1 Development ECU and M1 Build. Following an approval process, these packages can be loaded into M1 ECU hardware for sale to other customers. MoTeC lists Partner Packages on our website, however the sale of these packages and their associated hardware is the responsibility of the Developer.
The process to get a Partner Package from idea to sale is as follows:

1. Talk to MoTeC to see if there is already a package available to suit your needs.
   • Often it isn’t worthwhile to reinvent the wheel, but even if there is a package already, we won’t stop you doing it your way.
2. Discuss with MoTeC a price for your firmware and hardware, given your detailed specifications.
   • All Partner Packages are individually priced to specifically suit your application. See Pricing Guidelines to see how we price Partner Packages.
3. Use your own Development ECU to build the customised package in M1 Build.
   • If you do not have your own Development ECU, you can purchase this from MoTeC or work with a Developer or Dealer using their Development ECU.
   • All Partner Package development must be completed using a Development ECU.
   • It is highly recommended that Developers base their Package on one of the many sample M1 Projects available via MoTeC Online.
4. Test your package with the Development ECU in the intended application.
   • Test and modify the package using the Development ECU until the package is ready for general sale.
5. Submit the completed package and associated customer documentation to MoTeC.
   • MoTeC need only see the compiled package, not the Project (code). The Project itself remains the property of the Developer, and is never submitted to MoTeC.
   • MoTeC will check that the finished package matches the agreed specification.
6. MoTeC will create a Licence and part number for your Partner Package.
   • The part number is associated with the Developer that submitted the package. As such, they are the only ones who can sell an ECU with that package in it.
7. The Developer can then purchase ECUs and Package Licences using this unique part number and price to onsell to customers.
8. The Developer will need to load their licence and package into the ECU, and send it onto the customer.

Please note:

• The only person who can purchase the finished part number is the package submitter.
• If a Partner Package needs to be modified after this process it must be re-submitted to MoTeC for checking, along with a description of the changes. There is a one off fee each time a Partner Package is updated to cover the cost of checking and rebuilding the Package.
• If additional features are added to a Partner Package during a re-submit, then the price of the Package may have to be re-negotiated.
• Customer Support must be provided by the package Developer.

Partner Package Pricing

If your Partner Package has all of the features of MoTeC's GPR package, then generally it will be priced at the GPR price. You need to add new features to any MoTeC base package to make your Partner Package worthwhile and attractive to customers.

If your package is restricted to limited vehicles (via hard coded ref sync modes, number of cylinders etc.) then it will be priced lower than a package without those limitations.

A Partner Package will attract a higher value if it has features such as CAN messaging for OEM CAN integration, gearbox controls, specialised traction and launch controls, power steering controls, etc.

Volume Pricing

Volume pricing on M1 Partner Packages may be offered. Volume pricing is an agreed percentage reduction at specific volume break points. The break points are agreed up front, and paid back as a rebate as each break point is achieved.

All of the pricing and volume details should be discussed and agreed to before a Developer persues any new Partner Package. This will help to ensure that the project stacks up before putting in time and effort.