Thanks to Jeff at Hamstation I have a BCD436HP available to me now to do a side by side comparison with my new TRX-1.
Currently both the TRX-1 and BCD436HP are connected to the same antenna via a multicoupler. Both have the latest firmware updates. Both are programmed to scan two Con+ DMR trunked systems. Each of these have two sites. Both of these systems are programmed with a wildcard for the TRX-1 and ID SEARCH on the 436 to supposedly hear all traffic. Each Con+ system has a site local to me with a pretty strong signal. The TRX-1 has a third scanlist which contains conventional DMR. All entries are programmed using wildcards, i.e. cc:*,tg:*,sl:*. The 436HP has its conventional DMR programmed as single channel trunked systems and loaded via ARC536 Pro software. Again, both scanners are only programmed to receive the same exact systems, nothing "extra" in either.
The TRX-1 and 436HP seem relatively close on the Con+ systems although I have watched the TRX-1 scan right by a talkgroup that the 436HP is currently receiving on a few occasions. The largest issue I see is with conventional traffic. The TRX-1 is flat-out missing a volume of traffic from my local Eversource electrical utility company on a frequency of 451.125. The signal is very strong and that can't be used as a reason for non-reception. There are similar issues with other conventional frequencies albeit with weaker signal levels.Yet, the TRX-1 has no issue receiving other conventional traffic in the UHF range and keeps up fine with the 436. The programming for the ones that work and the ones that don't is exactly the same as shown in the example in the first paragraph.
I'm stumped as to why this is occurring other than it's early in the game for both and there will surely be improvements in firmware. But why exact same methods of programming for conventional DMR in the TRX-1 provides drastically different results is mystifying. Any suggestions, and/or if anyone else has both to compare, have you noticed anything similar?
Currently both the TRX-1 and BCD436HP are connected to the same antenna via a multicoupler. Both have the latest firmware updates. Both are programmed to scan two Con+ DMR trunked systems. Each of these have two sites. Both of these systems are programmed with a wildcard for the TRX-1 and ID SEARCH on the 436 to supposedly hear all traffic. Each Con+ system has a site local to me with a pretty strong signal. The TRX-1 has a third scanlist which contains conventional DMR. All entries are programmed using wildcards, i.e. cc:*,tg:*,sl:*. The 436HP has its conventional DMR programmed as single channel trunked systems and loaded via ARC536 Pro software. Again, both scanners are only programmed to receive the same exact systems, nothing "extra" in either.
The TRX-1 and 436HP seem relatively close on the Con+ systems although I have watched the TRX-1 scan right by a talkgroup that the 436HP is currently receiving on a few occasions. The largest issue I see is with conventional traffic. The TRX-1 is flat-out missing a volume of traffic from my local Eversource electrical utility company on a frequency of 451.125. The signal is very strong and that can't be used as a reason for non-reception. There are similar issues with other conventional frequencies albeit with weaker signal levels.Yet, the TRX-1 has no issue receiving other conventional traffic in the UHF range and keeps up fine with the 436. The programming for the ones that work and the ones that don't is exactly the same as shown in the example in the first paragraph.
I'm stumped as to why this is occurring other than it's early in the game for both and there will surely be improvements in firmware. But why exact same methods of programming for conventional DMR in the TRX-1 provides drastically different results is mystifying. Any suggestions, and/or if anyone else has both to compare, have you noticed anything similar?