I have a couple of observations and questions regarding the Midland P25 system. First, I have an observation of strange behavior with the BCD436. The first time I was in town I hadn’t updated the db so I programmed the Midland P25 system by hand in my favorites list and gave it its own QK. I started up and ran only that – it literally took about 2 minutes to lock onto the control channel (I had only programmed the control channel and alternates), but once it did, it worked fine – until I turned on another system. First I turned on Texas DPS (conventional system) and it seemed to knock the Midland P25 system off line, and it took another couple of minutes before it had a lock on the CC. However, when I turned on another P25 system (PBRIN), I never heard another peep from the Midland P25 system and I never did see any bars for that system while scanning (full bars when it was the only system, after a minute or two). But when I disabled the others, it finally started picking up the Midland P25 system again. By the way, the 436 handled the audio pretty well – both Phase I and II TGIDs. I went back a few weeks later and had programmed the system from the db in a favorites list – same kind of behavior. Has anyone else noticed that kind of behavior from the 436 on that system?
Second, does anyone know the WACN and SysID for this system? It’s not in the db so I programmed the Unication G5 with the wildcards (WACN:FFFFF; SysID:FFF) – it never showed any bars on any CC (had all freqs programmed in) before the “out of range” timeout. Maybe I should not have programmed all freqs in. I’m fairly new to the G5 and have that info for all the other systems. Unfortunately I didn’t take the laptop on that trip, so I could not play with it at all – I definitely will next time out there. If nobody knows the WACN/SysID, does anyone know a better way to program the G5 to find the system (I’m thinking maybe ONLY the one CC)?
Finally, just a report on the PSR800 on that system. No problem at all scanning the system – picked it up as soon as turning it on about halfway between Stanton and Midland, and running other systems at the same time were no problem. BUT, the voice decode was terrible – I had occasional intelligible audio, but it was probably 70% R2D2 sounding garble – that was the same on Phase I and II TGIDs.
Thanks for any help or feedback.
Second, does anyone know the WACN and SysID for this system? It’s not in the db so I programmed the Unication G5 with the wildcards (WACN:FFFFF; SysID:FFF) – it never showed any bars on any CC (had all freqs programmed in) before the “out of range” timeout. Maybe I should not have programmed all freqs in. I’m fairly new to the G5 and have that info for all the other systems. Unfortunately I didn’t take the laptop on that trip, so I could not play with it at all – I definitely will next time out there. If nobody knows the WACN/SysID, does anyone know a better way to program the G5 to find the system (I’m thinking maybe ONLY the one CC)?
Finally, just a report on the PSR800 on that system. No problem at all scanning the system – picked it up as soon as turning it on about halfway between Stanton and Midland, and running other systems at the same time were no problem. BUT, the voice decode was terrible – I had occasional intelligible audio, but it was probably 70% R2D2 sounding garble – that was the same on Phase I and II TGIDs.
Thanks for any help or feedback.
