Watching some in car footage i noticed the RPM guage seems to show the same readings alot. like "5445". its not smooth or updateing fast enuff? any thoughts on what would cause this.
Here's a link to a 30 sec video where you can see what i mean. https://youtu.be/LSXodl13IYc
MK2/Rpi on latest app and firmware.
USB cable from MK2 to Rpi dash
Rpm channel set to medium and 25htz (same as all other channels) pulled in from a CoilX attached to kettering type ignition (GM Hei)
Thanks, Dave
RPM slow response to app
Moderators: JeffC, rdoherty, stieg, brentp
Hi, is this your car's video, or something you found online?
Best would be to do a controlled test to carefully observe the RPM response. There's too little information in the video you shared for us to comment. Overall, RaceCapture calculates RPM on every ignition pulse, which will make it very high resolution.
Best would be to do a controlled test to carefully observe the RPM response. There's too little information in the video you shared for us to comment. Overall, RaceCapture calculates RPM on every ignition pulse, which will make it very high resolution.
Re: RPM slow response to app
Instead of starting a duplicate new topic, figured reply to this one.
I'm seeing RPM signal is delayed on tablet which is connnected via bluetooth to RaceCapture/Pro Mk4. RPM is coming over legacy OBDII (2003 Ford ecu).
Is RPM expected to be delayed over OBDII? Is tablet connection over bluetooth or wifi preferred?
I'm seeing RPM signal is delayed on tablet which is connnected via bluetooth to RaceCapture/Pro Mk4. RPM is coming over legacy OBDII (2003 Ford ecu).
Is RPM expected to be delayed over OBDII? Is tablet connection over bluetooth or wifi preferred?
Re: RPM slow response to app
Hi,
What you're experiencing is possibly a combination of things:
1. The ECU's protocol for older (pre 2008 ) is quite slow compared to the CAN protocol of newer cars. This will limit how fast individual channels will update.
2. The OBDII protocol is request-reply protocol where each requested channel takes turns being requested. We have a very smart querying engine where channels configured for faster update rates are queried at a higher interval, to help optimize the design. See our OBDII guide here for the rest of the story and on how to set up your system: https://wiki.autosportlabs.com/RC_OBDII ... erformance
Overall, our OBDII system - especially with our legacy adapter, is designed to display data as fast as your ECU will allow. See the notes here on the Legacy adapter:
https://wiki.autosportlabs.com/OBD2CAN# ... f_your_ECU
One other way to get faster RPM performance is to directly sense the RPM signal using RaceCapture/Pro.
https://wiki.autosportlabs.com/RaceCapturePro_RPM
https://wiki.autosportlabs.com/RaceCapt ... PM_Sensors
We hope this helps!
What you're experiencing is possibly a combination of things:
1. The ECU's protocol for older (pre 2008 ) is quite slow compared to the CAN protocol of newer cars. This will limit how fast individual channels will update.
2. The OBDII protocol is request-reply protocol where each requested channel takes turns being requested. We have a very smart querying engine where channels configured for faster update rates are queried at a higher interval, to help optimize the design. See our OBDII guide here for the rest of the story and on how to set up your system: https://wiki.autosportlabs.com/RC_OBDII ... erformance
Overall, our OBDII system - especially with our legacy adapter, is designed to display data as fast as your ECU will allow. See the notes here on the Legacy adapter:
https://wiki.autosportlabs.com/OBD2CAN# ... f_your_ECU
One other way to get faster RPM performance is to directly sense the RPM signal using RaceCapture/Pro.
https://wiki.autosportlabs.com/RaceCapturePro_RPM
https://wiki.autosportlabs.com/RaceCapt ... PM_Sensors
We hope this helps!