This post from a little over a year ago led to some experimenting and raised some questions:
Post in thread 'Control Channel Programming On NAS'
Control Channel Programming On NAS
I’ll state the question up front, and give some background on why I’m asking. What is the nature of the “flash” memory (in an APX 7000) where the adjacencies are stored that is mentioned in the post above? Such as: is it permanent? If not, what is the mechanism or occasion for purging or erasing? Is it possible to see what’s in it from using the standard APX CPS?
Background: Listening to GATRRS in Texas on an APX 7000 by NAS. Primarily the Austin-Travis site, but often the VHF sites to the West and NW (Blanco, Johnson City, Round Mountain, Llano South, Marble Falls, Burnet and Lampassas). Because of that post, I have been able to evolve my codeplug from having a separate “system” for each site, to having one system (smartzone coverage type) with only the CCs for site 1-7. I use the preferred site section in the personality to “allow” certain sites in the VHF areas. This has been working well, as I can now travel around in those areas (up and down hwy 281) and I’ll hear the various agencies without any adjustment on my part - roaming, if you will. I’ve also confirmed that while sitting at home (where clearly site 1-7 is dominant) I can listen to Blanco County or Marble Falls on VHF sites, while confirming on other devices that those TGs are not being carried on site 1-7.
So I think I’ve confirmed two things in an NAS situation (for this system anyway): 1) the radio will build a list of CCs for neighboring sites and use them; 2) the preferred sites section in the personalities seems to work as designed even in NAS, at least the “allowed” setting does - it will direct listening to specific sites and prevent it from landing on other sites.
Now the reason for the question: When traveling to North Texas on Hwy 281, I’ll go through Lampassas hearing everything fine. I’ll switch to other systems further North (conventional, Granbury, NTIRN, etc). Then on the return trip when I’m passing through again, it will still work on the Lampassas GATRRS site - as if it remembered (again, the system for that personality only has the 800 CCs from the Austin-Travis site). This last time though, I was doing some diagnostics and carried my laptop and cable with me, and tweaked my codeplug for other systems while in North Texas. I figured as I was going back South into the GATRRS area that the “flash” would be gone because of the programming session, and I’d be in the dark until back in range of the Austin-Travis site to start getting data from that CC. But I wasn’t - I started receiving Lampassas PD while in town. Just trying to figure out why - because other than the site ID listed in the personality, there is no specific Lampassas site programmed.
Post in thread 'Control Channel Programming On NAS'
Control Channel Programming On NAS
I’ll state the question up front, and give some background on why I’m asking. What is the nature of the “flash” memory (in an APX 7000) where the adjacencies are stored that is mentioned in the post above? Such as: is it permanent? If not, what is the mechanism or occasion for purging or erasing? Is it possible to see what’s in it from using the standard APX CPS?
Background: Listening to GATRRS in Texas on an APX 7000 by NAS. Primarily the Austin-Travis site, but often the VHF sites to the West and NW (Blanco, Johnson City, Round Mountain, Llano South, Marble Falls, Burnet and Lampassas). Because of that post, I have been able to evolve my codeplug from having a separate “system” for each site, to having one system (smartzone coverage type) with only the CCs for site 1-7. I use the preferred site section in the personality to “allow” certain sites in the VHF areas. This has been working well, as I can now travel around in those areas (up and down hwy 281) and I’ll hear the various agencies without any adjustment on my part - roaming, if you will. I’ve also confirmed that while sitting at home (where clearly site 1-7 is dominant) I can listen to Blanco County or Marble Falls on VHF sites, while confirming on other devices that those TGs are not being carried on site 1-7.
So I think I’ve confirmed two things in an NAS situation (for this system anyway): 1) the radio will build a list of CCs for neighboring sites and use them; 2) the preferred sites section in the personalities seems to work as designed even in NAS, at least the “allowed” setting does - it will direct listening to specific sites and prevent it from landing on other sites.
Now the reason for the question: When traveling to North Texas on Hwy 281, I’ll go through Lampassas hearing everything fine. I’ll switch to other systems further North (conventional, Granbury, NTIRN, etc). Then on the return trip when I’m passing through again, it will still work on the Lampassas GATRRS site - as if it remembered (again, the system for that personality only has the 800 CCs from the Austin-Travis site). This last time though, I was doing some diagnostics and carried my laptop and cable with me, and tweaked my codeplug for other systems while in North Texas. I figured as I was going back South into the GATRRS area that the “flash” would be gone because of the programming session, and I’d be in the dark until back in range of the Austin-Travis site to start getting data from that CC. But I wasn’t - I started receiving Lampassas PD while in town. Just trying to figure out why - because other than the site ID listed in the personality, there is no specific Lampassas site programmed.
