EFI For Big Blue
Locked
Re: EFI For Big Blue
 
Administrator
|
Re: EFI For Big Blue
Administrator
|
Yes, you did. But, you mean the GIN3 box. (Man, you have me worried! You are now 2 years older than I am, and look what those two years do to a man!
 )
 
Gary, AKA "Gary fellow": Profile
Dad's: '81 F150 Ranger XLT 4x4: Down for restomod: Full-roller "stroked 351M" w/Trick Flow heads & intake, EEC-V SEFI/E4OD/3.50 gears w/Kevlar clutches
|
Re: EFI For Big Blue
|
Administrator
|
Re: EFI For Big Blue
|
Administrator
|
Re: EFI For Big Blue
|
Administrator
|
Re: EFI For Big Blue
|
Administrator
|
Re: EFI For Big Blue
|
Administrator
|
Re: EFI For Big Blue
|
Administrator
|
Re: EFI For Big Blue
|
Administrator
|
Re: EFI For Big Blue
|
Administrator
|
Did quite a bit of running around today, but did manage to get one thing done towards EFI for Big Blue - found a "data link connector", aka OBD-II connector. Turns out that's not the easiest thing to find. Went to all three auto parts stores in town - nada. Finally called my friends at the salvage near here and they pulled the one below for me from an Aerostar, which means the wires are the right color. In fact, comparing it to the one shown in the '96 EVTM, this one has all the right wires and an extra to boot.
 I'm hoping tomorrow to marry the test harness Bill sent me with this connector, add a couple of switches for vehicle and keep-alive power, and it'll be ready for when I get the package from Core Tuning. 
Gary, AKA "Gary fellow": Profile
Dad's: '81 F150 Ranger XLT 4x4: Down for restomod: Full-roller "stroked 351M" w/Trick Flow heads & intake, EEC-V SEFI/E4OD/3.50 gears w/Kevlar clutches
|
Re: EFI For Big Blue
|
Re: EFI For Big Blue
|
Administrator
|
Re: EFI For Big Blue
|
Administrator
|
Now that you mention it, I think you did.
Well, this one will be either the one I wire in for Big Blue or Dad's truck. 
Gary, AKA "Gary fellow": Profile
Dad's: '81 F150 Ranger XLT 4x4: Down for restomod: Full-roller "stroked 351M" w/Trick Flow heads & intake, EEC-V SEFI/E4OD/3.50 gears w/Kevlar clutches
|
Re: EFI For Big Blue
|
Administrator
|
Re: EFI For Big Blue
|
Administrator
|
Re: EFI For Big Blue
|
Administrator
|
Re: EFI For Big Blue
|
Administrator
|
Makes sense. Thanks. But, it would be helpful if the Core Tuning web site or documentation, and preferably both, would explain that.
I sent Clint, and cc'd Ben and Adam, an email this morning explaining who I am and what I'm doing - both using their kit to do Big Blue and Dad's truck as well as documenting it as I go. And I asked why there are two versions of the documentation on Binary Editor, both authored by Clint but 10 years apart, and why their web site only links to the old one. Further, why neither document says that Binary Editor supports the cable they just sold me. And, I gave them a link to this thread as well as the forum/web site. Perhaps from my experience they can understand what is missing in their documentation and upgrade it. And, I hope that by thoroughly documenting what I/we do on Big Blue, whomever comes behind can do it much more easily.
Gary, AKA "Gary fellow": Profile
Dad's: '81 F150 Ranger XLT 4x4: Down for restomod: Full-roller "stroked 351M" w/Trick Flow heads & intake, EEC-V SEFI/E4OD/3.50 gears w/Kevlar clutches
|
Re: EFI For Big Blue
|
Administrator
|
I'm capturing this so Core Tuning can know what issues their customers may run into, as well as the work-around I found.
I just tried to install Binary Editor. The first thing the documents say to do is to install Microsoft's .NET package but that was already on the shop computer. However, when I then tried to install BE I got this error message:  So I tried installing Microsoft's 2007 Office System data connectivity components - to no avail because Microsoft said that I don't have any 2007 Office System applications on the PC. True, mine are all Office 365.  So, with quite a bit of Googling and several other attemps I did find a writeup that explains that installing Microsoft's 2007 Access database engine should work as it doesn't look to see what applications you have loaded. That installed nicely and then Binary Editor installed. Having said that, I don't know that it will work with Office 365. But at least BE installed. Meanwhile I texted with Adam and have a 9:00 call with him set up on Monday. However, I won't have the dongle that is coming in the mail, and that's needed in order to make BE fully functional. So we may have to reschedule. We shall see. And, I now have a test harness, thanks to Bill and a bit of solder, heat shrink, tape, and convolute.  
Gary, AKA "Gary fellow": Profile
Dad's: '81 F150 Ranger XLT 4x4: Down for restomod: Full-roller "stroked 351M" w/Trick Flow heads & intake, EEC-V SEFI/E4OD/3.50 gears w/Kevlar clutches
|
Re: EFI For Big Blue
|
Administrator
|
To help me get my head around what the "system" is that I'm working on, I created the block diagram below. The dashed lines indicate things that aren't always there. In other words, the EEC-V system will always be there, as will the Innovate wide-band AFR meter - until I move it to Dad's truck for tuning. But the Windows computer won't always be there. In fact, once the tuning is done and I'm happy with the way it runs then the it'll probably not be used again, unless I want to tweak something.
However, not shown is the Arduino computer I plan to use to convert the later fuel level sending unit's output to match the Bullnose gauge's input. And, it turns out that there's plenty of ways to interface an Arduino to an OBD-II port. For instance, this guy has a kit and says the Arduino can get and display the following info: Vehicle speed
|
Re: EFI For Big Blue
|