The page states that the file should be named Setup.alp and you have it without the capitol letter S, dunno if that matters tho.
BRD, is it recommended that ANY time you do a firmware/control set update or change the setup parameters, should you do a factory reset again?
Is it not possible to just hook your computer straight to the CPU and update it as you do the LIs or is it necessary to use a flash drive?
Sorry I am sure I am going to be asking a lot of dumb questions over the next while since I just ordered my ALP and will be doing plenty of research to get ready for it.
You have to use a flash drive. The advantage is that you only have to bring the flash drive out to your car to update, instead of a laptop, USB-Serial cable, etc. Makes updating easier, though not quite as real-time, since you have to do your settings/firmware on a computer, then copy to a flash drive and bring out to the car.
Also, if you use the USB extender that comes with the ALP, and have the port in an accessible spot, you can bury the CPU in the dash and you don't have to pull things apart to get at it to do updates.
Hopefully down the road the Bluetooth app will give you all that capability within the car, no computer or flash drive required.
Ok did the install today 3 heads up front factory reset then setup and control set update two for the back cable to short need two extenders put on order did it all still have not registered it yet but doing that as soon as i post this seems to be up to speed.
Hi guys I just got a A new al system and did not do any of the updates before hand did not know they were required :( and everything is buried in the dash. Im using the bluetooth module and don't have the the wired controller hooked up is there anyway to do the update when connected to bluetooth or do you have to have the controller hooked up ? please advise thanks in advance
If your system is running and operating with Bluetooth module then you had an update at some point and would no longer need the control module. If its brand new your installer should have used the Control Module to install the initial updates. If your system is running with the Bluetooth then you should be fine. Whoever installed the system should have installed the USB Extension cable somewhere convenient for you to load updates.
I installed it myself. i ran the update cable i did not do any updates initially i just plugged everything and powered it up. I don't think its operating as the car does not turn blue and the parking sensors don't even seem to work I downloaded the update to a usb and plugged it in but again it does not appear to have done anything different. when i turn the system on it blinks the led a few times and thats about it my phone connects to the system or at least the bluetooth module but not really anything else ? confused
You need to connect the Control Module and do the updates as described above. Once unit is updated the firmware will now fully recognize the Bluetooth module and you will not need the Control module any longer but for the first update you will need to connect the Control Module.
I installed an ALP system yesterday for a friend and it went smooth. I download the firmware, control software and settings file with his serial number but I did not complete the factory reset step.
I have a question about the factory reset. Is it still required for the latest firmware? It seemed to updated without the reset but I want to be sure.
Factory Reset lets the system know the install is done and that it needs to memorize all the sensor locations. Without doing it if you have a sensor failure you will never know since you never did the reset to tell the ALP your install is set. Once you do the factory reset just reload the settings file and you will be good to go and if you have a sensor error in the future the ALP will let you know and also tell you which sensor is having the issue.
I didn't see this mentioned in the first post or the rest of the thread, but if you have the HiFi module make sure you also download the voice pack file. I just spent about an hour banging my head on why I was only hearing loud beeps. :)
I have followed all "First Steps Required After Installing Your AL Priority System " but I never get reboot - "After your ALP installs the firmware it will reboot and load the Setup file"
I have tired many times and never get to a blue light. There are lots of beeps going on and lights flashing but I don't know if they are correct or not.
The install interface needs work , this is the most difficult radar/laser configuration I've come across .
How do I tell the firmware updated correctly ?
How do I tell what is not correct ?
Contacting the manufacturer and having them point me to here does not give me warm fuzzes (no offense to anyone here , from reading you all seem to have lots of knowledge on the product).
I'm sure that to folks that have done this a few times can see the blinking lights and hear the beeps and know what is going on
but lack of documentation leaves noob's to the product wanting to ship it back.
I bought SanDisk Cruzer CZ36 16GB USB 2.0 Flash Drive, format as msdos-fat, have setup.alp,U4xxxx.bin,UCSET.bin on it.
Post a video and it will help us tell you what the beeps and flashes are.
[I]Update:
I emailed movie to Radar Roy and Tom from antilaser. Tom saw movie said there were 7 beeps which meant corrupt firmware file.
He told me too download again and I was able to get it accept all of the firmware.
Thanks to all who helped.
Hi, I have installed my own system and am having issues getting it to work. I have a quad system with stir-r add on, currently my install is 90% done, I have controller resting in temporary location while I test the operation. I have 4 sensors, but only 2 connected at this stage because other 2 require some serious panel work to get installed.
Issues I am having:
1. I cannot find the setup.alp file anywhere on alpupdate, I have config.alp instead. Is that the new name being used, or do I need to rename it to setup.alp?
2. On ALP Connect I only have limited menu options available. In the "System Info" menu I can only see the ALP Connect version, but firmware, region etc are all unavailable. So I must be missing something in the install process.
Thanks
M
1. Yes, Setup.alp files are no longer used. Config.alp are the new setup files.
2. Until you update the firmware on a new unit the BT Modules will not recognize the ALP.
View the First Steps Required after installing your ALP thread.
Sent from my SM-G935T using Tapatalk
Cheers. Further information to the above, I followed all steps in this thread. The main issue I have is that after start up, the light flashes blue for about 3 seconds then breaks out into 5 solid red beeps which I assume are error codes.
Having followed the steps here exactly, I figure there is something possibly registration related. I registered today, and put in sensor serial number for all 4 sensors. Question:
1. Am I supposed to wait some period of time between registering and creating a U****** file?
2. Am I supposed to accurately assign sensor serial numbers to the correct controller port as per what ever I registered on ALP website?
I have no idea which sensors I assigned to which port compared to my actual install.
Thanks
M
Thanks, I will.
Have you ever encountered issues with sensors only working in specific ports, or are the fine to interchange? Not sure if it's the reason I'm getting the error codes.
Also I went out for a drive and the radar detector seems to be working through the hand control, but will not work properly with Connect. I can find the device and submit the PIN to connect (using HTC handset), but appears to have no proper functionality. I made some videos that show the issues, I will put on YouTube soon.
Thanks
M
Sensors need to be in the correct ports and when moving sensors to different ports you need to do a memorize sensors command. If you have 2 ports up front they need to be in ports F1 & F2. If you have 3 up front they need to be in F1, F2 & F3 with F2 in the center.
Also make sure you are using the latest version of ALP Connect. Do you have the new or old BT module. If new verify you have the controller in the controller port and not the CPU port.
Sent from my SM-G935T using Tapatalk