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

[BestRadarDetectors]

That last attempt seems like either the ALP didn't find the config.alp file on the flash drive (make sure your browser didn't rename it something like config(1).alp). The other possibility is the ALP thinks the config.alp on the drive is the same as the one currently loaded. Did you re-create the config or is this the same config that loaded incorrectly prior?

Also make sure you did in fact update the firmware on both units to 5.2.1, Config files do not load on older firmware.

[modsl55amg]

Also make sure you did in fact update the firmware on both units to 5.2.1, Config files do not load on older firmware.

BRD: Both ALP systems were previously upgraded to firmware version 5.2.1. All of the device information is described at the beginning of my original post.

[modsl55amg]

Problem resolved.

I generated a new Configuration file, with the three Profiles, and loaded it on to a properly formatted USB flash drive. Inserted flash drive in Car 2's ALP USB port, and load was successful. (Car 2 is the one I had problems with a few days ago). I then took the flash drive and inserted it into Car 1's ALP USB port, and load was successful (I changed a couple of selections from what was already in the system). I then downloaded a Statistics file from each system on to two different and properly formatted USB flash drives, printed hard copies, and compared them with each other. I also compared them with a hard copy printout of the Configuration file with the three Profile's selections. All selections on the three Profiles in the Configuration file matched the Statistics print outs.

I do not know what caused the original problem, but I now know that I can load a Configuration file with the three Profiles on to a flash drive and successfully load the file on to both ALP systems.

Thank you to everyone who posted advice and suggestions. I appreciate your help.