Help me help you

Status
Not open for further replies.

JoeBearcat

Active Member
Uniden Representative
Joined
Jun 30, 2020
Messages
1,883
Isn't that what we started off with on the first page of this thread? I wouldn't have wasted my time or anyone else's otherwise. "Feature request" :rolleyes:

If his spec was non-preemptive priority, adding preemptive priority would be a feature request. That still is not yet known and may prove to be the case. Or we can skip that if you happen to have a copy of his specs. :)
 

cg

Member
Premium Subscriber
Joined
Dec 13, 2000
Messages
4,686
Location
Connecticut
Do you want any 996P2 CC Data Logs from a Hytera Tier III system that will not trunktrack? I can also include a log on the same system on DSDPlus running concurrently. If so, a PM or email through this site or a location to post.

chris
 

JoeBearcat

Active Member
Uniden Representative
Joined
Jun 30, 2020
Messages
1,883
Do you want any 996P2 CC Data Logs from a Hytera Tier III system that will not trunktrack? I can also include a log on the same system on DSDPlus running concurrently. If so, a PM or email through this site or a location to post.

chris

Yes please. I will pm you.

Are you aware of any other models with this issue?
 

cg

Member
Premium Subscriber
Joined
Dec 13, 2000
Messages
4,686
Location
Connecticut
There are several users around that cannot trunktrack the system here. The system uses band plan based channels rather than a logical plan (CC=463.5125, Channel 2165). The frequency information is transmitted in the CC data stream. With DSDPlus, only the CC frequency needs to be programmed.

chris
 

GTR8000

NY/NJ Database Guy
Database Admin
Joined
Oct 4, 2007
Messages
15,738
Location
BEE00
@JoeBearcat Here's something that I haven't seen mentioned, which would be a big help to us dbadmins in receiving correct info for the RRDB: Have the DMR and NXDN capable scanners display the NetID (aka SysID) in DEC, not HEX. Only Motorola 3600 and P25 System ID's should be reported in HEX, whereas it's the industry standard to display DMR and NXDN Network ID's in DEC.

Yes, I concede that would likely be categorized as a low priority feature request, however not following the same standard that everyone else uses can be frustrating.
 

trentbob

W3BUX- Bucks County, PA
Premium Subscriber
Joined
Feb 22, 2007
Messages
5,926
I should probably stop following this thread. I'd hate to say something I shouldn't. I will say that poor JB seems to be taking a beating. :rolleyes:
As was predicted by one of our most 20 notable members #2, for those who don't know about that refer to the top 20 notable members regarding reaction score and see who they are. I'm not a player here as I'm only #7... I'm following and understanding every bit of this but I have been keeping my mouth shut. #2 said the honeymoon will soon be over. Well it's over a little sooner than I thought it would be and that didn't have to happen.

UPM... take care of the business at hand first... Modify the production line to solve and eliminate the cold solder joint problem. Modify the production line to eliminate the annoying hum. Advertise it widely and offer free repair no matter how old the radio is, then you will start to sell more radios. That's what it's all about right?...mmm... uh... RIGHT?

Once you have widely advertised those issues are solved and you are everybody's hero then you can start to work on the bugs. Because of Wendy Whistlers dishonest disclosure of a impending simulcast capable scanner after a vendor released information about the SDS 100 before it was ready for release, it hurt sales and caused the radio to come out way before it was ready. Paul worked hard with firmware updates to bring the radio up-to-date and functioning well as long as he could. We know that whistlers radio was vaporware and would never fit into a carcass of a psr-800 or psr-900 and come to fruition, they hurt Uniden sales as hapless Whistler fans sat on the edge of their chairs with fistfuls of money waiting for a radio that did not not exist. Paul delivered, he hit the home run. He made regular firmware updates that fixed the major problems with the radio, it was a work in progress and came out great.

Pace yourself UPM, you are up against a lot of very very smart people here... but... You're the man, fix the major flaws that are keeping people from buying the radios, if you need to offer a repair campaign then just do it and get it in the past. Then start to work on the bugs and the minor flaws.

You know it better than anybody, these ARE your flagship radios of the future and can be improved so much, there's so much left inside of them and you know it.

As always, no need to respond as you haven't in the past, just one man's opinion, as I'm entitled to... It's well intended... LOL. Hang in there. As I said you have three things to deal with, your superiors, your customers and yourself... I think you'll do well with the last two, as far as the first...??? :LOL:
 
Last edited:

JoeBearcat

Active Member
Uniden Representative
Joined
Jun 30, 2020
Messages
1,883
@JoeBearcat Here's something that I haven't seen mentioned, which would be a big help to us dbadmins in receiving correct info for the RRDB: Have the DMR and NXDN capable scanners display the NetID (aka SysID) in DEC, not HEX. Only Motorola 3600 and P25 System ID's should be reported in HEX, whereas it's the industry standard to display DMR and NXDN Network ID's in DEC.

Yes, I concede that would likely be categorized as a low priority feature request, however not following the same standard that everyone else uses can be frustrating.

That was discussed years ago. It really didn't go anywhere. But I am a fan of user options.
 

R0am3r

Salt Water Conch
Premium Subscriber
Joined
Apr 13, 2014
Messages
742
Location
Oneida County, NY
I should probably stop following this thread. I'd hate to say something I shouldn't. I will say that poor JB seems to be taking a beating. :rolleyes:

Oh c'mon.. @JoeBearcat is a big boy and is doing great. I'll wager that he can change the tone of this thread with one post about an imminent firmware update. If the update does nothing but provide the option of displaying the P25 NAC in Octal, most of you will rush to update your scanners, hail his genius, and then curl up into a ball while crying your eyes out because Uniden hasn't abandoned their users.
 

Ubbe

Member
Joined
Sep 8, 2006
Messages
9,243
Location
Stockholm, Sweden
ill give Illinois as an example here is what it contains after I avoided the 8 sites on wheels for Starcom 21 Illinois is 47 but Starcomm21 is multi state so has an ID of 0 which may be the problem

now it is saving but somehow it gets wiped out after I read the radio
Looks like a simple bug related to StateId=0 that can be easily corrected.

/Ubbe
 

WX4JCW

Member
Premium Subscriber
Joined
Jun 26, 2006
Messages
3,403
Location
Stow, Ohio
Oh c'mon.. @JoeBearcat is a big boy and is doing great. I'll wager that he can change the tone of this thread with one post about an imminent firmware update. If the update does nothing but provide the option of displaying the P25 NAC in Octal, most of you will rush to update your scanners, hail his genius, and then curl up into a ball while crying your eyes out because Uniden hasn't abandoned their users.
i can only curl into a ball if Uniden provides me a puppy
 

MStep

Member
Joined
May 2, 2005
Messages
2,183
Location
New York City
NEW AVOID OPTION REQUESTED

We currently have "Temporary Avoid" and "Permanent Avoid". What the SDS series could really use is a new avoid mode, "TIMED AVOID". This would be used when you want to avoid a frequency, TGID, System, etc, for a 'timed period", for example 1 minute, 5 minutes, or perhaps something in that range. Maybe something that is also a user programmable time period.

This would be very useful in situations for stuck carriers, superfluous transmissions, and other kinds of events that you want the radio to avoid for a few minutes and then come back into the scan cycle for re-evaluation without having to power down and power up the radio, which eliminates all temporary avoids. (I don't recall seeing this requested previously, if so, my bad.)

The sequence for activation could be one press avoid for "timed", two press avoid for "temporary" and three press avoid for "Permanent".
 
Status
Not open for further replies.
Top