MoTeC GPA and GPR - M1 Ecu Firmware Packages

The GPA and GPR are versatile M1 Packages for the operation of port-injected engines.

They can be configured to perform a vast array of tasks, from a simple engine to a dual

drive-by-wire quad cam boosted engine with sequential gearbox and more.

Configurable Ref/Sync modes accommodate many modern engine triggering systems. These

products also handle many modified road vehicle systems, such as air conditioning control

and has four additional definable control outputs.

The GPA and GPR packages incorporate many features, such as Pit Speed Limiting,

Switchable Fuel, Ignition and Boost Trimming, Knock Control, Intercooler Sprays, DBW and

CAM Control.

The GPR package has in addition to that list, Traction Control. Gear Change Ignition Cut,

Anti-Lag and Launch Control.

Ecu Input and Output pin allocations can be user-defined to suit individual requirements and

self updating wiring schematics are provided.

Finally these packages are comprehensively integrated with other MoTeC products, utilising

pre-defined CAN messaging for ADL/SDL/CDL, E888, VCS, GPS, ADR, BR2, PDM and SLM.

Features Common To GPA & GPR Firmware Packages

Operates gasoline port injected engines from 1 to 12 cylinders (M150 or M190) or 1 to 8

cylinders (M130 or M170)

Configurable ref/sync mode for many common engine types (refer to section on Engine Speed

Modes for current details)

Configurable Top Dead Centre for each cylinder allows for odd-fire engines

Configurable Ignition output pin for each cylinder allows for Coil-on-plug, Waste Spark, and

Distributor Ignition Systems

Configurable On-board Knock for each cylinder with 2 to 4 assignable knock sensors

(hardware dependant) and selectable center frequency

ENGINE MANAGEMENT AND DATA ACQUISITION SYSTEMS

MoTeC GPA and GPR - M1 Ecu Firmware Packages

Configurable Camshaft control from 1 to 4 camshafts

Configurable Boost control for a single turbo

Physical settings for Engine Displacement, Fuel Density, Stoichiometric Ratio, Fuel Pressure,

and Injector Linearisation allow for simplified engine start-up prior to tuning

Gearbox position detection via sensor or engine speed / wheel speed estimate

GPS acquisition and logging via CAN or RS232 (hardware dependant)

Intercooler Temperature and Spray control

Lap Distance, Time and Number via BR2 or Switched Input, with Split and Sector options

Race Time system with tables for Ignition Timing Compensation, Fuel Mixture Aim, Boost Limit,

and Throttle Limit.

Auxiliary Timer system with tables for Ignition Timing Compensation, Fuel Volume Trim, and

Fuel Mixture Aim

Engine Load Average channel with tables for Engine Speed Limit, Ignition Timing Trim, Fuel

Mixture Aim, Boost Limit, and Throttle Limit

Engine Run Time Total for engine hour logging

ECU CAN Receive from a defined ID Base Address for data reception from MoTeC devices

4 Configurable Driver Switches and 4 Driver Rotary Switches with each of 9 positions

simultaneously mappable to multiple functions such as:

Auxiliary Time, Race Time Reset, Engine Speed Limit Maximum, DBW Pedal Translation,

Ignition Timing, Fuel Mixture Aim, Boost Limit and Pit Switch

Analog Tachometer output with configurable Output Pin and scaling

Transmission Pump output with Transmission Temperature threshold and hysteresis control.

4 Optional Outputs for PWM Control of added actuators:

Duty Cycle tables using Engine Speed and Throttle or Manifold Pressure Axes

Activation based on Inlet Manifold Pressure or Throttle Position

Aux Output 1 includes tables for Ignition Timing Compensation, Fuel Volume Trim, and Fuel

Mixture Aim

ENGINE MANAGEMENT AND DATA ACQUISITION SYSTEMS

MoTeC GPA and GPR - M1 Ecu Firmware Packages

Optional channels for additional sensors via input pin and/or CAN message, including:

Airbox Mass Flow and Temperature

Ambient Pressure and Temperature

Air Conditioner Refrigerant Pressure

Air Conditioner Request

Boost Pressure

Brake Pressure Front and Rear

Brake Switch

Coolant Pressure and Temperature

Engine Oil Pressure and Temperature

Engine Crankcase Pressure

Exhaust Pressure Bank 1 and Bank 2

Exhaust Temperature (EGT)

Exhaust Lambda via LTC, LTCN, or PLM.

Fuel Pressure and Temperature

Gear Position

Gear Neutral Switch

Gear Shift Request

Intercooler Temperature

Steering Angle and Pressure

Transmission Temperature

Turbocharger Speed

Additional GPR Firmware Package Features

Configurable Anti-Lag for single turbo variants with Ignition Timing Limit, Fuel Volume Trim,

Ignition Cut, Engine Speed Limit, Boost Aim and Throttle Aim tables

Gearbox shift request via Up Shift Switch / Down Shift Switch or Gear Lever Force sensor

Gearbox Shift Control with Ignition Cut and Engine Speed matching

Configurable Launch Control with tables for Launch Engine Speed vs. Vehicle Speed, Launch

Throttle Limit vs.Vehicle Speed, Launch Boost Aim vs. Vehicle Speed, and Launch Fuel Volume

Trim vs. Vehicle Speed.

Mapping of Anti-Lag, Launch and Traction through the 4 Configurable Driver Switches and 4

Driver Rotary Switches with each of 9 positions.

Traction Control with tables for Aim Main, Aim Compensation, Control Range.

GPR-P adds paddle shift capability.

An M1 Development ECU is the same as any other M1 ECU, other than it has been loaded with an M1 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.