Reset, and upped a new config file, and all good now, thanks.Quote:
Originally Posted by BestRadarDetectors
Printable View
Reset, and upped a new config file, and all good now, thanks.Quote:
Originally Posted by BestRadarDetectors
I performed a "Reset Defaults and Memorize Sensors" on both ALP systems. I then inserted the flash drive into each ALP system's USB port. System said "Data Stored" within a couple of seconds. I checked all functions possible via the Yellow Menu....all were what I had selected/downloaded. I then performed the "Print Use and Statistics" function for both systems, printed the results, and compared them to the Configuration file with 3 Profiles which I had downloaded. All device information and Profile A/B/C Settings match exactly what I had selected. I don't know what caused the CHECKSUM FAILED message, but everything appears normal and OK. I'll probably be checking one of my car's ALP systems in the near future to verify the system is operating correctly and providing maximum protection.Quote:
Originally Posted by BestRadarDetectors
Thanks for the advice.
I received the checksum error when I first installed the firmware update. I downloaded a fresh copy of the new firmware a second time but it did not reinstall after plugging the USB stick into the control box a second time. However, everything appears to have installed correctly the first time. I'm up and running with the new ALP connect and the dual radar antenna.
I was going to ask if this would be necessary for those without the Net Radar. Guess it is. I'll generate a new config.alp when I download the new firmware hopefully today.Quote:
Originally Posted by BestRadarDetectors
I suggest if a new firmware requires creating a new configuration, that it's mentioned in the post announcing/describing the new firmware. :)
Everyone will need to load a new settings file after this update. If you are only running Laser you can use the factory defaults which would be Laser Defense with a LID Setting of 4 Seconds.Quote:
Originally Posted by radargeek
Did an OTA firmware update with my original USB stick in situ (have privacy key setup). All went as expected with no checksum failed warning. The old config file is on the USB stick so does it mean I have a default settings (4secs jam) or my previous settings which was infinite?
You should still create and load a new setup file since some option values have changed in the back-end.Quote:
Originally Posted by Fast n Frivolous
On http://alpupdate.com/Firmware it states current firmware is "is 5.2.3/6.7 released 2016-03-23".
I downloaded it anyway and will verify the firmware after installing - posting this as an FYI to BRD.
Yes, We already informed people of this. We always release to members quietly here before releasing to the public. What you will download will be 5.2.5 and the official emails and site information will probably get updated tomorrow.Quote:
Originally Posted by flyingunder
I see that VOLO just got some new lidar, BUT did not get near close enough to see what they're using?? He tried like hell to hit my front which has NO plate and even the RX65 M4 Bel I was running got an alert. Noobs!!
What is VOLO?Quote:
Originally Posted by ECMExpert
Sent from my SM-G935T using Tapatalk
Luckily I had no Checksum Fail messages. I copied update and config to my USB and everything updated without issue.Quote:
Originally Posted by modsl55amg
Why not just update the version info on the site? It's not like people check it every day or even every week. I typically do not even visit the site unless there is an announcement made here.Quote:
Originally Posted by BestRadarDetectors
You would be surprised how many people use website monitors to get notices when a website changes. There are probably hundreds that jump on the site the second it gets updated online.
Sent from my SM-G935T using Tapatalk
This is driving me nuts.
I loaded my old config file into the configuration page and used the old config file to generate a new config file. Then just to check that the format was okay, I selected all of the same options and then generated a brand new file from scratch. I then diffed both files to make sure that they matched, but no matter what I do, I cannot get the two files to match. I have double, triple, and quadruple checked all of the selected options with side by side browser tabs, and I can't even be 100% sure that the new file is the same as the old. There are 5 bytes that differ in the two files:
Attachment 5361
I mentioned several values have changed. Just create a new Config.alp file from scratch and you will be good to go.
So what you're basically saying is that not only is it not okay to reuse the old config files (we knew this already), but it's also not okay to load an old config file and use that configuration to generate a new config file?Quote:
Originally Posted by BestRadarDetectors
If we change values and you load old values you will still end up with incorrect values. Not sure what is difficult to follow? We said that values have changed and you will need to create a new config file. It will take you less than 2 minutes to create a new settings file.
Sent from my SM-G935T using Tapatalk
Not when you use 3 Profiles and have different STiR+ and LID/DLI settings in each. It's a royal pain to generate those config files, and involves opening two browser tabs and clicking back and forth to make sure I didn't miss anything.Quote:
Originally Posted by BestRadarDetectors
We ask users maybe once or twice a year to create a new config file. You can create one profile will all settings and then copy it to B & C and make the changes. It should take no longer than 5 minutes and I would bet you have wasted more than that trying to compare the different files.Quote:
Originally Posted by awj223
Sent from my SM-G935T using Tapatalk
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.
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.Quote:
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.Quote:
Originally Posted by radargeek
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.
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.
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..
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 :)
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.Quote:
Originally Posted by kimberdan
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.
Quote:
Originally Posted by Holla
Yes, 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:Quote:
Originally Posted by radargeek
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.)
No, you never mentioned that in the original post:Quote:
Originally Posted by BestRadarDetectors
I did find it mentioned in the email I got from AL:Quote:
Originally Posted by BestRadarDetectors
I also got this email from them today:Quote:
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?Quote:
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.
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.Quote:
Originally Posted by radargeek
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.
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
Can you elaborate on #4. A new self-test function added, checking if the system is properly configured. What exactly is checked and how and where you get the results of the check?Quote:
Originally Posted by BestRadarDetectors
Thank you
You will get a checksum error if your settings file is not up to date with valid settings. Just download and install a new config file with this update.Quote:
Originally Posted by Lenin
Sent from my SM-G935T using Tapatalk
Going to update tomorrow (Canada Day holiday!) To recap: I do the factory reset FIRST, then add all the new files from the USB like normal?
Install the firmware and you will probably get the error which will reset the defaults automatically after the update. Just make a new config.alp file from the alp update site and keep it on the drive and it will load it when done with the firmware and you will not have to do anything but insert the drive with the firmware and configuration file.Quote:
Originally Posted by wolfpacal
I though it was something more than that. I'm already using the new FW with a new config without any issues.Quote:
Originally Posted by BestRadarDetectors
I just upgraded my setup to v5.2.5, and everything seems to be working as expected (my laser tester is setting off the voice alerts and pro-mode tones).
But I'm curious if the behavior has changed, or if my memory is wrong, or maybe I did something different when creating the new settings file. IIRC when I would hit the left button on my HiFi module it would give me a double-beep and turn green, indicating parking mode only. Now when I do that it says "muted" and stays blue. Did something change with v5.2.5 or am I losing my mind? :)
Your LID setting probably expired and you muted the parking sensors. You need to supply more information LID Settings? After LID Settings?Quote:
Originally Posted by mikedotd
Here are the settings I changed from the defaults:Quote:
Originally Posted by BestRadarDetectors
Dark Mode - Dim
Status LED - Constant
Advanced options - PDC & LID
Pro Mode - Enable
LID Time - Unlimited
After LID timeout - DLI & Warm-up
I just started my car and hit the left HiFi button again (without firing the tester) and it still says "muted" and stays blue.
Single Press of the Button turns the Parking Sensors On or Off.Quote:
Originally Posted by mikedotd
It looks like I was wrong and it was a single press of the Menu button that put it in parking mode only:Quote:
Originally Posted by BestRadarDetectors
https://www.youtube.com/watch?v=83DGLOGJ1mk
But when I press the Menu button a single time nothing happens now.