Below is a table comparing our feature packed ECU range. Click on the model in the header row to get more information on the given product.
Below is a table comparing our feature packed ECU range. Click on the model in the header row to get more information on the given product.
PORT INJECTION ENGINES | DIRECT INJECTION ENGINES | ||||||||
---|---|---|---|---|---|---|---|---|---|
M130 | M150 | M170 | M190 | M122 | M141 | M142 | M181 | M182 | |
Outputs | |||||||||
Direct Injector | - | - | - | - | 4 | 8 | 8 | 12 | 12 |
Peak Hold Injector | 8 | 12 | 8 | 12 | - | - | - | - | - |
Low Side Injector | 2 | 6 | 2 | 12 | 6 | 6 | 6 | 6 | 6 |
Low Side Ignition | 8 | 12 | 8 | 12 | 4 | 8 | 8 | 12 | 12 |
Low Side Output | - | - | - | 6 | - | - | - | - | - |
Half Bridge Output | 6 | 10 | 6 | 10 | 6 | 10 | 10 | 10 | 10 |
Inputs | |||||||||
Universal Digital Input | 7 | 12 | 8 | 12 | 7 | 12 | 12 | 12 | 12 |
Digital Input | - | 4 | - | 4 | - | 4 | 4 | 4 | 4 |
Analogue Voltage Input | 8 | 17 | 8 | 17 | 8 | 17 | 17 | 17 | 17 |
Analogue Temperature Input | 4 | 6 | 4 | 6 | 4 | 6 | 6 | 6 | 6 |
Lambda Narrow Input | 0 | 2 | 0 | 2 | 0 | 2 | 2 | 2 | 2 |
Knock Input | 2 | 4 | 2 | 4 | 2 | 4 | 4 | 4 | 4 |
Communications | |||||||||
CAN Bus | 1 | 3 | 1 | 3 | 1 | 3 | 3 | 3 | 3 |
RS232 Port | 1^ | 1 | 0 | 1 | 1^ | 1 | 1 | 1 | 1 |
LIN Bus | 1^ | 1 | 0 | 1 | 1^ | 1 | 1 | 1 | 1 |
Flash Memory (MB) | 256# | 256 | 256 | 256 | 256 | 256 | 256 | 256 | 256 |
Physical Size (mm) | |||||||||
107x127x39 (mm) | |||||||||
162x127x39 (mm) | |||||||||
Weight (g) | 290 | 450 | 310 | 490 | 290 | 490 | 490 | 530 | 530 |
No. of Connectors | |||||||||
Plastic | 2 | 4 | 2 | 4 | 4 | ||||
Autosport | 1 | 3 | 3 | 3 | |||||
Pins | 60 | 120 | 66 | 136 | 60 | 120 | 120 | 136 | 136 |
PORT INJECTION ENGINES | DIRECT INJECTION ENGINES | ||||||||
---|---|---|---|---|---|---|---|---|---|
M130 | M150 | M170 | M190 | M122 | M141 | M142 | M181 | M182 | |
Outputs | |||||||||
Direct Injector | - | - | - | - | 4 | 8 | 8 | 12 | 12 |
Peak Hold Injector | 8 | 12 | 8 | 12 | - | - | - | - | - |
Low Side Injector | 2 | 6 | 2 | 12 | 6 | 6 | 6 | 6 | 6 |
Low Side Ignition | 8 | 12 | 8 | 12 | 4 | 8 | 8 | 12 | 12 |
Low Side Output | - | - | - | 6 | - | - | - | - | - |
Half Bridge Output | 6 | 10 | 6 | 10 | 6 | 10 | 10 | 10 | 10 |
Inputs | |||||||||
Universal Digital Input | 7 | 12 | 8 | 12 | 7 | 12 | 12 | 12 | 12 |
Digital Input | - | 4 | - | 4 | - | 4 | 4 | 4 | 4 |
Analogue Voltage Input | 8 | 17 | 8 | 17 | 8 | 17 | 17 | 17 | 17 |
Analogue Temperature Input | 4 | 6 | 4 | 6 | 4 | 6 | 6 | 6 | 6 |
Lambda Narrow Input | 0 | 2 | 0 | 2 | 0 | 2 | 2 | 2 | 2 |
Knock Input | 2 | 4 | 2 | 4 | 2 | 4 | 4 | 4 | 4 |
Communications | |||||||||
CAN Bus | 1 | 3 | 1 | 3 | 1 | 3 | 3 | 3 | 3 |
RS232 Port | 1^ | 1 | 0 | 1 | 1^ | 1 | 1 | 1 | 1 |
LIN Bus | 1^ | 1 | 0 | 1 | 1^ | 1 | 1 | 1 | 1 |
Flash Memory (MB) | 256# | 256 | 256 | 256 | 256 | 256 | 256 | 256 | 256 |
Physical Size (mm) | |||||||||
107x127x39 (mm) | |||||||||
162x127x39 (mm) | |||||||||
Weight (g) | 290 | 450 | 310 | 490 | 290 | 490 | 490 | 530 | 530 |
No. of Connectors | |||||||||
Plastic | 2 | 4 | 2 | 4 | 4 | ||||
Autosport | 1 | 3 | 3 | 3 | |||||
Pins | 60 | 120 | 66 | 136 | 60 | 120 | 120 | 136 | 136 |
PORT INJECTION ENGINES | DIRECT INJECTION ENGINES | ||||||||
---|---|---|---|---|---|---|---|---|---|
M130 | M150 | M170 | M190 | M122 | M141 | M142 | M181 | M182 | |
Outputs | |||||||||
Direct Injector | - | - | - | - | 4 | 8 | 8 | 12 | 12 |
Peak Hold Injector | 8 | 12 | 8 | 12 | - | - | - | - | - |
Low Side Injector | 2 | 6 | 2 | 12 | 6 | 6 | 6 | 6 | 6 |
Low Side Ignition | 8 | 12 | 8 | 12 | 4 | 8 | 8 | 12 | 12 |
Low Side Output | - | - | - | 6 | - | - | - | - | - |
Half Bridge Output | 6 | 10 | 6 | 10 | 6 | 10 | 10 | 10 | 10 |
Inputs | |||||||||
Universal Digital Input | 7 | 12 | 8 | 12 | 7 | 12 | 12 | 12 | 12 |
Digital Input | - | 4 | - | 4 | - | 4 | 4 | 4 | 4 |
Analogue Voltage Input | 8 | 17 | 8 | 17 | 8 | 17 | 17 | 17 | 17 |
Analogue Temperature Input | 4 | 6 | 4 | 6 | 4 | 6 | 6 | 6 | 6 |
Lambda Narrow Input | 0 | 2 | 0 | 2 | 0 | 2 | 2 | 2 | 2 |
Knock Input | 2 | 4 | 2 | 4 | 2 | 4 | 4 | 4 | 4 |
Communications | |||||||||
CAN Bus | 1 | 3 | 1 | 3 | 1 | 3 | 3 | 3 | 3 |
RS232 Port | 1^ | 1 | 0 | 1 | 1^ | 1 | 1 | 1 | 1 |
LIN Bus | 1^ | 1 | 0 | 1 | 1^ | 1 | 1 | 1 | 1 |
Flash Memory (MB) | 256# | 256 | 256 | 256 | 256 | 256 | 256 | 256 | 256 |
Physical Size (mm) | |||||||||
107x127x39 (mm) | |||||||||
162x127x39 (mm) | |||||||||
Weight (g) | 290 | 450 | 310 | 490 | 290 | 490 | 490 | 530 | 530 |
No. of Connectors | |||||||||
Plastic | 2 | 4 | 2 | 4 | 4 | ||||
Autosport | 1 | 3 | 3 | 3 | |||||
Pins | 60 | 120 | 66 | 136 | 60 | 120 | 120 | 136 | 136 |
#- M130 was 128MB until (Rev P)
^- M130 (Rev Q and above) and M122 have LIN and RS232 as alternate functions on other pins
Direct Injector Outputs (M122, M142, M182)
Maximum Injector Voltage = 80
Maximum Peak Current = 20
Maximum Hold Current = 15
Direct Injector Outputs (M141, M181)
Maximum Injector Voltage = 188
Maximum Peak Current = 20
Maximum Hold Current = 10
Image
Product Details
Image
Product Details
Advances in technology have increased the demands on a vehicle’s components, especially the ECU. This demand has reached the point where a single firmware to ECU configuration cannot meet the market’s ECU requirements (even with increased capacity and processor speed).
The M1 series was conceived by MoTeC to overcome this one-to-one, firmware to ECU limitation, by designing a system where operational efficiency, advanced features and flexibility are its primary objectives. At its core, M1 provides the ability to develop a suite of flexible and tailored solutions (packages), making it ideal for any application (however complex) and category management.
Targeted Solutions - We've done the configuration work for you, tailoring the ECU firmware to a specific vehicle or engine. In some cases this includes integration with vehicle control systems beyond the engine, for example, stability control, cruise control. Complete Plug-In kits are available for some applications, including any additional hardware and wiring looms as required. See targeted solutions for Vehicle, Bike, PWC or Snowmobiles.
GP (General Purpose) Solutions - MoTeC's GP Solutions offer the flexibility to suit numerous port and direct injected gasoline engines. Comprising of:
Development Solutions - Those who are skilled at coding can now develop fully customised control strategies at the firmware level, creating unique ECU functionality for themselves or other customers. Developers can build custom controls into an existing package, or create a new project from scratch. In either instance, the resulting firmware can be loaded into a single Development ECU or rolled out for customers around the world to purchase.
Ruggedised - Sometimes an extra level of protection for electronic components is required, such as marine applications or environments subject to dirt or dust. Our Ruggedised M1 hardware ensures maximum longevity under these extreme conditions.
M1 Tune is the tuning software for MoTeC's M1 ECUs. It is very different to MoTeC's previous ECU Manager software so we recommend customers watch our training webinars to help familiarise themselves, and use the comprehensive in-built Help.
M1 Tune software is free to download and within the program is a sample package for you to examine.
Link M1 Tune.
System Requirements:
The M1 Tune application allows many customisable screen layouts to make your engine calibration easier and faster. To get the most out of Tune, you should use the highest screen resolution possible. Using a low screen resolution will reduce your layout options.
Webinars
You can also watch introductory webinars on M1 Tune. Link
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.
Link M1 Build.
The M1 ECU allows different levels of access for different users e.g. engine tuner, chassis tuner, data engineer, and scrutineer. Each user can have a separate login to restrict access to particular areas of tuning and data logging.
The M1’s advanced security system is based on public-key cryptography, the cornerstone of secure internet transactions, so it is virtually impossible to change the ECU function without authorised permission. Security is enforced by the ECU and protected by a microprocessor with integrated measures to prevent tampering.
The M1 series ECUs come with three configuration options.
Locked Configuration
A locked configuration is appropriate when an ECU contains specific firmware to suit the application. The user can tune the engine in the normal way but the ECU cannot be re-configured for another application.
Standard Configuration
The standard configuration allows the user to load a selection of firmware packages available from MoTeC. They incorporate different levels of functionality and the user can choose one to suit their requirements. Additional packages can be loaded into the ECU as and when requirements change.
Open Configuration
The open configuration provides a fully flexible ECU solution that can be precisely tailored to individual requirements. Third party developers can be trained to use MoTeC M1 Build software to develop their own control strategies.
Intellectual property is protected by the M1 ECU’s security system and remains with the ECU owner.
The combination of an advanced security strategy, configurable firmware and a high performance processor make the M1 ECU an ideal choice for categories with restrictions in place for either performance parity or cost containment. Firmware can be written specifically for the category, limiting the functionality to the class requirements.
Multiple data logging sets are available which can be partitioned with restricted access to allow generation of both judicial (scrutineering) and team data from the same device.
The M1 ECU’s security system prevents unauthorised access to data and implementation of unspecified functionality.
To ensure that you only pay for what you want, M1 licensing has been conveniently split into three parts. The three licences are firmware, logging and analysis as set-out below.
Together with the hardware purchase of an M1 Series ECU, MoTeC's M1 solution includes firmware which is purpose built for the given application. The firmware licence pricing structure varies according to the number and complexity of functions the firmware performs.
M1 customers wanting to replace an existing Firmware Licence in their ECU may be able to trade it in to reduce the cost of the new Firmware Licence. The trade in value is 80% of the price of the old Licence. Customers will only be charged the difference between the trade in value and the new Licence cost.
Example:
Original Licence cost $1,000
Trade it in for $800
New Licence cost $1200
Customer only pays $400
Like any other purchase, these transactions are completed through an authorised MoTeC dealer.
Important conditions to the Trade In System:
The logging licence determines the number of channels and the sample rates available, as shown in the table below.
DATA LOGGING | PROVISIONAL | LOG SETS | MAX SAMPLE RATE | CHANNELS |
---|---|---|---|---|
Logging Licence - Level 3 | Optional | 8 | 1000 Hz | 2000 |
Logging Licence - Level 2 | Optional | 1 | 200 Hz | 200 including diagnostics |
Logging Licence - Level 1 | Standard | Fixed log set and rate |
There are two levels of analysis licence available. This licence reflects which of the following analysis software you can use:
Whether you are new to MoTeC or are accustomed to our older ECUs, learning M1 terminology and becoming familiar with these definitions will help you get to know our M1 ECUs:
An M1 Package is the file that is loaded into an M1 ECU. An M1 Package contains the entire ECU state including the tuning data, Worksheets, security and the M1 Firmware. M1 Packages themselves are opened and modified in M1 Tune.
An M1 Build Project is the complete source-level definition which is compiled using M1 Build into an M1 Package. A Project defines the M1 ECU functionality, and is designed within the M1 Build application.
M1 Firmware is the ECU operating code which is generated by M1 Build by compiling an M1 Build Project. This is distinct from an M1 Package, as it does not contain the tuning data or Worksheets. A firmware can be loaded into an ECU that has a matching Firmware Licence.
An ECU Licence is the file that is loaded into an M1 ECU that contains one or more Firmware Licence(s) and ECU Options such as logging. The Firmware Licences contained within the ECU Licence control which M1 Firmware can be loaded into the ECU. An ECU can be limited to allow the loading of one M1 Firmware only, or multiple depending on the ECU Licence contents.
This is issued to M1 developers at the time of purchasing the M1 ECU and Development Licence. It is used as a security measure to ensure that a developer’s firmware can only be loaded into an ECU with the matching M1 Development Licence.
This is the Licence that turns an M1 ECU into a Development ECU. The M1 Development Licence is installed into an M1 ECU at the time of purchase and allows the loading of firmwares built with the matching M1 Build Key.
This is an M1 ECU that contains an M1 Development Licence. The particular model of hardware is selectable.
In the M1 environment, the tuning and calibration information used within an M1 Package is considered to be the Tuning Data. When a Package is first built, all of this data is left blank. To populate the tables and parameters, these values can be migrated from an existing Package or filled in one item at a time using M1 Tune.
This is the distribution file which is used for all M1 Packages, either through the website or for passing Packages from one PC to another. A Package Archive is a self-extracting file which is unpacked by an installed version of Tune, into the correct directory, without the end user needing to know the directory structure or naming systems.
This is a Package developed in-house by MoTeC engineers for a particular application. It is visible to all on MoTeC Online, and may be installed in an M1 ECU with a matching Licence, which may be purchased via a dealer through MoTeC Online. MoTeC support staff can offer comprehensive assistance for these products.
This is either a pre-release version of a new Package, or a pre-release update of an existing Package. In either case it is available to logged-in users, but may not have complete help or all features implemented. It is made available without obligation, and will not be supported by MoTeC support staff until publicly released.
This is a Package developed by an M1 Developer using an M1 Build Key and an M1 Development ECU. It may be based on a Public Package with unique features added by the developer to offer a specific solution.
A Partner Package is visible in MoTeC Online only to the partner, after login. They can purchase a Licence for each ECU and sell this on to their customers. MoTeC support staff will not provide assistance for these Packages, it must be provided by the Partner.