V1.30 G2-G5 Firmware Released

[hfd26]

My Depar


Something is very wrong with this firmware, and 1.4 - it hasn't been reliable since 1.1. 1.2 is false alerts, 1.3/1,4 are not alerting, and this is VHF conventional QCII Motorola, not anything custom, etc.

I have not tried the conventional part with this new fw. Ive been using the p25 and so far everything is working as ive wanted it to. 1.1 the pager only alerted 1 tone, on 1.2 the pager wouldnt alert at all on p25, now with 1.3 it works even works with stacked tones. I really dont have any complaints except I wish the bluetooth would play audio through my truck. Its connects but no sound.

 

[kikito]

Hopefully, I found the correct solution. I simply removed 1 TalkGroup, leaving a total of 63 TalkGroups, instead of 64 and all seems to be working properly.

You must have me blocked or ignoring me because I brought that up several times in the past week...

 

[JASII]

You must have me blocked or ignoring me because I brought that up several times in the past week...

Hopefully, I am not doing either one, but sometimes I don't read every post. Is that embedded anywhere in a Help Section of the PPS itself?

 

[CcSkyEye]

I had the same problem when I went to 1.3 fw. I changed my tone A to 1000ms tone B 3000ms tone C 5000 gap between two digital to 500ms short tone detection 400ms and lone tone detection 400ms. These seem to work so far and now it alerts the 2 tone on p25. We use a motorola vhf system.

Just had our nightly pager test which is a long tone, this didn't do the trick either.

The search for a fix continues.

 

[hfd26]

Just had our nightly pager test which is a long tone, this didn't do the trick either.

The search for a fix continues.

Do you know your tones timing for the A tone and B tone and long tone. If not maybe someone from your dispatch center could tell you.

 

[CcSkyEye]

Do you know your tones timing for the A tone and B tone and long tone. If not maybe someone from your dispatch center could tell you.

I don't know the timing, two tones (A and B) is working perfect. Just the long tones that I'm having issues with, on two different systems.

I have played around with timing several times now. Copying the timing on the version 1.2 which did change when going to version 1.3 for some reason, plus they added the tone qualifying.

Thanks for the help, Ill keep you posted.

 

[box23]

I may have missed it in the various threads and replies, but can a talkgroup be programmed as blocked via PPS?

For my purposes I need to use TG-monitor, but there are a couple talkgroups I would like to permanently block rather than having to do it manually every time. I have not found such a setting in PPS, but I may have overlooked it.

 

[N6ML]

I may have missed it in the various threads and replies, but can a talkgroup be programmed as blocked via PPS?

For my purposes I need to use TG-monitor, but there are a couple talkgroups I would like to permanently block rather than having to do it manually every time. I have not found such a setting in PPS, but I may have overlooked it.

I don't know of any way to do that.

 

[blackbelter]

Upon installing the 1.3 FW, I have noticed that my G5 sounds better and the usual pop and echo on my Power amp have disappeared , however not all the information from the previous PPS was rolled over automatically to the new version of PPS. I had to manually adjust some areas.

 

[BenScan]

I may have missed it in the various threads and replies, but can a talkgroup be programmed as blocked via PPS?

For my purposes I need to use TG-monitor, but there are a couple talkgroups I would like to permanently block rather than having to do it manually every time. I have not found such a setting in PPS, but I may have overlooked it.

I haven't tried it, but it might be worth experimenting with this idea. Maybe set up the talkgroup with encryption, and just put a random key in, maybe if the key doesn't match it will skip the channel? I haven't messed with encryption at all, so not sure if that's even a possibility.

 

[jimv]

Programming Failed.

I've read through the posts and have not found one related to the problem I am experiencing, so, I'm asking for some help.

I successfully downloaded the PPS and backed up my profile. I closed the PPS and then successfully installed the 1.3 firmware on my G5. After rebooting I confirmed 1.3 was installed (see screenshot). I opened PPS V0.3.16.9 and connected my device. I attempt to program and receive a "Programming failed" popup within a minute every time (see screenshot).

I uninstalled the PPS and reinstalled it and attempted programming again, but, same issue.

I downgraded to firmware V1.2 and opened the new PPS and it successfully programmed. I re-downloaded another firmware 1.3 and installed. Connected to the new PPS and again "Programming failed".

Not sure what I need to do to leverage the features of 1.3 as I cannot enable TGIG Hold Setting etc. and program those features into my G5. At least I know I can downgrade back to V1.2 and use this PPS update TGs, systems, frequencies etc.

Hoping someone can help a Brother out.

Thanks,

Jim

 

[Hit_Factor]

Programming Failed.
....

Hoping someone can help a Brother out.

Thanks,
Jim

Event viewer will likely have an error message stored in it. Launch event viewer, go to windows logs, then system logs. There will be lots and lots of information events. I doubt any of those will have anything worthwhile. Look for Error and Warning events.

As you can see, the events are sorted by when they occur. It might be easiest to open event viewer, then in PPS cause the error.

Here is an example error message. The event ID number near the bottom is what you want to enter into Google to find a solution. This could be a problem with your computer.

 

[bob550]

Hoping someone can help a Brother out.

I would try building a new profile with perhaps only one system programmed and see if you get the same error. There may be some incompatibility with V1.3 in your existing profile.

 

[jimv]

Event viewer will likely have an error message stored in it. Launch event viewer, go to windows logs, then system logs. There will be lots and lots of information events. I doubt any of those will have anything worthwhile. Look for Error and Warning events.

As you can see, the events are sorted by when they occur. It might be easiest to open event viewer, then in PPS cause the error.

Here is an example error message. The event ID number near the bottom is what you want to enter into Google to find a solution. This could be a problem with your computer.
View attachment 90657

Thank you for your recommendation. Since I redownloaded and installed firmware version 1.3 around 1410 hours my time, I reviewed the event viewer around that time period (see attached) and saw a couple of Warnings. One of them (pasted below), might be the issue. I'll continue troubleshooting and thank you again for your help.

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID

{C2F03A33-21F5-47FA-B4BB-156362A2F239}

and APPID

{316CDED5-E4AE-4B15-9113-7055D84DCC97}

to the user xxxxxx\xxxxxx SID (S-1-5-21-111092842-2142062493-2308269392-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.

 

[jimv]

I would try building a new profile with perhaps only one system programmed and see if you get the same error. There may be some incompatibility with V1.3 in your existing profile.

And the winner is, Bob550!

Thank you sir for that recommendation. I created a simple profile with one system and a couple of TGs. and successfully reprogrammed. You can see within the attached I now have the functionality I was hoping for. Now the challenge will be to figure out how to recreate my existing profile with upwards of 40 systems, into a "new" profile. At least I know it's not a hardware or software issue.

Thank you again, Bob.

v/r

Jim

 

[bob550]

And the winner is, Bob550!

Hahaha, what's my prize? I'm glad that worked for you as the V1.3 is a worthy upgrade. Unfortunately, the hard work is ahead as you'd be best by adding back one system at a time to see if the error is reproduced. Perhaps @Uni1 can offer a clue as to what may have gone wrong here.

 

[jimv]

Hahaha, what's my prize? I'm glad that worked for you as the V1.3 is a worthy upgrade. Unfortunately, the hard work is ahead as you'd be best by adding back one system at a time to see if the error is reproduced. Perhaps @Uni1 can offer a clue as to what may have gone wrong here.

I'm working on it now, beginning with the manual addition of all of my VHF frequencies.

 

[wcoriston]

I have a lovely new bug showing its face now where my voice messages are just disappearing at random. I can go to sleep with 43 messages and wake up with 3.

 

[cpetraglia]

I have not tried the conventional part with this new fw. Ive been using the p25 and so far everything is working as ive wanted it to. 1.1 the pager only alerted 1 tone, on 1.2 the pager wouldnt alert at all on p25, now with 1.3 it works even works with stacked tones. I really dont have any complaints except I wish the bluetooth would play audio through my truck. Its connects but no sound.

BT has been my pet peave since I bought my G4. When Unication released it's first G4 and G5 series pager, the BT protocol was 9 years old at 2.1. Now it's like 12 years behind the industry standard.

I believe as long as it works with their own ear bud accessories, that's all that's important to them.

 

[belvdr]

BT has been my pet peave since I bought my G4. When Unication released it's first G4 and G5 series pager, the BT protocol was 9 years old at 2.1. Now it's like 12 years behind the industry standard.

I believe as long as it works with their own ear bud accessories, that's all that's important to them.

Regardless of the version, the real issue is they implement their audio as a phone call, not a media device.