BCDx36HP v1.18.00 Update

[bearcat]

FW 1.18 Update: I monitored two NXDN4800 Trunked systems today for several hours. The hanging TG with no audio is gone. The Alias tags are appearing about 100% of the time on one system and about 99% of the time on the other. I also ran the LCN finder on one system with 7 freqs. It found 6/7 with two minutes. I determined which freq it did not find and started monitoring it conventionally on another radio. There was no voice activity on that freq for over an hour or more. So that being said LCN finder would never find that one anyway. So I would say the LCN finder is working very well also.

I have not seen any other adverse effects with 1.18 (so far)

1.18 for me is working great.

 

[RadioDitch]

Was OpenSky and TETRA added to this firmware update?

Yeah, but the only thing you can hear when you use the 1.18 Super Secret Squirrel VIP Edition to listen to OpenSky is the tears and misery of those forced to use OpenSky.

 

[werinshades]

FW 1.18 Update: I monitored two NXDN4800 Trunked systems today for several hours. The hanging TG with no audio is gone.

Still seeing it in a NXDN 4800 system in ID Search mode as well as firmware 1.17.00. In firmware 1.16.00...it would show briefly and the scanner would skip over it then continue to ID Search. Have to press Lockout to get rid of it.

 

[bearcat]

Still seeing it in a NXDN 4800 system in ID Search mode as well as firmware 1.17.00. In firmware 1.16.00...it would show briefly and the scanner would skip over it then continue to ID Search. Have to press Lockout to get rid of it.

That is interesting. I had been seeing it with 16/17. I did not see it one time today and the system was very active.. Maybe you can send Paul a Debug file?

 

[Voyager]

Just a thought, but @werinshades: Has your scanner had the capacitor added? Maybe noise is masking the data.

 

[werinshades]

Just a thought, but @werinshades: Has your scanner had the capacitor added? Maybe noise is masking the data.

I'm primarily using the 536 for NXDN searching.

 

[Voyager]

OK. Maybe desense or interference? (thinking primarily adjacent channel, but any type is possible)

Do you have a 436 to try it on? While it is really a longshot, maybe something wasn't carried over.

 

[werinshades]

OK. Maybe desense or interference? (thinking primarily adjacent channel, but any type is possible)

Do you have a 436 to try it on? While it is really a longshot, maybe something wasn't carried over.

I'm awaiting to see if another contributor who monitors the same system is experiencing it on his 436. He also reported the issue in Firmware 1.17.00. We're thinking it might be data being sent to individual radios? The TGID's are looking like UID's that are active on the system. On Firmware 1.16.00, we would see the false TGID"s, but the scanner wouldn't "hang" on it. I'll await to see his results, so we can decipher if this is 536's software only? Good suggestions from both of you...thanks.

 

[dallascowboys]

BCDx36HP v 1.18.00 Update

Good Afternoon everyone,
JUST A THOUGHT, UPMan with everyone using different means to test which may be giving wrong transmission information and not everyone being on the same page, if Sentinel is ready for download maybe download it and see what happens, this way EVERYONE is seeing, hearing and reporting the same information.
AGAIN JUST A THOUGHT

Have a great day

 

[INDY72]

Alias display is working nicely. MASSIVE help in IDing unknown TG. Seeing a Company Name pop up is a good clue to who it is lol. And seeing a tag of BUS 137 and DISP pop up when your hearing a School bus business can quickly confirm your suspicions!

Now I wish that they used Aliases on P25 and DMR systems.... Would make life easier for some of us lol.

 

[werinshades]

FW 1.18 Update: I monitored two NXDN4800 Trunked systems today for several hours. The hanging TG with no audio is gone. The Alias tags are appearing about 100% of the time on one system and about 99% of the time on the other. I also ran the LCN finder on one system with 7 freqs. It found 6/7 with two minutes. I determined which freq it did not find and started monitoring it conventionally on another radio. There was no voice activity on that freq for over an hour or more. So that being said LCN finder would never find that one anyway. So I would say the LCN finder is working very well also.

I have not seen any other adverse effects with 1.18 (so far)

1.18 for me is working great.

Still seeing it in a NXDN 4800 system in ID Search mode as well as firmware 1.17.00. In firmware 1.16.00...it would show briefly and the scanner would skip over it then continue to ID Search. Have to press Lockout to get rid of it.

That is interesting. I had been seeing it with 16/17. I did not see it one time today and the system was very active.. Maybe you can send Paul a Debug file?

Just a thought, but @werinshades: Has your scanner had the capacitor added? Maybe noise is masking the data.

I'm primarily using the 536 for NXDN searching.

OK. Maybe desense or interference? (thinking primarily adjacent channel, but any type is possible)

Do you have a 436 to try it on? While it is really a longshot, maybe something wasn't carried over.

I'm awaiting to see if another contributor who monitors the same system is experiencing it on his 436. He also reported the issue in Firmware 1.17.00. We're thinking it might be data being sent to individual radios? The TGID's are looking like UID's that are active on the system. On Firmware 1.16.00, we would see the false TGID"s, but the scanner wouldn't "hang" on it. I'll await to see his results, so we can decipher if this is 536's software only? Good suggestions from both of you...thanks.

Just confirmed we're both still seeing it. 436/536 NXDN 4800 system.

 

[Voyager]

I would say time for a log.

 

[bravo14]

I have noticed today on Cap+ System the signal bars went from 5 bars to 2. That is on the 536hp FW 1.18

 

[freqseeker]

I have noticed today on Cap+ System the signal bars went from 5 bars to 2. That is on the 536hp FW 1.18

I have noticed that a few times right after a firmware update. I power down the radio and turn it back on and everything is back to normal. This isn't just with DMR. Did you just update the firmware?

Vince.

 

[bravo14]

I have noticed that a few times right after a firmware update. I power down the radio and turn it back on and everything is back to normal. This isn't just with DMR. Did you just update the firmware?

Vince.

I'm using FW 1.18 I have to wait til morning too see if it effects the analog signal on a trunk system. When the 1st FW came out for NXDN I lost 2-3 bars on analog and digital.

 

[Voyager]

SO many times it's been mentioned, but so many still bring it up. The S-meter is just a reference. The real tale is "do you hear the signal"? Has the signal changed or JUST the s-meter? Maybe they made it more stingy. But if it didn't affect the actual signal, no harm.

For a long time (I'm talking many decades) manufacturers have shown how their S-meter reads higher for the same signal than their competition. That doesn't mean that receiver hears better. It means the meter reads higher. The signal could actually be weaker depending on the S-meter design.

Bottom line:
You don't tug on superman's cape
You don't spit into the wind
You don't pull the mask off that old lone ranger
And you don't trust S-meters, Jim

 

[N9PBD]

Alias display is working nicely. MASSIVE help in IDing unknown TG. Seeing a Company Name pop up is a good clue to who it is lol. And seeing a tag of BUS 137 and DISP pop up when your hearing a School bus business can quickly confirm your suspicions!

Now I wish that they used Aliases on P25 and DMR systems.... Would make life easier for some of us lol.

The Alias display is even working on ham radio NXDN repeaters and hotspots!

 

[jonwienke]

Bottom line:
You don't tug on superman's cape
You don't spit into the wind
You don't pull the mask off that old lone ranger
And you don't trust S-meters, Jim

Exactly. There is no defined standard signal level for "4 bars".

Also system engineers will sometimes change antenna configuration, which can change the signal level going into the radio. It's also possible a bird crapped on your antenna and partly shorted it out. Or maybe the firmware recalibrated the s-meter so that each bar is an additional 9dB of signal instead of 6dB to extend the meter's useful range.

If reception quality hasn't degraded, its not a major issue.

 

[bearcat]

Now that the Alias function is working well. I did notice that the UID will appear a split second (sometimes) before the Alias. Which is fine by me, however do not make judgement on how well the Alias works via your recordings. It appears the recorded files contain just the UID even though the Alias actually did appear. Which makes sense.

 

[hiegtx]

Now that the Alias function is working well. I did notice that the UID will appear a split second (sometimes) before the Alias. Which is fine by me, however do not make judgement on how well the Alias works via your recordings. It appears the recorded files contain just the UID even though the Alias actually did appear. Which makes sense.

I have not set one of my units to record, full time, a NXDN system, then review the recordings for aliases. However, I am seeing the alias display when using Replay to review the last batch of receptions from a local NXDN public safety TRS.

I'll have to set up a recording session, then review those specific files to see whether the alias shows up.