Stuck on “Preparing Programming Data”

[Enjoi19]

Hi all,

Now that I’ve owned my G4 for a bit I decided to go through and redo a fresh profile the way I wanted to. Spent a few hours at it and was happy. Went to go program it and it’s stuck on “Preparing Programming Data”. Left it for several minutes, tried a few attempts but it never uploads to the G4. Just spins endlessly. The program is not frozen or hung up. But it does increase its resource use significantly, so something has it stuck.

When I go back to my old profile, it will upload fine.

- Both profiles have the same version

- I’ve reinstalled PPS.

- Removed profile and imported again.

Any ideas? I can spend some time hacking away at the existing profile but I spent a fair bit of time mapping out a ton of radio IDs I’ve got for the main system I monitor and manually inputting them. Would rather not do it again but if I have to..

 

[jonwienke]

How many radio IDs?

 

[Enjoi19]

How many radio IDs?

Around 300

 

[jonwienke]

That shouldn't be enough to overload/hang the pager. Sounds like a PPS or firmware bug.

 

[Enjoi19]

That shouldn't be enough to overload/hang the pager. Sounds like a PPS or firmware bug.

Definitely don't think I overloaded it - got only a handful of conventional, 12 trunked, 14 zones total, and 300ish IDs. It definitely doesn't like something along the line. Maybe just have to start over.

 

[jonwienke]

Any possibility the profile model is set wrong?

 

[Enjoi19]

Any possibility the profile model is set wrong?

There's the two side by side. I even ran it through the conversion tool just in case it was confused, no dice.

Just made a brand new profile and one system in it, and it uploaded instantly. Guess I'll start from square one and slowly upload as I progress along to see where it fails.

 

[bob550]

Any ideas? I can spend some time hacking away at the existing profile but I spent a fair bit of time mapping out a ton of radio IDs I’ve got for the main system I monitor and manually inputting them. Would rather not do it again but if I have to..

Did your previous profile also contain radio ID's?

 

[Enjoi19]

Did your previous profile also contain radio ID's?

It did.

I'm in the midst of redoing things now, with the RIDs and will update soon on how it goes.

 

[Enjoi19]

Added in my main couple of systems and about 160 IDs. No issues uploading, I'm a bit distant from the nearest one but it picked up.

Might just have to chalk this one up to software bugs. Though hard to narrow down much.

 

[Enjoi19]

I continued recreating my problematic programming and found the issue. When I imported from RR, some of the TGIDs were the same on 2 different systems. This seems to be what hung it up, once I removed the second ones it worked fine. Guess if I happen to go out to that region, I'll have to make a separate profile for it.

 

[jonwienke]

Unication's handling of talkgroups is completely borked for multiple systems. Dumping them all together into one pool instead of keeping them associated with a particular system causes all sorts of issues.

 

[Enjoi19]

Im surprised it doesn’t throw a flag for duplicates like it does for RIDs. Very odd really.

 

[CFP387]

I have experienced this problem with PPS v3.16-20 but when I upgraded to v3.16-21 I haven't had any trouble.

 

[kearthfan101]

I'm glad someone else is having the same issues. I am running PPS v3.16.21 and have pulled my hair out the last week with this issue, and I agree, I bet it is the duplicate TG ID's shared by multiple systems. I tried going through and cleaning them up but there really isn't much I can do since they're mainly for local systems.

I'm at 52 zones, 51 systems, 1330 groups, and 549 ID's so I'm not exactly the perfect citizen, but I agree wholeheartedly as well with jonwienke that the TG's should be sorted into the system they belong to...

I should also add that it gets held up on the "programming data" screen for 5-10 minutes before finally responding and eventually writing to the pager. So it does eventually work, but you gotta let it sit there a while.

 

[bob550]

I continued recreating my problematic programming and found the issue. When I imported from RR, some of the TGIDs were the same on 2 different systems. This seems to be what hung it up, once I removed the second ones it worked fine. Guess if I happen to go out to that region, I'll have to make a separate profile for it.

When performing any large-scale RR import, you'd have to sort the resulting Group List by TGID to check for duplicates.

 

[Enjoi19]

When performing any large-scale RR import, you'd have to sort the resulting Group List by TGID to check for duplicates.

This was actually a fairly specific import - not a huge statewide system or anything like in the US we often see, just a few different cities fire departments here. But definitely would be necessary on some of the huge systems. Generally I go through and omit things I'm not interested in (fire prevention, training). It turned out the reason why I'd never experienced it previously with the same systems was because some of these talkgroups that were conflicting are new paging ones that weren't previously there (One system has been coming together slowly the past few months). But it's a distant one I don't go too close to often.

 

[bob550]

I would expect neighboring systems not to have identical TGID's, but distant ones could. That said, if PPS doesn't fuss about duplicates upon entry into the list, it shouldn't complain when programming the pager either. In all, it smells like a bug.

 

[Enjoi19]

Just in case anyone local to Ontario runs across this thread - Waterloo has new talkgroups that have some matching IDs to Toronto

Toronto Emergency Services Trunking System, Toronto, Ontario

Toronto Emergency Services Trunking System Profile

www.radioreference.com

Waterloo Region Trunking System, Tri-Cities Area, Ontario

Waterloo Region Trunking System Profile

www.radioreference.com

 

[kearthfan101]

same for ICI and LA-RICS in Los Angeles CA

Interagency Communications Interoperability (ICI) Trunking System, Los Angeles County, California

Interagency Communications Interoperability (ICI) Trunking System Profile

www.radioreference.com

Los Angeles Regional Interoperable Communications System (LA-RICS) Trunking System, Los Angeles County, California

Los Angeles Regional Interoperable Communications System (LA-RICS) Trunking System Profile

www.radioreference.com

Really hoping it's a bug!!