I can't seem to find any information about how to write for ecus. There's plenty of threads on buying a tuner and such, but how do the people actually write the software to read and flash any car cpu software.

There doesn't seem to be anything on amazon about automotive cpu programming and google results are overwhelmed by basic programmer unit questions.

Where do people go to learn about how to write command and control, airbag, abs etc, programming and are there any books out there that has any insight into this?

 

I don't much about the actual programming part. Are you wanting to write your own program? There are few people that have problems installing canned or custom tunes. They happen but from what I can see it's rare. I would imagine that this is a complex system and the smallest screw up on the part of a programmer or tune could cause major and expensive problems. I think your better off purchasing a programmer and having custom tunes written for your vehicle.

If I miss interpreted and you are wanting to learn how to write programs for the purposes of tuning (for a living). You may have to talk to some of the well known tuners on this and other forums. They may be able to point you in the right direction.

 

No, you're on point. I'm not trying to make a living out of it, but it seems to be a 'black art' vs. any other programming methodology that has loads of books written about it. I'm in IT, and basically anything I run into (or is thrown at me) I can get a book or 3 about it and feel it out, and there doesn't seem to be anything out there with regards to automotive systems.

 

Starters via google........

http://eectuning.org/forums/

http://www.contour.org/ceg-vb/showth...uning-overview


This is what a few of us use. There is a PRP discussion forum which is open to licensees only. http://www.lasotaracing.com/MOPRP.html#anchor

Modular tuning discussion.......

http://www.modularfords.com/forums/f...49-Ford-Tuning

 

I see your point. Can't say I have ever looked for book on this topic, mostly because this is far outside my comfort zone.

Good luck trying to find some info or forums about writing your own tunes.

 

A good read for twenty bucks.
http://www.amazon.com/Engine-Managem...tt_at_ep_dpi_1

 

I was less interested in tunes, because there is info out there.

I was more thinking at the factory system level, i.e. trying to merge the best of say a navigator's awd drivetrain and other non-f150 available features with the lightning or harlety powerplant in an 4x4 f150 kind of thing. More of trying to undifferentiate the product lines at a software level (with appropriate donor vehicles). Do appreciate the info so far though.

 

First off, the following assumes that you want to add components to your truck that it was not originally designed for. If all you're doing is pulling parts off a different model (FX4 parts to a 4x4 for instance) please disregard this post and save yourself a half-hour of reading

however if you DO plan to put those non-f150 parts on your truck...

I hate to crush your dreams, but I want to save you from starting down a path of endless rabbit trails. I'm not trying to be judgmental, just helpful and hopefully save you much agony

Just to clean up the jargon:

MCU = microprocessing unit, when i say this i am talking about the specific chip that powers your engine computer (think CPU in your home computer)

ECU = engine computer unit, I'm speaking of the whole processing device (think the tower of a home desktop PC)

EEPROM = Electrically Erasable Programmable Read-Only Memory. Think of this as a spreadsheet full of just numbers (bad description, but it will work for now)

Let's start with your original post.

• First off, you don't write programs for an engine computer, you change values stored on an EEPROM (or similar device) that the engine computer reads.
  
• If you did want to write a program for the engine computer you would need to know the MCU architecture and manufacturer (ARM, AVR, etc.) have a complete development environment (with specific cross compiler), and an excellent handle on programming in both C and the specific assembly language of the MCU. You will also need to find some way of programming the MCU in-circuit (JTAG, etc.) This, admittedly, is not too hard to come by. But...
  
• Assuming you are able to do the above, then the hard part kicks in: You'll need to know the specifications of EVERY electronic component that talks to the MCU (it's voltage levels, communication protocols, etc.) and what data each device provides. Now you'll also need to have a deep understanding of the underlying principles involved with everything from the internal combustion engine (timings, compression ratios, heat transfer, etc.), to the transmission specs (minimum times to shift, max temps, etc.) to the 4wd system (and many more systems left out b/c this post is already obnoxiously long), and use this data to generate a digital feedback controller (probably using some nice software like MATLAB to help you). Once the controller is made, you'll need to tune it. You don't want to have to re-load the program every time you change some variables, so what do you do? You have the controller algorithm access an EEPROM to pull its values from. This is more or less what your ECU does right now. You then can use the EEPROM to tweak (tune) the system as you see fit. Hopefully at this point you can see why changing something like an air intake (which requires only a variable change in the control algorithm) is vastly different than adding/changing hardware that the ECU doesn't know how to control (different parts, even if they perform the same task, can be completely incompatible communication wise).

Ok, now to your most recent post...and why the above matters.

• The program that comes installed on the ECU of your vehicle is designed to interact with the components (and varieties there of) that shipped with your truck. So you will either have to re-write some of the code that deals with the engine talking to, say, an AWD system instead of a standard 4x4 system. Unfortunately, you can't just re-write *some* code, you have to re-write it all.
  
• Now the above doesn't apply if you just want to put more air through the system, change gear ratios, or even add more fuel...all these changes can be accounted for by changing the EEPROM data (remember that controller I mentioned earlier?). But putting an AWD system on a truck with an ECU that isn't programmed for it may prove impossible...er...improbable

I really wouldn't attempt such without a good team of engineers that are experienced with digital control design, embedded electronic design, and all sorts of mechanical engineering experience.

Just my two cents. If you do it anyways, best of luck!

 

Excellent post ncTidalWave. Well done.

 

SCT's Advantage software evolved from several years of hacking Ford PCM codes by various individuals. It would be a huge undertaking. However, the software exists. Check our SCT's Pro Racer Package. It's not cheap but it's a bargain based on trying to develop the software yourself, not to mention a means to flash the PCM.

 

Not entirely true...One of the founders of SCT was previously employed in a rather high position by the Big Blue Oval in the Power Train Division and left there with a whole lot of information pertaining to their programming.

 

Shhhh!!! That's top secret.