Anyone else using this combo?

Apparently I don't have something setup right.

I get the fuel pump prime at key on, but I get a constant SES. I don't get the on and off SES at key on that I should.

 

Bill,

The APU1 should work straight out of the box without having to readjust your offsets or anything. It should automatically upload to the 'top' of memory at F000-FFFF for the 4k files. If more is used, as I think it might be on the EBL, then it'll still send it to the top of memory and you should be OK.

If everything is working properly on the binary/emulator, then you SHOULD get a single blink of the SES light when you key on (after a 20+ second key-off cycle) with any OBD1 GM ECU. Then when you start, the SES light should go out. If not, then something is wrong. If you're able to datalog via OBD port even so, then it could be just a legitimate error code. If you can't datalog, then something is wrong with the binary/etc.

With that in mind, give it another whirl. Let me know what you come up with.

-Craig

 

Thanks Craig!

No info displayed to the WUD.

Hooked up AutoXray scanner. No communication there either.

Tried jumping out pins A to B. No response. Continuous SES that came on with key on.

Checked continuity from ALDL pin B to A9 on ECM connector. No continuity.

Checked continuity from ALDL pin E to A8 on ECM connector. No continuity.

Also jumped ALDL pin A to ALDL pin G (fuel pump relay). Pump ran.

 

Needed to do some double checking before I posted. The EBL board will send data with nothing more then power to the ECM. However, without an valid BIN the data is meaningless. But still useful.

Try this:

Pull the AutoProm out, connect a laptop to the EBL and start the WUD. At key-on, engine-off, the WUD display should jump to a random setting of values. You can open a data log and see if it is actually collecting data.

This will verify that the ECM & EBL are actually running. If the display jumps and you can collect data then the ECM & EBL are running.

If you have an EPROM burner try the stock EBL.BIN file. See if you then get valid data on the WUD. If so, then move on to trying the AutoProm.

RBob.

 

I am getting data to the WUD without the AutoProm connected.

I reconnected AutoProm and was still getting data, but it was incorrect. 2 bar MAP, 9 lbs of boost, etc.

Loaded a bin into the AutoProm and hit the Emulation button on TunerPro. Green light indicating Emulation.

Still getting the constant SES.

I flipped around the ribbon cable from the AutoProm (so that the cable is over top of the EBL). HUD reads correct data. TPS movement is correct, etc.

Hit the Emulation button on TunerPro, but now says its not emulating. Guess that's what threw me off. I was using green light indicating emulation to determine the correct orientation of the ribbon cable.

Now I get the SES on, then off, then a constant SES at key on.

Adjusted the BPC vs Vac table, but it appears I'm overfueling.

Do I need to adjust the Min and Max Asynch Pulse widths? 80 lb injectors.

Also, WOT TPS is 93%. Should I make adjustments to get closer to 100%?

Thanks!

 

OK. Have it up and running

I can now also emulate. How does the emulation tie into the VE learn?

When I attempt to datalog with the WUD, it asks for a file number. I've failed at trying to create a file.

Is the base idle/IAC still set by shorting pins A to B on the ALDL? I've shorted these together and has no effect.

 

The green light in TunerPro simply tells you that any changes you make in the editor will be uploaded to the emulator. TunerPro has no idea whether or not you actually have the emulator hooked to your ECM at all, let alone whether you have it hooked up correctly.

 

Sweet, another backward ribbon cable mystery solved!

 

 

The VE Learn creates a new BIN, ready to go. After a learn session has completed just load the new BIN into the emulator.

For data logging the file popup requires a file name. The default extension will be .DAT, so no need to type that. Type in a file name to save the data log to and click the button ('open'?). Just need to be sure that it is on the hard disk, not the floppy or CD ROM drive.

The short A to B and key on should still close the IAC. Did it a few months back. The IAC will do a reset at key off after an engine run. To set the throttle blades adjust the screw to achive an IAC count of 5-10 steps during a warm idle.

RBob.

 

Thanks

Thinking there was an issue with slot B on the ALDL, I tried a jumper wire from A on the ALDL to A9 on the ECM. Still no effect on IAC. Shorting A to B should still flash codes, correct?

I know the IAC is functioning while running by watching the HUD.

 

One word of warning on "knowing the IAC is functioning while running by watching the HUD"....

I had a stuck TPS on my car, but it wasn't showing in the data stream - the numbers in the streamare what the ECM told the IAC to do, not what it actually did. There is no feedback on where the IAC is to the ECM. It tells the IAC what to do and assumes it did it properly. So you could still have an IAC problem.

 

Yes.

RBob.

 

Guess I should've said it seemed to be working. The steps were being displayed on the HUD and the engine speed was varying with the IAC steps.

 

From the drawing I have, it looks like slot B on the ALDL is a straight shot to A9 at the ECM. Is this not the case?