AL Priority - What Have I Been Hit By?

[Mirage]

Another cool feature for those of you that are not familiar is the Settings & Use Statistics generation.

To Get the Stats:


Connect USB flash drive to the USB port in AL Control Box, or in USB extension cable,
Enter Yellow Menu by long press of MENU button,
Press NEXT 7 times then press ENTER (you will enter Service Code sub-menu and LED will turn white),
Now Press NEXT 2 times then press ENTER and wait for sound sequence to finish,
Again Press NEXT 2 times then press ENTER and wait for sound sequence to finish,
Once more press NEXT 2 times then press ENTER.
AL system will store your present settings and use statistics to USB flash drive by creating a file named Setup.alp. If file storing was successful the system will alert you with a short blue LED light. The AL system will exit yellow menu after a few seconds of being inactive.
Connect this USB flash drive to your computer.
Click Browse and find the Setup.alp file on your USB memory drive and press Upload.



You will get results like this:



Device information


Serial number
XXXXXXX


Firmware version
4.2.2


Region
North America


Power Cycles
37


Control Set FW version
2.4


Control Set HW version
1


Settings


Audio Volume
5


Parking detection range
3


Silent Power-up
Disabled


Dark Mode
Enabled


Parking enabled sensors
Rear1, Rear2


GPS Antenna
Enabled


PDC Speed Limit
n/a


Working mode
Parking and Laser Interference Defense


Pro mode
Enabled


LID Speed Limit
n/a


Radar Antenna Model
Not Connected


Radar Settings



LID Time
Unlimited – Test purposes



Specific LID settings


Vitronic Poliscan
Speed scanner
Enabled


Unicam Camera
Section speed control
All sensors ON


NJL SCS
Speed-laser
Enabled


Riegl
Speed-laser
Enabled


Trafic Observer
Speed scanner
Enabled


Stalker
Speed-laser
Maximum Power



Alerts by Source Speed-laser


Marksman and UltraLyte
1


Atlanta SpeedLaser Stealth
0


Kustom ProLaser 1
0


Kustom ProLaser & ProLite
4


Redspeed SpeedGuard
0


Riegl
0


Stalker
5


LTI Truspeed
1


Unipar - SL700
0


NJL SCS 101 & 102
0


Jenoptik – Laveg
0


Leivtec XV 2
0


Laser Ally
41



Error Sensitive Lasers


Jenoptik LaserPatrol
0


Jenoptik TraffiPatrol XR
0


ProLaser 2 & Atlanta SpeedLaser
0



Speed Section Control


Camea - IR Camera
0



Speed Scanner


Traffic Observer
0


Vitronic Poliscan
12



Radar


K-band
0


Ka-band
0


X-band
0


POP
0




These are my stats from the testing this weekend. Now the interesting part is the Vitronic Poliscan hits. Hmm.. Not possible in my state so will need to look into this further. As you can see we tested the snot out of the DALA.

[RigToFly01]

May I say that this thread should be "STICKY"

[Holla]

To get into these "settings" is it outlined anyplace for us to look at and do in a manual or the ALP website

[Mirage]

Go here and you can look at the settings:

http://www.alpriorityupdate.com/

Click Setup. You don't have to have a serial number to look at the settings. The other two selections require a valid serial number.

[BestRadarDetectors]

Statistics might have several bugs as the process is being redone to incorporate the full radar integration. When the integration is complete I will do a full write-up.

[Mirage]

Statistics might have several bugs as the process is being redone to incorporate the full radar integration. When the integration is complete I will do a full write-up.

Ok great. Yeah the Poliscan hits were odd. Everything else looks like it is right on the money other than a few of the counts don't appear to be correct. But it correctly identified all the guns we used on Friday.

[winterbrew]

I got a couple of Camea IR section controls appear on launch firmware, but no more problems on 4.2.2. I think one of the 4.2.2 updates was 'improve Poliscan detection, and reduce falsing'

[BestRadarDetectors]

As you can see we tested the snot out of the DALA.

Your AL Priority is still a virgin... Here are my stats:

Device information
Serial number XXXXXXX
Firmware version 4.2.2
Region North America
Power Cycles 96
Control Set FW version 2.4
Control Set HW version 1
Settings
Audio Volume 3
Parking detection range 3
Silent Power-up Disabled
Dark Mode Disabled
Parking enabled sensors Front1, Front2, Front3, Rear1, Rear2
GPS Antenna Enabled
PDC Speed Limit n/a
Working mode Parking and Laser Interference Defense
Pro mode Disabled
LID Speed Limit n/a
Radar Antenna Model STIR+
Radar Settings X, K, Ka
LID Time Unlimited – Test purposes
Specific LID settings
Vitronic Poliscan
Speed scanner Enabled
Unicam Camera
Section speed control All sensors ON
NJL SCS
Speed-laser Enabled
Riegl
Speed-laser Enabled
Trafic Observer
Speed scanner Enabled
Stalker
Speed-laser Maximum Power
Alerts by Source Speed-laser
Marksman and UltraLyte 50
Atlanta SpeedLaser Stealth 2
Kustom ProLaser 1 2
Kustom ProLaser & ProLite 39
Redspeed SpeedGuard 0
Riegl 0
Stalker 156
LTI Truspeed 76
Unipar - SL700 0
NJL SCS 101 & 102 0
Jenoptik – Laveg 0
Leivtec XV 2 0
Laser Ally 240
Error Sensitive Lasers
Jenoptik LaserPatrol 0
Jenoptik TraffiPatrol XR 0
ProLaser 2 & Atlanta SpeedLaser 8
Speed Section Control
Camea - IR Camera 0
Speed Scanner
Traffic Observer 0
Vitronic Poliscan 9
Radar
K-band 0
Ka-band 0
X-band 0
POP 0

[Mirage]

Your AL Priority is still a virgin...

You might want to remove that serial number oh experienced one... LOL. You have to remember mine was in 1 day! So yes still very much a virgin!

[BestRadarDetectors]

You might want to remove that serial number oh experienced one... LOL. You have to remember mine was in 1 day! So yes still very much a virgin!

LOL... I am sure yours will see some more action but my unit has a big head start. I do notice I also have 9 Poliscan's listed so one of the guns is coded to the wrong name and we will have to get that fixed.

[Mirage]

LOL... I am sure yours will see some more action but my unit has a big head start.

I have a feeling you'll keep the lead on this one, but I must say you sure were testing that Stalker. :nightmare:

I can't wait to test some more.

[Mirage]

I do notice I also have 9 Poliscan's listed so one of the guns is coded to the wrong name and we will have to get that fixed.

It's the LTI LR-100. I just shot it again and the Poliscan value increased to 13.

[BestRadarDetectors]

It's the LTI LR-100. I just shot it again and the Poliscan value increased to 13.

Have no doubt we will get this fixed Monday.

[winterbrew]

Sometimes with my laser tester set for Ultralyte (100pps), if I shot my Blinder HP-905 a few times with it, it would eventually announce 'Vitronic Poliscan'

Vitronic PoliscanSpeed = 100 pps.

Probably explains why youre getting IPT on the 100pps UltraLyte if its responding with the Poliscan algo.

[Mirage]

Sometimes with my laser tester set for Ultralyte (100pps), if I shot my Blinder HP-905 a few times with it, it would eventually announce 'Vitronic Poliscan'

Vitronic PoliscanSpeed = 100 pps.

Probably explains why youre getting IPT on the 100pps UltraLyte if its responding with the Poliscan algo.

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.

[RedRocket]

Sometimes with my laser tester set for Ultralyte (100pps), if I shot my Blinder HP-905 a few times with it, it would eventually announce 'Vitronic Poliscan'

Vitronic PoliscanSpeed = 100 pps.

Probably explains why youre getting IPT on the 100pps UltraLyte if its responding with the Poliscan algo.
Excellent observation on your part,wb !
Could very well be the culprit.

[winterbrew]

Here's the data from the manual ;



9.2 LIDAR
Range of measured distances 10 m – 75 m
Measuring frequency 100 Hz
Number of measurements/scans 158
Angular resolution (horizontal) 0.28 °
Horizontal measurement angle 45 °
Horizontal beam spread 6 mrad
Vertical beam spread 19 mrad
Depth resolution 312.5 mm
Pulse duration 15 ns
Pulse width 4.5 m
Resolution A/D-converter 8 bit
Power supply 12 V DC
Laser class 1

We used to think it was VPR, as some YouTube vids with Whistler RD's which display pulse rates, used to show it shifting between about 65 - 100pps over a few seconds.

The reality is that as the lidar beam scans across the road, the RD picks this up as a change in pulse rate.

HTH

[Mirage]

After testing again today it appears if you disable the poliscan it will also disable the alerts for LR-100. So it looks like AL will need to take a look at the two and correctly identify which one is being used as apparently they have different jamming algos even though they are 100pps each.

[RedRocket]

The reality is that as the lidar beam scans across the road, the RD picks this up as a change in pulse rate.

HTH
Oh,so it's not an oscillating back-and-forth sweep then.Sounds more like a multifaceted,rotating mirror it would seem to be.

[winterbrew]

Oh,so it's not an oscillating back-and-forth sweep then.Sounds more like a multifaceted,rotating mirror it would seem to be.

I'm told there's a rotating prism type thing in there :)

Here's some blurb from our local police force ;



The PoliScanspeed camera is designed to concurrently detect, track and enforce multiple
vehicles on single lane and multi-lane roads. It uses 3D scene capture and vehicle tracking
to determine the speed of each vehicle and whether the vehicle is exceeding the set speed
limit.

The PoliScanspeed camera uses a high resolution scanning laser, constantly capturing the
scene within the measurement zone. This enables individual vehicles to be detected and
precisely tracked through the measurement zone.

Our LEO's also use the 100pps Ultralyte's so will take it easy for a a bit. Hopefully the ALP is not trying to use the UL100 algo against the Poliscan :)

[RigToFly01]

Does the ALP have an option to dump date and time of hits? I did some testing with new friends on Monday with a wide range of guns. Driving in today I got hit but saw no car on my side. I am worried when I do the information dump to USB key, today's hit will be lost in Monday's testing. Any way to avoid this until we get the iphone app?

[BestRadarDetectors]

Does the ALP have an option to dump date and time of hits? I did some testing with new friends on Monday with a wide range of guns. Driving in today I got hit but saw no car on my side. I am worried when I do the information dump to USB key, today's hit will be lost in Monday's testing. Any way to avoid this until we get the iphone app?

ALP only stores the types and total of encounters on the AL CPU. Date and Time is something you will need the App for if its important to you.

[RedRocket]

Does the ALP have an option to dump date and time of hits? I did some testing with new friends on Monday with a wide range of guns. Driving in today I got hit but saw no car on my side. I am worried when I do the information dump to USB key, today's hit will be lost in Monday's testing. Any way to avoid this until we get the iphone app?
You should see these models in your AL-P "Incident Log" history:
LR B,*Laser Ally,TruSpeed,TruSpeed S,SpeedLaser T !

(*LaserAlly = 3 diff. versions we used)


p.s.-any other Type appearing in your list could be the one you got hit by going to work.

[RigToFly01]

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

(*LaserAlly = 3 diff. versions we used)


p.s.-any other Type appearing in your list could be the one you got hit by going to work.


Device information
Serial number XXXXXXX
Firmware version 4.2.2
Region North America
Power Cycles 30
Control Set FW version 2.4
Control Set HW version 1
Settings
Audio Volume 3
Parking detection range 3
Silent Power-up Disabled
Dark Mode Enabled
Parking enabled sensors Front1, Front2, Front3, Rear1, Rear2
GPS Antenna Enabled
PDC Speed Limit n/a
Working mode Parking and Laser Interference Defense
Pro mode Disabled
LID Speed Limit n/a
Radar Antenna Model Not Connected
Radar Settings
LID Time Unlimited – Test purposes
Specific LID settings
Vitronic Poliscan Enabled
Speed scanner
Unicam Camera All sensors ON
Section speed control
NJL SCS Enabled
Speed-laser
Riegl Enabled
Speed-laser
Trafic Observer Enabled
Speed scanner
Stalker Maximum Power
Speed-laser
Alerts by Source Speed-laser
Marksman and UltraLyte 9
Atlanta SpeedLaser Stealth 0
Kustom ProLaser 1 0
Kustom ProLaser & ProLite 0
Redspeed SpeedGuard 0
Riegl 0
Stalker 4
LTI Truspeed 2
Unipar - SL700 0
NJL SCS 101 & 102 0
Jenoptik – Laveg 0
Leivtec XV 2 0
Laser Ally 5
Error Sensitive Lasers
Jenoptik LaserPatrol 0
Jenoptik TraffiPatrol XR 0
ProLaser 2 & Atlanta SpeedLaser 0
Speed Section Control
Camea - IR Camera 0
Speed Scanner
Traffic Observer 0
Vitronic Poliscan 1
Radar
K-band 0
Ka-band 0
X-band 0
POP 0


Maybe I was hit by Vitronic Poliscan? Is that a stationary trap?

[Mirage]

Maybe I was hit by Vitronic Poliscan? Is that a stationary trap?

It is a stationary trap. I think Maryland has them so they are somewhat in your area. This is also the one that was showing up on my stats with a count of 13 and I know for sure they are not in my state. I think at the moment we believe this is a bug on the AL stats, but won't know for sure until the next firmware release.

[thesilverbullet]

very nice to pull the history - escort could take a lessen here...

[BestRadarDetectors]

It is a stationary trap. I think Maryland has them so they are somewhat in your area. This is also the one that was showing up on my stats with a count of 13 and I know for sure they are not in my state. I think at the moment we believe this is a bug on the AL stats, but won't know for sure until the next firmware release.

Mirage,

Have you pulled stats and checked it again since the firmware update to see if your history still reflected the Poliscan?

[Mirage]

I have not, but will tonight when I get home. Do the stats get reset with new firmware update?

[BestRadarDetectors]

I have not, but will tonight when I get home. Do the stats get reset with new firmware update?

No, The stats do not get reset with updates.

[nano]

I got a couple of Camea IR section controls appear on launch firmware, but no more problems on 4.2.2. I think one of the 4.2.2 updates was 'improve Poliscan detection, and reduce falsing'
Volvo laser cruise control triggered my rear sensor with the launch firmware. After deactivating the Camea-option it was gone. BTW this type of speed control is only used in the czech republic (Europe), so you can safely disable it.

[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!

347

[RigToFly01]

396

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]

396

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?

416

[hitechrr]

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

[radargeek]

Is there a way to clear/reset/zero the gun statistics, after downloading them?

[BestRadarDetectors]

Is there a way to clear/reset/zero the gun statistics, after downloading them?

At this time there is no way to reset statistics.

[shanetrainST]

Never Heard of that one before, happened when I was doing some testing with my Stalker

970

[KrpA]

Czech automatic section speed camera. ALP can detect IR reflector of that system even during the day.

http://www.camea.cz/en/traffic-applications/enforcement-systems/section-speed-control-2/

Where did you buy your unit? I think that there is no CAMEA systems in Australia.

[shanetrainST]

Czech automatic section speed camera. ALP can detect IR reflector of that system even during the day.

http://www.camea.cz/en/traffic-applications/enforcement-systems/section-speed-control-2/

Where did you buy your unit? I think that there is no CAMEA systems in Australia.

Thanks for that
This was all under test conditions with my own gun, on a road with no other Lidars around.
It happened during one of my runs
Also got a few long range PT's that my ultralyte never found

[KrpA]

It's possible that ALP caught few pulses of your Stalker while you didn't aim the car and that caused CAMEA alarm. After that it switched to Stalker.
It's weird only because CAMEA should be disabled in that region (that's the reason why I asked you where did you buy your unit.

PT's on Ultralyte? That sounds weird. How far? Ultralyte 100 or 125 pps?

[shanetrainST]

It's possible that ALP caught few pulses of your Stalker while you didn't aim the car and that caused CAMEA alarm. After that it switched to Stalker.
It's weird only because CAMEA should be disabled in that region (that's the reason why I asked you where did you buy your unit.

PT's on Ultralyte? That sounds weird. How far? Ultralyte 100 or 125 pps?

I run North American setting for my test runs, The Australian setup file is lacking the unlimited mode

Stalker did all the PT's, But I have both 100 & 125 model Ultralyte Kph&Mph and never really had to many PT's with them only super close.

[KrpA]

But there is 9 second limit on Australian version even if you use North American settings.

[deano]

I also use another country while testing its a shame that Australia chose the 9 second limit I have had friends turn to LI because of this even could get them a good deal but they decide to move away

[shanetrainST]

But there is 9 second limit on Australian version even if you use North American settings.

Still rocking older firmware on my second cpu

[BestRadarDetectors]

What version stalker did you get. I know it was probably a used one from the usual sources. Was it an old 3.5?

[shanetrainST]

What version stalker did you get. I know it was probably a used one from the usual sources. Was it an old 3.5?

A5.1 SUP Firmware

[BestRadarDetectors]

A5.1 SUP Firmware

Any idea when it was last certified? I hate to go crazy trying to find an issue with a gun that might have been certified years ago and might be out of spec?

[shanetrainST]

Any idea when it was last certified? I hate to go crazy trying to find an issue with a gun that might have been certified years ago and might be out of spec?

I haven't the slightest clue, I know it was almost brand new when I received it, apparently it was his backup lidar that he rarely used. Manufactured march 2008.

After receiving some good advice from KrpA, possibly turning the Maximum setting on will fix the PT's.

I still sent AL a recording as the Camea thing has me wondering?
971

[winterbrew]

ST - Isn't yours an Aussie version, which is actually the EU version in km/h if that makes any difference ?

Camea falses - I had two in my logs on retail release firmware, but I also got two a couple of weeks ago on 4.3.4 firmware just after dark, but put that down to a motorbike headlight that was behind me. As KrpA says, they shouldn't really be enabled on Aussie regional firmware.

[shanetrainST]

ST - Isn't yours an Aussie version, which is actually the EU version in km/h if that makes any difference ?

Camea falses - I had two in my logs on retail release firmware, but I also got two a couple of weeks ago on 4.3.4 firmware just after dark, but put that down to a motorbike headlight that was behind me. As KrpA says, they shouldn't really be enabled on Aussie regional firmware.

Yep, its the Australian version.
In all my time driving around with the ALP, I have never had a Camea alarm. But I was on US for testing when it happened

Yea, if we have Camea in the Australian firmware, it has to go as I have never heard of it

[winterbrew]

After receiving some good advice from KrpA, possibly turning the Maximum setting on will fix the PT's.

Mines A 5.6 SUP firmware (USA gun), and I've always had my ALP Stalker power set to max as they are not used in WA. My A 5.6 SUP has never thrown an E04 jam code in testing with my ALP set to max

[Qui-Gon]

Not sure if this has been answered or not, but after pulling the stats from the CPU, do the statistics reset? Just curious...

[radargeek]

Not sure if this has been answered or not, but after pulling the stats from the CPU, do the statistics reset? Just curious...AFAIK they don't reset, and there presently is no way to reset them. Hopefully a future update will add this. It would be nice to be able to clear the statistics, especially after a testing session.

So, when you pull stats, save them on your computer so you can compare them to see what "new" guns you were hit with.

Chronological logging would be nice to have. Presently only the iPhone app with the bluetooth adapter can do this.

[indytoatl]

I was able to follow the instruction and created the setup.alp file on my flash drive. I plugged the flash drive in my computer and went to http://www.alpriorityupdate.com/Setup and click the browse button, found the file file and clicked upload.
I can see my current configuration settings but nothing about any stats. What am I missing here?

[dukes]

I was able to follow the instruction and created the setup.alp file on my flash drive. I plugged the flash drive in my computer and went to http://www.alpriorityupdate.com/Setup and click the browse button, found the file file and clicked upload.
I can see my current configuration settings but nothing about any stats. What am I missing here?

Go here instead of setup.

http://www.alpriorityupdate.com/Statistics

[indytoatl]

I rode past a leo today and got a laser alert on Vitronic Poliscan but I didn't see any police activity inside or outside the car. Any idea what other device would trigger this frequency?
I also got hit by Georgia State Patrol with the DragonEye near Conyers, GA on i20 east.


Device information

Serial number XXXXXXX
Firmware version 4.3.6
Region North America
Power Cycles 334
Control Set FW version 3.2
Control Set HW version 1
Connected sensors

Connected sensors when manually memorized Front2, Rear1, Rear2
Connected sensor (actual) Front2, Rear1, Rear2
Settings

Audio Volume 5
Parking detection range 3
Silent Power-up Disabled
Dark Mode Dimmed
Parking enabled sensors Front1, Front2, Front3, Rear1, Rear2
GPS Antenna None
PDC Speed Limit NONE
Working mode Parking and Laser Interference Defense
Pro mode Disabled
LID Speed Limit NONE
Radar Antenna Model Not Connected
Radar Settings
LID Time Unlimited – Test purposes
Specific LID settings

Vitronic Poliscan
Speed scanner Enabled
Unicam Camera
Section speed control All sensors ON
NJL SCS
Speed-laser Enabled
Riegl
Speed-laser Enabled
Trafic Observer
Speed scanner Enabled
Stalker
Speed-laser Maximum Power
Alerts by Source Speed-laser

Marksman and UltraLyte 0
Atlanta SpeedLaser Stealth 0
Kustom ProLaser 1 0
Kustom ProLaser & ProLite 2
Redspeed SpeedGuard 0
Riegl 0
Stalker 0
LTI Truspeed 0
Unipar - SL700 0
NJL SCS 101 & 102 0
Jenoptik – Laveg 0
Leivtec XV 2&3 0
Laser Ally 1
Error Sensitive Lasers

Jenoptik LaserPatrol 0
Jenoptik TraffiPatrol XR 0
ProLaser 2 & Atlanta SpeedLaser 0
Speed Section Control

Camea - IR Camera 0
Speed Scanner

Traffic Observer 0
Vitronic Poliscan 1
Radar

K-band 0
Ka-band 0
X-band 0
POP 0
MultaRadar CD 0
Print

[64pvolvo1800]

Infinity does it to mine

[indytoatl]

Is there a way to tell from your iPhone if you were hit with front or rear laser other than the real-time display?

[indytoatl]

Thanks, I disabled the poliscan.

[BestRadarDetectors]

Is there a way to tell from your iPhone if you were hit with front or rear laser other than the real-time display?

It will display it on the screen and will verbally tell you if its a front or rear hit in the app. If you are using the included remote LED it will also illuminate different colors during an alert if its from the front or rear.

[indytoatl]

It will display it on the screen and will verbally tell you if its a front or rear hit in the app. If you are using the included remote LED it will also illuminate different colors during an alert if its from the front or rear.

It would be nice to add the direction feature to the history. I would like to know which direction the alert came from if I only have time to press the parking button and slow down. It's an intense moment even for a seasoned driver ;-)

[Vortex]

Thanks for posting this. It seems complicated at first, but once you do it a few times, it's not so big a deal.

I can get the ALP to save the setup.alp file to my USB drive and it gives me the successful blue blink, but when I upload the file to the website, it tells me "Uploaded file is not valid" which is bizarre.

Looking at the logs you posted, I wish there was a timestamp based log you could create saying at this date and time you were shot with this gun, at that date and time you were shot with that gun, etc.

The way things currently are with a simple counter, once you start using it for a while, unless you remember where you left off, you may not know which gun's counter got ticked up by 1.

I'm definitely looking forward to the Hifi module to give me the verbal announcements like my 905's, and I hope there's a short alert audio package available which will announce the gun quickly.

[BestRadarDetectors]

Thanks for posting this. It seems complicated at first, but once you do it a few times, it's not so big a deal.

I can get the ALP to save the setup.alp file to my USB drive and it gives me the successful blue blink, but when I upload the file to the website, it tells me "Uploaded file is not valid" which is bizarre.

Looking at the logs you posted, I wish there was a timestamp based log you could create saying at this date and time you were shot with this gun, at that date and time you were shot with that gun, etc.

The way things currently are with a simple counter, once you start using it for a while, unless you remember where you left off, you may not know which gun's counter got ticked up by 1.

I'm definitely looking forward to the Hifi module to give me the verbal announcements like my 905's, and I hope there's a short alert audio package available which will announce the gun quickly.

With using the latest versions of ALP Connect if you are hit the announcement will continue to play the alert message in full even if the threat stops. I expect the HiFi module will do the same.
I have also requested in the future that they add a Last 5 Alerts to the ALP Stats so you will see the last 5 active alerts in order and you will still having the running totals as well.

[Vortex]

With using the latest versions of ALP Connect if you are hit the announcement will continue to play the alert message in full even if the threat stops. I expect the HiFi module will do the same.
I have also requested in the future that they add a Last 5 Alerts to the ALP Stats so you will see the last 5 active alerts in order and you will still having the running totals as well.

Oh nice, fantastic on both accounts. :)

[licwid]

Finally got painted tonight, but I have now realized I didn't have a "baseline" of stats so I'm not sure what they were using :(
Hope the last 5 feature comes soon

[indytoatl]

I was tagged by a leo yesterday and my iPhone showed a frontal alert for ProLaser2. When I looked at the stats it showed up under, "Error Sensitive Laser". What does that mean?

[BestRadarDetectors]

I was tagged by a leo yesterday and my iPhone showed a frontal alert for ProLaser2. When I looked at the stats it showed up under, "Error Sensitive Laser". What does that mean?
Error Sensitive Laser are guns that can display jam codes.

[Holla]

I was tagged by a leo yesterday and my iPhone showed a frontal alert for ProLaser2. When I looked at the stats it showed up under, "Error Sensitive Laser". What does that mean?

Mine said that too until I was told to go into settings and change the Voice Pack setting from simple to Detailed!!

[BestRadarDetectors]

Mine said that too until I was told to go into settings and change the Voice Pack setting from simple to Detailed!!
Yes... Detailed will show the gun names and not just the type.

[Radarrob]

I was tagged by a leo yesterday and my iPhone showed a frontal alert for ProLaser2. When I looked at the stats it showed up under, "Error Sensitive Laser". What does that mean?Sounds like you got shot
with a laser atlanta gun.Prolaser 2 don't throw jam codes only the laser atlanta's.PL2 is the same pulse rate as the laser atlanta's.

[BestRadarDetectors]

Disregard previous post. I found out where to upload it on alpupdate

So it says ive been hit 5 times time?

Its only gone off 3 times for me... why is that??



Probably hit you consecutively on one or more of these. It will count the trigger pulls so Marksman and UltraLyte 3 could have been just one hit but 3 pulls.

[tawwwd]

I see 3 on marksman ultrlyte and 2 on laser ally?

Firmware version 4.4.2
Region North America
Power Cycles 31
Control Set FW version 3.3
Control Set HW version 1
Connected sensors
Connected sensors when manually memorized
Connected sensor (actual) Front1, Front2, Front3, Rear1, Rear2
Settings
Audio Volume 5
Parking detection range 3
Silent Power-up Disabled
Dark Mode Dark
Parking enabled sensors Front1, Front2, Front3, Rear1, Rear2
GPS Antenna None
PDC Speed Limit NONE
Working mode Parking and Laser Interference Defense
Pro mode Disabled
LID Speed Limit NONE
Radar Antenna Model Not Connected
Radar Settings
LID Time 4 seconds
Specific LID settings
Vitronic Poliscan
Speed scanner Enabled
Unicam Camera
Section speed control All sensors ON
NJL SCS
Speed-laser Enabled
Riegl
Speed-laser Enabled
Trafic Observer
Speed scanner Enabled
Stalker
Speed-laser Maximum Power
Alerts by Source Speed-laser
Marksman and UltraLyte 3
Atlanta SpeedLaser Stealth 0
Kustom ProLaser 1 0
Kustom ProLaser & ProLite 0
Redspeed SpeedGuard 0
Riegl 0
Stalker 0
LTI Truspeed 0
Unipar - SL700 0
NJL SCS 101 & 102 0
Jenoptik – Laveg 0
Leivtec XV 2&3 0
Laser Ally 2
Error Sensitive Lasers
Jenoptik LaserPatrol 0
Jenoptik TraffiPatrol XR 0
ProLaser 2 & Atlanta SpeedLaser 0
Speed Section Control
Camea - IR Camera 0
Speed Scanner
Traffic Observer 0
Vitronic Poliscan 0
Radar
K-band 0
Ka-band 0
X-band 0
POP 0
MultaRadar CD 0

[tawwwd]

Probably hit you consecutively on one or more of these. It will count the trigger pulls so Marksman and UltraLyte 3 could have been just one hit but 3 pulls.

Ah that could make sense then!
Im new to this whole jammer thing haha

[BestRadarDetectors]

Ah that could make sense then!
Im new to this whole jammer thing haha

You might have had one long alert but if they released the trigger and pulled it again the second pull would register as another hit but it might have been the same encounter so you did not realize it.

[tawwwd]

You might have had one long alert but if they released the trigger and pulled it again the second pull would register as another hit but it might have been the same encounter so you did not realize it.

Could be the case. All 3 alerts seemed to go the full 4 sec JTK then blinked green.

I got one of the overpass hits on camera.


http://vid1052.photobucket.com/albums/s455/schiss/20141213_131700_zpsbuiz9vfh.mp4

[oddpedestrian]

Could be the case. All 3 alerts seemed to go the full 4 sec JTK then blinked green.

I got one of the overpass hits on camera.


http://vid1052.photobucket.com/albums/s455/schiss/20141213_131700_zpsbuiz9vfh.mp4
I can't see this could you upload to YouTube?

[tawwwd]

I can't see this could you upload to YouTube?

Sure

https://www.youtube.com/watch?v=1qpgGVXD644&feature=youtu.be

[hussein]

Sure

https://www.youtube.com/watch?v=1qpgGVXD644&feature=youtu.be

lol, OT, but when I saw the Youtube preview image, I was like hmm that looks like AB!

[tawwwd]

lol, OT, but when I saw the Youtube preview image, I was like hmm that looks like AB!

Haha!
How could you tell?! :eyebrows:

I think this place is the speed enforcement capital of the universe! I believe these vans are the dragoncam laser ally? I really wish there was a way to confirm a jam from our end!

[Qui-Gon]

Haha!
How could you tell?! :eyebrows:

I think this place is the speed enforcement capital of the universe! I believe these vans are the dragoncam laser ally? I really wish there was a way to confirm a jam from our end!

Your confirmation is the BEEEEEEEEEEEEEEP you hear! :)

[hussein]

Haha!
How could you tell?! :eyebrows:

I think this place is the speed enforcement capital of the universe! I believe these vans are the dragoncam laser ally? I really wish there was a way to confirm a jam from our end!

If your sensors are the same height, depth, level with the ground, 18" apart, you should be good. No tickets is a good delayed indicator, heh.

[JStump2490]

lol, OT, but when I saw the Youtube preview image, I was like hmm that looks like AB!

Looks like I might be upgrading to rear heads soon after seeing this

[tawwwd]

If your sensors are the same height, depth, level with the ground, 18" apart, you should be good. No tickets is a good delayed indicator, heh.
theyre perfectly straight and I have coverage of my plate and all the chrome on my bumpers.

They do point up just a little because of the rake on my truck (back end site 3/4" higher than the front). I was going to adjust it and make it flat but I figured that might be better because of the angle on the overpass shots. Seems to work so far.

[modsl55amg]

Your AL Priority is still a virgin... Here are my stats:

Device information
Serial number XXXXXXX
Firmware version 4.2.2
Region North America
Power Cycles 96
Control Set FW version 2.4
Control Set HW version 1
Settings
Audio Volume 3
Parking detection range 3
Silent Power-up Disabled
Dark Mode Disabled
Parking enabled sensors Front1, Front2, Front3, Rear1, Rear2
GPS Antenna Enabled
PDC Speed Limit n/a
Working mode Parking and Laser Interference Defense
Pro mode Disabled
LID Speed Limit n/a
Radar Antenna Model STIR+
Radar Settings X, K, Ka
LID Time Unlimited – Test purposes
Specific LID settings
Vitronic Poliscan
Speed scanner Enabled
Unicam Camera
Section speed control All sensors ON
NJL SCS
Speed-laser Enabled
Riegl
Speed-laser Enabled
Trafic Observer
Speed scanner Enabled
Stalker
Speed-laser Maximum Power
Alerts by Source Speed-laser
Marksman and UltraLyte 50
Atlanta SpeedLaser Stealth 2
Kustom ProLaser 1 2
Kustom ProLaser & ProLite 39
Redspeed SpeedGuard 0
Riegl 0
Stalker 156
LTI Truspeed 76
Unipar - SL700 0
NJL SCS 101 & 102 0
Jenoptik – Laveg 0
Leivtec XV 2 0
Laser Ally 240
Error Sensitive Lasers
Jenoptik LaserPatrol 0
Jenoptik TraffiPatrol XR 0
ProLaser 2 & Atlanta SpeedLaser 8
Speed Section Control
Camea - IR Camera 0
Speed Scanner
Traffic Observer 0
Vitronic Poliscan 9
Radar
K-band 0
Ka-band 0
X-band 0
POP 0

Tom (BRD),

Regarding the "Print Settings & Use Statistics" feature of the ALP system:

1. Is the firmware upgrade for this feature supposed to be installed into the ALP system when the other files are installed via a Flash Drive, e.g. (Uxxxxxxx.bin, UCSTHIFI.BIN, VOICEPAKCK.ALP, setup.alp), in order for the system to collect/store data for later retrieval?

2. Or is the "Print Settings & Use Statistics" firmware supposed to be loaded onto a Flash Drive, then inserted into the flash drive port EACH time the owner wants to retrieve information from the system that the "Settings & Use Statistics" feature provides, and writes onto the flash drive while it is inserted?

Thank you in advance for your advice.

[BestRadarDetectors]

Statistics will only work after you install a firmware update since it will not work with the firmware shipped on the unit. Once you update the firmware you should have no issues pulling a report.

[modsl55amg]

Statistics will only work after you install a firmware update since it will not work with the firmware shipped on the unit. Once you update the firmware you should have no issues pulling a report.

OK, Thanks Tom/BRD.

[RadarNinja]

I would like to add these statistics and echo previous posts for needed statistics (in order of importance) for export:

1) Date/time of hit.
2) Sensor that was (initially) hit or at least front/rear designation.
3) Latitude / longitude (GPS) at hit.
4) Duration of hit.
5) Vehicle speed during hit (if it could be disabled).