So the website doesn't remap the values when you upload an old config file and then generate a new one? I would think it should.
I uploaded my old config and then generated a new one, and it is working fine as far as I can tell. I'll re-generate them from scratch if necessary, but it's easy to miss something in the process. Maybe I'll generate one from scratch, and also upload an older and a current one and re-download, and diff them to see.
If I passed you on the right, YOU are in the wrong lane!
2016 Encounters/Saves (to date): 33.8: 1/1 (last 4/13) | 34.7: 1/1 (last 3/11) | 35.5: 19/11 (last 8/28) | K: 1/1 (last 6/26)
2015 Encounters/Saves: 33.8: 1/0 | 34.7: 13/4 | 35.5: 19/10 | K: 4/1 | LIDAR (sighted/hit with/save): 4/1/1
ACTIVE CMs: Redline X, K, Ka 2,4,5,8 (highway/long trip RD) | New! V1C 3.8945 K, Ka CS, TMF2 w/YaV1 (in-town RD) | ALP Quad | BlackVue DR650GW-2CH
awj223 (06-23-2016), modsl55amg (06-23-2016)
Did I mention that I have 3 different files, each with 3 different profiles? Why should I have to regenerate all of those from scratch, when it's so easy to miss one item here or there, because no one at AL could program the website to spit out a good new configuration file when it reads in an old one? A lot of what I change in the different profiles is that I program different bands for the RD (Ka subbands, RDR, TSR, etc). It's easy to accidentally forget to mark TSR for one Profile of one file if you are generating this stuff manually. Now that you're supporting Net Radar, a lot more of your customers are going to be doing this.Originally Posted by BestRadarDetectors
That's the problem. I diffed the two files, and there were still 5 bytes that came out different. And because AL doesn't tell me what each byte means, I have no idea if those bytes are critical to the operation of the device.
Another issue: I got the "checksum failed" message after updating, followed by "data stored". I think what's happening is that the device tries to read the old configuration file (stored on the device), the checksum fails, and then it loads the new configuration file (the "data stored" message), after which time everything behaves like it should. This message could make it seem like something is wrong to many people, when in fact there is nothing wrong.
modsl55amg (06-23-2016)
I did some experimentation, generating configs from scratch as well as converting older ones, or uploading current and re-downloading, and doing binary compares on them. I see the same thing you do, a handful of bytes are different when converting. They appear to be bytes carried over from the old file without being changed, but have different defaults when creating a new config from scratch. Perhaps they're not important configuration values, or they're values used only in a different region such as Europe where there are different guns. I did try changing every parameter available on the page (including features I don't use like radar and GPS) to see if the "question bytes" changed. They didn't, except for one of the bytes when I created a European profile and changed all the settings from the defaults.
The file does appear to get remapped other than that, so I think all the important bytes are updated, and I haven't run into any issues when converting configs when updating firmware. Even when they went from setup.alp to config.alp, I was able to convert it using the website without having any issues. Since they provided the upload feature on the website, I'm sure they designed it with the idea that one could update an existing configuration to the latest version this way.
Of course, there's no way to know for real without a layout or description of what each of the bytes means. I suppose if someone has a weird issue, one of the troubleshooting steps could be to create a new config from scratch and see if it helps.
Last edited by radargeek; 06-23-2016 at 09:23 PM.
If I passed you on the right, YOU are in the wrong lane!
2016 Encounters/Saves (to date): 33.8: 1/1 (last 4/13) | 34.7: 1/1 (last 3/11) | 35.5: 19/11 (last 8/28) | K: 1/1 (last 6/26)
2015 Encounters/Saves: 33.8: 1/0 | 34.7: 13/4 | 35.5: 19/10 | K: 4/1 | LIDAR (sighted/hit with/save): 4/1/1
ACTIVE CMs: Redline X, K, Ka 2,4,5,8 (highway/long trip RD) | New! V1C 3.8945 K, Ka CS, TMF2 w/YaV1 (in-town RD) | ALP Quad | BlackVue DR650GW-2CH
awj223 (06-23-2016), modsl55amg (06-23-2016)
Just my 2 cents.. I also got the check sum fail... I came in and re down loaded everything to a USB that I use all the time at it worked fine.. so IDK if anyone is using a different USB but that might be an issues for some as well... I put the new files on the new USB and it went right in with no problems..
modsl55amg (06-24-2016)
I got checksum fail as well (had Firmware/config on USB) but as soon as it loaded the New Config file that i had on my stick, all was good--first time it has done that to me ,probably just another added check they incorporated with the file install! Im sure as hell not loosing any sleep over this as a few are lol
ALP Quint
Red-Line 2/5/8
The checksum fail is a result of the new firmware when it boots up for the first time and reads the old stored configuration. I don't know why that happens with just this update and not past ones (especially when profiles were added), but I digress... maybe they changed the checksum algorithm in this update.
In any case, generating a new config on the website and loading it gets rid of the checksum error and ensures all your settings are correct. As a rule of thumb I always make a new config.alp and put it on the same USB as the firmware when I do an update, so everything gets updated in one go.
Last edited by radargeek; 06-24-2016 at 01:18 PM.
If I passed you on the right, YOU are in the wrong lane!
2016 Encounters/Saves (to date): 33.8: 1/1 (last 4/13) | 34.7: 1/1 (last 3/11) | 35.5: 19/11 (last 8/28) | K: 1/1 (last 6/26)
2015 Encounters/Saves: 33.8: 1/0 | 34.7: 13/4 | 35.5: 19/10 | K: 4/1 | LIDAR (sighted/hit with/save): 4/1/1
ACTIVE CMs: Redline X, K, Ka 2,4,5,8 (highway/long trip RD) | New! V1C 3.8945 K, Ka CS, TMF2 w/YaV1 (in-town RD) | ALP Quad | BlackVue DR650GW-2CH
kimberdan (06-24-2016), modsl55amg (06-24-2016)
I got checksum fail as well (had Firmware/config on USB) but as soon as it loaded the New Config file that i had on my stick, all was good--first time it has done that to me ,probably just another added check they incorporated with the file install! Im sure as hell not loosing any sleep over this as a few are lolYes, Its a new Check to make sure users have a current config file loaded to make sure the system is configured properly. Its noted in the notes I posted in the first post:
Control Box Firmware update Report (21.06.2016)
Release 5.2.5/6.8
1. Added support for Net-Radar detector.
2. Added support for ALP Radar/GPS Plugin 3.
3. Added support for the latest Android ALPConnect app.
4. A new self-test function added, checking if the system is properly configured.
5. Support improved for several LIDARs.
6. Bug-fixes (Laser, Radar, PDC, etc.)
Last edited by BestRadarDetectors; 06-24-2016 at 01:28 PM.
Need Help Choosing a Radar Detector for your needs? Visit our website: http://www.bestradardetectors.net, Send us a PM or call us at 1-888-229-7594
Before looking at an Escort Radar Detector you should really check out Uniden Detectors.. Uniden R1 & R3 are the best performing radar detectors for the money.
jfr3170 (06-24-2016), modsl55amg (06-24-2016)
No, you never mentioned that in the original post:I did find it mentioned in the email I got from AL:I also got this email from them today:Control Box firmware
5.2.5/6.8
1. Added support for Net-Radar detector.
2. Added support for ALP Radar/GPS Plugin 3.
3. Added support for the latest Android ALPConnect app.
4. A new self-test function added, checking if the system is properly configured.
5. Support improved for several LIDARs.
6. Bug-fixes (Laser, Radar, PDC, etc.)
SPECIAL NOTICE: A "CRC Checksum Failed" warning may occur after performing the initial firmware upgrade.Is that an issue only if you do an OTA update and don't have a new config.alp handy?IMPORTANT NOTICE for ALPCONNECT APPLE DEVICE USERS:
If you are running your ALP system over ALPConnect installed on an Apple device (iPhone, iPod, iPad...) and if you run a radar antenna in your ALP system, you are advised not to upgrade to the newer ALP Control Box firmware before an upgrade for ALPConnect for Apple is released. If your ALP system is upgraded to the latest Control Box firmware version 5.2.5. your ALPConnect app on your iDevice will loose GPS and Radar functions.
If I passed you on the right, YOU are in the wrong lane!
2016 Encounters/Saves (to date): 33.8: 1/1 (last 4/13) | 34.7: 1/1 (last 3/11) | 35.5: 19/11 (last 8/28) | K: 1/1 (last 6/26)
2015 Encounters/Saves: 33.8: 1/0 | 34.7: 13/4 | 35.5: 19/10 | K: 4/1 | LIDAR (sighted/hit with/save): 4/1/1
ACTIVE CMs: Redline X, K, Ka 2,4,5,8 (highway/long trip RD) | New! V1C 3.8945 K, Ka CS, TMF2 w/YaV1 (in-town RD) | ALP Quad | BlackVue DR650GW-2CH
modsl55amg (06-24-2016)
Look again.. You are quoting me from post 457 which was posted before the official update which is always in the first post. I cant expect people to read through hundreds of posts so we only keep the 1st posted updated with all firmware information. In fact I think we will probably lock this thread and leave it for information only and not discussion and if people have questions on a firmware they can start their own thread.
The Apple issue we posted about separately already. That issue has nothing to do with how someone updates its because the Apple ALP Connect is older and it has an issue with the current firmware and Apple updates are always much slower.
Need Help Choosing a Radar Detector for your needs? Visit our website: http://www.bestradardetectors.net, Send us a PM or call us at 1-888-229-7594
Before looking at an Escort Radar Detector you should really check out Uniden Detectors.. Uniden R1 & R3 are the best performing radar detectors for the money.
modsl55amg (06-24-2016), Qui-Gon (06-30-2016), radargeek (06-24-2016)
Just getting around to the latest update (my home PC is FUBAR) - had to download everything from a work PC.
Sent from my LGL44VL using Tapatalk
STi-R: the ORIGINAL!
AL Priority TRIPLE
ALP Hi-Fi Module
ALP Add-on wish list:
2 more heads
Posting Permissions
Reply With Quote
Connect With Us