"Error 2"

[itwasntme]

Last night while sitting in traffic, at a standstill for about 10 min, I received a false Polliscan alert. About 4 min later I received a single "error 2" announcement. I only started using the ALP connect in ernest yesterday for a total of 4hrs drive time. 2hrs continuous driving to my destination with no falses and, no error 2s and 2 hrs continuous driving back home with one error 2 about an hour into my return trip. The error 2 alert was momentary and did not repeat itself. I power cycled the ALP about four times with no error messages. I continued driving approximately 1 hr with no more errors. The Polliscan alert I kind of expected eventually. I have the false rejection for that disabled. The parking sensor feature is disabled.

The error 2 is another story. Is it possible to get an error 2 and not have a problem with one of the sensors or their connections? Is it possible to get a "false" error 2? If I get the error 2 message does that mean a sensor is no longer working or, is it working unless I continue to get more error 2 messages? If a particular sensor has a problem, how would I know which sensor? Has anyone else gotten an error 2 in this manor?

I have been using the the standard control set up till this point for travel without issue. I have used the 1.3 connect version prior to yesterday only to verify a software updates and short testing sessions using a LIDAR. Before my trip yesterday I upgraded to the 1.4 version and lost the GPS speed indication on the application. I think that bugs being worked out though.

[BestRadarDetectors]

Pull a statistics file and it will show memorized positions and actual current positions, If one sensor is missing you will know which sensor triggered the error. If stats shows both configurations are the same it means that all sensors are reporting and working and at one point a sensor did not call home when expected. It can happen but you will need to just keep an eye on it.

[itwasntme]

Thanks for the quick response Tom. I pulled the stats. Everything appears to be as it should. One question though. I notice the parking detection range is at "9" in the stats. I selected the parking detection disabled option. Can both of these settings be in place simultaneously? I went back to the ALP site and reentered all the settings, made sure parking detection was disabled and downloaded it to the ALP. I then pulled another stats file and it still shows parking detection range "9".

[BestRadarDetectors]

Thanks for the quick response Tom. I pulled the stats. Everything appears to be as it should. One question though. I notice the parking detection range is at "9" in the stats. I selected the parking detection disabled option. Can both of these settings be in place simultaneously? I went back to the ALP site and reentered all the settings, made sure parking detection was disabled and downloaded it to the ALP. I then pulled another stats file and it still shows parking detection range "9".

"9" is the Disabled Option....

1 2 3 4 5 6 7 8 Disable (Disable holds the 9th value)

[ballaz]

Sorry to resurrect an old thread but I am also getting the error 2 message multiple times during my commute. There is not error upon 1st power up of the ALP, but during my commute the error occurs several times. I pulled the stats file and it shows dual heads being connected and functioning properly. Any advice on how to rectify this problem? Firmware: 4.5.2, sensors connected to port F1 and F3 because F1 nad F2 was giving me the same error 2 message. All other setting are factory default.

[BestRadarDetectors]

Sorry to resurrect an old thread but I am also getting the error 2 message multiple times during my commute. There is not error upon 1st power up of the ALP, but during my commute the error occurs several times. I pulled the stats file and it shows dual heads being connected and functioning properly. Any advice on how to rectify this problem? Firmware: 4.5.2, sensors connected to port F1 and F3 because F1 nad F2 was giving me the same error 2 message. All other setting are factory default.

You cant run ALP with F1 & F3 as ALP will always be looking for F2. ALP requires F1 & F2 and the use of F3 is only used if all 3 heads are used and when that is the case the center head needs to be connected to the F2 port so that the heads are in order. Put the heads back to F1 & F2, Do a factory reset and if the error occurs again immediately pull a stats file to see which head is tripping the error.

[RedRocket]

Sorry to resurrect an old thread but I am also getting the error 2 message multiple times during my commute. There is not error upon 1st power up of the ALP, but during my commute the error occurs several times. I pulled the stats file and it shows dual heads being connected and functioning properly. Any advice on how to rectify this problem? Firmware: 4.5.2, sensors connected to port F1 and F3 because F1 nad F2 was giving me the same error 2 message. All other setting are factory default.

Since I upgraded to the same f/w & also added Hi-Fi option recently at the same time, I too have encountered this Error 2 w/ the double flashing red LED on Control Set.I've found it to be caused by something in close proximity to 1 or more of the Front 3 Sensors when parked & powering "ON" the Priority after the engine is running.I believe it is just a misinterpreted "nearby object" Parking sensor function.By backing away & entering the roadway,the Error 2 clears itself within a second or two.

My Parking sensor "set point" is at #3 distance.
As you didn't mention it happened at home,but only during your commute...when "in" traffic are you stopping or possible traveling (tail-gating) to closely to other vehicles ?
What is the "set point" of your Parking distance function in the Set-Up table ?

[shanetrainST]

Error 2

Every time I come across someone running LI's my system gives that error. Easy explanation

[BestRadarDetectors]

Is everyone receiving Error 2 running HFi? Hifi does consume a lot more current than the standard controller. If install is not solid with good solid power connections we have seen some strange errors.

[RedRocket]

Is everyone receiving Error 2 running HFi? Hifi does consume a lot more current than the standard controller. If install is not solid with good solid power connections we have seen some strange errors.

Ok,I took another look at my Error 2 situation moments ago.

For me it is definitely caused by the proximity of the Lilac bush near the Front of my car where I normally park in my driveway.With my Parking "set-point" at #3 in the Set-Up table I cannot get any closer than 19-20ft spacing distance to that Lilac bush (& most likely any other object) when powering "ON" the Priority.Besides the double red LED flashing,the HiFi audio reports - "Error 2,lose or disconnected wire cable or defective sensor" !

I also found the Priority WILL NOT power "OFF" (when in Error 2 state) by holding down the power button on the Control Set pad.I had to pull the fuse that is in the +12v feed to the Control Box(CPU).I rolled my car backwards increasing the spacing distance to the bush to ~25ft...re-inserted the fuse & powered "ON" the Priority & it booted-up w/o the Error 2 just as it should.