Out of curiosity... Which programing software are you using? (Manual programming of even these `simple' trunk tracking scanners is fraught with multiple `gotchas' that using either of the 2 `leading' programing packages can/will eliminate. [Disclaimer: *I* have and use *both* WIN97 and PSREdit300 for programming these particular `style' radios.])
Having said that... *I* would first check to see if you actually have the correct banks activated, then check to see if you have the correct talkgroup `sub-banks' selected for the trunked system you want to listen to. (The main difference between `closed' and `open' for the banks is whether or not one hears just the programmed talkgroups or *all*, not just the programmed programmed, talkgroups on said system. In this case I wouldn't begin to worry about it being a problem.) Having made *that* check, though some would say that it would be the second check, the next check I'd make would be to make certain that the control channels, or in the case of a system that requires frequencies that have to be programmed in a LCN order, that had been entered were not locked out, or improperly locked out, by some happenstance. (The reasoning for my `order' of checking is that the first things I looked at are basically `main screen' items for each bank. Checking the `lockout status' of the control channels, conventional channels, and also talkgroup IDs within the `sub-banks', are separate `scroll-able' `windows' within that `main screen'.)
Now, with my PRO-2055s/97s, I have tried to keep the number of `conventional' freqs programmed into various trunked banks down to an absolute minimum preferring to, if possible, to dedicate a separate bank to them. Even though it can sometimes `eat up' banks it helps keep things a bit easier to listen to quite a bit of the time. (I *will* admit that when I only had a single PRO-2055 and PRO-97 {GAACK! That was such a long time ago! GRIMACE!} I *did* tend to try and cram as much as I could into each bank. SWMBO can relate many `horror tales' about times when I was almost going nuts trying to lock and unlock things just trying to stay on top of a `developing situation' without getting interrupted by something not even vaguely associated with whatever it was I was trying to follow because I had a bank to `cluttered'!) The other `side effect' of doing so meant that if I was trying out listening to a new system it made it a lot easier to trouble shoot my programming of that system. Eventually one ends up with certain systems one listens to the majority of the time and has other, separate, programming files that one can upload whenever needed.
If you haven't yet picked up some programming software I urge you to go and get at least WIN97 and PSREidt 300 and take advantage of their `trial periods' and give them both a good workout. Not only will that help you decide which one you like to use but, it will greatly help figuring out what your problem(s) may be and correct it/them. (Another disclaimer: For my PRO-2055s/97s *I* prefer WIN97 because one can have multiple programming files loaded into it at one time and can much more easily `cut-n-paste' data between the various files as needed. I will also admit that I do find a few times when PSREdit300 can do things easier and then I use it instead. But, then, I will also admit that I am a bit of a gadget/software `phreque'/`collector' and have *many* such `duplicates' around. {WAN GRIN!})
Oh, yeah... I am *also* known to write rather long`epistles' for replies. {GRIN!}