MS3 EDIS 4 wasted spark

The additional BIP373 arrived in the post today. I needed to find a space to install the extra driver within the Megasquirt casing. I decided to remove one of the large sense resistors (R38) from the heat sink to make space for the new ignition drivers.

I figured this would be okay to remove as I am only intending to use one single large injector (750cc), meaning the second injector bank won’t be used (which R38 protects).

BIP373 Additional Ignition Driver MS3

Install Twisted (Python) on CentOS 6

Make sure the current system is up-to date

yum update

Install the necessary packages required to satisfy Twisted’s dependancies.

yum install wget python-devel python-zope-interface

Also install the Development Tools

yum group install “Development Tools”

Download the Twisted Framework (example location: ~/src)


Extract files and install

tar jxvf Twisted-12.1.0.tar.bz2
cd Twisted-12.1.0.tar.bz2
python install

Test the installation was successful by creating a Python test file.


Insert the following lines:

import twisted
import twisted.web

Save the file

Ctrl-X (Enter filename when prompted)

Execute the file with hopefully no errors


Damn you Wasted Spark

1st Generation Ford EDIS 4 Coil Pack

I have been working on the ignition output of the Megasquirt today, however have ran into a few snuggles. It was briefly decided many months ago that we would initially use a Ford EDIS-4 coil-pack running a wasted-spark, combined with a VR sensor pinched from a scrap Zetec engine. Upon the initial build of Megasquirt I saw a few entries related to EDIS style ignition setups and thought nothing more as I wouldn’t have to cross that bridge until we install it in the car.

That time has now arrived haha. Upon re-reading the MegaSquirt 3 assembly documents, the EDIS setups mentioned there utilise an individual unit that is separate from the main MegaSquirt, known as the EDIS module. This module combines the tach input from the VR sensor and coil driver ignitions into a single unit. From my understandings, the module sends a tach signal to the MegaSquirt in a format similar to how Coil-Negative ignition works.

For our setup we aren’t using the EDIS module, instead I want to be able to run Direct Coil Control. Which removes the necessity of the EDIS module by connecting the VR sensor and EDIS coil directly to the megasquirt itself. Three reasons why I prefer this approach;

  1. I don’t have a spare EDIS module lying about.
  2. I want to avoid installing any extra ancillaries in the engine bay.
  3. The Megasquirt is capable of Direct Coil Control, so naturally I want to make use of it.

I already know that the EDIS-4 is two separate coil packs stuck together in a single unit and I already know that my Megasquirt comes included with a single coil driver. Upon further research on the Megasquirt forums I have come to the conclusion that I need to install an additional Bosch BIP373 Ignition Driver into the ECU. A quick search on Google for the Bosch part turned up on a few distributors in the UK, all of which were currently out of stock.Logged onto to DIYAutoTune where I knew they would have the part in stock, $19 total including delivery.

In hindsight, I would of ordered the extra ignition module when I first bought the MS3 kit in summer 2011. However back then we was only going to run a ‘Fuel-only’ setup, and that was also before we decided to run a turbo. Ohh how times have changed.

I will write another post relating to installation and testing of the driver, when the parts arrive from the States.

UPDATE: Follow on post can be found here.

Which slice of Pi to try?

Raspberry Pi Logo SVG

I was one of the lucky few to get hold of my Raspberry PI during it’s initial release earlier this year. Since then I haven’t really done much with it, apart from tinkering around with the different OS’s available for installation.

I plan to use my Pi for a future project named “open-dash” (project details coming soon), which will essentially require the Pi to boot ASAP and run a simple GUI application in fullscreen upon startup. The application will simply display statistical data and will not require the use of a keyboard or mouse.

So this weekend I have been experimenting with the different OS’s easily available to install on the Pi, from

  • Raspbian “wheezy”
  • Soft-float Debian “wheezy”
  • Arch Linux ARM
  • QtonPi

Straight away from just looking at the list I can rule out the “Soft-float Debian Distribution”, as it is not utilising the full capacity of the Pi’s hardware by relying on software to perform tasks that instead of using the hardware that will be quicker.

1 down, 3 to go.
I propose a simple test to help me draw an initial conclusion. I will create a simple test application to be executed upon system boot, and time how long it takes until execution occurs. I will begin research into using minimal based installation images, to strip use of any unwanted packages that would be otherwise unnecessarily loaded, in effort to reduce overall boot time. Without looking at other users benchmarks, I am aiming for a sub 10 second boot time.

UPDATE 18.11.12

After trying numerous distro’s, I was struggling to find a sub-10 second boot time. Official releases of Raspbian boot in about 20 seconds, un-official stripped down releases of Raspbian¬†claiming to be ‘minimal’, didn’t prove to be much quicker. However the official release of Arch Linux boots in near enough damn it 10 seconds, which seems to be promising. Hopefully with a little tweaking I can reduce the boot time even more by removing unnecessary services, as well as looking into a re-building a custom kernel.