AP16+ - PIR False Triggering

[Traveler]

Glad to hear that you found the problem with the PIR's. Going back to your post play delay issue, I don't know your reason for needing just a 3 - 5 second post delay but one way to get that would be to edit your .WAV files and add 3 - 5 seconds of silence to the end of them.

JackMan,

The only reason I even considered a post play delay is because earlier in this thread JonnyMac said, " . . . you should set the POST delay pot when using any kind of PIR or user triggering to prevent immediate re-triggering." I was only trying to follow his instructions. I don't want a post paly delay if its going to have to be 15 seconds. That kind of defeats the purpose of even having a motion sensor. Thanks for the suggestion though.

Traveler

[JackMan]

I don't want a post paly delay if its going to have to be 15 seconds. That kind of defeats the purpose of even having a motion sensor.

That would depend on what your application is. The post play delay is a very handy feature when using the AP-16+ for prop audio, so when someone triggers the PIR it can't be re-triggered until the delay has expired. This prevents the same person from triggering the audio and/or prop multiple times.

[JonnyMac]

I have an idea about the POST delay pot; I'm not saying it will get implemented, I'm just throwing spaghetti to see if it sticks.

What if the first half of the pot range was 0 to 30 seconds, and the last half was 30 seconds to 3 minutes?  This would give fine(r) control over the low end, coarser control -- where you don't really care -- on the high end.

Thoughts?

Now... it will always require tweaking because those aren't super-precise pots (they don't need to be).

[Traveler]

JonnyMac,

That gets my support!

Traveler

[JackMan]

Jon,
    That's not a bad idea but honestly, it's fine like it is. If someone needs less than 15 seconds they probably don't need a post delay at all.

[Traveler]

I just think that the great flexibility a user has to control how the unit is setup can only be a good thing. It certainly doesn't hurt to give people greater choices.

Traveler

[JonnyMac]

An update has been posted that extends the manual start input debouncing and allows slightly-finer resolution of the POST-play pot on the low  end.  Note that in testing, the pot jumped from 0 seconds to 5 seconds; just the nature of the beast (simple pot).

[Traveler]

An update has been posted that extends the manual start input debouncing and allows slightly-finer resolution of the POST-play pot on the low  end.  Note that in testing, the pot jumped from 0 seconds to 5 seconds; just the nature of the beast (simple pot).

Thanks for the update JonnyMac! That helps.

Traveler