yessirDo you have the Whistler programming cable?
yessirDo you have the Whistler programming cable?
Already have that drive installed. Attempted upload again. Still nothing.Save this zipped file to your computer and extract. Run the extracted file.
yessirDid you purchase the key and register ARC500?
yes, i can download from the scanner.Your file does not cause my scanner to reset. Are you able to download from the scanner?
Thank you!I believe that you either have a scanner or cable problem. There is only one thing left to try. Go back to my post #36 and reload the CPU firmware. Be warned that if there is a communication problem, it could disable your scanner. If you have any problems, I will contact Whistler tech support for you and explain the situation.
Thank you!
I have a handhelod whistler scanner to which I just attempted to upload from the ARC500 and the same thing happened. 'Nothing enabled'. NOt sure what that means but I don't think the problem is the scanner. Something to do with the software or the upload. I have two cables, one from each of the scanners when I bought them and have tried them both to no avail so I don't think it's the cables either.I believe that you either have a scanner or cable problem. There is only one thing left to try. Go back to my post #36 and reload the CPU firmware. Be warned that if there is a communication problem, it could disable your scanner. If you have any problems, I will contact Whistler tech support for you and explain the situation.
@sgtmark : Are you also writing the "Trunked.gr5" file to your scanner? I just want to confirm that you and tvengr are working with the same file.I uploaded the "Trunked" file to my PRO-106 and it is scanning. Other than the ARC500 software or scanner firmware being corrupted, I cannot think of anything else other than a defective scanner.
Please verify that you are trying to upload the "Trunked" file. Are they both the same Whistler cable? Since the same problem occurs with both cables and scanners, the only common items are the driver and software. Try uninstalling the driver and reinstalling it with the driver I attached in case it is corrupted. If the same problem still occurs, the next thing to check is the software. The file doesn't cause my scanner to reboot. It could be something in the upload module of the software. Make sure you have the registration key available before trying the next step. Uninstall ARC500. Download a new file from Butel Software and reinstall it. Register the software with the key. Try uploading the "Trunked" file again.Are you also writing the "Trunked.gr5" file to your scanner? I just want to confirm that you and tvengr are working with the same file.
I attempted the upload with both cables to no use. I uninstalled and reinstalled and nothing. I think i'm about out of options here.Please verify that you are trying to upload the "Trunked" file. Are they both the same Whistler cable? Since the same problem occurs with both cables and scanners, the only common items are the driver and software. Try uninstalling the driver and reinstalling it with the driver I attached in case it is corrupted. If the same problem still occurs, the next thing to check is the software. The file doesn't cause my scanner to reboot. It could be something in the upload module of the software. Make sure you have the registration key available before trying the next step. Uninstall ARC500. Download a new file from Butel Software and reinstall it. Register the software with the key. Try uploading the "Trunked" file again.
For reference, I installed the ARC500 trial and successfully wrote all 3 of the .g5 files to my GRE PSR-500. The upload completed successfully, and the scanner started scanning upon completion. I did not get the "File System initialized to defaults" or "Nothing Enabled" messages. This seems to replicate avenger's resultsI attempted the upload with both cables to no use. I uninstalled and reinstalled and nothing. I think i'm about out of options here.
From your description, I'm not sure that the EEPROM test was run successfully. I suggest trying to run this again.I tried the EEPROM test like you suggested but not sure what was supposed to happen then. It looked like it just gave some internal software info like number of freqs and such.