Magnesium ECU (M1)

[JamieA]

With a bit of luck, the M1 software will be available for download on Friday.

As for specific hardware, availability, Ill put up some info on that next week.


regards,

Jamie

[Fast_Moto]

Any chance you could post up a more detailed explanation of the different ECU software license levels (not logging)?

Also, will there be an option to do your own programming of the ECU?

[hapikacsa]

Hi all,

I have a M142 ECU. I did not recive any documentation with it and on the MoTeC homepage or anywhere else on the internet I can not find manuals or docs about this ECU.
From example files it is clear that I can find the pinout of the connectors in the M1 Tune program, but first, it would be an advantage to be able to connect to the ECU, but without connectors pinout I do not know which pins are for the power supply and for communication form the 4 connectors .
So the main question is, how can I reach any docs about this ECU, or just a pinout drawings the make the connection between the laptop and the ECU?

[Martin]

The pinouts are package dependent. This means the package dictates what the pins are. When you open your package in TUNE, you can look at the wiring for that specific package.

What engine are you running?

[dan]

I am serious looking at the M150 for a project. I have been getting up to speed as fast as I can. Questions?

1. When can we expect more information on the LIN Bus? Is this the same Bus as the GMLan or the GM Class 2
Bus, and can it be setup to work with the GMLan or the GM Class 2 Bus?

2. Has anyone looked at the nominal through put (output from the ECU) for the Ethernet port I am not asking
about the link speed of 1 Gbps? Would be helpful.

3. Regarding the ignition outputs. What recommendations are there for hardware? Is an external ignition
module needed or can the outputs be wired directly to discharge coils. Does a specific selection of coils and
injectors affect this requirement?

4. I have read through a number of the forum entries. There has been some discussion about simulators. One thing I have seen in other control systems software is the ability to step through the software and see how the code changes values (input and outputs) line by line. This is very useful when you can move quickly between the development side and the active side of the software (Build to Tune and back) to make minor corrections in the code quickly. I see this as very important given the rising costs of software development and tuning costs. With this new software, the link between software and hardware can be decupled opening up a lot of options. Developers will be developing software for ECU they may not have ready access too. It may be impractical to obtain access to an ECU during software development. With this software you will be able to develop code for any M1 ECU at any time.

5. As an end user of the hardware, I would expect a base worksheet would be available for every piece of hardware manufactured by Motec. Can we expect worksheets for Display, Switches (keypad), GPS units, Light Bars, GPS units, etc.? A hardware certification program is really needed. Something that can be done to ensure hardware can work with the Motec M1 platform. With greater flexibility in the software, hardware, and the CAN Bus, more manufacturers equipment can plug into the CAN Bus’ and interact with ECU and other Motec devices. There are a number of 3rd parties making hardware already been used in race vehicles; (Race Grade, is this the same as Motec West in the USA - Some Race Grade devices appear to be resold through the Motec website), SpeedHut (Orem Utah USA) with Can Bus interconnection protocol (J1939) as an example, Race Grade Tire Monioring System appears to be a new product, Bosch MotorSports ABS System, and GM is beginning to place Can Bus controllers inside there transmissions (Bus Controlled 6L90e, 6 speed automatic). I am sure there will be other like companies of interest as time moves forward.

With all this flexibility come options and options and choices and complexity.

[Fast_Moto]

Just a couple of quick responses based on my experience with Motec.

2. In my experience, the ethernet port on the ECU is used only for communication with the ECU and possibly for indirect communication with some other modules (e.g. LTCD) for configuration through the ECU. In my experience the ethernet port is pretty quick. However, when you are downloading 100+MB of data from a race, it will still take a litte while to download. So, in effect, I have found the ethernet speed to be fairly fast and also not to be critical because of its limited purposes.

3. In my experience, non-OEM Motec ECUs do not contain ignition amplifiers. You will need to use an external amplifier. I think ECU reliability is an important factor for using an external amplifier. I have blown amplifiers in the past and it would have put me out of commission if that had been in the ECU.

4. Motec has base datasheets for all their products. You can download them from their website and in general they are as good as datsheets from any other manufacturer. I have not had any difficulty figuring out whether a particular product is compatible with another. With regard to the M1 ECU, the compatibility is determined in large part by the package you want to use. You can get racegrade datasheets from Motec USA. I am sure I am not telling you anything you don't know, but to use a third party product, you will probably need to be able to freely program CAN communications and set up custom CAN templates. Whether you can do that will again depend on the specific M1 build package.

Motec also has some application notes that can help you with specific applications -- whether tuning PID control, setting up CAN communications, etc. These are not widely publicized, but if you have a specific problem, you could contact Motec and they may have something handy to help you.

Hope this helps.