Extremely frustrating
There are several similar user inputs to different pieces of software you could be talking about.
Dave has mentioned at least one that is specific to his Dash2 and not your setup.
You think/assume that you have changed nothing significantly, but this may not be so to the hypersensitive RPM reading hardware or in the confused R-T software.
1) Hardware
a. Is the wiring identical?
I mean the location and bundling, etc of all the two vehicles' looms, not just the routing of the RPM trigger wire.
I know the problem is persisting in your car. If you didn't have to disturb the trigger wire in yours other than unplugging it, I'd be tempted to discount this point.
b. Are the ignition components the same?
They might be the same make and model, but unless you removed your distributor, etc...
Please don't laugh
As above, back in your car, things are still stuffed, so...
2) Software
a. Is the software the same?
I.E have you updated to a new version?
I make this as a general point, because when you uninstall and install the new version, all the settings go back to default.
b. I'm guessing that you are aware of the above, but have you checked all the areas that change in Analysis?
(i) Vehicle Options - this is a somewhat moot point, as the default is 2, as you require.
(ii) Variable Manager
c. DL2 Configuration: What is the sample rate on RPM?
Is it possible that you have used a different CF card that has a different SETUP.BIN file on it which has without you realising it reconfigured the logger?
If this has happened, it could explain why the Dash is crazy too.
I may have left something out. As I have not worked with any of the R-T displays, I am not savvy to the areas where the possible SNAFUs arise.
![Idea :idea:](./images/smilies/icon_idea.gif)
R-T would be well served to append all device configuration details to each log file.
I would not be surprised to learn that you have already attended to all of the above.
WRT the max r.o.c, the higher the number the less that it does. This should be intuitive. In my experience, when the RPM spikes high (and usually stays high), it is normally due to noise. Noise is not a black or white thing, it will always be present to some degree. A lower max r.o.c is needed to filter more noise.
I have been tricked more than once and not checked or changed the Vehicle Option "number of pulses" before I've begun changing the max r.o.c and sent myself crazy.
It is quite possible to have the max r.o.c too low, in which case the graph looks a bit like yours, with lots of straight lines. There are sometimes horizontal lines as well, where the valid changes are clipped, and RPM is understated when the number is way too low.
Bearing this in mind, I would reduce the max r.o.c before I increased it. You should not need to smooth over a full second (I am assuming that your "1" refers to smoothing in Analysis Variable Manager).
I am used to other systems where any smoothing can be defined in both time and no. of samples. More work for R-T, but it is confusing when in some fields it's time and others, samples.
Hope something here is of help.
![Smile :)](./images/smilies/icon_smile.gif)