not alot we can do without more information, bench setups to test with and ecu's to use. Time is a big problem, myself using little time i have spare on our ecu programming. These things just dont happen over night but in matter of years usually.
https://pcmhacking.net/forums/view ... =27&t=2518
New member with non GM PCM help wanted
-
Holden202T
- Posts: 10311
- Joined: Sat Feb 28, 2009 9:05 pm
- Location: Tenambit, NSW
- Contact:
Re: New member with non GM PCM help wanted
whats the 808, 1987 model ?? hehehe 
No matter what the question is, the answer is always more horsepower! 
Just starting out? Have a read of the getting started guide
Basic tuning of a delco ECM with $12P thread
Advanced tuning of a delco ECM with $12P thread
Just starting out? Have a read of the getting started guide
Basic tuning of a delco ECM with $12P thread
Advanced tuning of a delco ECM with $12P thread
Re: New member with non GM PCM help wanted
yeh that's it, then vs-vy type ecu's started in 1995.
To start out you need to know how assembly works and hex etc, tables like this come in handy as you will need to know how 68hc16 code works.
http://www.cse.chalmers.se/~svenk/mikro ... ctions.htm
Then get a bench setup, i use a jimstim and some extra freqency generators for vss and maf, with your pcm it would be easy to start by removing the eeprom and putting in a socket so you can download your code then start playing and rewrite to the eeprom. If there is no ADX for datalogging then you will first need to find the device code of your ecu on the bus, then start looking up the tables and find out what data on the tables is what. Once you have a useable adx and bench setup going then you start looking at code, making changes and looking for what the tables affect.
GM use routines to process data from tables, so it will lookup the routine to pull data from a table, usually one for 2D and one for 3D, though there maybe more depending on how the data is to be read and result calculated, once you find reference to this you can start finding your tables then defining them in a xdf in tunerpro.
If you make changes to the file and ecu fails to run properly there maybe a checksum to update, a checksum is defined somewhere in the bin and is calculated from a predetermined area in the code. Also if the ecu fails to run on the bench from the start there maybe security that needs to be disabled, because you have no body module with a valid key, on ours the injectors will fail to run and the datastream can become unreliable.
Sometimes to help find things quicker you can use a port monitoring software on your pc and watch for data while you use a scantool.
Anyway this should be plenty to keep you going.
To start out you need to know how assembly works and hex etc, tables like this come in handy as you will need to know how 68hc16 code works.
http://www.cse.chalmers.se/~svenk/mikro ... ctions.htm
Then get a bench setup, i use a jimstim and some extra freqency generators for vss and maf, with your pcm it would be easy to start by removing the eeprom and putting in a socket so you can download your code then start playing and rewrite to the eeprom. If there is no ADX for datalogging then you will first need to find the device code of your ecu on the bus, then start looking up the tables and find out what data on the tables is what. Once you have a useable adx and bench setup going then you start looking at code, making changes and looking for what the tables affect.
GM use routines to process data from tables, so it will lookup the routine to pull data from a table, usually one for 2D and one for 3D, though there maybe more depending on how the data is to be read and result calculated, once you find reference to this you can start finding your tables then defining them in a xdf in tunerpro.
If you make changes to the file and ecu fails to run properly there maybe a checksum to update, a checksum is defined somewhere in the bin and is calculated from a predetermined area in the code. Also if the ecu fails to run on the bench from the start there maybe security that needs to be disabled, because you have no body module with a valid key, on ours the injectors will fail to run and the datastream can become unreliable.
Sometimes to help find things quicker you can use a port monitoring software on your pc and watch for data while you use a scantool.
Anyway this should be plenty to keep you going.
-
VX L67 Getrag
- Posts: 2883
- Joined: Sun Aug 02, 2009 9:16 pm
- Location: Bayside, Melbourne, Victoria
- Contact:
Re: New member with non GM PCM help wanted
HOLY CRAP, there's some good info there!!!!!
Now I just need a better brain to figure it all out, is there controller sheets like that for most units & where how do you find out what controller they have?
Now I just need a better brain to figure it all out, is there controller sheets like that for most units & where how do you find out what controller they have?
Re: New member with non GM PCM help wanted
yes there is usually instruction sets for each processor in there datasheets or something similar.
-
VL400
- Posts: 4991
- Joined: Sun Mar 01, 2009 2:54 pm
- cars: VL Calais and Toyota Landcruiser. Plus some toys :)
- Location: Perth, WA
- Contact:
Re: New member with non GM PCM help wanted
Thats some interesting construction using the flex board.
Once you get to these more complex ECUs disassembling them becomes exponentially more difficult. Sometimes its good to have disassembled simpler (read older) PCMs first to get an idea of what goes on in there.
Once you get to these more complex ECUs disassembling them becomes exponentially more difficult. Sometimes its good to have disassembled simpler (read older) PCMs first to get an idea of what goes on in there.