Issues with systems coming back in range after using PPS V4

[JSsignal16]

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 does. I've tested this with other systems and still have the same issue. The only way I can get my VHF G5 to reacquire a system is to switch to another system and switch back. Has anyone else observed this?

 

[JSsignal16]

I forgot to mention that the V4 profile I loaded to my VHF G5 was created from scratch and verified all settings are the same with the V3 profile on the UHF G5.

 

[jtwalker]

I believe the external antenna on a G5 is just for 800 band. Never tried it but seems logical that it would not impact your reception of VHF/UHF by removing it.

 

[JSsignal16]

You are correct. But all the systems I've tested with were 800mhz systems. I noted the VHF G5 and UHF G5 in my post for easier distinction.

 

[jtwalker]

Well I don't have this issue because I NEVER take the antenna off my G5. If you are doing this on a regular basis, I'd suggest you stop ... for reliability.

Maybe someone else will have more useful information for you.

 

[JSsignal16]

I agree with you 100 percent. I've never taken my antenna off in the 7 years I've owned these G5s before this discovery. I only took it off in this instance to replicate an issue that was observed while driving. The system I was listening to went out of range but did not come back in range in an area I know to have strong reception of the same system. Thank you your reply.

 

[cmlewis1969]

I have been having the same issue dropping my home system (700) in areas within line of sight of 1 of the towers. It started for me about 3 weeks after updating firmware and using V4 of PPS. Still have not figured it out after 3 months.

 

[FishScan]

Use the old PPS and write to the pager.

 

[JSsignal16]

I have been having the same issue dropping my home system (700) in areas within line of sight of 1 of the towers. It started for me about 3 weeks after updating firmware and using V4 of PPS. Still have not figured it out after 3 months.

In my case my home system comes in fine and doesn't drop out. It's when I try to receive a neighboring system, that has good reception for the most part, and then drive through known dead spots in my county, the G5 goes out of range for that system as expected. The problem is it (G5 programed with V4) doesn't come back is range at all, when I then go into areas with strong reception of the same system. My other G5 on the same system (programed with V3) comes back in range.

 

[cmlewis1969]

I dumped my V3 program back into my pager and monitored for a couple of days now. Noting in the same locations i still get the same results. Shows out of range then almost immediately is back in range with 4+ bars on the receiving strength. Crazy thing is even setting still it will go out of range, and without moving pops right back in range full strength. With my APX portable right next to the G5 it NEVER looses signal.

 

[belvdr]

I see this behavior using PPS v4 and a G4. I'm also running firmware 1.33 and never touched 1.34. It's as if it never goes back to searching for a signal.

 

[JSsignal16]

So when it goes out of range, does it make the out beep and flash the Out of Range banner across the screen?

 

[belvdr]

So when it goes out of range, does it make the out beep and flash the Out of Range banner across the screen?

My G4 flashes the banner. It simply continues flashing until I turn it off/on.

 

[JSsignal16]

My G4 flashes the banner. It simply continues flashing until I turn it off/on.

Yeah it sounds like we're having the same issue. I'm also running 1.33. But my other G5 programed with V3 doesn't have the problem at all. So I'm thinking it might be something in V4. I understand that this issue may not be apparent for most people. The G5 does an amazing job staying locked onto systems, even more distant ones, and if it does go out of range (usually while in motion) most just change to a closer system and won't continue to try to receive the same distant system they were first listening to.

 

[belvdr]

Yeah it sounds like we're having the same issue. I'm also running 1.33. But my other G5 programed with V3 doesn't have the problem at all. So I'm thinking it might be something in V4. I understand that this issue may not be apparent for most people. The G5 does an amazing job staying locked onto systems, even more distant ones, and if it does go out of range (usually while in motion) most just change to a closer system and won't continue to try to receive the same distant system they were first listening to.

I can confirm it's PPS v4. I imported my 3.x file into PPS v3 and re-programmed. It worked as it should and reacquired the site within a few seconds.

 

[cmlewis1969]

My G5 will display the banner and the out of range noise, it doesnt switch to another location because my county is a simulcast system on a regional network and all the radios in the county are set to prioritize the simulcast system even if a better signal on a neighboring site is there. I did reload my program from a V3 pps, with no change, unfortunately i did upgrade to 1.34 FW and shortly afterwards all this started.

 

[JSsignal16]

My G5 will display the banner and the out of range noise, it doesnt switch to another location because my county is a simulcast system on a regional network and all the radios in the county are set to prioritize the simulcast system even if a better signal on a neighboring site is there. I did reload my program from a V3 pps, with no change, unfortunately i did upgrade to 1.34 FW and shortly afterwards all this started.

Have you tried downgrading firmware to 1.33?

 

[jtwalker]

Have you tried downgrading firmware to 1.33?

From what I’ve read, this is not possible.

 

[blackbelter]

Perhaps you’re thinking of the original 1.34 for the Beta testers which could not be reverted back . The latest 1.34 had multiple issues thus it was removed from the Unication site. Per my dealer the 2.01 has minimal changes and may not worth upgrading from 1.33.

 

[jtwalker]

Perhaps you’re thinking of the original 1.34 for the Beta testers which could not be reverted back . The latest 1.34 had multiple issues thus it was removed from the Unication site. Per my dealer the 2.01 has minimal changes and may not worth upgrading from 1.33.

That was 1.4 for beta testers. I am definitely talking about reverting back off the GA 1.34 but I am just going by what others say.