Jump to content
The mkiv Supra Owners Club

Interesting new Motec info


Chris Wilson

Recommended Posts

Motec have finally released Windows based software for their flagship M800 ECU, and it also allows mapping of the Toyota / lexus VVti system. Some details below. i have a brand new M800, wiring loom, and snesors in stock, totally unused, with latest updates and all options enabled. Not cheap, and I would want a professional loom making for me to be happy about installing it on a MKIV. Not being a "proper" auto electrician this would be one install I'd farm out... The M800 I have would be well below list.

 

The Windows version of M800 ECU software has arrived.

 

This is the first official release of M800 ECU Manager 2.0.

 

M800 ECU Manager is an all-new implementation of the M800 tuning

software that completely replaces the old M800 DOS EMP software.

 

It is a fully integrated 32-bit Windows application with Graphical User

Interface.

 

 

There are some important things to note:

 

COMMUNICATION

All communication is done using the MoTeC CAN Cable. The serial

interface is no longer supported, though the M800 still supports an

RS232 datastream.

 

UPGRADING THE ECU

To upgrade an ECU to run this version, select Utilities | Upgrade ECU

Version.

 

OPERATION

The operation of ECU Manager is very much like E.M.P. For users

familiar with E.M.P. please read the help topic ECU Manager Software |

For EMP Users, this will quickly explain the main differences. The help

is accessed by selecting Help |Topics.

 

KNOWN ISSUES

"Sticky" Mouse - If an ADL is connected and the M800 is not connected

the mouse becomes "sticky" while ECU Manager is running. (Turn the ADL

off to remedy.)

 

Interaction with Dash Manager. (Can't use CAN Cable at the same time.)

 

Graph - Y axis not reversed for Ign, etc.

 

 

MISSING FEATURES (Compared to DOS EMP)

Copy From/to Floppy (Send to) (Get From).

PC Telemetry Output.

 

 

CHANGES SINCE VERSION 1.68

 

CAM Control for BMW Vanos:

This function requires an enable code to operate. The Vanos control

software has been validated on several BMW models. Contact MoTeC for

details.

 

CAM Control General:

Changed CAM position measurement strategy to suit more engines

 

Drive by Wire:

The diagnostic error for TP & TP2 will now also occur if the sensor

reading exceeds the Throttle Hi and Lo settings to warn if TPHI/LO are

incorrectly set

Added Aux output Function 125 Drive by Wire Error. This may be used to

control the clutch on some Drive by Wire motors.

Fixed the Drive by Wire idle function - sometimes wasn't initialised

correctly

 

New ref/sync offset parameter:

Ref & Sync offset levels can now be adjusted for magnetic sensors. This

is useful when sharing sensors with the factory ECU and the signal is

not symmetrical around 0V.

 

Added Ford Falcon Ref/Sync mode:

Suits BA series Falcon and includes cam position measurement via sync

sensor for CAM control

 

Added Lexus REF/Sync Mode:

Suits IS300 and includes cam position measurement via sync sensor for

CAM control

 

Added BMW Ref /Sync mode:

Suits engines with Vanos where the sync sensor is also used for cam

position measurement, such as M5

Ref : 60-2, MAG, FALL : 60 evenly spaced teeth with two missing (per

rev)

Sync: 8-1, HALL, FALL : 8 evenly spaced teeth with one missing (per

cycle)

CRIP: typically 445

 

Added Honda Ref /Sync mode:

Suits Integra type - R and Civic type - R

Ref : 12+1: n evenly spaced teeth + 1 extra tooth (per rev)

Sync: 4+1 : 4 evenly spaced teeth + 1 extra tooth (per cycle)

 

Lambda Control:

Wide and Narrow band short term trim are now set to 0 if long term trim

is off and closed loop control is not active.

Added Lambda pressure compensation mode - high exhaust back pressure

effects the measured lambda value

Modified heater control strategy for Lambda stop.

Added flag for narrow band sensor fitted.

Wide and narrow band control can now be implemented based on LA2 only.

Useful for M800 OEM's

 

Boost Control changes:

New 3d boost compensation table for exhaust temp

 

Stepper Motor Idle speed control:

Change to idle speed start condition. Now aim RPM/2

Change to idle speed stop condition. Idle control now stops at RPM

Added IGN switch input to idle stop condition. Will not step if IGN

switch is off.

Added half step function to idle speed control

 

Ground speed limiting:

Cut type and randomiser added to ground speed function. Previously used

same cut type and randomiser as the RPM limit

 

Traction control - mode slip sources:

Additional combinations added for the digital inputs that can be used

for speed inputs.

 

Gear Change Ignition Cut:

Increased Gear Change Ignition Cut maximum rearm delay to 2.55 seconds

 

Other Auxiliary functions:

PID Boost control. For most applications the normal boost control setup

should still be used. Includes a table for boost min duty in PID Boost

control. Selected when the Minimum Duty setup parameter is set to -1.

PID fuel pump control. For fuel pressure control without a pressure

regulator and fuel return line

 

General Auxiliary Output Changes:

Added RPM,EGT1-EGT3 to the Y Axis parameter for the Auxiliary Output

setup

 

General:

Change to post start decay calculation to reduce coarseness on long

delay times.

Letters at the end of the version string are now displayed by EMP.

Ability to send data sets via CAN to ADL

Added EGT channels 3 to 8

Added lambda channels for 12 cylinders

Added user channels 5 to 8

Link to comment
Share on other sites

If this is the top of the range Motec it must be some serious money . . . how different would a 5 or 600bhp car equipped with a top notch, top price ECU like this feel on the road compared to something like the AEM which retails at about $1400 I think. Would the average driver be able to feel the difference? (Assuming both ECU's were mapped to a decent standard.)

Link to comment
Share on other sites

The main advantage you get from more expensive ECUs is the flexibility to use them how you want. The cheap ones might allow you to only change fuel and ignition maps and have very little else to offer. More expensive ones like the Motec have more features - far more maps to control the various features, more user definable output channels etc...

 

I work for a company that designs very high spec ECUs mainly for motorsport. The ECU I write embedded software for is used in loads of race cars; Touring cars, Formula Palmer Audi and many more. Our higher spec ones are used in WRC. The ECUs are expensive but offer hundreds of configurable maps to control every aspect of the car, many user definable outputs, logging and so on.

 

So basically, different ECUs are targetted at different markets. You probably wouldn't want to run one of our ECUs on a Supra (at least not on a road car), due to the cost and work involved and many of the facilities would be wasted. The Motec looks like it would suit a road car well due to support for existing sensors.

 

James.

Link to comment
Share on other sites

Circa 3K, would have to add it up, maybe a bit less, but not much. Now the new software is out it is appealing to keep it, as it will work with nigh on any car now. As with all ECU's buying it an having it fitted is the easy bit, mapping is the really tricky and time consuming part.

Link to comment
Share on other sites

Originally posted by Adam Wootten

If this is the top of the range Motec it must be some serious money . . . how different would a 5 or 600bhp car equipped with a top notch, top price ECU like this feel on the road compared to something like the AEM which retails at about $1400 I think. Would the average driver be able to feel the difference? (Assuming both ECU's were mapped to a decent standard.)

 

Prabaly little difference, but the Motec will allow far more trickery, but more trickery = more mapping time = big bucks :(

Link to comment
Share on other sites

Originally posted by JamesG

The main advantage you get from more expensive ECUs is the flexibility to use them how you want. The cheap ones might allow you to only change fuel and ignition maps and have very little else to offer. More expensive ones like the Motec have more features - far more maps to control the various features, more user definable output channels etc...

 

I work for a company that designs very high spec ECUs mainly for motorsport. The ECU I write embedded software for is used in loads of race cars; Touring cars, Formula Palmer Audi and many more. Our higher spec ones are used in WRC. The ECUs are expensive but offer hundreds of configurable maps to control every aspect of the car, many user definable outputs, logging and so on.

 

So basically, different ECUs are targetted at different markets. You probably wouldn't want to run one of our ECUs on a Supra (at least not on a road car), due to the cost and work involved and many of the facilities would be wasted. The Motec looks like it would suit a road car well due to support for existing sensors.

 

James.

 

Care to say who it is you work for? Zytek? EFI Technology? Just being nosey :D

Link to comment
Share on other sites

Originally posted by Chris Wilson

Care to say who it is you work for? Zytek? EFI Technology? Just being nosey :D

 

Sure :) I work on Pectel ECUs. The company is part of Pi Group, which is, in turn, owned by Ford. So the ECUs get used in the Ford WRC team and the Jaguar F1 team.

 

We borrowed Colin McRae's Focus after the GB rally last year, but I didn't get to drive it :(

http://www.compsoc.man.ac.uk/~jamesg/gallery/rallycar

 

James.

Link to comment
Share on other sites

My bad.... for some totally unknown reason i always forget about Pectel, and yet they are a superb bit of kit. Rarely see them advertised much, maybe that's it? I would be fascinated to know what the current thinking on mapped WI systems on the WRC cars is, can you share any inside info, even if it's a bit "out of date" or generalised? Last i saw was them using a BIG pump and mapped injection onto the back of the intake valves on each cylinder. Weren't Pectel one of the first to really get to grips with anti lag on the turbo cars?

Link to comment
Share on other sites

Yeah, Pectel have done electronics for Ford for a long time - stuff like the eight-injector board for Escort and Sierra Cosworths.

 

I can't say I know that much about the WRC. I'm actually quite new to automotive programming anyway (I was a Playstation games programmer for a couple of years before this job).

 

The main things I need to understand for embedded programming of the ECUs are what is required of the control systems i.e. how the box deals with inputs, what outputs are required and what maps will be provided. It's then up to the user to set up the ECU as they see fit.

 

James.

Link to comment
Share on other sites

Originally posted by JamesG

Sure :) I work on Pectel ECUs. The company is part of Pi Group, which is, in turn, owned by Ford. So the ECUs get used in the Ford WRC team and the Jaguar F1 team.

 

Heh, I used to work for Pi Technology, was a windows programmer, though I have "played" with some of the other ECUs that were knocking about while I was there. :)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. You might also be interested in our Guidelines, Privacy Policy and Terms of Use.