[Possibly fixed by Alex] Incorrect identification of incoming Private Call

User avatar
W0RMT
Posts: 178
Joined: Sat Nov 16, 2019 12:45 pm
Location: Louisville, CO USA

[Possibly fixed by Alex] Incorrect identification of incoming Private Call

Post by W0RMT » Sat Nov 16, 2019 5:37 pm

Is TA set on by default? Is that why the opening CW ID is "TAA"? I can't seem to find any setting to enable/disable in the CPS or on the radio.

VK3KYY
Posts: 7596
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: Incorrect identification of incoming Private Call

Post by VK3KYY » Sun Nov 17, 2019 8:12 pm

TA is on by default but the CW ID is another problem

The CW ID is keying P C , for Private Call

This is because it thinks someone is making a Private call to you.

But the Private Call handling has a bug, which is probably related to the ID display problem in general.

I will logged it as a bug

https://github.com/rogerclarkmelbourne/ ... /issues/83

User avatar
W0RMT
Posts: 178
Joined: Sat Nov 16, 2019 12:45 pm
Location: Louisville, CO USA

Re: Incorrect identification of incoming Private Call

Post by W0RMT » Sun Nov 17, 2019 8:43 pm

Got it.

It's keying PC? Sure sounds like TAA to me. Shows you how good my CW is ;)

G4EML
Posts: 934
Joined: Sat Nov 16, 2019 10:01 am

Re: Incorrect identification of incoming Private Call

Post by G4EML » Sun Nov 17, 2019 9:27 pm

Are you talking about the CW that is sent when you first power on the radio?
That is <CT> which signifies the start of a message. I am assuming that is why it was chosen for the power up sound. (Of course it may be just a coincidence)
<CT> could equally be written as <TAA>
Because pro-signs don’t have spaces between the letters either interpretation is valid.
In either case the sound is the same ‘dah dit dah dit dah’ indicating start of message.

Colin

VK3KYY
Posts: 7596
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: Incorrect identification of incoming Private Call

Post by VK3KYY » Sun Nov 17, 2019 9:30 pm

Colin

No. I think its the "PC" that is sent to indicate an incoming private call.

For some reason, occasionally the ID detection system seems to think there is an incoming private call when there isn't

I think this may happen more when using reflectors, but its very intermittent for me, so hard to fix

G4EML
Posts: 934
Joined: Sat Nov 16, 2019 10:01 am

Re: Incorrect identification of incoming Private Call

Post by G4EML » Sun Nov 17, 2019 9:36 pm

OK I have never noticed that.
It’s just that the original question was talking about the ‘Opening CW ID’ which I read as the power on tone which could sound like TAA to some ears.

VK3KYY
Posts: 7596
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: Incorrect identification of incoming Private Call

Post by VK3KYY » Sun Nov 17, 2019 10:31 pm

Someone asked me to add a notification tone for the private call so that the could leave the radio turned on with the volume up, but not listening to a TG.

I added code to key a "P" .--. but they said that was too short, so I changed it to PC .--. -.-.

However the problem goes back to the general problem I have with reading the ID from the LC frame etc, partially because the radio is listening to both TS.

In the longer term, I think I'm going to need to disassemble one of my older GD-77's and try to solder some wires onto the SPI pins that connect the MCU to the C6000, so that I can capture what the MCU is sending to the C6000 and what the C6000 responds with.

I know I can do it, but its a sod of a job, because of the size of the pins on the MCU, and I've not had time at the moment.

User avatar
W0RMT
Posts: 178
Joined: Sat Nov 16, 2019 12:45 pm
Location: Louisville, CO USA

Re: Incorrect identification of incoming Private Call

Post by W0RMT » Sun Nov 17, 2019 11:03 pm

G4EML wrote:
Sun Nov 17, 2019 9:36 pm
OK I have never noticed that.
It’s just that the original question was talking about the ‘Opening CW ID’ which I read as the power on tone which could sound like TAA to some ears.
Yes- I was referring to the *opening CW ID* which does sound like TAA (or CT).

VK3KYY
Posts: 7596
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: Incorrect identification of incoming Private Call

Post by VK3KYY » Sun Nov 17, 2019 11:07 pm

Ah.

OK.

You mean -.-.-

My total misunderstanding ;-)

There is a bug with the PC thing, but thats another problem

TA is enabled by default, but is secondary to the internal database, because by default BM only sends the Callsign and not the name, unless the operator updates their Self Care page/

I probably need to add an option for DMR ID mode, to specify what people want to see.

But I'd be surprised if people would want to have TA as a priority over the internal DMR ID database.

User avatar
W0RMT
Posts: 178
Joined: Sat Nov 16, 2019 12:45 pm
Location: Louisville, CO USA

Re: Incorrect identification of incoming Private Call

Post by W0RMT » Sun Nov 17, 2019 11:27 pm

Because the internal database size is small, I like being able to receive TA if it is present with the data. At least the callsign (e.g. from BM) even if they have not updated their text in selfcare.

Otherwise I do like the filtered ID download in the community CPS, with the added inactivity filter. That's good stuff. But I just haven't found myself loading individual IDs in since I can't just load them all.

It would be nice to have the option; TA or DMR ID data

Post Reply