struggling!

Post Reply
KO4BFY
Posts: 10
Joined: Sat Feb 08, 2020 4:16 am

struggling!

Post by KO4BFY » Thu Feb 13, 2020 3:33 am

I'm struggling with setting up a codeplug. My initial needs are basic.
1. TG 3100 USA
2. TG 91 Worldwide
3. TG 9990 Parrot

I have each set up as a digital contact.
A TG List (Brandmeister) with each contact above added

Whenever I attempt to use parrot, the target on pi-star remains at 3100. I'd appreciate guidance!

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

Re: struggling!

Post by VK3KYY » Thu Feb 13, 2020 4:39 am

Hi

Look on your PiStar dashboard and confirm that you are transmitting on the TG you think you are.

You an manually enter any TG, simply by entering # THE_TG_NUMBER then press the Green button.

BTW. AFIK Parrot on BM is a Private Call to 9990 , rather than a Group call.

To make a private call, press ## THE_PC_NUMBER then press the Green button


IMHO. Brandmeister is quite buggy in terms of leaving a TG. If you Enter # 91 GREEN and press Tx for a few seconds, this will setup a static route to your hotspot from TG 91, so you'll then get all the TG 91 traffic being set to you.

However you'll find that if you subsequently want to go back to TG 3100 , (and press # 3100 GREEN) and hold the PTT for a while, you'll still get traffic coming through on TG 91 for ages.

I have found that I need to make repeated attempts to go to another TG after having been on TG 91.


Also, in theory if you transmit on TG 4000, its supposed to release you from the current static route, but in my experience this doesnt work. (at least not for 91 and possibly not for any TG)

Note.
There is a quirk in the firmware. If you transmit on TG 4000, BM will respond with a recorded voice, but BM sends from DMR ID 4000, so this gets treated as an incoming private call (which it technically is) and you get a prompt about whether you want to accept / return the call.

So just Press RED to get ride of the Private Call message if that happens.

(I think we'll need to put in a special workaround for this quirk with BM using strange ID numbers for their message transmissions)

User avatar
4I1RAC
Posts: 141
Joined: Thu Nov 28, 2019 5:25 am
Location: Philippines
Contact:

Re: struggling!

Post by 4I1RAC » Thu Feb 13, 2020 6:33 am

Some master servers use a different parrot talkgroup or private call ID. Which server are you using?
Angelo, 4I1RAC / N2RAC
Brandmeister Philippines support team
Talkgroups
- 51518 crosslinked to DX1ARM 431.600 MHz Fusion repeater, Metro Manila
- 98977 Opengd77
- 515 Philippines

https://n2rac.com

User avatar
m1dyp
Posts: 322
Joined: Sat Nov 16, 2019 8:03 am
Location: Hertfordshire, U.K.

Re: struggling!

Post by m1dyp » Thu Feb 13, 2020 6:53 am

VK3KYY wrote:
Thu Feb 13, 2020 4:39 am


Note.
There is a quirk in the firmware. If you transmit on TG 4000, BM will respond with a recorded voice, but BM sends from DMR ID 4000, so this gets treated as an incoming private call (which it technically is) and you get a prompt about whether you want to accept / return the call.

So just Press RED to get ride of the Private Call message if that happens.

(I think we'll need to put in a special workaround for this quirk with BM using strange ID numbers for their message transmissions)
in the options menu, I set 'allow pc:off'
73 de Ken :D

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

Re: struggling!

Post by VK3KYY » Thu Feb 13, 2020 8:31 am

m1dyp wrote:
Thu Feb 13, 2020 6:53 am
in the options menu, I set 'allow pc:off'
That's a good work-around, but we probably need to do a better fix in the code.

Technically the firmware is working OK, but the way BM transmits these audio messages via a PC is problematic

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

Re: struggling!

Post by G4EML » Thu Feb 13, 2020 10:13 am

Roger,

The ‘accept private call’ prompt is something that most radios don’t do. If they receive a private call they just receive the call, then if the user responds within a hang time the reply is automatically sent back to the originator as a private call.

I know you introduced the prompt so it didn’t rely on a hang timers but in this case it seems to be a hindrance rather than a help. Maybe have an option to enable or disable the prompt.

Colin

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

Re: struggling!

Post by VK3KYY » Fri Feb 14, 2020 2:59 am

Hi Colin

I've done a modification to handle these special source ID's differently, which I have posted to the other thread that has this as a similar problem.
viewtopic.php?f=7&t=631


The Private Call accept screen is now only displayed for ID's >= 1000000 , because this seems the minimum ID that would ever be allocated to a normal operator.

The only lower ID than this in the RadioID.net database seems to be

302911 RADIOID

But I've no idea what use that I would have, the details are

All Regions None RESERVED


Which implies its more like a ID for a All Call.

KO4BFY
Posts: 10
Joined: Sat Feb 08, 2020 4:16 am

Re: struggling!

Post by KO4BFY » Fri Feb 14, 2020 4:59 pm

Thanks for the tips. Doing ## 9990 got Parrot working. I also discovered the user guide on github which I had somehow missed so that's helping too. And I successfully used hotspot mode with pistar so things are looking up!

Post Reply