MoTeC M1 Development

Name: MoTeC M1 Development
SKU: 3404
Price: 100.00 EUR
Availability: InStock

€100.00

The release of M1 Build signals a new era for engine management customisation. No longer are you restricted to merely modifying the parameters made available via a tuning application. If a new strategy is required to give you the competitive edge, then the combination of an M1 Development ECU* and an M1 Build Development Toolkit is ideal for you.

THE BASICS

What is M1 Build?

M1 Build is an IDE (Integrated Development Environment) used to generate MoTeC’s M1 ECU packages. M1 Build allows customers to open existing projects, and customise them to suit their specific needs.

How is M1 Build used?

Using M1 Build, developers can drag, drop and configure predefined modules to generate their tailored ECU package. Additional strategies can be developed to further customise your project.

What can M1 Build do?

M1 Build creates an ECU package that includes the unique strategies developed by you for your application. When completed, the resultant customisations can immediately be tested in the vehicle.

YOU’RE THE EXPERT

M1 Build – Creating competitive advantage.

MoTeC provides fully functional example projects within the M1 Build Development Toolkit.
Extend the example projects with custom strategies, such as:

Create bespoke launch control strategies that take advantage of your vehicles drivetrain.
Create a traction control strategy that can be calibrated per venue.
The tailoring options are limitless.

To create competitive advantage with M1 Build, you can either write your own unique strategy, or use a third party M1 developer to do so. There is even the option to have your local MoTeC office do the customisations.

M1 Build – Modern vehicle integration.

Aftermarket engine management system manufacturers are quickly learning that it is no longer possible for a dealer to install a replacement ECU for a modern car using the usual menu based tuning applications. With this issue holding back replacement ECU’s for modern cars, it has fallen back to the ECU manufacturer to build car specific hardware and firmware for each new vehicle that they release. This is leaving a large hole in the market where there are no aftermarket ECU’s that can run many new cars.
After identifying this arising problem, MoTeC created M1 Build, which allows rapid ECU development for modern vehicles. MoTeC used M1 Build to create the M1 Nissan R35 GT-R and
M1 Toyota 86 packages, and now you can use this powerful tool also.

M1 Build – Onsell your intellectual property.

MoTeC sells M1 Development ECU’s* on which you can load your customised package to onsell around the world. This means M1 developers can build their own vehicle specific ECU, which could be the only ECU replacement option available.
Approved M1 Partner Packages will be linked to MoTeC’s website list of available packages.

WHAT DO YOU NEED?

To write firmware for M1 ECU’s.

M1 Build is the MoTeC M1 ECU integrated development environment.
M1 Build software, some sample projects and a great deal of documentation is available to be downloaded from the MoTeC website. This software is freely available to evaluate this new environment, and develop an understanding of this amazing new technology.
When you decide to become a M1 Build developer, order your M1 Build Development Toolkit from a MoTeC dealer. This toolkit allows creation of finished packages from M1 Build. These packages can be loaded onto an M1 Development ECU*.

To use firmware created by an M1 developer.

Use the M1 ECU Hardware Technical Note to determine which M1 ECU is right for your application. Choose from hardware with:

Direct Injection or Port Injection
Millspec or plastic connectors
Compact or high pin count cases

Order your required M1 ECU, and an M1 Development Package Licence from your MoTeC dealer.

* M1 Development ECU is an M1 ECU with an M1 Development Package Licence.

Add to Wishlist

Category: MoTeC ECU, PDM, Dash Display, Video, Diff Controllers Tags: Develoment, Ireland, M1, mapping, MoTeC, TDP, tdp.ie

Description

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 more 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 Development Licence and an M1 Development ECU. The features of M1 Build include:

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 that 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 ECU’s ensuring that only the intended ECU’s can be loaded with your package.

DOCUMENTATION SUITE

The M1 development kit includes a comprehensive suite of reference documentation. The documentation includes the following manuals:

M1 Tune User Manual

The M1 Tune user guide is training document intended for use by all users of the MoTeC M1 product.

This guide contains detailed instructions on how to us the M1 tune software, and explains 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 ECU’s
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 includes these items:

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

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

Brochures

File	Size	Last Updated
M1 Build Flyer	864 KB	Nov 18th 2013 15:46
MoTeC Brochure – M1 Build	1 MB	Mar 14th 2014 16:57

M1 DEVELOPMENT ECU

An M1 Development ECU is the same as any other M1 ECU, other than it has been loaded with anM1 Development Package Licence. One of these ECU’s must be purchased for a developer to be able to build a package and test it. The M1 Development Package Licence prepares the M1 ECU to accept packages which have a correlating M1 Build Package Licence. For most users, the M1 Build Package Licence will be purchased, at the same time as an M1 Development ECU, and as such, all of the licences will match at the time of purchase.

One M1 Build Package Licence can be used to write firmware for many M1 Development ECU’s. Therefore, when a developer purchases additional M1 Development ECU’s, they will each get an M1 Development Package Licence which correlates with the developers M1 Build Package Licence. M1 Development ECU’s can be used for in-house development, or sold as to as tailored ECUs to customers.

Using this model, a developer could buy additional M1 Development ECU’s, and sell them to customers. The developer could then write a package’s for the customer and push the new code into customers ECU at any time.

If the end customer wanted to do their own development, then they would need their own M1 Build Package Licence, and M1 Development ECU.

M1 Development ECU’s can be re-licensed at any time at no cost from one M1 Development Package Licence to another. This allows M1 Development ECU customers to move their firmware development around between different developers when required.