Autosport Labs

Just starting to configure my RCP, and the RPM appears to be about 3x higher than it actually is. I've played with the pulse per revolution settings -- between 1, 3, 6, and the values don't seem to care. I've also played with the clock divider which causes the values to get very erratic when not set to clock/128. It seems clock/128 is correct, and the rest of the internet thinks the bmw m50 has a pulse per revolution of 3, but the RCP doesn't seem to care what I set it to. It reads ~3k rpm at idle (~1k actual) when set to 1 ppr, or 3 ppr, or 6 ppr. Am I not changing the scale in the right location? If it comes down to it, we'll just divide by 3 in our heads, but it'd be nice to get the correct value displayed.

http://www.autosportlabs.org/viewtopic.php?t=3711
You are not the only one to get the rpm divider "stuck." It happened to me and someone else. I reflashed the firmware, tried different rpm dividers, read them back out and my rpm still read 2x high.

Hi,

We have a preliminary fix for this issue; you can find the 1.1.11 firmware here:

http://dropcanvas.com/bthz0

I didn't do a general release as there are some new API stuff mixed in to enable the mobile app. It's mostly additive stuff with mostly sane refactoring of existing code; please test it as much as possible. If its at least as good as 1.1.10 + pulse per rev bug resolved, I'll do a general release.

There's also a fix for Race Analyzer in there to possible address crashy situations with the real-time logging view.

Please let me know how it works!

I had the same issue. Not sure if I had the 1.1.10 or 1.1.11 firmware (this was last month).

-Scott

I am getting the same 3x problem and changing any of the advanced input sensors inputs makes no difference in the value displayed.

Brent - thanks for the response below.

Hi,

We will shortly be posting an updated/official firmware release shortly that will address this issue. I'll notify this thread so you can install and re-test.

Thanks for the reply Brent. I had to reflash my unit after a bad script put it in a bad loop. Now Race Capture is exactly 300rpm too low.

Hi,

Thanks for the update. When you say it's 300 RPMs too low, what base RPM is that at? Trying to understand what % off you're seeing.

Brent -

It appears that when my digital timing light says 1240 rpm the Race capture says 940. This appears consistent from 900 (600 on race capture) to 3000 (as high as could go in testing).

brentp wrote:Hi,

We have a preliminary fix for this issue; you can find the 1.1.11 firmware here:

http://dropcanvas.com/bthz0

I didn't do a general release as there are some new API stuff mixed in to enable the mobile app. It's mostly additive stuff with mostly sane refactoring of existing code; please test it as much as possible. If its at least as good as 1.1.10 + pulse per rev bug resolved, I'll do a general release.

There's also a fix for Race Analyzer in there to possible address crashy situations with the real-time logging view.

Please let me know how it works!

Is this still the latest/best firmware and software for us to download and try?

-Scott

We have a 1.1.12 firmware ready to release! Will get it out today.

Released here. also see release notes.
http://autosportlabs.net/RaceCapturePro ... e_Releases

Still reading too high. At idle it reads ~1700rpm. At 2000rpm it reads 5600rpm. When I shut off the motor it reads 997.

Car is 1991 E30 BMW 318is M42 4 cylinder DIS.

RA 1.11
RCP Firmware 1.1.12

Under Advanced Setting for Pulse:
Mode: RPM
Clock Divider: Clock/128
Pulse Per Revolution: 1

-Scott

If I set the Pulse Per Revelotion to 2, it is much closer now, about 200rpm off.
Off: 498
At Idle: ~850rpm
1000: ~1200
2000: 2150
3000: 2150

Actually close enough.

-Scott

This needs to be dead on for multiple reasons. I think the "logging 10% fast" is related to what you're seeing here. Investigating; will update here when we find a fix!