finally got a TACH signal... but..

Post by **brentp** » Wed Mar 01, 2017 9:49 pm

From my understanding, it's doubtful it would be needed for measuring RPM, but it could always be added later.

The reason why you need 0.5 pulse per revolution is that your coil fires once per 4 combustion cycles, with individual coil packs. As far as I know, there isn't an ignition system combination that would fire less frequently than that across the 4-cycle internal combustion engine set up.

bahnstormer · Post by **bahnstormer** » Tue Mar 14, 2017 5:07 pm

ahh ok cool.

When is the update being released?

Thank you,

Johnathan

bahnstormer · Post by **bahnstormer** » Wed Mar 22, 2017 8:30 pm

Brent,

When is the update being released? We need the tach working for the weekend. Please update this forum with the link to the newest release.

Thank you,
J

Post by **brentp** » Wed Mar 22, 2017 9:34 pm

Hi,

The solution for this is a change in the app, and we'll have it in the next app release. We won't have it available by this weekend, but - there's a way for you to be able to set it behind the scenes in the meantime: Here's how:

* Read your configuration and save it to a file
* Edit the file in a plain text editor and find the timerCfg section. You'll see something like this:

Code: Select all

   "timerCfg"&#58; &#123;
      "0"&#58; &#123;
        "alpha"&#58; 1.0,
        "max"&#58; 8000,
        "min"&#58; 0,
        "mode"&#58; 0,
        "nm"&#58; "RPM",
        "ppr"&#58; 1,
        "prec"&#58; 0,
        "speed"&#58; 1,
        "sr"&#58; 0,
        "st"&#58; 0,
        "ut"&#58; "rpm"
      &#125;,

Note the "0" following timerCfg - this corresponds to the first timer channel; "1" is the 2nd, and "2" is the 3rd.

Find where it says

"ppr": 1

Change this to be:

"ppr": 0.5

This will set it to 0.5 pulse per revolutions.

Save the configuration file. Load this updated file into the app, and then write it back to the unit.

You should see the change reflected in the RaceCapture dashboard.

Thanks, Let us know if that works for you!

davef_dci · Post by **davef_dci** » Thu Mar 23, 2017 12:08 am

if I put it on 1 it shows 660 at idle, the engine idles at 1300. At the limiter 6500 it shows 2700rom. Everytime I go up it splits the number in half.

Just pointing out that 2700 isn't 1/2 of 6500 right? Might have been a typo but i thought I'd point it out in case you're waiting for a fix that's not going to solve your problem.

-d

bahnstormer · Post by **bahnstormer** » Thu Mar 23, 2017 12:32 pm

Brent, thank you. I will give that a shot.

Dave, I agree. Some where I recall reading about the "slow", "medium", and "fast" response and how it changes accuracy at different RPM. That is what im blaming the difference there on.

I will update and report back,

Thank you.

J

Post by **brentp** » Thu Mar 23, 2017 3:07 pm

The slow / medium / fast changes the clock speed of the timer which affects how fast or slow of a pulse it can read. You can select the option that works best for your needs. Usually Medium is what people use for measuring engine RPM.

Let us know what you find out!