I'm willing to bet that's PEBCAK. Either that or his radio failed to get an OTAU channel plan update, which I hear is a big functionality perk of this system (so every radio doesn't have to get serviced every time they add a new TG)
More of it this evening though I couldn't catch a location. Sounds like that's widespread radio testing going on all over the place- heard callsign PMO (perhaps Project Management Office?) doing the portable testing at Shock Trauma with a 'Base' station using 2125701 during that time you mentioned yesterday. Notably, both radios were in the 212#### series, not the 211 used by MdTAP. However, I did see 2125701 come up on PORT's TG with no voice sometime yesterday- this spread may indicate that Base and possibly PMO's radio are FiRST project staff conducting initial testing.
Interesting, though, that the TG they were using was 8561 when the new MSP-M simulcast is on 8564. If that's where MSP-M is going to stay (which is anybody's guess) maybe that's another State TG.
Though you're right, time will be the telling point. Right now I'm just babbling guesses... probably because I have too much time on my hands.
EDIT: Also updated RID list in the Wiki in case anybody wants to pull from that or add to it. (again way too much spare time)
Since this trunk is listed as Phase II in the database (and only the PSR-800 can do it - albeit with a serious problem with X2 decoding - with the recently-released beta firmware) I assume all you guys are using 800s to track this? Or is FIRST running Phase I during the break in period?
Curious...Mike
My understanding is that the entire system is Phase II TDMA. We were told you must have an APX series radio to talk on the system.
dpcain said:I'm willing to bet that's PEBCAK. Either that or his radio failed to get an OTAU channel plan update, which I hear is a big functionality perk of this system (so every radio doesn't have to get serviced every time they add a new TG)
ka3jjz said:Since this trunk is listed as Phase II in the database (and only the PSR-800 can do it - albeit with a serious problem with X2 decoding - with the recently-released beta firmware) I assume all you guys are using 800s to track this? Or is FIRST running Phase I during the break in period?
Curious...Mike
troymail said:It's probably an option but in theory there is supposed to be a "compatability" capability such that if a Phase 1 radio appears on a talkgroup, that talkgroup automatically goes to P1 mode for the duration. Of course, that then consumes 2 slots or "channels" for the duration which isn't good - particularly if you only have a small number of frequencies to start with. This is the mode PG is operating under using X2. The problem is if any P1 user simply turns the radio on the listen on a X2 (and P2?) system, it effectively immedately degrades the system capacity so I can understand why the State may not want to do that. Another reason might be to "nudge" people into coming onto the state system rather than keeping their own (and Motorola wants to sell more radios!)
The control channel still consumes a full (two slot) frequency (for now anyway) - which is actually bad because it still suffered somewhat from the modulation issues we've all experinced in the Phase 1 systems that have popped up in the area recently.
(Pvt) data (GPS, etc.?) consumes the full frequency (and appears alot but for very short durations).
dpcain said:I suspect the novox keyups are users testing system connectivity by making sure they get the go-ahead beep when they TX. I don't usually see that phenomenon with active users (MdTA K P and TC units)
So rather than "the radio gets absolutely everything to do with knob and zone assignments from the control channel upon affiliation and that information isn't permanently stored in the radio" which is one way to read what you just said, I think what you're trying to tell me is that upon affiliation, the client radio receives updates to its own knob-and-zone assignments when applicable from the control channel. That knob-and-zone assignment, which I think as a former Phase I user (though I'm clearly not the brightest bulb in this thread) logically must be stored in the radio so it is still usable in failsoft and direct functionality in event of failsoft fallback or going out of range of the system, is what I meant by the possibly not-perfect-techie-jargon term 'channel plan'.You don't use "channel plans" on these radios as you do scanners. If the control channels are in there (which being so new they will be fairly current) it gets what it needs to talk from the control channel. Its also called OTAP (Over the air programming) and is an option on these systems.
And I read in several places as this system was being installed pre-testing that one of the major concerns of the FiRST team is that with a limited number of frequencies available they will have significant capacity issues if FDMA radios frequently affiliate with FiRST once it is at full running capacity- seems like similar stuff to what troymail is referring to (if not the same publications). Without offending your sarcasm, I don't think we plebes are at all assuming that this system has been planned by two guys running on a cranium-sphincter force feedback loop: instead we are using what we've gleaned from observation and research to draw out possibilities and talk over issues.It is true that if a FDMA radio affiates to a TDMA system is will go back to a 12.5 channel, but when designing systems to support this, that capacity is looked at and built out to support it. Its not like there are two guys sitting in a room with a sales guy. We have entire teams and reams of paper (yes paper) with all sorts of coverage and capacity solutions with the budget limitiations and to work within stated goals and performace specifications.
Turn who off? I'm just curious, I don't know what you mean. And yes, quite right- that's exactly what I'm seeing. A quick press with perhaps a quarter second of actual transmission of background noise. Sometimes not even that- just an RID popping up on my recording list, taking up about a second of recording space with no audible transmission at all.If (and some departments turn them off) they are doing this, it only requires a quick press. If they are not getting a channel grant they will get a bonk tone in either configuration. If they were truely playing around, there would be a good chance that you would hear some sort of nearby feedback. We see this all the time when conventional users get their first trunked radios. Sometimes you hear good things.
I'm aware that what I'm hearing is an echo, and all of that is standard but programmable. What I was saying is that what I heard in that echo was not what I remember as the go-ahead-and-talk beep from motorola radios (albeit that's a memory from using XTS radios, not the new APX, but as you said yourself that shouldn't matter), but sounded exactly like the Harris version of that, indicating to my ears that I was hearing somebody in an echoing hallway talking into a Harris radio.The tones are the same since the first radios brought to market had them. You can also have some additional tones but what your normaly hearing is an echo from inside the patrol car. I have an addition tone set to mine with the encyption features enabled. Its all in the programming.
Oh weird, so FMT is coming out over the QA site too? huh, guess some of their radios must be affiliating with it instead of BC.. or somebody over there like a bay bridge unit was listening.
(FYI 8564 is at last check a simulcast of MSP Barrack M VHF)
When you guys updated from Library 159 to 160 did you get the five new talkgroups? I didn't and I'm trying to figure out why. I performed the update and followed all of the prompts. I checked the CDAT on the PC first and it didn't show the new talkgroups and then I also did it on the scanner and no new groups were added. The only thing that I've done with the system is change the alpha tag for the system name, but was told that it doesn't matter. I was just wondering how all of you made out.
Thanks,
Rich C