Page 1 of 1

Advisor II Error while Programming pager

Posted: Fri Feb 08, 2008 8:52 am
by Hoseman292
Hello,

I recieve the error message, "WARNING: Frequency entered is not in the range of the receiver.
Any other key to abort".

Once I press any key the software returns to main menu.
The only changes I've made was to the name displayed on the pager. No changes were made to the frequency (931.8625), cap codes, etc.

Any help would be greatly appreciated.

Tim
Hoseman292@aol.com

Re: Advisor II Error while Programming pager

Posted: Sun Feb 10, 2008 9:44 pm
by Hoseman292
** BUMP BUMP**

Any suggestions fellas? TPG, I know you're out there. :lol:


Thanks,
Tim

Re: Advisor II Error while Programming pager

Posted: Fri Feb 15, 2008 1:27 pm
by Zack08
Are you reading it from the pager, changing the text, and then loading the same file back in?

Does the frequency show up correctly in PPS when you read it?

Is it possible that the software you're using is older than what was used for initial programming?

Re: Advisor II Error while Programming pager

Posted: Sat Feb 23, 2008 3:40 pm
by Hoseman292
motosynth947 wrote:Are you reading it from the pager, changing the text, and then loading the same file back in?

Does the frequency show up correctly in PPS when you read it?

Is it possible that the software you're using is older than what was used for initial programming?
Hi and thanks for the reply. Yes I am reading the pager which is successful. The pager frequency is correct. The only change that is made is the name indicated on the display that appears when the pager is initially powered up.
Once i press F2 to PROGRAM PAGER the error occurs and the only option that becomes available is to exit.
Any help that you can offer would be greatly appreciated.

Tim

Re: Advisor II Error while Programming pager

Posted: Sun Feb 24, 2008 10:34 am
by Zack08
I'm wondering if the pager was initially programmed with a newer version of PPS than what you are using. FYI, the newest revision of the software is 06.15.11. I would suggest using that version and see if the same problem occurs.

Other than that, I have no idea what the problem could be, since nothing else was changed.

Good luck!