Are you volunteering Crispy?
The Megasquirt. I took the time to build it when I was working in the Middle East as I was away from the Bellytank and it was one of the few contributions I could make during that time.
The problem with buying a complicated piece of equipment and getting to know all the ins and outs and assembling it a couple of years ago, is that my muddied brain has to try and remember everything I once knew back then.
The other problem is that it is all acronyms and similar ones at that tax my bad with names brain at the best of times.
Finally it is designed to be used on ANY engine and so the variables are endless and not being a engine management expert, navigating through what we need is a course of find the acronym, work out what it means, work out is that we need, move on to the next acronym.
But that in the end isn't what slew me on the weekend. I can handle step by step processes, I have the patience of a cricketer and the training of a stop motion animator, and I know with the right data we'll get there in the end.
What is currently the bar from progress is that it seems that there is an error in my wiring or a failure in a component of the thing as we are not getting the RPM readout we should from the device in test mode. Cripes!!!!
I cannot work out yet if it is the Megasquirt, or its testing device "the stim" that is malfunctioning. With only two weeks to go I had hoped we would spend tuning the unit, not only getting it attached and running.
The purpose for having this unit is two fold, firstly so we can maximise our power tand running smoothness. Secondly, and perhaps most importantly, we don't know what the existing computer will do when we go over its natural limits of rpm...
So I am going to research that latter question this week whilst trying to resolve our megasquirt issue. Fingers crossed that one will pay off.
dik