Thread: Speedcam audio warning - non TTS

Originally Posted by Brown Dog

osiris4isis ...

100 miles? I hope not. You mean 100ft. LOL!

I guess I should of quoted to make the question clearer. In your example in first post, you have
500 - 200 = 300 m - First audio warning
300 - 200 = 100 m - Second audio warning
then I asked where does 300 comes from for the "Second audio warning"

Then you answered
300-200=100 - third warning

So is it second or third warning? And where does 500 comes from
500-200=300 - second warning

If it depends only on warn_distances (which is 700) and approach_beep_distances (which is 200), where are you getting 500 and 300 for the following:
700-200=500 - first warning
500-200=300 - second warning
300-200=100 - third warning

And if 1=192 why have 192 when 1 can be used just fine. The value of 1 have been around for a long time (Amigo); but 192 is mentioned very recently, gotta be a reason why it was introduced.

I think using a different value (700 instead of 500) caused confusion. A clearer answer would have been something like:
the approach_beep_distances is subtracted from the value in warning_distances (based on speed) for each iteration of the warnings
1st warning: 500-200=300
then we use the 1st warning distant to compute the 2nd warning:
300-200=100
we do this until the warning distant is less than the approach_beep_distances.

But I've seen the following example with distances (more than one), posted on other sites
approach_beep_distances="1,25,30,50,100"
which makes the computation like
1st warning: 500-1=499
2nd warning: 499-25=474
3rd warning: 474-30=444
4th warning: 444-50=394
5th warning: 394-100=294
6th warning: 294-100=194
7th warning: 194-100=94
So this would give us a non-linear control of alert distances, right?