Possible PPS bugs

[mdsxfire]

We had to do an entire dept pager reprogram due to a dispatch issue. The only thing that was changed was the timing of our A and B tones, so the pagers were read tone length changed and then reprogrammed. I did one company with PPS 3.16.29e and another person did the other companies with one of the first versions of PPS 4.xx. Every pager that was reprogrammed with the 4.xx PPS is having issues constantly going out of range and then when going out of range not being able to acquire the control channel for 10-15 unless u change knob or power off and on, this is fairly consistent with all this 4.xx pagers. None of the pagers I programmed with 3.16 are having this issue and when going into diagnostics with one of each of the pagers the one programmed with 3.16 has on average a 20dbm better signal. Anyone ever heard of this or have an idea of what the issue could be besides PPS gremlins

 

[belvdr]

PPS 4 is garbage right now. I can reproduce what you're seeing as well. Program with v4, and it has issues with roaming. Program with v3 and all the issues go away.

 

[mdsxfire]

Amazing glad to confirm my suspicions since that’s literally all it could be, also glad we didn’t upgrade to 1.35 F/W since once u do u can no longer us the older PPS..I’m good with staying 1.34 and 3.16

 

[mdsxfire]

On a side note is there any way to downgrade from 1.35 to 1.33

 

[belvdr]

Amazing glad to confirm my suspicions since that’s literally all it could be, also glad we didn’t upgrade to 1.35 F/W since once u do u can no longer us the older PPS..I’m good with staying 1.34 and 3.16

FWIW, I'm using PPS 3.16.29E with firmware 1.35. I was previously at 1.33. Unication has no release notes on 1.35 either, so maybe it is supported. Who knows for sure.

 

[belvdr]

On a side note is there any way to downgrade from 1.35 to 1.33

I read that going from 1.40 to 1.33 involved:

1. Installing 1.20
2. Upgrading to 1.33

I do not know if the same is needed for 1.35 > 1.33 but thought it would be good to know.

 

[mdsxfire]

FWIW, I'm using PPS 3.16.29E with firmware 1.35. I was previously at 1.33. Unication has no release notes on 1.35 either, so maybe it is supported. Who knows for sure.

I tried reading a pager with F/w 1.35 on it with PPS 3.16.29e and it told me it was an invalid unnipps file

 

[mkinkade]

I've experienced the same thing with PPS 4, with it dropping out of range for no reason, and not reacquiring the tower unless you change the knob to another tower and back, or cycle the power. It also won't automatically acquire the tower if you're travelling back into range of the tower unless cycling the knob or power. This was identified by someone in a previous thread about 2 months ago, but they still haven't fixed it.

 

[belvdr]

I tried reading a pager with F/w 1.35 on it with PPS 3.16.29e and it told me it was an invalid unnipps file

Ok, I didn't do that. I only wrote to the pager using an existing profile. I'm installing 1.33 now over top of 1.35 and will report back.

 

[mdsxfire]

I've experienced the same thing with PPS 4, with it dropping out of range for no reason, and not reacquiring the tower unless you change the knob to another tower and back, or cycle the power. It also won't automatically acquire the tower if you're travelling back into range of the tower unless cycling the knob or power. This was identified by someone in a previous thread about 2 months ago, but they still haven't fixed it.

that’s just great. We literally just went through a **** show for 3 months with our dispatch and pager activation issues we reprogram to address it and these bugs pop up, thankfully I programmed one company with the 3.16 and they had zero issues

 

[mkinkade]

I changed the 'Out of Range Alert Setting' in E11-5 to Alert Repeatedly every 30 seconds, so at least I'll know it.

 

[belvdr]

I was unsuccessful in reverting back from 1.35. I tried 1.20, 1.30, 1.31, 1.32, and 1.33. All errored out in some fashion, but the pager remained at 1.35.

 

[belvdr]

I tried reading a pager with F/w 1.35 on it with PPS 3.16.29e and it told me it was an invalid unnipps file

I reprogrammed my pager with PPS v3, running firmware 1.35. I was then able to read it in successfully.

Maybe you tried to read a pager programmed from PPS v4?

 

[RaleighGuy]

Amazing glad to confirm my suspicions since that’s literally all it could be, also glad we didn’t upgrade to 1.35 F/W since once u do u can no longer us the older PPS..I’m good with staying 1.34 and 3.16

That is not correct, I have a G5 with FW 1.35 and I continue to use PPS V3.29.

 

[mdsxfire]

That is not correct, I have a G5 with FW 1.35 and I continue to use PPS V3.29.

No apparently once u program a pager with 4.xx u can’t go back and program it with 3.xx

 

[RaleighGuy]

No apparently once u program a pager with 4.xx u can’t go back and program it with 3.xx

I tried reading a pager with F/w 1.35 on it with PPS 3.16.29e and it told me it was an invalid unnipps file

That wasn't what you said happened, that makes a difference.

 

[mdsxfire]

That wasn't what you said happened, that makes a difference.

Exactly and after posting that I tried a few other things and found that out so I was agreeing with u
And I said exactly what happened actually that I tried reading a pager with 1.35 with 3.16 and it said invalid..that is what happened

 

[belvdr]

Exactly and after posting that I tried a few other things and found that out so I was agreeing with u
And I said exactly what happened actually that I tried reading a pager with 1.35 with 3.16 and it said invalid..that is what happened

It had a PPS 4 profile programmed to it. If you program it with a PPS 3 profile, it will read successfully.

 

[AYoung2600]

No apparently once u program a pager with 4.xx u can’t go back and program it with 3.xx

That’s not true. I programmed my G4 with a version 4 software and was experiencing the out of range problem. I was able to rewrite my old file in version 3.29 and the pager started functioning correctly again.

 

[mdsxfire]

I guess what I’m getting at is I can’t take the profile on the pager and work on it with the older PPS since it was programmed by 4.xx I can rewrite a profile on 3.xx and then program the pager
More so it sounds like the 4.xx PPS needs some work