Before the update the radio id was on line 5 in large yellow...after the update the rid is on line 6 in small white. Line 5 now has a big yellow worthless tg id of either 1 or 4095....it still has to be a 1 freq trunk sys to see the rid's.....
HomePatrol-1 Extreme Upgrade Post-Release Thread
- Thread starter UPMan
- Start date
- Status
Wow, the lengths some people will go to to complain...
If you've got a one-frequency trunk system (which, if you're getting a talkgroup, is what you have, not a "conventional" P25 frequency), the talkgroup is being transmitted. If you're seeing 1 and/or 4095, then your "one-frequency trunk" actually has two talkgroups in use. The local "conventional P25 frequency" always sends a TG of 1 for me too.
The fact of the matter is, the radio ID is secondary to the talkgroup in a trunk system, regardless of whether it's a one-frequency trunk, a Motorola system, a P25 system, or an EDACS system. The TG should always be displayed on the "Channel" line and the radio ID, if available, should be displayed in addition to (but not in place of) the TG. The only time when a radio ID would/should be displayed without a talkgroup is in a private call (I-Call).
Feel free to lobby for larger text or text with better contrast for the radio ID. But don't try to get the talkgroup obscured again after we just succeeded in getting it to show up again in the 2.01 update. Not every system is like the one you are trying to monitor, and many people need/want it to be the way it is now.
If you've got a one-frequency trunk system (which, if you're getting a talkgroup, is what you have, not a "conventional" P25 frequency), the talkgroup is being transmitted. If you're seeing 1 and/or 4095, then your "one-frequency trunk" actually has two talkgroups in use. The local "conventional P25 frequency" always sends a TG of 1 for me too.
The fact of the matter is, the radio ID is secondary to the talkgroup in a trunk system, regardless of whether it's a one-frequency trunk, a Motorola system, a P25 system, or an EDACS system. The TG should always be displayed on the "Channel" line and the radio ID, if available, should be displayed in addition to (but not in place of) the TG. The only time when a radio ID would/should be displayed without a talkgroup is in a private call (I-Call).
Feel free to lobby for larger text or text with better contrast for the radio ID. But don't try to get the talkgroup obscured again after we just succeeded in getting it to show up again in the 2.01 update. Not every system is like the one you are trying to monitor, and many people need/want it to be the way it is now.
I 2nd that. Don't change anything.
I would also add that the UID decoding is much better now also.
Sent from my iPad using Tapatalk
I would also add that the UID decoding is much better now also.
Sent from my iPad using Tapatalk
I meant to make mention of that. On digital talkgroups, it would appear that the RID (UID) is coming up even on continuations (i.e. in the middle of the conversation). On analog TGs (my only UID-equipped system in range is a Motorola mixed mode), it only comes up on the initial grant, not if you jump in in the middle of things. Still, much better than before.
...sigh...
Keep it like it is, honestly it is fine, only thing i might vote for are different color themes but that isnt a huge issue
Viper43
Member
- Joined
- Jul 23, 2005
- Messages
- 3,272
lol, if we had different color then the color blind would complain..... (being sarcastic....I think...)
Looks to me like UID alpha tags truncate at 14 characters if the talkgroup ID in 4 digits and truncates at 13 if the TG ID is 5 digits .... at least that's what is happening on my display ... I think.
I have two identical alpha named UIDs, one truncates at 13, the other at 14 and the only thing I can spot is the TG IDs are different. Anyone see the same ?
I have two identical alpha named UIDs, one truncates at 13, the other at 14 and the only thing I can spot is the TG IDs are different. Anyone see the same ?
EJB
20 + year membership
Thank you Upman for another free (and painless) update
EJB
20 + year membership
Double sigh.....
EJB
20 + year membership
I could take this so many places.....but why would Uniden want to keep you from your wife...and possibly loose a future customer
Cause I have to constantly mess around with the HP and Sentinel, Lol I am not complaining.
Viper43
Member
- Joined
- Jul 23, 2005
- Messages
- 3,272
I just couldn't resist....
Anyway, yeah, I keep using the Discovery on different trunked systems. I am actually setting up a schedual so I can look at that and run discovery on specific systems for the events and hopefully come away with some new TGID's that are not known. I also run discovery when there is a major incident to see if somethin new appears. Today a new TGID poppred up on one system before a parade and that TGID has never come up before.
Anyway, yeah, I keep using the Discovery on different trunked systems. I am actually setting up a schedual so I can look at that and run discovery on specific systems for the events and hopefully come away with some new TGID's that are not known. I also run discovery when there is a major incident to see if somethin new appears. Today a new TGID poppred up on one system before a parade and that TGID has never come up before.
EJB
20 + year membership
I set myself up pretty good
Seriously, this is a darn good radio, Any feelings of regret after buying it are gone.
I used this the other day looking for a repeat (and audio capture) of something that popped up on a local TRS seen on a different scanner. I ran it in "New Only" mode. Now, the question I have is in relation to how this works.
In reference to Discovery - "New Only" mode:
As it is scanning, does it actually skip all known TGs?
Or, does it actually stop on all TGs and just not log/record them?
I guess that really is two questions but one topic. The reason I ask is after a 2 day run it revealed 4 new TGs with minimal audio in them and some of the audio seemed to be in the middle of conversations, like it was already going on (which I could understand) but also I lost the end of the conversation and none of the audio I got ever went to the limit I had set (120 sec). In other words, it was like it was loosing the target conversation but then getting hung up on something I was ignoring.
The end result was of the 4 new TGs identified, only one had enough audio to make a guess at what it was and it was the longest stretch of audio recorded (54 secs) but it was severely fragmented. Obviously I can load these finds into another scanner (or the HP-1) and scan only on them to see what develops but ...
That's not my experience with trunked discovery mode. The recordings are clear and identifiable (so long as they have some "meat" to them and aren't just somebody clicking a mic or yelling "WHEREUAT?!").
Logging "New Only" stops only on unknown TGs. Logging "All" also only stops on unknown TGs, but marks in the summary/detail log that it is getting hits on the "known" TGs (but not recording them).
"Compare to database: Off" treats the entire system as unknown TGs and records everything.
Logging "New Only" stops only on unknown TGs. Logging "All" also only stops on unknown TGs, but marks in the summary/detail log that it is getting hits on the "known" TGs (but not recording them).
"Compare to database: Off" treats the entire system as unknown TGs and records everything.
Jay,
Thanks for the insight. Well I had it set to only record and log new and compare to the DB, so I am not sure what happened. The site I was monitoring is very active and, if listening to it, seldom goes less than 5 or 10 seconds without some activity, so I was grasping at straws trying to figure out why it didn't do what I though it would. I guess I will just resort to using IDTracker instead. Sounds like I need to finish setting up the listening post.
Thanks for the insight. Well I had it set to only record and log new and compare to the DB, so I am not sure what happened. The site I was monitoring is very active and, if listening to it, seldom goes less than 5 or 10 seconds without some activity, so I was grasping at straws trying to figure out why it didn't do what I though it would. I guess I will just resort to using IDTracker instead. Sounds like I need to finish setting up the listening post.
Viper43
Member
- Joined
- Jul 23, 2005
- Messages
- 3,272
I had some odd hits on Indys MECA system, turns out that some were actually from STARCOM21 in Ill somehow gitting into MECA. The strangest thing is some of those TGID's were clearer than MECA's own TGID's. Not sure how thats getting into the mix but it does.
As for the amount of time for recording Lou, it only records what it hears, and what you seem to be getting is what I got off Columbus Public Safety the other night where, as above it was another system coming through. Turned out one recording gave the county as the officer called in he says "Tippecanoe County". Odd, never heard them at home before! Tried the actual system and nothing, but it comes through at times while running Columbus Public Safety.
The only two things I can think of are, one, repeaters somewhere are picking up a signal and sending it through the other system somehow or, in the case of Ill StarCom21 it would seem it might be a microwave link somwhere thats getting mixed with MECA. I doubt I am actually hearing the Ill system on the East side of Indy though. The giveaway that it was StarCom21 was a couple calls, one for a gas leak in Danville on 4316, which just happens to be a gas company TGID in Danville Ill on StarCom21. The other clue was Ashkum (sp?) and the TGID's for that traffic matching the Ashkum Ill ISP Post.
So maybe what you have there is a mix of more than one system somehow such as what I am seeing. It does make ID'ing them interesting, but aggravating when the traffic is sporadic at best. But the HP can only record what it actually hears too.
As for the amount of time for recording Lou, it only records what it hears, and what you seem to be getting is what I got off Columbus Public Safety the other night where, as above it was another system coming through. Turned out one recording gave the county as the officer called in he says "Tippecanoe County". Odd, never heard them at home before! Tried the actual system and nothing, but it comes through at times while running Columbus Public Safety.
The only two things I can think of are, one, repeaters somewhere are picking up a signal and sending it through the other system somehow or, in the case of Ill StarCom21 it would seem it might be a microwave link somwhere thats getting mixed with MECA. I doubt I am actually hearing the Ill system on the East side of Indy though. The giveaway that it was StarCom21 was a couple calls, one for a gas leak in Danville on 4316, which just happens to be a gas company TGID in Danville Ill on StarCom21. The other clue was Ashkum (sp?) and the TGID's for that traffic matching the Ashkum Ill ISP Post.
So maybe what you have there is a mix of more than one system somehow such as what I am seeing. It does make ID'ing them interesting, but aggravating when the traffic is sporadic at best. But the HP can only record what it actually hears too.
Viper,
Thanks for that added insight. I am not sure it is applicable in my case though. Basically what I am monitoring is the TxWARN P25 system and most TGs on it can be verified by checking what the related TG is on the TxWARN Moto system. In other words the one TG I was able to get enough audio was TG 1118. That is the same as TG 17888 on the TxWARN Moto TRS. It is SmartX'd to the P25 TRS whenever a radio is affiliated with 1118, so I know there is more traffic on it.
I need to see if I can put a test together and see if I can figure out what is going on.
Thanks for that added insight. I am not sure it is applicable in my case though. Basically what I am monitoring is the TxWARN P25 system and most TGs on it can be verified by checking what the related TG is on the TxWARN Moto system. In other words the one TG I was able to get enough audio was TG 1118. That is the same as TG 17888 on the TxWARN Moto TRS. It is SmartX'd to the P25 TRS whenever a radio is affiliated with 1118, so I know there is more traffic on it.
I need to see if I can put a test together and see if I can figure out what is going on.
- Status
