On the end of the crank Ray Debben had made a rotor to trigger the ECU.
I made a sticker so that the various trigger points could be understood easily (so I could strobe the timing without confusion).
With everything wired in and checked I loaded the software onto the laptop and connected it to the ECU.
After a little fiddling to get the laptop comms settings right, the ECU and the laptop talked to one another.
The great thing about the software is that it gives a dashboard that shows all the sensor readings.
There is also a setup screen that lets you configure the system to the sensors and the engine config that you have. Some of these are obvious, some are standard settings.
The software comes with a list of standard maps, I chose one for a Suzuki that with a little fiddling looked ok to make a start.
The system also has an oscilloscope function that allows you to see the signals from the crank sensor. Every time you start the engine the ECU has to understand where the engine is on its cycle and fire the sparks and fuel accordingly. The oscilloscope trace allows you to see what the ECU sees from the crank sensor- if there is any problem (false triggering etc) then the ECU does not configure and the fuel and sparks don’t happen.
This is the display trace.
I had a lot of problems here, but eventually got a good enough signal for the sparks to switch on.
Pressed the start button with the fuel pump fuse in place and the motor just cranked and cranked.
I fiddled with the cold enrichment and with a sudden roar the engine sprang into life.
Promptly stopped, but it was alive.
Then its back to the set-up screens and look for problems-
Otherwise its looking at the fuelling/ignition tables.
With more fuel I got the engine running for a few minutes to do two things, first I checked the ignition timing with a strobe and second I “balanced the carbsâ€.
There are several ways to add more fuel for example. Cranking enrichment, cold engine enrichment and adding fuel to the main fuel map. As you get more familiar with the systems so you get more able to identify which table to fiddle with.
After several sessions the bike ran, but quite rough, and started intermittently.
One word of warning when considering FI- whenever something went wrong I found it easy to get bogged down in my naivety, seeing shadows of complicated problems when often the problem was basic and nothing to do with the FI.
So, having got frustrated and stuck I asked Ray Debben for some help. He started by checking the ignition timing, and found his strobe did not trigger very well. I was not so familiar with strobe so I hadn’t really noticed the problem.
At least now I had a problem to investigate.
I purchased one of those Gunsen ignition testers- great to check the power of sparks.
This tool revealed that the sparks were terribly weak. First problem was my old plug leads were leaking sparks around the place (where they touched the engine cases), second was that the standard signal that the ECU was sending to the coils was not enough to give a beefy spark- so with a simple adjustment of the set up table (but outside the recommended range) the coils were delivering strong sparks. But still they were irregular at tick over.
After looking at the oscilloscope trace and the error codes- it was clear that the crank sensor was not delivering the goods. After some research I found that the crank sensor I was using was an induction type. This means that it is a little magnet on a metal bar with a coil around it. The magnet creates a magnetic field and as the metal teeth of the timing rotor pass the sensor the field is distorted and induces a pulse in the coil- and where there is a gap in the teeth there is a clear null period to trigger the ECU.
The problem is that the electrical pulses induced in the coil are dependent on the speed of the passing tooth, its distance from the sensor, the size of the gaps between the teeth and the metal mass of the tooth itself. Clearly with a production set up the system can be tailored to ensure the signal is reliable in all conditions, my set-up however was marginal and did not produce a very reliable signal at low rpm. To get over this I found a Hall effect sensor with the right characteristics. The signal it generates is very clean and is not speed dependent- I just had to provide power to it.
Here is the new sensor in position.
At last, the bike started reliably and ticked over smoothly.
z650/1400 bonneville hybrid.