DTAForum.com - a forum for the DTA ECU

Hi all. We're still trying to put the miss-fire to bed on the S1000rr. On the diagnostic display we have 250 odd cam tooth errors, but was wondering when this count starts from as we have done a fair bit of running recently. I realise there is a reset button at the bottom of the window but we have never used this. So is the count from the last map change? The user manual does not cover this question.

Thanks.

The count is from the last 'reset'
I reset it every time I go in there.

Thanks Rob, so with a count of 250 odd over 2 to 3 hours running I can ignore this and look elswhere.

No, but this may be a VR sensor? and give a poor signal at low speed. If that is the problem you will see the count rising at low rpm. If this is happening try setting 'only sequential above' 2000 rpm
Have a look at the diagnostic screen as the engine is running, this should highlight if there is a problem in this area. One of my engines throws a few errors during cranking but that's all, but that's a hall sensor.

IIRC we have the engine set to run sequential only above 2000rpm, but will check this to be sure.

We had an issue with the standard BMW electronic hall effect tps, the ecu wasn't happy with it and it was causing a random miss-fire from start up, this has been cured by fitting a 'standard' resistive tps. What we have now is a time related miss-fire. The engine will start and run, but after a few laps the miss-fire will return. The engine will not rev but idles fine, bear in mind it idles at around 1600rpm so the slightest touch of throttle takes it out of batch and into sequential. Switch the ecu off and on and on again and all is fine for a couple more laps.

Stupidly I forgot to tick the check boxes of any useful things to watch in the data logger, so can't refer to that.

Yeh, get the logging working, blind without it

250 cam errors is nothing. You will often get a couple as the ECU transitions from wasted spark to sequential, so you can ignore low counts.
At 3000 RPM you're looking at 25 cam pulses per second, at 12000 it will
200. If there was a genuine cam sensor error that caused misfires, you're rapidly in to the thousands.

Your problem is elsewhere.

Thanks guys, just ruling out things one at a time.