So I've had this eerie feeling when something happens in my car on the MS, and I look at the logs, that I wasn't quite at the RPM I thought I was at judging from the tach. Something at "5400 or 5500" on the tach was at 5100 in the logs, etc.


This was taken at "7000" RPM, but it was recieving a signal of only 6790



In fact, at ~1k, the tach is dead on. Here's how I put it elsewhere:

I fed the tach known spaced tach pulses, and found that the tach is accurate at low RPM (1000), and from ~1500-~4000 is picks up linearly about 175 rpm of offset (it reads high). Then it stays there until ~7200 (reading ~7375) and by 7500 it's reading correct again, which it retains through 8000 rpm, which is as high as I tested.

So, just an FYI....

More pics at 1000 rpm steps here:
http://abefm.smugmug.com/gallery/470...78447143_jQFm9

 

Good info. Now build something to correct it.

 

My tach is way off just like yours. I have my hard cut rev limiter setup for 7200 RPM but the tach indicates something like 7500-7600 when i hit the limiter.

 

I believe a similar phenomenon exists in the NA. Well, at least mine. Fairly accurate at low rpm, but not even close (couple hundred off) up top.

 

That oil pressure gauge is scary looking.

 

Yea Abe, ya *might* wanna check your oil level one day.

 

my tach is extreamly slow.... i posted up about it a while ago. just makes you feel better bout redlining it

 

I lovingly fashioned a post to the guys who write the MS-II extra code, thinking this handy bit of artisandry would be what it would take to fix the issue, asking for a scaling factor on the RPM out pulse train.

However, it seems even that wouldn't work, since the response varies across the board.

Quite annoying.

Oh, and I run synthetic oil, so I only build 3 psi of pressure. That's all it needs, I could run it there all day, and it was smooth as silk in that picture, too.

 

I'm 500 rpm off at redline. indicated 7500 but the dyno and datalogs show 7000.

 

That's really interesting! I believe I checked in the past with my scope and my jimstim is pretty decently accurate, but I was definately ~200 rpm over at an indicated 7000, and I think I was pretty much right on at 7500.

I've got a 2000... Yours is 99? Maybe it's just in the tolerance, but wow...

 

The NB revs ~6700 standard, tach usually shows ~7200 then.

 

01 hydra. interesting aside, after letting off the gas on the dynojet, the rpm went up to 7550 on the datalog.

 

I don't have a Miata yet, so forgive my ignorance...

Are you saying the problem lies in the dashboard tachometer, or are there any boxes that the tach signal pass through that might influence the results?

Is this something we can fix, or something we have to band-aid?

 

I'd say the 'band aid' is just knowing it's off.

Hmmm, another fine dynojet 'feature' it sounds like to me. I'll trust my NIST traceable oscilliscope before something that can't tell if RPM are increasing or decreasing.

Redline is quoted as being 7200 - and from my recent testing, I would say the offset is smaller than that - though it sounds like yours agrees with Y8ts...

 

I have seen this on my '99 with MS as well. A couple of times I thought the rev limiter was not working correctly but confirmed afterwards it is working just fine. As long as the MS is correct the dash tach error is not a big deal for me.