I'm running TunerPro RT with a Moates Ostrich in Emulation mode for tuning my engine. TunerPro RT doesn't save datalogs right now on 160 baud systems.

So how feasible is it to tune properly? The best I can do is monitor the sensor data in realtime, which isn't always possible when your driving (can be dangerous too). Without datalogging, am I not just "shooting in the dark"?

I plan to work around this by using WinALDL to datalog until TunPro is fixed. Does that sound like my best option?

From the research I've done, I see the best approach is:
1. Fuel settings
- first idle
- WOT next
- then "fill in the blanks" in cruise modes

2. spark tables next

AM I on the right track?

Thanks all,
Tony

 

It used to be the only to, tune.
But, with all the software, available nowadays, it's just more cost effective, and as you noted safer to do it with datalogging.

Datalogging, and Widebands, just save your time effort and money in the long run. While the intial cost is high, those items quickly pay for themselves.

 

I am getting nowhere awfully fast.

Latest version of TunerPro RT (today's) with the correct BIN and XDF files etc. Uploading the BIN to Ostrich declares "success", but clicking the "Verify BIN" gaves me a FAILED. The Help files only tells you to try again, which I've done many times, but the BIN just won't upload properly.

The engine barely idles and the Check Engine light is on.

I put the PROM back in, it runs fine (or at least it's back to ususal).

 

Update:

In Tools/Preferences/ALDL-Emulation

Uncheck - Disable Checksunm
Uncheck - Quick verify mode

TunerPro seems to upload BIN properly and verifies as OK.
Hopefully this will also work when plugged into the ECM in the car.

 

Make sure you have the key in the on postion when you first upload and verify your bin to you ostrich. It won't work unless the ecm is powered up. Found this in a post on Moates' site.