MOTEC M1 CUSTOM FIRMWARE FOR MAZDA 6 MPS

Available Options

M1 Custom Firmware for Mazda 6 MPS

Share This Item:

This listing is for M1 Custom Firmware for Mazda 6 MPS

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.

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.

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

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

M1 DEVELOPMENT ECU

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.