Hi! I have been using and loving the ALPriority for quite a while now. However, I upgraded to the latest firmware ( version is 5.1.1/6.1 released 2015-04-24) and the self test always fails now. I cannot start up the ALP and it gets stuck in a mode where it is blinking red and beeps twice repeatedly on start-up. This used to happen only when I was right in front of a wall. Now it always happens. Can ALP please release a patch to fix this self test update? Thank you!
Do a full hard reset and then try to reinstall the latest firmware/control set update.
If that fails, contact your distributer. Eg BRD.
Beeping a repetitious 2 solid beeps? The new self test is supposed to catch failures and prevent you from driving and thinking you are protected if there is an issue. A continuous solid double beep when you start your ALP will only occur if your sensors are all blocked or you have a sensor failure, While in this state just disconnect one sensor at a time until it stops and you will see which sensor is causing the sensor check to fail. We expected with this firmware we would find some failures which is a good thing to catch problems and not ignore them.
Hello and thanks for the responses. I have determined what the problem is. The problem is not that I have faulty sensors or cables. I disconnected/connected and checked many times. After many experiments, I have determined that the problem is that the self test seems to require about 50-100 meters of clear space in order to turn on now! The self test before this latest 5.1.1/6.1 firmware only required about 10-20 meters, which was sensible. I know the intentions are good, but this does not work well in practice at all. I live in an urban area with a lot of traffic, so there are not many stretches of clear road that allow me to turn on the ALP. My friend is also having the same problem after upgrading to the latest firmware. We both love the product, but we can barely even use it now. I am only able to pass the self check less than half the time! Please revert the self test back to a practical distance so we can use our ALPs. Thank you!
Quote:
Originally Posted by imjammin
There still seems to be something amiss then.
I have updated my system as well, and I don't need anywhere near that amount of space to turn my unit on. Just yesterday at the courthouse with a concrete wall infront of it (2 feet away) it fired up fine. Also yesterday, parking behind a vehicle at my mates house (maybe 3 feet behind it), the unit fired up fine.
1) Do you have them set as parking sensors?
If yes,
2) What distance are they set at for parking sensor alerts?
That was going to also be one of my questions.. I keep my parking sensors on 2 or 3 max. What do you have yours set at?
Quote:
Originally Posted by imjammin
I can start mine up in front of a wall without issues and I am running the new firmware with the extended start up test. You should run a deeper test to ensure you don't have further issues.
https://youtu.be/XAHqBZOUdVk
10-20 meters makes no sense. I park my car in front of my garage door but when I pull up I wait till my parking sensors alert and then back up until they stop. When I start the car the next morning there are no issues. What is the distance you have your parking sensors set at? Try 2 or 3 Max and when you pull in see that they are not alerting to interference when you shut the system off.Quote:
Originally Posted by imjammin
Mine start up fine too in front of a wall. 20-30 meters is like 60-90ft. Doesn't make sense at all.
I have my parking sensors set to disabled. Is this why it will not start up with obstacles?