ADL Bottom Line Override Won't Disappear

[dbm55]

I set up an "Elapsed Time" timer which starts on the first beacon hit and works properly (start condition= "Beacon Updated and Lap Number = 0"). On the bottom line of my dash I am displaying Minimum Lap Time and Ground Speed. I want to override those values on every beacon hit with the "Elapsed Time" timer and hold it for 10 seconds before reverting back to the original values (Min. Lap Time & Ground Speed). The Problem: It overrides just fine on the first pass by the beacon, but it never reverts back to the original bottom line values. The only theory my crew chief has on this is that it might have something to do with the fact the timer is constantly updating. Note, however, that the override condition is set to "While the following channel is true: Beacon", Not "When any one of the values is updated", which should eliminate the "constantly updating" theory as a problem.

Here is a screen shot of the Display Setup:

ADL Display Setup.gif (51.12 KiB) Viewed 12508 times

And here are the Override Settings:

ADL Override Setup.gif (77.47 KiB) Viewed 12508 times

Does anyone have any idea why this won't work? For the record, I also tried eliminating the Minimum Lap Time (Value 1) on the override and making the Timer the only value without success.

Any help would be much appreciated!

[David Ferguson]

I think the beacon channel is a special case, looking at it in I2, it is 0 until the first beacon is detected, then it becomes some odd non-zero value briefly, then returns to 1. This repeats for each lap . That would explain the behavior you are seeing.

Perhaps you could make a user condition for the start of a lap (ie. Lap Start is true when Lap Number updates, or when Lap Distance is < xxx and Beacon is true). Then use that condition for your override.

[dbm55]

Wow, I hadn't thought of looking at it in I2 -- thanks for the tip! Yes indeed that will cause the problem I was seeing. Interesting though, that in my case it reverts to 56, not 1. Could this have something to do with the Beacon ID?

Great suggestion to set the override condition to a User Condition; I have done that and will test it next time out.

Thanks, again.

[David Ferguson]

My ADL data was made using a digital input beacon channel (BRX style), not BR2 so that's probably the difference.

I had another thought for your user condition -- have about StartLapCondition set to Running Lap Time < 10s (or whatever time you want the overrides to stay active.