belvdr
No longer interested in living
- Joined
- Aug 2, 2013
- Messages
- 2,567
Correct you cannot import a v4 profile export or read a device programmed with v4 using v3.
You can use v3 to create a new codeplug and overwrite the v4-programmed device.
-
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.
Possible PPS bugs
- Thread starter mdsxfire
- Start date
You can use v3 to create a new codeplug and overwrite the v4-programmed device.
Or the FW since 1.35 was never officially released as a stable FW, it came out as a beta, it is now being released (without release notes). Have you tried to do a factory reset and then using V3 PPS?
The out of range problem definitely seems to be related to PPS 4 latest release 36. I have pagers on 1.33 firmware programmed with PPS 4 that experience the issue. Same units previously programmed with 3-16-29E never had the issue.
I have developed a workaround for this: turn full spectrum scan on, program the appropriate parameters as they pertain to your system, and the radio will go back in range instead of remaining OOR. Verified working with my G2 and G5. Long story short: Full spectrum scan MUST be turned on if you want your pager to go back in range if you are using PPS 4.0 or above. You're welcome.
If it actually has to scan for it, it's extremely slow in my experience. But, I'll try it. Thanks.
I said it's a workaround, not a fix, so it's obviously not ideal. The burden of responsibility is on Unication, not us users, to fix the bug. They should also improve those internal antennas while they are at it so systems on the secondary band are not constantly going OOR in the first place.
I'm using 4.0-36 software with 3 g5s on 1.35 with no issues.
I get them out of range and then they come right back.
I tried on the 4 different sites I can get from my house and all worked fine
I get them out of range and then they come right back.
I tried on the 4 different sites I can get from my house and all worked fine
mdsxfire
EDBM
Sounds like a temp fix if u have no other choice, but unication needs to address this since none of our pagers ever went out of range like this before, and the ones that I have reprogrammed in the last few days with the 3.xx PPS are back to not having any issues. I’ll just stay with 1.33 programmed on 3.xx for now
mdsxfire
EDBM
Agreed the secondary band antennas are horrible I get it’s a secondary band but both are more than likely being used give us something a little better. Our second band is VHF which we had to use while county was working on our 7/800 tones and it was borderline useless
- Joined
- Dec 22, 2005
- Messages
- 2,109
Good Intel. I have been slowly using PPS 4.0.36 to build a new code plug. I wrote one and all has been well, while stationary.
I was mobile with it a couple days ago and it was downright buggy. Many out of range
notifications. Some momentary, some longer. Interesting development.
Running 1.32 FW
I was mobile with it a couple days ago and it was downright buggy. Many out of range
notifications. Some momentary, some longer. Interesting development.
Running 1.32 FW
Last edited:
ErikSwan
Member
Related thread:
forums.radioreference.com
I can't reproduce this issue on my VHF G5N with firmware 2.01. Note that the new G5N with 2.01 firmware can only be programmed with PPS v4; PPS v3 is not supported. I suspect this is isolated to the older revision G5 models.
Issues with systems coming back in range after using PPS V4
I've noticed my VHF G5 is not reacquiring systems that go out of range. I've tested it with my local system side by side with my other UHF G5, which I haven't programed with V4 yet, and the VHF G5 does not reacquire my local system when I remove the antenna and put it back on, but the UHF G5...
I can't reproduce this issue on my VHF G5N with firmware 2.01. Note that the new G5N with 2.01 firmware can only be programmed with PPS v4; PPS v3 is not supported. I suspect this is isolated to the older revision G5 models.
