- Status
Update went through without any problems. Thanks Uniden and Upman!! You guys rock.
@Buddrousa I let the LCN FINDER run all day long without succes. It found the first LCN rapidly but lost signal after so it can't find the others LCN.
the only way to bypass this problem : I deleted the found LCN and rerun LCN FINDER and so on.
After new firmware update, my scanners will not hold on a site anymore when listening to a P25 phase 1 system. When I hold on a site/channel, the Dept still cycles through all the sites in my county. Before, when I used hold on a site/channel, it would actually hold on the particular site I wanted. Not sure which update worked properly last but after reading others with problems, I noticed it myself. Please fix so that I can hold on a particular site like before. As it is now, I would have to make a favorites list for every site in my county.
I've tried all combinations and scanner still cycles through all the sites in my county. It holds on the entity but still cycles through every site in my county. It would actually hold on the site in some previous versions.
No, I do not see the words Site Hold on the screen. No matter what sequence I use the System, Dept, Channel Hold, my scanners still cycle through all the county sites. For the last 4 years when I Hold on Channel, it would lock that particular site until I released the Hold.
I can Push the DEPT/SITE button and all 5 of my X36's hold on the site are you using Firmware 1-21-00
Just tested these as I type.
Just tested these as I type.
That is a design change, not a bug. Holding on a channel or department no longer holds on a site. Older firmware versions would hold on whatever happened to be active when you placed a channel or department hold. Now you have to hold on the site (FUNC, then DEPT) if you want the scanner to hold on a particular site. The new functionality allows you to choose which site is held; the old way only allowed you to hold on whatever random site happened to be active when you placed the department or channel hold.
Thanks Jon, I tried the FUNC, then DEPT and it works great. Didn't know about that new feature. All Good. Before, I could see what site was active (436 Only) before I held on that particular site as the 436 shows more info than the 536. Thanks again for the lesson.
Guess I never knew about it or needed it until now. Before when I hit channel hold, it held on that particular site being received until I released it no matter if the dept or system was on hold or not. This new to me way is good too. Thanks. Learn something new every day.
It works slightly differently. When you press Func+Site, the background goes gray for a few seconds. While that is grey, you can scroll through the sites. Once it reverts to normal, you are locked on that site. If you want to change the site again, you need to press Func+Site once more.
It works and it works better than it used to, but the functions are slightly different. It took me a few tries to get the hang of it.
It works and it works better than it used to, but the functions are slightly different. It took me a few tries to get the hang of it.
No, it doesn't make sense and at some point Uniden might correct that. Actually, I'm not quite sure what the Channel Hold holds on when you switch Systems. It might be the equivalent slot on that system, which would be more or less at random.
Was in Hershey Pa for a concert, and had my 436 on 3 different DMR sysyems. The random, ghosting user id and tg problem is still there.
Even while one radio was talking, the uid was randomly changing, and multiple random tg ids were poping up...
Sent from my SM-G935V using Tapatalk
Even while one radio was talking, the uid was randomly changing, and multiple random tg ids were poping up...
Sent from my SM-G935V using Tapatalk
This now sounding like it is only a few of the scanners that are having that DMR ghost tg/rid issue. It is unlikely a global fw release would be helpful on this now. More likely that its going to have to be more specific to the user fix that can be applied to only those having this issue. The issue has been resolved on MOST scanners about 2 or 3 fw releases ago, and the NXDN ghosting seems to have been resolved with the last one and this one.
For those that are still having the DMR ghosting, time to make some logs for the Uniden Guys to look at closer and see if they can spot the issue.
For those that are still having the DMR ghosting, time to make some logs for the Uniden Guys to look at closer and see if they can spot the issue.
From my experience with this early on in the DMR release, proximity to the transmitter site might factor in.
I doubt its due to a hardware issue in only some scanners. It's more likely to be an oddball configuration on some systems, or a side effect of RAS, which makes error correction impossible on systems that use it. Weak signal + RAS is going to have erroneous TG and unit IDs, and there's little that can be done to fix that.
- Status
