To anyone looking to acquire commercial radio programming software:
Please do not make requests for copies of radio programming software which is sold (or was sold) by the manufacturer for any monetary value. All requests will be deleted and a forum infraction issued. Making a request such as this is attempting to engage in software piracy and this forum cannot be involved or associated with this activity. The same goes for any private transaction via Private Message. Even if you attempt to engage in this activity in PM's we will still enforce the forum rules. Your PM's are not private and the administration has the right to read them if there's a hint to criminal activity.
If you are having trouble legally obtaining software please state so. We do not want any hurt feelings when your vague post is mistaken for a free request. It is YOUR responsibility to properly word your request.
To obtain Motorola software see the Sticky in the Motorola forum.
The various other vendors often permit their dealers to sell the software online (i.e., Kenwood). Please use Google or some other search engine to find a dealer that sells the software. Typically each series or individual radio requires its own software package. Often the Kenwood software is less than $100 so don't be a cheapskate; just purchase it.
For M/A Com/Harris/GE, etc: there are two software packages that program all current and past radios. One package is for conventional programming and the other for trunked programming. The trunked package is in upwards of $2,500. The conventional package is more reasonable though is still several hundred dollars. The benefit is you do not need multiple versions for each radio (unlike Motorola).
This is a large and very visible forum. We cannot jeopardize the ability to provide the RadioReference services by allowing this activity to occur. Please respect this.
Sorry y'all. I had to go out of town suddenly and the forum didn't alert me to the replies. Glad to see you got it worked out. Looks like all factory profiles include this setting enabled by default. Hopefully they change that in the future.
Most if not all random Unication issues are programing and or systems related . Of course that is my opinion as I have never experienced such as this issue . They are solid professional grade receivers to monitor single system with optimum results .
I have asked a friend monitoring the same systems to see if he had a check box there already. That will help me decide a little more if that was the issue. I don't recall this bleed over happening when I bought the pager, but since I was still working on programming it, it could have been happening and I didnt know.
@ResQguy Any chance you can explain what that setting does? Is the setting making it remember the last UID or TGID? I ask because Unication never mentioned this setting for me to check, and took my pager back as a warranty issue instead of suggesting this! It has now been two weeks that I'm without a pager.
Sorry y'all. I had to go out of town suddenly and the forum didn't alert me to the replies. Glad to see you got it worked out. Looks like all factory profiles include this setting enabled by default. Hopefully they change that in the future.
@ResQguy Any chance you can explain what that setting does? Is the setting making it remember the last UID or TGID? I ask because Unication never mentioned this setting for me to check, and took my pager back as a warranty issue instead of suggesting this! It has now been two weeks that I'm without a pager.
I have received my new pager from Unication. I have removed the Private Call ID from the programming. The pager is working PERFECTLY now!! I never added that into the pager, we believe as others stated that it was in the pager from the start. Thank you @ResQguy for the assist, condition corrected!
I have received my new pager from Unication. I have removed the Private Call ID from the programming. The pager is working PERFECTLY now!! I never added that into the pager, we believe as others stated that it was in the pager from the start. Thank you @ResQguy for the assist, condition corrected!