Wednesday, 20 June 2012

RPM signal issues


Time for a bit of an update on this. Unfortunately, I am still chasing a clean, reliable rpm input to the ECU. I have given up on trying to take the input from the coil packs, simply because I would like to have the Microsquirt control ignition timing as well as fuel at some point so there is no point going through the pain twice.

I have made some bit of progress though. First is the trigger wheel definition. I made the fundamental mistake of not physically looking at the wheel myself and relying on pictures from the manual. Of course I didn’t realise that I was looking at pictures of a trigger wheel on an mc17 CBR250 which has the 8-1 trigger wheel. It was only after one of the members on the cbr250.com forum questioned me on this that I realised that the mc22 trigger wheel was a 12-3 definition. That explained some of the erratic signals and why the rpm was jumping to over 21,000rpm at idle. The ECU was expecting teeth where there was none and gaps where there were teeth.

The problem is that this didn’t fix the issue… It did make it better as in the signal peaks read by the ECU were consistent with the actual running rpm of the engine but the signal was still constantly dropping to zero. I tried a few combinations of noise filters within the Microsquirt software but to no avail. After contacting DIYAutotune who I bought the Microsquirt from, they have advised that I try switching to MSII/Extra firmware as it includes some extra diagnostics tools to help isolate the issue. One of these is the trigger tooth logger. I should be able to use this function to see if the ECU is actually reading each trigger tooth correctly and thereby tell me whether I need to concentrate on the VR signal coming into the ECU, or the settings within the ECU.

I have an idea that if the signal entering the ECU is the issue then I will attempt to convert the VR signal to a Hall signal externally using an LM1815 chip and feed that into the ECU. The ECU should be able to read the square wave Hall signal much more easily and cleanly than the AC VR signal.

Also, I have decided to go ahead and modify the GSR400 throttle bodies right away rather than attempt to tune the system on modified carburettors and then do it all again with throttle bodies. I am currently preparing the drawings for the throttle bodies, butterfly valve rods, fuel rail and fuel rail mount adapters so that I can get quotes from a few machine shops and get it kicked off. Once the throttle bodies are ready, that will be a major part of the project complete.

4 comments:

  1. This comment has been removed by the author.

    ReplyDelete
  2. I agree about using LM1815. I am using one to tap the pulse generator for Megasquirt. Works like a charm. Mine is a single cylinder though.

    I still have issues like fluctuating MAP reading which is expected on a single cylinder engine and the tuning software losing connection with the engine running, reads fine with the engine off. Noise? Got any suggestion?

    ReplyDelete
    Replies
    1. Thanks Edgar. It should work with a multicylinder aswel. I may have the issue solved for now though so if I can get away without using a conditioner circuit I will.

      I know what you mean about the fluctuating MAP. I have it also but probably not as bad as you. Have you tried using a vacuum reservoir to smooth out the pulses? There is also input smoothing lag factors in the Microsquirt V3. Not sure if it is in the Megasquirt modules? It is designed to smooth out the signal so maybe it will work for you. I havent played with it much myself yet.

      Delete
  3. on a single cylinder you need a cam sensor so the megasquirt will take the MAP signal lecture only once every two revolutions at the exact same timing so the fluctuation will be almost nill. it just cant work properly if the megasquirt takes a lecture at every revolution on a single because there is juste too much pressure variation between admision and expansion stroke. And with just a crank sensor, it will take the measure at every revolution.

    ReplyDelete