Tuning Wiki

This is a historical revision. Read the current page or return to its history.

Page organisation in this revision
Page type
Reference hub
Subject
Engine ECU
Parent
MoTeC standalone ECUs
Applies to
No ECU-specific applicability
Tool groups
None
Manufacturers
None
MoTeC M122 ECU
MoTeC M122 product image from the manufacturer datasheet; reproduced with permission.

MoTeC M122 is an M1-family programmable ECU, part 13122. The manufacturer identifies it for up to 4 cylinders and direct injection. M1 hardware is paired with a software package; features, channels and licences depend on the loaded package and hardware revision. MoTeC M122 product information and product image.

Identification and inputs/outputs

FieldManufacturer comparison
Injection hardware4 direct injector outputs; 6 low-side injector outputs
Ignition4 low-side ignition outputs
Half-bridge outputs6
Universal digital inputs7
Analogue voltage / temperature inputs8 / 4
CAN buses1
Connector configurationtwo plastic, 60 positions

Numbers describe hardware capacity; they do not establish simultaneous availability for a specific application. MoTeC’s M1 comparison distinguishes port, inductive direct and piezo direct drivers. Check the exact injector and package; an external driver is not interchangeable with an internal driver.

Wiring and pinout

Use the M122 connector pinout and datasheet on the manufacturer product page. Connector type, keying and positions vary across M1 models; do not copy pin functions from another ECU. Verify the hardware revision, package, output allocations, wiring orientation, electrical limits and power and earth provisions against the exact unit.

Manufacturer connector tables

These tables reproduce the complete connector position and designation lists from the MoTeC M122 datasheet. Pin identifiers are kept as printed, including letter case. Check the original connector views, mating key, wire size, electrical ratings and hardware revision before connecting. Output functions depend on the ECU package and configuration; direct-injection models require their specified drivers and precautions.

Connector A — 34 positions

PinDesignationFunction
A_1OUT_HB2Half Bridge Output 2
A_2SEN_5V0_ASensor 5.0V A
A_3IGN_LS1Low Side Ignition 1
A_4IGN_LS2Low Side Ignition 2
A_5IGN_LS3Low Side Ignition 3
A_6IGN_LS4Low Side Ignition 4
A_7INJ_LS3Low Side Injector 3
A_8INJ_LS4Low Side Injector 4
A_9SEN_5V0_BSensor 5.0V B
A_10BAT_NEGBattery Negative
A_11BAT_NEGBattery Negative
A_12INJ_LS5Low Side Injector 5
A_13INJ_LS6Low Side Injector 6
A_14AV1Analogue Voltage Input 1
A_15AV2Analogue Voltage Input 2
A_16AV3Analogue Voltage Input 3
A_17AV4Analogue Voltage Input 4
A_18OUT_HB1Half Bridge Output 1
A_19INJ_D1A_POSDirect Injector 1A +
A_20INJ_D1B_POSDirect Injector 1B +
A_21INJ_D2A_POSDirect Injector 2A +
A_22INJ_D2B_POSDirect Injector 2B +
A_23INJ_LS1Low Side Injector 1
A_24INJ_LS2Low Side Injector 2
A_25AV5Analogue Voltage Input 5
A_26BAT_POSBattery Positive
A_27INJ_D1A_NEGDirect Injector 1A -
A_28INJ_D1B_NEGDirect Injector 1B -
A_29INJ_D2A_NEGDirect Injector 2A -
A_30INJ_D2B_NEGDirect Injector 2B -
A_31OUT_HB3Half Bridge Output 3
A_32OUT_HB4Half Bridge Output 4
A_33OUT_HB5Half Bridge Output 5
A_34OUT_HB6Half Bridge Output 6

Connector B — 26 positions

PinDesignationFunction
B_1UDIG1Universal Digital Input 1
B_2UDIG2Universal Digital Input 2
B_3AT1Analogue Temperature Input 1
B_4AT2Analogue Temperature Input 2
B_5AT3Analogue Temperature Input 3
B_6AT4Analogue Temperature Input 4
B_7KNOCK1Knock Input 1
B_8UDIG3Universal Digital Input 3
B_9UDIG4Universal Digital Input 4
B_10UDIG5Universal Digital Input 5
B_11UDIG6Universal Digital Input 6
B_12BAT_BAKBattery Backup
B_13KNOCK2Knock Input 2
B_14UDIG7Universal Digital Input 7
B_15SEN_0V_ASensor 0V A
B_16SEN_0V_BSensor 0V B
B_17CAN_HICAN Bus High
B_18CAN_LOCAN Bus Low
B_19SEN_6V3Sensor 6.3V
B_20AV6Analogue Voltage Input 6
B_21AV7Analogue Voltage Input 7
B_22AV8Analogue Voltage Input 8
B_23ETH_TX+Ethernet Transmit+
B_24ETH_TX-Ethernet Transmit-
B_25ETH_RX+Ethernet Receive+
B_26ETH_RX-Ethernet Receive-

Software and context

M1 Tune configures supported packages, while M1 Build is used to develop packages. ECU and logging features depend on installed licences. MoTeC downloads; MoTeC model index.