I was just wondering is there anything available in order to change values on the fly as you would with an accel dfi system. So you wouldn't have to keep burning and plugging in.

Thanks

 

Try http://www.kalmaker.com.au/ they have a system to convert a 1227165 to map using 1, 2 and 3 bar maps with a new autotune feature (closed loop fueling only).

I scored a copy a while ago and have been enjoying it ever since

Best part is that with the way the Aussie dollar is its real cheap in US dollars.

 

I took a look at this site; it's quite interesting, but doesn't go into any detail on the physical modifications to the 7165 ECU.

What exactly do you have to change or add to the ECU to get the on-the-fly capability? And how do you make your changes permanent?

 

With the existing ECMs (7730 or 7165), it is impossible to program "on the fly" as there is no circuitry in the ECM to "write" to the prom (as I understand it). Further, if you WERE able to change things "on the fly" the ECM would have to know how to alter the checksum or you'd encounter a Code 51.

Personally, I believe you should make notes and do analysis in the comfort (and safety) of your home rather than while driving. It wouldn't be the first time that some change that I made caused some unforeseen difficulty that didn't show up immediately. Besides, if you are trying to modify the VE tables, I think it would be better to capture a LOT of information first and then use those results (eg. the average BLM or INT values over a long amount of data captures). I have noticed that there are "short term" transitional values that settle down after a bit of driving. If you were to react to all those transitional changes, you would most likely mess up your VE values.

I do admit that being able to add a little spark "here and there" while driving would have it's advantages, but you can also accomplish that with "mechanical means" if you were so inclined. I personally don't know how you would be able to scan the ALDL if you were using a program to alter the eprom (again via the ALDL) or vice versa without a "hardware change" to ECM.

But, I still think it is best to analyze all of your sensor readings from a data capture in the safety of your own home rather than when you are behind the wheel of a car. This is worst than the guy fighting with his wife on his cell phone while driving in rush hour traffic.

Lastly, with making changes to the BIN and then loading it onto the eprom, you can keep past versions. If a particular change didn't workout or (heaven forbid) make the engine not run, you can always reburn a previously known "good version". If you did such a thing while "programming on-the-fly" you may not have a "previous known good version" and just disabled yourself on the side of the road.

[This message has been edited by Glenn91L98GTA (edited August 28, 2001).]

 

On many of the ecms there is a way to access the processors RAM, and do on the fly tuning, or do some reflashing of a SRAM (?) when installed in place of a eprom. Thu the ALDL.
That's how the drivibility teams did it at different times.

Kalmaker makes use of this unused code. Some folks think the references to various impossible addresses are for rebooting etc, it's for the add on tuning stuff or ecm testing stuff, that repair facilities use, from what I've been told.

Wassa a guy that had done an auto select for 1-2-3 bar map sensors, and write on the fly thru the aldl for a 8625.

 

I use this software quite a bit , and I gotta agree with Bruce , as you are doing the on the fly change you do have to sit back and take a look at what is going on and attack the tune progresively.

To modify the 165 all that is required is to change the MAF wiring for TPS and swap a few pins at the ecu end (also delete a few like egr ) and a internal wire to be added to a SRAM board that is used in place of the memcal . Note the wiring mod can be done and then use Tunercats $5D defintion file without buying kalamker but you are not on the fly then .

I believe the code has been rewritten internally to allow this real time programming and it must swap between 2 binary images in the SRAM as the changes are made. I am only summising all this as the SRAM is twice the size of the binary file.

The new version, which I havent upgraded to yet but I have had a play with it , does auto tune (closed loop only but I found you want to be pretty close to start with before turning ) and does a 1 ,2 and 3 bar map sensors.

With the issue of the loosing where your previous change it can be undone if you havent saved the change and you are only modifying on point at a time not a whole calibration - gotta be careful not to move the mouse too fast thogh sometimes.

I dont sell the stuff , just something I found that works for me and a hell of a lot better than fitting the Haltech of ACCELL etc

JMY2c worth.

 

Do you ever have a stall when making changes?. Even swapping files, I'd image that to happen. Code might be so large that at the point of switching code it goes fail soft mode for an instant.

 

Might writting me off list?

 

Grumpy email me off list I cant see your email address to send to you.

I dont feel any stutter at all when making a change , in fact I have downloaded a completely different bin file to the ecu while driving and only noticed the engine note changing as it is swapping between tables ?

Another unique feature is having two sets of ignition , fuel maps , rpm cuts etc that can be switched between or interpolated between if you use two pots.

I have used this quite a bit to chage between a good igniton map to another map that was 4 deg more advanced and then moving the **** while driving to find the point on BSFC .(better than changing actual map value as it is easy to hit a lot more than 4 deg w by accident as you go over a bump or wrong key input - i like to play it safe).

bossute@iprimus.com.au

 

I have contacted Alan at Injection Connection (Kalmaker) and will probably be buying StreetPro3. At present, I have a DFI Infinity (the original Accel Power Processor, before Accel bought DFI). I have had no problem programming it on the fly. Note that Kalmaker says to not do that yourself and if you have a passenger doing it, they should have the screen turned away from you. Kalmaker has a lot more capabilities than my Infinity. I especially want the water injection control capability so I can do away with the funky pressure switch that came with my Paxton. And with their crappy (for them) exchange rate, this system is only $550 shipped! Move over DFI, Haltech, etc., etc..

 

I just hope they don't pack up and leave for 6 months or so like they did before, and just left their customers in the Outback.

 

Yeah Alans not a bad bloke , I got my setup of him after trying for ages to locate the mob that used to sell it , they just disappeared.
He seems helpful enough and the big advantage for me was he only lives about 50kms away so no problems getting technical support.he even leant me his version of the new software so I could have a play with it as a beta testa to see if I wanted to upgrade.
Gotta say its great not having to pull the memcal out every time I want to experiment.

 

Can you read the final bin in the Kalmaker so you can burn a prom with the same code?.
So you can use it on another car?.

 

How about this emulator? -

http://www.xtronics.com/memory/EPROM.htm#Emulator

Anyone have any info on this???

 

Feedback I have gotten from others is that no one has seemed to gotten it to work. Maybe someone has now. But until I can get positive feedback, I suggest passing on it.

Tomcat, sounds pretty interesting. Wish there was something like that for SD. You've definitely got my interest.

 

If you ever get the calibration 100% you can burn a eprom from the finished calibration file BUT you have to buy another security device to go under the eprom , something to do do with the extra code that looks for this "pal" to protect his copyright ! I think the eprom will work for 1 startup or 60 mins runtime if no "pal" in place.
For my mind I leave the "kalmaker board" in the computer as when it is in the BLM table is increase for higher resolution , something to do with the sram board having more memory ?
I have got it to work sucessfully on 5 TPI setups no problems.
Oneof the early issues I believe was that the calibrations supplied where for the Aussie Holdens which use a different ignition system so the reference angle nneds to be changed.
As it has its own datalogger built in the with the 8192 bauld the old issue of not being able to datalog the aussie stuff at the high speed is resolved.

I tried the emulator route with poor results as each change you had to stop the car and download , with this stuff I just sit in the passengers seat and add or subtract timing/fuel and analys what the result is instantly , so I can see what the car wants without the conditions changing for each test.