Announcement

Collapse
No announcement yet.

Odometer output and timers

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Odometer output and timers

    I have an odometer happily ticking away based on time and speed. The time interval is based on the global logic setting. If I set it to a different timer (Output) in configurator, it doesn't run. If I change the local Logic timer setting it still runs at the global setting. Can one function be set to a different timer?

    What logic will pulse an output as each whole 0.1 mile passes to trip my separate non volatile odometer module? Multiply by 10 and some sort of integer function?
    Attached Files

  • #2
    Originally posted by ACCLR8N View Post
    I have an odometer happily ticking away based on time and speed. The time interval is based on the global logic setting. If I set it to a different timer (Output) in configurator, it doesn't run. If I change the local Logic timer setting it still runs at the global setting. Can one function be set to a different timer?

    What logic will pulse an output as each whole 0.1 mile passes to trip my separate non volatile odometer module? Multiply by 10 and some sort of integer function?
    There are now (as of about 6 months ago I believe) only 3 timers: "io", "logic", and "gui". So you can run the functions on any of those three.

    How are you getting the odometer input? Are you doing this in MDX, or are you reading an input?
    Fusion Brain Version 6 Released!
    1.9in x 2.9in -- 47mm x 73mm
    30 Digital Outputs -- Directly drive a relay
    15 Analogue Inputs -- Read sensors like temperature, light, distance, acceleration, and more
    Buy now in the MP3Car.com Store

    Comment


    • #3
      No special timer for one logic function? I can live with that I suppose. I don't understand why it won't run on any other timer or what that timer pop-up window is supposed to do, but I don't need to.

      The odometer input is one of your frequency to voltage boards hooked up to my car's VSS. The function above assumes constant speed for the duration of the logic timer: 65ms. I calculated an error of +8% during hard acclr8n at 500ms. No error at steady cruise. I deemed well within the OEM allowable 12%.

      ...anyway, I got my T45A2 LCD Module for Christmas. Simple counter with 10 year non volatile memory. One channel permanent, the other resettable. One lead pulse for trip, hold for trip reset easy enough for MDX and a Fusion Brain output. The counter input lead needs a pulse every 0.1 of whatever you are counting. Miles in my case. I'm stuck on what logic evaluates the output above to decide a whole tenth has passed by to trigger a Fusion Brain output pulse.

      Comment


      • #4
        Solution

        This works: Since the odometer function above re-starts at zero every time MDX launches, I start a variable at 0.1. If the odometer is equal or greater than the new variable, output on and d+0.1 to the evaluation variable, else output off. Upping the "on" priority corrected the occasional skipped pulse.

        I was able to do this in configurator.
        Attached Files

        Comment

        Working...
        X