elkabong

Well I finally got around to throwing my 8746 mod'd with EBL, HAM and Ostrich in my 84 Vette.

The ECM immediately through code 33 (map hi) and Whatsup had intermittent comms. I guess I have a little more work to do on porting over my 383 bin. The comm setup is Radio Shack Serial to USB converter - with WinAldl it worked flawlessly. Has anyone experienced a similar issue with the comms?

At least it started which is a good thing.

RBob

iTrader: (1)

The MAP high is common with big cams. Need to set the diagnostic threshold higher. The parameter name is:

MALF33 - MAP Hi BARO Limit (n-bar)

Pick the one that matches your MAP sensor (1 or 2 bar). Then set it 15 to 20 KPa higher then the idle MAP reading.

For the intermittent comm, I recall testing with the RS serial-to-USB and it worked. What are the symptoms? Can't always connect? Dropped data? The data rate of the EBL is much higher then WinALDL. It may be an issue where a wireless card or infrared port is using CPU and interrupts.

RBob.

elkabong

The comm thing is weird - rebooted and whala. M$ at its finest. I will adjust the map settings - thx..

elkabong

Well I am still have problems with the comms.......

Here is my setup for clarity.
ECM - 8746 modified with HAM (84 Corvette), EBL using the Ostrich
Laptop - Toshiba Satellite (A105-s4004)
Dual Core - 1.6ghz
Memory - 1GB
4 USB ports (used flawlessly with 7747 ecm/Ostrich/WinAldl)
OS - WinXP Media Center (glorified xp pro)

When I fireup WhatsUp the software looks as if it is functioning because I see various colors on the bars but when I start the vehicle there is no activity on the display - the display is frozen. No RPMs or no measurements of any kind. Also when I shut down Whatsup.exe the whole screen goes blank and I have to reset the system by holding down the power button unti it resets. I have tried configuring the usb port for com1 & com7 but the same thing happens. I have also reinstalled the radioshack driver and it work 3 times (start up then shutdown) then the same crap started. I also seem to be getting a code 51 now. Does the disable checksum in Tunerpro RT work the same way as with my 7747 - eg I can disable it and a 0xaa gets stuff in the address for the checksum? I noticed EBL uses byte 6 & 7 for the checksum can I stuff a 0xaa there to disable it? fwiw - the jumper settings in the Ostrich are correct.

I have no problems with WinALDL and my 7747 ECM. With the EBL I am using a 8746. I have also disabled the IAT but I am still getting code 23 (IAT), Code 33 (Map sensor high) and now Code 51 this I got through the SES.

RBob

iTrader: (1)

To disable the checksum set the MaskID to 0xAA (not the actual checksum). I'm not sure that will solve the issue. It will prevent a fast flashing SES, but it may mask other issues.

Can you burn a PROM and try it that way? With the errors it seems that the ECM isn't getting good data. I can also burn your BIN into an EPROM and mail it to you.

With the engine running seeming to trip up the system, I have to ask, what spark plug wires and spark plugs are you using?

RBob.

elkabong

I will dig around for a eprom. I have a burner but probably not the eprom. What type of eprom should I use for a 8746?

They are AC Delco plugs and mallory 8mm wires.

I also have a different serial to usb converter and I am going to give that a go. I was not able to get this converter to work with WinALDL but heck who knows....

This is what I see when I view the Malf dialog.

RBob

iTrader: (1)

For an EPROM can use a '128 or '256 size. For a '256 (such as a 27C256) will need to stack the BIN. Just double it. TP has this capability. For a 27C128 it is a straight burn.

The reason I ask about the plug wires is that a recent thread s10wildside was having a lot of issues when the engine was running. It was tracked down to having solid core wires on the engine. Once swapped over to some suppression type wires all of the problems ceased.

For the malfuction codes it woudn't hurt to clear them. Can pull the ECM fuse for a few seconds. It may also be worth doing a bunch of key-on, engine-off testing with the various serial to USB cables. Try starting and stoppping the WUD, can hit the gas pedal to see if it is still active. Then key off for 10 seconds and key back on.

If it all works with the engine off, then fails with the engine on. I'd be suspicious of noise. An bad alternator can also create a lot of noise.

RBob.

Toehead

My conectivity problems were caused by noise.. Engine off, seemed to work. Engine on, the data began to scamble, never to recover.
I replaced my data cables with twisted pair shielded CAT5 and all is well again.

elkabong

I took the EBL off the 8746 and put it on my 7747. So far it is working and I have data. I guess the 8746 ECM has some issues. The motor is running pig rich but I really have not tweaked anything. A big bonus was no error codes. Tomorrow the WB02 gets installed.

RBob - Do you have any recommendations on settings for a mild 383 with 90 lb injectors and XRam? I figure I would ask and hopefully save myself some time in the hot garage.

Fast355

iTrader: (2)

Talk to Dominic Sorresso, he has essentially the same setup but with a 350.

RBob

iTrader: (1)

That is good news.

As for initial setup I calculated a BPC of 101. This is with the flow at 90 #/hr and 6.3L of displacement. If you had this setup running on another ECM can move the SA and VE tables over. Otherwise fire it up and see how it runs. If it's in the ball park do some driving around and let the VE Learn bring the VE tables in.

May need to reduce the TPS% AE some. But it is hard to say with the XRam on there.

RBob.

elkabong

I have to say it..... The EBL is truely an amazing device. I was able to get her to a driveable state in about 20 mins.

Time for more reading and tweaking....

Dominic Sorresso

El,

Let me know if you need any tips or pointers.

elkabong

I will take any tip or pointer you manage to throw my way... Right now I am trying to figure out the VE Lean (blm no wb yet) for a coarse setting. It does not seem to be working for me - i am probably doing something stupid.

azc4vette :at: ***.net

Dominic Sorresso

El,

What exactly isn't working for you? Are you using a C/L bin?

elkabong

I just cant get VE learn to function. I only get updated cells at 2000 rpm. The update blm's are also higher in value which does not make sense because I know I am running rich (o2 sensor is at .9 volts) and I would expect the updated cells to be lower to reduce fuel. The rest of the cells are unchanged. I validate the bin using the compare bin function in TunerPro RT. It is odd. I have tried locking and unlocking the blms but no change. I have also set the temp threshold high for closed loop and adjusted the CTS parameters in WhatsUp to 0 and 220. But the same thing, only the cells at 2000 rpm get updated.

Dominic Sorresso

Have you checked the BLM Learn params in the bin? You have the MAP, RPM windows. Then there's the CTS C/L Threshold that I have set to 59C. C/L comes in after that temp. Have you tried, locking BLMs first and tuning using the WB first. That's the best way to rough in the tune then unlock and tune with BLMs. I set the Learn VE params in WUD at 75 to 103C. No sense in going lower than that, or higher. Are the updated BLMs at idle? I just installed an IAT sensor and that has made a difference in the stability of the BLMs.

elkabong

The learn param's are at the default values - map upper 99.69/lower 28.75 - rpm upper 3600/lower 450. Right now I do not have the WB installed so I am just using VE learn with the BLMs (not wb). I am not getting any updates at idle. All the other parameters are close to what you stated.

elkabong

The learn param's are at the default values - map upper 99.69/lower 28.75 - rpm upper 3600/lower 450. Right now I do not have the WB installed so I am just using VE learn with the BLMs (not wb). I am not getting any updates at idle. All the other parameters are close to what you stated.

RBob

iTrader: (1)

That does sound strange. When in VE Learn does the rectangle change to green? That is a sign that it is in learn mode. Note a throttle blip will change the rectangle to yellow until things settle down again.

If you have a data log to play back, do that and flip between the VE Learn display and the graphical display. On the graphical display check the closed loop and learn indicator lights, and the BLM value. If the BLM is near 128 there won't be a change in VE. And the ECM needs to be in closed loop and learn mode (ECM blm learn mode).

You are welcome to email me a log file (zipped if possible). I'll take a look at it.

RBob.