Just wanted to share this stuff with the DIY EFI crowd.
I'm wrapping up the #97 landracing car's EFI system. It's more appropriate to call it a "Powertrain Management System" as it does a heluva lot more than run the injectors and coils. Figured I'd share all the inputs and outputs I am running. This is 100% DIY, I assembled all three of the computers in the car myself. I am using as much Open Source tools as I can find, the goal is to make this a competitive and informative system that's reliable and gives us useful data.
To that end, we've come a long way with Megasquirt in a few years.
Here's what I am monitoring (inputs) on the megasquirt 3x, some of these are routed to the MS3x via CAN Bus using a JB Performance "IO Extender" which is a DIY electronics kit add on to Megasquirt devices:
Crank position (every 10 degrees)
Cam position (one signal per engine cycle)
Throttle Position
Manifold pressure (vacuum, boost)
Pre-intercooler air temp
Post-intercooler air temp
Fuel Pressure
Fuel Temperature
Oil Pressure
Oil Temperature
Coolant Temp
Coolant Pressure (monitor this to avoid headgasket failure!)
Intercooler Coolant Temp
Exhaust Gas Temp on all 8 cylinders
Front wheel speed
Rear wheel speed
Suspension Travel at all four corners (using linear potentiometers from RacePak)
Turbine Speed on both turbos (uses a cool Borg Warner sensor!)
Left and Right bank O2 sensors, wideband
GPS Speed
That all works out to nearly 200 separate circuits. +5v, +12v, low current grounds, high current grounds, etc. Most sensors require power, ground, and signal wiring.
So far I have everything working except the EGTs (waiting on custom cable lengths to be made).
I have the system set up to run a single red warning light (MSD light) to notify the driver of any critical problems. So far I have the following that will light up the shutdown light:
high coolant temp
high coolant pressure (head's lifting!)
low oil pressure
low fuel pressure
high oil temperature
I do NOT let the computer control the actual shutdown of the car - that's up to the driver. I'm simply letting him know that the computer is seeing something we all decided beforehand, we don't like. If the driver is on a record run in the last mile, red light be damned!
AS for computers in the car, I am running:
(1) a Megasquirt-3x in full sequential EFI and spark mode. This is the only CRITICAL computer in the car. It's gotta stay running. I carry spare parts, and a complete Engine Simulator for testing this box thoroughly.
(2) a JB Performance "IOX" box, this thing is awesome. It takes 20+ inputs of all types, and routes all their data over the CAN Bus (same thing as RacePak VNET) into the megasquirt-3x, making all those extra inputs usable inside the megasquirt-3, and writing them to the datalogs with the rest of the megasquirt data. Basically the IOX adds a ton if Inputs and Outputs to the whole system. This box CAN die if it has to, as all of its inputs are noncritical to engine operation.
(3) an Intel "CarPC" that I assembled myself using a VoomPC2 case, an Intel Atom processor at 1.8ghz, it's just like a laptop without the monitor and keyboard. THe reason I added this box (cost $550), was because the fastest way to record megasquirt data - maximizing samples per second - is through a good old 115200bps COM port. So I bolted this computer in the car to not only capture all the megasquirt log data, but to act as a communications server with its WiFi antenna so I can connect remotely from the push truck and monitor critical data as the car is on course... and I can also manually toggle the shutdown light in the car, remotely. Finally, if the car is in range of a wifi hotspot or has its Verizon AirCard installed, I can connect to the car from ANY internet connection and make adjustments, view run data, and even tune it remotely if I need to.
When all was said and done, for all these inputs and outputs including the sensors we've spent less than $5000. The bulk of that money is in sensors that couldn't be built by hand.
I welcome any comments or questions. I've been preparing this for 3 years, testing, testing and testing nonstop to work out as many bugs as possible before our runs which happen in one month.
-Scott
I'm wrapping up the #97 landracing car's EFI system. It's more appropriate to call it a "Powertrain Management System" as it does a heluva lot more than run the injectors and coils. Figured I'd share all the inputs and outputs I am running. This is 100% DIY, I assembled all three of the computers in the car myself. I am using as much Open Source tools as I can find, the goal is to make this a competitive and informative system that's reliable and gives us useful data.
To that end, we've come a long way with Megasquirt in a few years.
Here's what I am monitoring (inputs) on the megasquirt 3x, some of these are routed to the MS3x via CAN Bus using a JB Performance "IO Extender" which is a DIY electronics kit add on to Megasquirt devices:
Crank position (every 10 degrees)
Cam position (one signal per engine cycle)
Throttle Position
Manifold pressure (vacuum, boost)
Pre-intercooler air temp
Post-intercooler air temp
Fuel Pressure
Fuel Temperature
Oil Pressure
Oil Temperature
Coolant Temp
Coolant Pressure (monitor this to avoid headgasket failure!)
Intercooler Coolant Temp
Exhaust Gas Temp on all 8 cylinders
Front wheel speed
Rear wheel speed
Suspension Travel at all four corners (using linear potentiometers from RacePak)
Turbine Speed on both turbos (uses a cool Borg Warner sensor!)
Left and Right bank O2 sensors, wideband
GPS Speed
That all works out to nearly 200 separate circuits. +5v, +12v, low current grounds, high current grounds, etc. Most sensors require power, ground, and signal wiring.
So far I have everything working except the EGTs (waiting on custom cable lengths to be made).
I have the system set up to run a single red warning light (MSD light) to notify the driver of any critical problems. So far I have the following that will light up the shutdown light:
high coolant temp
high coolant pressure (head's lifting!)
low oil pressure
low fuel pressure
high oil temperature
I do NOT let the computer control the actual shutdown of the car - that's up to the driver. I'm simply letting him know that the computer is seeing something we all decided beforehand, we don't like. If the driver is on a record run in the last mile, red light be damned!
AS for computers in the car, I am running:
(1) a Megasquirt-3x in full sequential EFI and spark mode. This is the only CRITICAL computer in the car. It's gotta stay running. I carry spare parts, and a complete Engine Simulator for testing this box thoroughly.
(2) a JB Performance "IOX" box, this thing is awesome. It takes 20+ inputs of all types, and routes all their data over the CAN Bus (same thing as RacePak VNET) into the megasquirt-3x, making all those extra inputs usable inside the megasquirt-3, and writing them to the datalogs with the rest of the megasquirt data. Basically the IOX adds a ton if Inputs and Outputs to the whole system. This box CAN die if it has to, as all of its inputs are noncritical to engine operation.
(3) an Intel "CarPC" that I assembled myself using a VoomPC2 case, an Intel Atom processor at 1.8ghz, it's just like a laptop without the monitor and keyboard. THe reason I added this box (cost $550), was because the fastest way to record megasquirt data - maximizing samples per second - is through a good old 115200bps COM port. So I bolted this computer in the car to not only capture all the megasquirt log data, but to act as a communications server with its WiFi antenna so I can connect remotely from the push truck and monitor critical data as the car is on course... and I can also manually toggle the shutdown light in the car, remotely. Finally, if the car is in range of a wifi hotspot or has its Verizon AirCard installed, I can connect to the car from ANY internet connection and make adjustments, view run data, and even tune it remotely if I need to.
When all was said and done, for all these inputs and outputs including the sensors we've spent less than $5000. The bulk of that money is in sensors that couldn't be built by hand.
I welcome any comments or questions. I've been preparing this for 3 years, testing, testing and testing nonstop to work out as many bugs as possible before our runs which happen in one month.
-Scott
Comment