Throttle Cut Diagnostic Help On Motec M130

Hello, I'm looking for some pointers diagnosing this issue track side to get throttle back. The car is down over 6 seconds a lap on a 2 minute course.

Symptom: Fuel Output Cut Count number continues to rise. Throttle cuts to 65-67% suddenly after going to full throttle. Throttle pedal sensor shows 100% while throttle aim, position, and pedal all show 65-67%

Hardware: M130 ECU, C187 dash

Background: No history of this problem after many dyno runs and multiple road races. Only recent changes to package file (tune) were lowering the threshold of oil pressure warnings. The car had run fine after these recent changes. I am not a motec tuner, but am familar with the software and regulary support motec cars trackside.

Diagnostics: See screen shot of diagnostics in timeline. Fuel output cut count is the only item I'm seeing as possible cause.

Pictures don't help. How about the log files (or a snippet showing the problem) that you are using?

I would also provide the M1 package so we can look at the parameters that might be causing this.

My guess is you have a Throttle Pedal Translation that is controlled by a driver switch and it has been switched accidentally or an Engine Speed Limit has been triggered by something (look at "Engine Speed Limit State").

I find that looking at all channels with "State" in the name is often useful. What is the "Throttle Aim State"? Launch State? etc.

Thanks David,

I had previously looked those states and didn't see any smoking guns. The throttle aim did match the TB position, which we knew already.

You were right about the driver switch. There was a physical switch we were not aware of (car previously built by other party). There was logic in the driver display control switch that changed the map when held down for more than a half second. Best we can tell is that driver switched display screens on track, held the switch over .5 seconds and then did it again to confirm the map switch without knowing.

I have to say that your guess was pretty darn good! I also need to give credit to Shane T who also guessed it was a driver induced map switch as well.

Live and learn I guess!

Did exactly what you said, but not at all what was wanted. At least you have fixed the car for the next event..