EFI For Big Blue

[grumpin]

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.

Good find!

[85lebaront2]

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, I thought I sent a connector with the GIN3 box and EEC-V plug.

[Gary Lewis]

Gary, I thought I sent a connector with the GIN3 box and EEC-V plug.

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 Lewis]

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.

Bill - I'd like to pick your brain on various things about Core Tuning as what I read on their site is very confusing.

For instance, I ordered the Direct Flash package as that's what Adam recommended. In fact, after reading further on their site I was concerned that it is the wrong package and called him back. But he checked what I'd ordered and assured me it is the right thing.

The package includes:

1) Binary Editor w/Dongle

2) Includes All Supported Strategies

3) Pro Direct Flash Cable

4) OBDII License

But when reading the Getting Started document on Binary Editor it says "Supports multiple hardware types ie Moates, TwEECer, EEC Tuner, Drew Technologies, ELM 327, ELM 320." There's no mention of "Pro Direct Flash Cable". What am I missing?

Then in Section 2.2 of the document it says "plug in the hardware device". I'm assuming that is the Pro Direct Flash Cable - right? If so, again there's no mention of that cable in the 2.2.1 table, and therefore no URL from which to get the drivers.

Am I looking at old documentation? What cable do you have?

[Gary Lewis]

Bill - I'd like to pick your brain on various things about Core Tuning as what I read on their site is very confusing.

For instance, I ordered the Direct Flash package as that's what Adam recommended. In fact, after reading further on their site I was concerned that it is the wrong package and called him back. But he checked what I'd ordered and assured me it is the right thing.

The package includes:

1) Binary Editor w/Dongle

2) Includes All Supported Strategies

3) Pro Direct Flash Cable

4) OBDII License

But when reading the Getting Started document on Binary Editor it says "Supports multiple hardware types ie Moates, TwEECer, EEC Tuner, Drew Technologies, ELM 327, ELM 320." There's no mention of "Pro Direct Flash Cable". What am I missing?

Then in Section 2.2 of the document it says "plug in the hardware device". I'm assuming that is the Pro Direct Flash Cable - right? If so, again there's no mention of that cable in the 2.2.1 table, and therefore no URL from which to get the drivers.

Am I looking at old documentation? What cable do you have?

Update: While the file linked to above, Binary Editor Getting Started, is what is available via the Core Tuning web site, it is dated 12 Aug 2009 and is Revision A. However, by doing a Google search I found a file called Binary Editor Help that is dated April 1 2019 and is Revision 5.166. The latter file contains the 17 pages of the first file and adds 69 more pages! And both were written by Clint Garrity, the 3rd person in Core Tuning.

I haven't, yet, fully read the larger of the two, but will do ASAP. Perhaps it answers some of my questions, but is sure to raise several more.......

[85lebaront2]

Update: While the file linked to above, Binary Editor Getting Started, is what is available via the Core Tuning web site, it is dated 12 Aug 2009 and is Revision A. However, by doing a Google search I found a file called Binary Editor Help that is dated April 1 2019 and is Revision 5.166. The latter file contains the 17 pages of the first file and adds 69 more pages! And both were written by Clint Garrity, the 3rd person in Core Tuning.

I haven't, yet, fully read the larger of the two, but will do ASAP. Perhaps it answers some of my questions, but is sure to raise several more.......

The pro direct flash cable is only for the EEC-V/OBD-II systems and is the interface between your laptop and the vehicle, the other equipment listed are primarily for use with EEC-IV systems where the EEC cannot be reflashed and requires a piggyback tuner (Moates, TwEECer etc.) The software supports these, but, in order to use any of them the license has to reflect it.

[Gary Lewis]

The pro direct flash cable is only for the EEC-V/OBD-II systems and is the interface between your laptop and the vehicle, the other equipment listed are primarily for use with EEC-IV systems where the EEC cannot be reflashed and requires a piggyback tuner (Moates, TwEECer etc.) The software supports these, but, in order to use any of them the license has to reflect it.

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 Lewis]

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.

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 Lewis]

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.

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

Engine RPM

Throttle position

Calculated/absolute Engine load

Engine coolant temperature

Intake temperature

Intake pressure

MAF flow pressure

Fuel pressure

Barometric pressure

Ignition timing advance

Engine running time

Vehicle running distance

So, that might be a way to get the additional info I was planning on having the Arduino display - potentially in a display housed in a F600ish radio bezel. And, I could have switches in the switch openings for things like the air compressor, PTO input to the EEC to up the idle, parallel the batteries, etc.

[FoxFord33]

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

Engine RPM

Throttle position

Calculated/absolute Engine load

Engine coolant temperature

Intake temperature

Intake pressure

MAF flow pressure

Fuel pressure

Barometric pressure

Ignition timing advance

Engine running time

Vehicle running distance

So, that might be a way to get the additional info I was planning on having the Arduino display - potentially in a display housed in a F600ish radio bezel. And, I could have switches in the switch openings for things like the air compressor, PTO input to the EEC to up the idle, parallel the batteries, etc.

Man, alive! Cool stuff! I know it will work, just a matter of grabbing all the handles.

I use the ELM 327 for OBDII. It was like $6 a few years ago. I have only ever run free software from my android with it, and it does all I need, but there is capacity for quite a lot, depending on what you can make the ship's computer plus the Arduino glean from sensors (factory or additional). I think you might remember that we found out Apple (at that time) did not play well with the way the bluetooth connection code stacked, and therefore wouldn't communicate. But I don't know if they have changed anything with that. Anyways, in future, someone with a popular interface will be able to talk to the truck.

I'm going to be looking into what it would take for me to go from OBD to OBDII on my 93. Just for curiosity's sake, unless it's not too difficult.