4.0.0-RC3 Problem

General support for the Pi-Star System
oz1cbk
Posts: 51
Joined: Wed Apr 11, 2018 11:59 am

Re: 4.0.0-RC3 Problem

Post by oz1cbk » Sat Apr 20, 2019 8:08 am

I have now installed 3.4.17
Run update and it now 20190402

Run firmware update and it now run HR3.26

THANK YOU for all Your help.

Ole - OZ1CBK

oz1cbk
Posts: 51
Joined: Wed Apr 11, 2018 11:59 am

Re: 4.0.0-RC3 Problem

Post by oz1cbk » Sat Apr 20, 2019 8:51 am

And it end up with the same as I started, It wont send out to dcs004 B.

Öle.

oz1cbk
Posts: 51
Joined: Wed Apr 11, 2018 11:59 am

Re: [solved] 4.0.0-RC3 Problem

Post by oz1cbk » Sat Apr 20, 2019 10:29 am

I hope it is solved.

Ohh, I have misunderstanding PRIVATE / PUBLIC in Node Type

If it is Privat, it dont work. In Public and the hotspots call in RPT1 and RPT2 in the radio, it works.

What a BUM - Okay i'm not 17 anymore :)

THANKS FOR ALL HELP.

Ole - OZ1CBK

User avatar
KE0FHS
Posts: 846
Joined: Wed Apr 11, 2018 8:40 pm
Location: Colorado, USA
Contact:

Re: 4.0.0-RC3 Problem

Post by KE0FHS » Sat Apr 20, 2019 1:27 pm

Node Type determines whether radios with callsigns other than the Pi-Star General Configuration Node Callsign can access the hotspot. When selecting this, keep in mind the regulations in your country pertaining to the control operator function. For a personal hotspot in the U.S., you can set this to Public, but unless you actually intend to allow radios with other callsigns to access the hotspot, it's may be best to leave it set to Private.

So if your Node Type is set to private and your radio's callsign is different from Pi-Star Node Callsign, you won't be able to transmit.
73, Toshen, KE0FHS
Playing with Pi-Star (unofficial notes about setting up and using Pi-Star):
https://amateurradionotes.com/pi-star.htm

oz1cbk
Posts: 51
Joined: Wed Apr 11, 2018 11:59 am

Re: 4.0.0-RC3 Problem

Post by oz1cbk » Sat Apr 20, 2019 1:35 pm

Okay, Thanks.

BUT if I set hotspot call in the radio's RPT1 and RPT2 and set hotspot to private, it dont work.

So now it set together. If I used another call in the radio RPT1 and RPT2 it dont work.

It have to be the same.

Ole - OZ1CBK

M1DNS
Posts: 363
Joined: Thu Apr 05, 2018 5:30 am

Re: 4.0.0-RC3 Problem

Post by M1DNS » Sat Apr 20, 2019 1:59 pm


oz1cbk wrote:Okay, Thanks.


... If I used another call in the radio RPT1 and RPT2 it dont work.



Ole - OZ1CBK


That is correct. The rpt1 rpt2 need to be set for the installation.
eg. If I set my rpt1 to anything other than M1DNS B in my radio my transmissions would be ignored by my hotspot.

The rpt1 & 2 must match the call in the configuration.

Andrew M1DNS, (Mod)

Andrew M1DNS.
Pi-star Admin Team.

User avatar
KE0FHS
Posts: 846
Joined: Wed Apr 11, 2018 8:40 pm
Location: Colorado, USA
Contact:

Re: 4.0.0-RC3 Problem

Post by KE0FHS » Sat Apr 20, 2019 2:19 pm

Yes, for D-STAR, RPT1 and RPT2 in your radio for a channel you'll use with your hotspot must always match RPT1 and RPT2 that are set up in the Pi-Star D-Star Configuration settings (this is true whether your Node Type is set to Private or Public).

Beyond that:
  • For D-STAR: if your hotspot Node Type is set to Private, the callsign set up in your radio must match the Node Callsign set up in the Pi-Star the General Configuration settings.
  • For DMR: if your hotspot Node Type is set to Private, the CCS7 ID set up in your radio must match the CCS7/DMR ID set up in the Pi-Star General Configuration settings.
73, Toshen, KE0FHS
Playing with Pi-Star (unofficial notes about setting up and using Pi-Star):
https://amateurradionotes.com/pi-star.htm

oz1cbk
Posts: 51
Joined: Wed Apr 11, 2018 11:59 am

Re: 4.0.0-RC3 Problem

Post by oz1cbk » Sat Apr 20, 2019 4:26 pm

Thanks Andrew and Toshen.

I learn all the time :D

Ole - OZ1CBK

Post Reply