Pro96com and BCD325P2

Status
Not open for further replies.

FlashP

Member
Joined
Dec 19, 2002
Messages
196
Reaction score
0
I just noticed weird behavior with the 325 and Pro96com: it's missing the patches. I don't know whether the radio misses them completely, or the interface between hardware and software is losing them.

The local P25 Phase 2 system has two TGs patched (59208 & 209), they toggle "add" and "remove" with each transmission. Using a 396XT, the program shows and tracks these transmissions... with the 325P2, neither the patch nor the individual groups are shown at all.

Attached files were logged minutes apart. 396XT reception is lousy and intermittent, but it logged patches. 325 was solid but it didn't show the patched transmissions, which I monitored on a separate receiver. Any ideas?
 

Attachments

  • PSRDump-201_325P2.txt
    49.6 KB · Views: 133
  • PSRDump-201_396XT.txt
    89.6 KB · Views: 113
  • GrantLog-201_325P2_csv.txt
    196 bytes · Views: 97
  • GrantLog-201_396X_.csv.txt
    3.5 KB · Views: 118
  • PatchLog-201_396XT_csv.txt
    713 bytes · Views: 94

mikey60

Member
Joined
Sep 15, 2003
Messages
3,543
Reaction score
55
Location
Oakland County Michigan
Looks to me like the data output on the 325P2 has some issues. It looks like some TSBKs are missing in the decoded data sent to the program.

Just in the first 10 lines there are 4 TSBKs that as presented are invalid. If they passed the CRC, they would get logged as unknown packets.

P25,300000042A1EFE04B16CC5A9 - OK
P25,8940C02A9540558C800A0430 - OK
P25,37FD00003715813C0111EE6D - OK (First of 2)
P25,2AFF2918700000006BEDB851 - OK (Second)
P25,340025083C64019FFA0026E8 - OK
P25,1FABFFF0067C080399420000 - Invalid MFGID
P25,340055053FF401955600754D - OK
P25,5FEAA803C3EBCA2F00B2EC5B - Invalid MFGID
P25,0010E749E749E749E742FEC0 - Invalid MFGID
P25,142AC604202A0003FFFE0007 - Invalid MFGID

It's possible these are the second or third part of a multi-part TSBK, but it's hard to tell.

Mike
 

FlashP

Member
Joined
Dec 19, 2002
Messages
196
Reaction score
0
I see a post under "Uniden" about the 996P2 not tracking patches... I haven't seen that problem, but when in scan mode I have both TGs programmed so it may be masked.

No change with "Extended".
 

mikey60

Member
Joined
Sep 15, 2003
Messages
3,543
Reaction score
55
Location
Oakland County Michigan
Actually the second packet in my previous post is also invalid MFGID value so 5 out of the first 10.

I note the Motorola signature packets in the overall dump file, so these are definitely not packets that should exist. I do see some valid patch announce packets in there but nowhere near the normal frequency of them I would expect to see. Probably why the patch log is showing the patches coming up and down to much.

Mike
 

FlashP

Member
Joined
Dec 19, 2002
Messages
196
Reaction score
0
In the XT output (which was only about 40% copy), the patches seem to be announced only when they're actually transmitting; they evaporate from the Pro96com display tab shortly after the Group grant goes away. I don't see a problem there - just a feature of the system.

The 325P2, on the other hand, has a major flaw.
 

mikey60

Member
Joined
Sep 15, 2003
Messages
3,543
Reaction score
55
Location
Oakland County Michigan
That could be a weak signal issue there. Patch announcement on the MPSCS where I live are pretty constant. They change though depending on what radios are affiliated with the site in question.

Mike
 

FlashP

Member
Joined
Dec 19, 2002
Messages
196
Reaction score
0
Nah, it's the same way when I move to a spot with 100% copy. The patch log is almost as big as the grant log.
 

mikey60

Member
Joined
Sep 15, 2003
Messages
3,543
Reaction score
55
Location
Oakland County Michigan
Very odd. Pro96Com will keep a patch active without an update from the control channel for a pre-set amount of time, at which point it will time out and be removed. With those messages being sent so far apart, that's what's probably happening there.

Mike
 
Status
Not open for further replies.
Top