View Full Version : Menu button short press function
RadarNinja
08-31-2015, 08:33 PM
It's my understanding that when you are being hit by lidar in defense mode, if you tap / short press either of the control unit buttons, jamming will be killed immediately.
There is a setup option called "Menu button short press function" which has three options: Fog lights, None, and Force parking only. Does changing that option change the kill behavior?
Follow-up questions:
If you kill jamming, does it go back into defense mode automatically?
If you kill jamming and are in expert mode, does it continue to sound while you're being hit?
BestRadarDetectors
08-31-2015, 09:16 PM
Option has no effect during an alert. During an alert either button will kill. If you are using LID settings the jammer will come back online in 60 seconds.
RadarNinja
08-31-2015, 09:19 PM
Thanks!
After kill, does it continue to sound as you're being hit if you're in expert mode?
BestRadarDetectors
08-31-2015, 09:24 PM
Thanks!
After kill, does it continue to sound as you're being hit if you're in expert mode?
Not unless you choose detection after LID on the setup file.
http://images.tapatalk-cdn.com/15/08/31/b9c12cc6448d77b47c034b07c82ce6e2.jpg
RadarNinja
09-01-2015, 12:36 AM
I wanted to see how long they hit so I'll enable DLI & Warm-up. Thanks.
RadarNinja
09-01-2015, 03:02 AM
BRD,
I am not getting consistent results on these settings. The sounds the ALP makes / doesn't make are different depending on the LID time.
Setup for all tests:
Latest CPU and control unit firmware.
North American region.
HiFi German.
Dim mode.
Constant LED.
Pro mode: Enabled.
Menu button short press function setting: None.
After LID timeout setting: DLI & Warm-up.
VoicePack mode: Detailed.
ALP testing FOB set to Marksman / Ultralyte.
Expected behavior upon hit for non-unlimited LID:
Siren and light, then voice and light, then voice when LID turns off, then constant pro mode buzzing until hit stops. Tapping a button at any point mutes all sound.
Actual behavior:
LID time of 4 seconds, I get siren and light, then voice and light, then voice when LID turns off, then constant siren and light until hit stops. Tapping a button on the control unit during constant siren does not mute the siren.
LID time of either 8 or 9 seconds, I get siren and light, then voice and light, then pro mode buzzing sound and light, then at 8 or 9 seconds voice when LID turns off. After that, only light continues to show presence of lidar.
LID time of either 8 or 9 seconds, I get siren and light, then voice and light, then pro mode buzzing sound and light. If control unit button is tapped during buzzing, all sound stops. After that, only light continues to show presence of lidar.
Is there any way to get the expected behavior at all LID times?
BestRadarDetectors
09-01-2015, 09:18 AM
The system is doing what its designed to do. Under no real world situation will you ever be targeted for that long of a period of time. I am not sure what your concerned with? You set your LID to 4-5 seconds and if targeted it will kill and give them a reading after your LID expires and you go on your merry way. If you have DLI & Warm Up on it will still alert you maybe 2 seconds after you kill while they get your speed. Once the trigger is released the 60 second recycle timer gets kicked off. Pro Mode is a testing mode designed for internal use and we allowed members to use it because some liked it. There will not be any changes to Pro-Mode. If you want buzzing use the standard controller, HiFi was designed for users that want the Gun ID's and direction and that is the priority regardless of the mode for the alerts.
RadarNinja
09-02-2015, 12:32 AM
Last week I was targeted for 15+ seconds.
The sounds the ALP makes / doesn't make are different depending on the LID time. Were you able to replicate the issues I described?
Why are they called mute buttons if when timeout is 4 seconds tapping them doesn't silence the unit?
BestRadarDetectors
09-02-2015, 05:20 AM
Last week I was targeted for 15+ seconds.
The sounds the ALP makes / doesn't make are different depending on the LID time. Were you able to replicate the issues I described?
Why are they called mute buttons if when timeout is 4 seconds tapping them doesn't silence the unit?
I can guarantee you that you were not targeted with laser for 15+ seconds unless you were in unlimited jamming and if you jammed that long you deserve a ticket. The beauty of the ALP is its crazy sensitive sensitivity and its ability to detect scatter better than any other product on the market giving you alerts before you are the actual target in many cases. This gives you additional time to slow and kill before they shoot you. The reason the sounds are different in Pro Mode is because its a Professional Testing mode which allows you to hear the signal strength of the incoming signal and the sounds will change based on the signal strength. This mode is not for the average driver but for the enthusiast that wants all the details they can get.
Mute Button during an alert switched over to a KILL button this way you can KILL the defense mode immediately even before your LID settings are up so if you do get scatter and the timer kicks off you can slow and kill before you are in the Kill zone and they would get an instant speed reading with no worry about having to Jam them.
RadarNinja
09-02-2015, 12:45 PM
BRD,
It's possible the LEO was not targeting me specifically, but very unlikely.
More likely is muscle car spotted + car in fast lane + easy pickings due to PSL below 85th percentile + LEO who wanted to meet his quota and move on to real law enforcement = long hit.
Good product, yes. But it does not mute when you press the mute button.
BestRadarDetectors
09-02-2015, 01:21 PM
BRD,
It's possible the LEO was not targeting me specifically, but very unlikely.
More likely is muscle car spotted + car in fast lane + easy pickings due to PSL below 85th percentile + LEO who wanted to meet his quota and move on to real law enforcement = long hit.
Good product, yes. But it does not mute when you press the mute button.
Turn OFF : 'DLI + WARM UP' if you want to mute it and not be in Detection Mode. If you ask to be in Detection Mode after the Timer Expires even after you mute (Kill the alert) it will continue to alert you while it still receives a signal.
radargeek
11-03-2015, 02:18 PM
I just got my ALP the other day and was bench testing it today (haven't installed it in the car yet) and found the same thing. The audio "buzzing" when being shot in Pro Mode only sounds when it's in LID and actually jamming, and then only after the siren (so, about 5 seconds in, at which point you're jamming way too long in the real world). After the timeout or a manual JTK, when it switches to DLI it just plays the siren over and over if I continue shooting at the head. It never plays the "buzzing". Only the LED indicates if you're still being targeted.
During any reasonable JTK time (i.e. under 5 seconds) you'll never hear the buzzing at all, even if you continue to be shot after the JTK. The LED is the only indication that you're being shot.
When reviewing dashcam video it would be nice to be able to hear the buzzing in real time even after JTK. The LED won't necessarily be visible in the video depending on its location and whether it's day or night. While driving I'd be watching the road, not the LED.
I think the buzzing should override the siren when in pro mode, both before and after JTK (maybe a quick siren to get your attention at first, but then switch to the buzzing after 1 second or so).
awj223
11-03-2015, 07:21 PM
I just got my ALP the other day and was bench testing it today (haven't installed it in the car yet) and found the same thing. The audio "buzzing" when being shot in Pro Mode only sounds when it's in LID and actually jamming, and then only after the siren (so, about 5 seconds in, at which point you're jamming way too long in the real world). After the timeout or a manual JTK, when it switches to DLI it just plays the siren over and over if I continue shooting at the head. It never plays the "buzzing". Only the LED indicates if you're still being targeted.
During any reasonable JTK time (i.e. under 5 seconds) you'll never hear the buzzing at all, even if you continue to be shot after the JTK. The LED is the only indication that you're being shot.
When reviewing dashcam video it would be nice to be able to hear the buzzing in real time even after JTK. The LED won't necessarily be visible in the video depending on its location and whether it's day or night. While driving I'd be watching the road, not the LED.
I think the buzzing should override the siren when in pro mode, both before and after JTK (maybe a quick siren to get your attention at first, but then switch to the buzzing after 1 second or so).
Bad idea. There needs to be some indication that you've killed, otherwise it's too easy to make a mistake and think you've killed when you really haven't. If you want to know if you're being shot when reviewing video, then mount your external LED where the dashcam can see it.
'' There needs to be some indication that you've killed ''
The best indication is the screetching ...if you hear it ... you are jamming :eek-new:
https://www.youtube.com/watch?v=KvNgDNZ8EWI&feature=youtu.be
radargeek
11-04-2015, 08:46 AM
Bad idea. There needs to be some indication that you've killed, otherwise it's too easy to make a mistake and think you've killed when you really haven't. If you want to know if you're being shot when reviewing video, then mount your external LED where the dashcam can see it.The "Interference Detection Only" message tells you you've killed, does it not? And even if I were to "miss" I would be running a 3 or 4 second LID timeout anyway.
The only way to make it visible to the dashcam is to mount it in a spot where I wouldn't be able to see it myself (or mount it in the middle of the windshield!) And then it still won't be visible in bright daylight, and at night it's going to light up like a disco. Cop says "I shoot this car and the windshield lit up, and I couldn't get a reading right away... hmmm..."
I may have to experiment with a location like Tman has his though, just to see if it works there (and if I can SEE it there!)
'' Cop says "I shoot this car and the windshield lit up, and I couldn't get a reading right away... hmmm..."
Do not worry ...just tell him it's a cop detector :thumbs2:
awj223
11-04-2015, 12:45 PM
The "Interference Detection Only" message tells you you've killed, does it not? And even if I were to "miss" I would be running a 3 or 4 second LID timeout anyway.
Yes, but I've found that your brain can miss the most obvious things when you're in a panic, and I run unlimited LID. That's why it's best to have continuous indication.
radargeek
11-04-2015, 01:56 PM
Yes, but I've found that your brain can miss the most obvious things when you're in a panic, and I run unlimited LID. That's why it's best to have continuous indication.That's why there should be an immediate and obvious "ping" sound as soon as you either hit the JTK button or the timeout expires, so you get feedback that you killed successfully. Though I think the "Interference Detection Only" message cuts in immediately upon JTK, correct? You'd be listening for it as you hit the button. I'll experiment some more with mine on the bench tonight.
Anyway, when I install my ALP, I'll try the LED in the spot Tman has his, and see how that works. But since I'm in an illegal state it may be obvious at night to a cop when they see a light in the windshield that coincides with their trigger pulls.
Maybe my next invention will be a little box that connects between the CPU and external LED, which emits a sound whenever the LED turns red. It could then give "Pro Mode" audio pulse feedback even after the JTK for videos.
Another way to give feedback for successful JTK would be to switch from a red to a yellow LED for the pulse feedback after JTK.
'' The "Interference Detection Only" message tells you you've killed, does it not? ''.
Rightly . Advice : listen to Wife '' stop the screeetching '' :whoo:
curmudgeon
11-05-2015, 09:17 AM
That's why there should be an immediate and obvious "ping" sound as soon as you either hit the JTK button or the timeout expires, so you get feedback that you killed successfully. Though I think the "Interference Detection Only" message cuts in immediately upon JTK, correct? You'd be listening for it as you hit the button. I'll experiment some more with mine on the bench tonight.
Anyway, when I install my ALP, I'll try the LED in the spot Tman has his, and see how that works. But since I'm in an illegal state it may be obvious at night to a cop when they see a light in the windshield that coincides with their trigger pulls.
Maybe my next invention will be a little box that connects between the CPU and external LED, which emits a sound whenever the LED turns red. It could then give "Pro Mode" audio pulse feedback even after the JTK for videos.
Another way to give feedback for successful JTK would be to switch from a red to a yellow LED for the pulse feedback after JTK.
Note the location of the external led in my install (inspired by Tman) It's right below the inspection and registration stickers. I also have it set to relatively dim. If a LEO is shooting you at night, he'll also be getting glare back from either your headlights or tail lights.
http://radarandlaserforum.com/showthread.php/31-Eastcoast-CounterMeasure-Installer?p=50860&viewfull=1#post50860
radargeek
11-05-2015, 10:02 AM
Note the location of the external led in my install (inspired by Tman) It's right below the inspection and registration stickers. I also have it set to relatively dim. If a LEO is shooting you at night, he'll also be getting glare back from either your headlights or tail lights.
http://radarandlaserforum.com/showthread.php/31-Eastcoast-CounterMeasure-Installer?p=50860&viewfull=1#post50860Dimming won't help since it's only dim while idle. It goes to full brightness during an alert.
It's easy enough to test it since I have a PL3. I can park my car, leave the lights on, walk 100' away and shoot, and see if I can see the LED.
curmudgeon
11-05-2015, 10:10 AM
If you have other electronic devices on the dash (dashcams, gps, etc) they also would be a plausible (to the point of being a more likely) explanation/reason for the LEO if he even noticed light on the dash. My radio (in dash) I have set to blue, and that sometimes reflects at night into rear glass, and then (more faintly) back to front windscreen.
Powered by vBulletin® Version 4.2.5 Copyright © 2025 vBulletin Solutions Inc. All rights reserved.