TG and ID issue with Repeater

[DO4CZ]

Hallo
I have 2x GD-77 in operation, 1 device as a hotspot and one for normal operation.
I often had the TG: 0 problem and also tested Alex's new firmware.
With GD-7 hotspot only in the BM-Network so far everything is ok here, no TG: 0 or other problems.
I keep testing ...

Just had TG: 0

Firmware: last from Dec 21 2019 09:09:36 (3eb8e9e)

[DL4LEX]

That was a TG 0 on transmit?
Everything else here was TG 0 on receive.

[DO4CZ]

I haven't sent / nothing.
The first picture from the previous post was from the GD-77 hotspot, nothing on the display showed TG 0.
Previously, i.e. with the previous versions (without fix), TG 0 was always in the display of the GD-77 hotspot.

Was probably from the reception ...
Here are 2 screens from my profile that show => no sending.

The entry at the top is from afterwards when I switched everything off again and pushed the PTT to 2620.

Maybe a coincidence or BM has / had a problem?!?
I keep watching this...

[DL4LEX]

So that's Tier 2 version running in hotspot mode?
The hotspot in the Tier 2 version is not stable. So there might be some problems.

[DO4CZ]

Hi Alex
Previously, Tier 1 version was also running.
I know that the Tier 2 version is causing problems, but since yesterday's fix it has been running much better (as far as TG 0 is concerned).
As it is now, you can work very well with it, TG 0 was always the main problem here.

I keep watching ...

[KU4ZD]

It would be nice to find a way to have a larger ID data base.

I have seen that Hamdigital may be having some problems but they should get them worked out.

. So... I can't fault the code in the GD77 for that, but I wonder if the database at HamDigital is up-to-date?

Hamdigital may be having some problems

I noticed another thread on the forum saying PiStar was not displaying callsigns correctly either.

For VK, I've had to stop using Hamdigital, because currently with the Foundation classes now able to use digital modes, some VK callsigns have 4 letters, and HamDigital does not seem to be able to handle these.

Hence why I added the import from the radioid.net users.csv

But unfortunately that's not much use in the USA as there are too many IDs to fit in the memory.

[W1AEX]

Roger and Alex,

I loaded the [3eb8e9e] test firmware into my second (new) GD77 and have been running it alongside my old one which also is flashed with [3eb8e9e]. Both radios have displayed the TG flawlessly during this 2 hour run and have also displayed the call sign of most stations. Using the Last Heard list I have checked a few of the DMR ID's for stations that did not display their call and confirmed they are not in my DMR-ID database that is currently installed in both radios. So it seems that the DMR ID lookup is working fine since if the ID is present it displays the call sign.

The new GD77 did crash one time while scanning my DMR ALL zone which has Brandmeister, ARES, and DMARC repeaters installed during the 2 hour session so it looks like both radios are doing that randomly. As I recall Alex mentioned that the scan crash issue is already logged in github so I am assuming that is still being investigated.

So, with this (OpenGD77_201912210909.sgl) test firmware on both of my radios the TG display is perfect and the DMR-ID lookup is working. Also, the Last Heard list is catching everything perfectly.

Nicely done! 73, Rob W1AEX