AL Priority - What Have I Been Hit By?

[nano]

I'm not sure the Poliscan is 100pps or the AL would have had no issue with the LR-100. I'm no expert on the poliscan, but I think it's VPR regardless since it's not used in my area I am going to disable it and test this morning against the LR-100 to see if your assumption is correct. It would make sense if the AL was detecting poliscan and sending the wrong jamming signal that we would get IPT. I am confident that AL will have this all worked out tomorrow and I'm glad we were able to help them make the device that much better. I'll let you guys know what I find.

The problem with the pulsrate of 100pps is that there three different laser guns which are using this frequency. First there is the LTI Ultralyte with 100pps, the Jenoptik LaserPatrol and Vitronic PoliscanSpeed.

Since the LaserPatrol is very sensitive to jam codes, it was necessary to set the priority to this gun. A LJ only processes the frequency of the incoming signal, so it is not possible to differentiate, between those guns. Measuring the pulse length is not possible (~10 ns).

The VPS is really a pain in the ass. Detecting is quite difficult, because of the working principle. A laserdiode is sending 15800 pulses per second to a rotating mirror, which splits the pulses to a measurement area of 45°. In theory the incoming signal should be 100 pps, but the reality looks different. The problem is the rotating mirror which isn't rotating with a constant speed. This leads to a "variable" plusrate. The interesting thing is, that for a valid measurement a constant angular velocity system is not necessary, because only the time of flight (from sending the pulse out, to receive it back) is important.
When measuring the laser pulses of the VPS with a high accurate meter you can see that the frequency is jumping on a basis of 100 Hz. Because of this, it is very hard for a LJ to recognize the VPS with a 100% and not falsing to a different signal.
The AL G9 sometimes had problems detecting the VPS, which leads sometimes to a interrupting alarm. In this case, the VPS wasn't recognised correctly and no jamming signal was sent. The much fast processor(s) of the ALP are very helpful in terms of VPS.
Jamming the VPS is another story.

[RedRocket]

^ - Very interesting details concerning the Poliscan.
How much does the frequency "wobble" (vary) +/- around 100pps ?

[RedRocket]

You should see these models in your AL-P "Incident Log" history:
LR B,*Laser Ally,TruSpeed,TruSpeed S,SpeedLaser T !

@RigToFly01 - hmmm, I noticed in your "Alerts by Source Speed-Laser" list(see post #24) that while you were targeted w/ an Atlanta SpeedLaser lidar there is no showing of it in your list !

p.s. - It was not in STEALTH mode,btw.As there is only 1 listing for Laser Atlanta maybe that's why...then again shouldn't there also be a 2nd listing for NORMAL mode ?

[JohnBoy]

Having the history right in the app is pretty sweet!

[RigToFly01]

On my Daily commute today, This is what I saw when I looked down to check on the app. I was in heavy traffic when this happened. Hence the low speed.

#1 Is this a true alert or still a bug?
#2 Is there a way to with the current app that it can show GPS of this encounter?
#3 I still have the LED light connected to the system, I know for a fact that the LED did not go off for this alert, Is that correct or is it a bug?

Thanks

[BestRadarDetectors]

On my Daily commute today, This is what I saw when I looked down to check on the app. I was in heavy traffic when this happened. Hence the low speed.

#1 Is this a true alert or still a bug?
#2 Is there a way to with the current app that it can show GPS of this encounter?
#3 I still have the LED light connected to the system, I know for a fact that the LED did not go off for this alert, Is that correct or is it a bug?

Thanks

1. The LR100 bug was corrected if you are running the current firmware.
2. Great idea and maybe in a future release we can capture GPS cordinates
3. If the LED did not go off it might have been a false alert from a laser guidance system mapped incorrectly to the wrong alert in the app. You dont have a cam by any chance do you?

[RigToFly01]

3. If the LED did not go off it might have been a false alert from a laser guidance system mapped incorrectly to the wrong alert in the app. You dont have a cam by any chance do you?

I do not yet. It's my next big investment. I started a thread in the other section asking for suggestions. I roughly know were I was when the alert happened. I drive this exact route everyday and never got this alert before I installed the rear sensors. The next time I drive in will be on the 1st. I will lookout in the area and see if I get it again.

Can we also add to the History that it will state if it was the front sensors or the rear sensors when you have a quad setup?

[BestRadarDetectors]

I do not yet. It's my next big investment. I started a thread in the other section asking for suggestions. I roughly know were I was when the alert happened. I drive this exact route everyday and never got this alert before I installed the rear sensors. The next time I drive in will be on the 1st. I will lookout in the area and see if I get it again.

Can we also add to the History that it will state if it was the front sensors or the rear sensors when you have a quad setup?

I will ask but wont get an answer for a few days. AntiLaser is on holiday break and I promised not to bother them unless something was urgent.

[RigToFly01]

3. If the LED did not go off it might have been a false alert from a laser guidance system mapped incorrectly to the wrong alert in the app. You dont have a cam by any chance do you?

So, on today's commute it happened again. No LED alert. This happened in a completely different location than the other day. At least 20 miles from the other false alert. This is looking more and more like a bug. Tom, is there a way for me to upload the freq of this alert so it can get fixed?

[hitechrr]

I had a false from a IR light on a camera at a gated community.