I think the intent with the moates setup is to allow tuning on the fly while datalogging on the fly. When your finished, you burn to a chip and go.
Craig sent me an EEC V file from a Ford diesel pickup to determine the best spot to "inject" some code to grab data values that can't be seen the normal way so they can be data logged. The same principal used on the EEC IV's.
It sure will be nice to have an alternative to data log that won't cost an arm and a leg like the Tweecer RT does.
For anyone with an 89/90 SC can see some of the information I've decoded so far for these cars by going to
http://www.eecanalyzer.net/ and downloading BE (Binary Editor). You do not need to register it at this time. Make sure you download the definition file called GURE which covers these cars and you can download the C0S.bin which is for the auto's and the L0E1.bin file for the 5spds. If you want to look at this, pm me your email addy so I can send you an updated def file as the one on the site is a couple weeks old
.
I'm testing BE right now for writing to the moates chip and so far so good so that support should be released shortly.
EA is a good program as well, and has assisted me in tuning my car by analyzing the datalog files I've generated out of the EEC. I'm wrapping up a program that will work with the EEC Tuner for datalogging, and will hopefully be sending Dave D's way for testing soon. The program will convert the bin file to an EEC file so you have the benefits of BE for editing and using the same settings in the EEC Tuner.