But that's a programmer. NOT a scan tool.
But it will enable me to at least read data, no?
What do people with an 88 Duke (DIS) use to scan? Obviously, WinALDL won't work.
Nope. All it will do is decode and edit EPROMs. There is a separate program used to read and burn them, that is included in the "package".
What you need is an OBD1 scan tool. (NOT just a code reader.) They're kind of uncommon, now. But the ones that are out there are not terribly expensive.
I've got an AutoXray 6000. Does OBD1 and OBD2. Don't recall if I've ever used it to scan my Duke, but there really isn't any reason that it shouldn't. It scans everything else, and provides sensor readings and etc. (The display says that it goes up to 2005, but I've read much newer cars with no problem.)
Works like WinALDL, only it's self-contained. Has its own display. Doesn't need a laptop.
If you buy an AutoXray, be aware that they are out of business. Nobody is around to support them. You'll have to buy all your cables and stuff off of eBay, if you don't get them with whatever you buy.
Actron is another "consumer" brand of scan tool.
You might find an old GM Tech1 scan tool, but they might need a lot of expensive modules to make them work. (Not sure, on this point.)
Edit - I was poking around and saw a bluetooth device that supports OBD1 and an android phone or computer, including TunerPro. It has a selectable ALDL baud rate. 160 baud or 8192 baud.
It occured to me that you might be using a similar device. The baud rate of the 88 (and 87) Duke must be set to 8192. They're the only Fiero ECMs that use that baud rate.
If the baud rate is wrong, it could cause bizarre readings, such as what I was seeing on your "dashboard" display. ("negative" temperature readings, etc.)