Anomaly encountered when loading identical Profiles, into two different ALP systems.

[BestRadarDetectors]

Not trying to hijack the thread, but while on the subject of anomalies, I turned on the car the other day - ALP went through its boot up process, but the light stayed green for a good 30 -60 seconds before turning blue. Is this normal? I don't ever recall it taking so long for the LED to turn blue. Could it be the cold weather? First time it happened, I was ready to put in the USB, because it was green for so long, and as I was ready to put it in, it turned blue.

The default if you do not have the Skip First Warm-up option enabled is a 60 second warm-up period before it goes into defense mode.

[awj223]

The default if you do not have the Skip First Warm-up option enabled is a 60 second warm-up period before it goes into defense mode.

I hope that AL website is updated so that we can load in an old CONFIG.ALP file and it will set all of the parameters to their old values, and any new parameters can either be set to a default value or flagged so that the user can choose, then can successfully generate a new file. When I tried this in the past, it could load in an old file, but once it had done so, if the file was NOT in the same format (was of a previous revision), it wouldn't successfully generate a new file. This is especially important now that we have 3 profiles per file. With so many parameters to set, it's extremely easy to overlook something and the only way I can ensure that everything is set properly is to open two browser tabs and click back and forth to make sure everything is exactly the same. As you can imagine, doing this 3 times for 3 profiles leaves a lot of room to screw something up.

[radargeek]

I hope that AL website is updated so that we can load in an old CONFIG.ALP file and it will set all of the parameters to their old values, and any new parameters can either be set to a default value or flagged so that the user can choose, then can successfully generate a new file. When I tried this in the past, it could load in an old file, but once it had done so, if the file was NOT in the same format (was of a previous revision), it wouldn't successfully generate a new file. This is especially important now that we have 3 profiles per file. With so many parameters to set, it's extremely easy to overlook something and the only way I can ensure that everything is set properly is to open two browser tabs and click back and forth to make sure everything is exactly the same. As you can imagine, doing this 3 times for 3 profiles leaves a lot of room to screw something up.

I've been able to load old setup.alp files to the website and they loaded successfully. By default they get loaded to profile A, but you can then copy it to B and/or C from the website, tweak them to your liking and then download a new config.alp file.

If you're not using profiles, you can just upload a setup.alp and then download a new config.alp, easy as pie!

Of course, if you upload a config.alp with profiles to the website, all the profiles will be loaded on the page so you can edit them and create a new file.