Help with Dstar.

General support for the Pi-Star System
Post Reply
M0ITB
Posts: 4
Joined: Wed Nov 03, 2021 11:35 am

Help with Dstar.

Post by M0ITB »

Hi all,

I am running a pistar, and want to set it up for dstar, but i am having a persistent problem. i am using an icom 9700. every 20 seconds or so, my pistar sends an audio transmission in a female voice which says for example "linked to REF001 charlie". I can understand why it might do it when i first link to a reflector, but this is all the time every 20 seconds or so.

can anyone help with what is going on?
M1DNS
Pi-Star Team
Posts: 1395
Joined: Thu Apr 05, 2018 5:30 am

Re: Help with Dstar.

Post by M1DNS »

Does it actually say linked to, or linking to?

Either your dropping off the network. Either by way of ur own wifi, net connection or from the reflector your linking/ trying to link with. Or your not sucessfully linking.

One other Q. are you registered to access dplus reflectors like 1c? If not, you need to be.

Watch whats reported by pistar livelogs and report back what they're showing. Might give us more an idea to futhur help.

Sent via smoke signals from my SM-G935F M1DNS (Admin)

Andrew M1DNS.
Pi-star Admin Team.
M0ITB
Posts: 4
Joined: Wed Nov 03, 2021 11:35 am

Re: Help with Dstar.

Post by M0ITB »

it says linked to, and i have so far tried with 30c and 1 c.

I have no problem linking to reflectors using the local d star repeater.

I also have a pretty stable wifi and internet connection here ( I have a leased fibre line, static IP etc)

my callsign is registered on the dstar network. do I need to do something else if I want to access reflectors via a hotspot?

I don't know where within pistar I would find the logs?

Thanks for your help
M0ITB
Posts: 4
Joined: Wed Nov 03, 2021 11:35 am

Re: Help with Dstar.

Post by M0ITB »

Log output

I: 2022-04-23 17:38:33.699 it is to be used for educational purposes only. Its use on
I: 2022-04-23 17:38:33.699 commercial networks is strictly prohibited.
I: 2022-04-23 17:38:33.699 Copyright(C) 2015-2020 by Jonathan Naylor, G4KLX and others
M: 2022-04-23 17:38:33.699 MMDVMHost-20210617_PS4 is starting
M: 2022-04-23 17:38:33.699 Built 16:32:57 Jun 17 2021 (GitID #9106fd6)
I: 2022-04-23 17:38:33.699 General Parameters
I: 2022-04-23 17:38:33.699 Callsign: M0ITB
I: 2022-04-23 17:38:33.699 Id: 2345919
I: 2022-04-23 17:38:33.699 Duplex: no
I: 2022-04-23 17:38:33.699 Timeout: 240s
I: 2022-04-23 17:38:33.699 D-Star: enabled
I: 2022-04-23 17:38:33.699 DMR: disabled
I: 2022-04-23 17:38:33.699 YSF: disabled
I: 2022-04-23 17:38:33.699 P25: disabled
I: 2022-04-23 17:38:33.699 NXDN: disabled
I: 2022-04-23 17:38:33.699 POCSAG: disabled
I: 2022-04-23 17:38:33.699 FM: disabled
I: 2022-04-23 17:38:33.699 Modem Parameters
I: 2022-04-23 17:38:33.699 Port: /dev/ttyAMA0
I: 2022-04-23 17:38:33.699 Protocol: uart
I: 2022-04-23 17:38:33.699 RX Invert: no
I: 2022-04-23 17:38:33.699 TX Invert: yes
I: 2022-04-23 17:38:33.699 PTT Invert: no
I: 2022-04-23 17:38:33.699 TX Delay: 100ms
I: 2022-04-23 17:38:33.699 RX Offset: 0Hz
I: 2022-04-23 17:38:33.699 TX Offset: 0Hz
I: 2022-04-23 17:38:33.699 RX DC Offset: 0
I: 2022-04-23 17:38:33.699 TX DC Offset: 0
I: 2022-04-23 17:38:33.699 RF Level: 100.0%
I: 2022-04-23 17:38:33.699 DMR Delay: 0 (0.0ms)
I: 2022-04-23 17:38:33.699 RX Level: 50.0%
I: 2022-04-23 17:38:33.699 CW Id TX Level: 50.0%
I: 2022-04-23 17:38:33.699 D-Star TX Level: 50.0%
I: 2022-04-23 17:38:33.699 DMR TX Level: 50.0%
I: 2022-04-23 17:38:33.699 YSF TX Level: 50.0%
I: 2022-04-23 17:38:33.699 P25 TX Level: 50.0%
I: 2022-04-23 17:38:33.699 NXDN TX Level: 50.0%
I: 2022-04-23 17:38:33.699 POCSAG TX Level: 50.0%
I: 2022-04-23 17:38:33.699 FM TX Level: 50.0%
I: 2022-04-23 17:38:33.699 TX Frequency: 439500000Hz (439500000Hz)
I: 2022-04-23 17:38:33.699 Use COS as Lockout: no
M: 2022-04-23 17:38:33.704 Opening the MMDVM
I: 2022-04-23 17:38:35.715 MMDVM protocol version: 1, description: MMDVM_HS_Hat-v1.4.6 20180720 14.7456MHz ADF7021 FW by CA6JAU GitID #10c725c
I: 2022-04-23 17:38:35.736 Display Parameters
I: 2022-04-23 17:38:35.736 Type: Nextion
I: 2022-04-23 17:38:35.736 Port: /dev/ttyUSB0
I: 2022-04-23 17:38:35.736 Brightness: 50
I: 2022-04-23 17:38:35.736 Clock Display: yes
I: 2022-04-23 17:38:35.736 Display UTC: no
I: 2022-04-23 17:38:35.736 Idle Brightness: 20
I: 2022-04-23 17:38:35.736 Temperature in Fahrenheit: no
I: 2022-04-23 17:38:35.736 Screen Layout: DIY by ON7LDS
I: 2022-04-23 17:38:35.736 Display baudrate: 9600
I: 2022-04-23 17:38:35.747 Interfaces Info
I: 2022-04-23 17:38:35.748 IPv4: lo:127.0.0.1
I: 2022-04-23 17:38:35.748 IPv4: eth0:192.168.50.210
I: 2022-04-23 17:38:35.748 IPv4: wlan0:192.168.50.83
I: 2022-04-23 17:38:35.748 Default interface is : eth0
I: 2022-04-23 17:38:35.748 IP to show: eth0:192.168.50.210
I: 2022-04-23 17:38:36.023 D-Star Network Parameters
I: 2022-04-23 17:38:36.023 Gateway Address: 127.0.0.1
I: 2022-04-23 17:38:36.023 Gateway Port: 20010
I: 2022-04-23 17:38:36.023 Local Port: 20011
I: 2022-04-23 17:38:36.023 Mode Hang: 20s
M: 2022-04-23 17:38:36.023 Opening D-Star network connection
I: 2022-04-23 17:38:36.023 Opening UDP port on 20011
I: 2022-04-23 17:38:36.023 RSSI
I: 2022-04-23 17:38:36.023 Mapping File: /usr/local/etc/RSSI.dat
I: 2022-04-23 17:38:36.025 Loaded 14 RSSI data mapping points from /usr/local/etc/RSSI.dat
I: 2022-04-23 17:38:36.025 D-Star RF Parameters
I: 2022-04-23 17:38:36.025 Module: B
I: 2022-04-23 17:38:36.025 Self Only: yes
I: 2022-04-23 17:38:36.025 Ack Reply: yes
I: 2022-04-23 17:38:36.025 Ack message: BER
I: 2022-04-23 17:38:36.025 Ack Time: 750ms
I: 2022-04-23 17:38:36.025 Error Reply: yes
I: 2022-04-23 17:38:36.025 Remote Gateway: no
I: 2022-04-23 17:38:36.025 Mode Hang: 20s
M: 2022-04-23 17:38:36.270 MMDVMHost-20210617_PS4 is running
M: 2022-04-23 17:38:58.500 D-Star link status set to "Linking to REF001 C "
M: 2022-04-23 17:38:58.776 D-Star link status set to "Linked to REF001 C "
M: 2022-04-23 17:39:00.683 D-Star, received network header from M0ITB /INFO to CQCQCQ via REF001 C
M: 2022-04-23 17:39:07.594 D-Star, received network end of transmission from M0ITB /INFO to CQCQCQ , 7.1 seconds, 0% packet loss, BER: 0.0%
M: 2022-04-23 17:39:29.650 D-Star link status set to "Linking to REF001 C "
M: 2022-04-23 17:39:29.932 D-Star link status set to "Linked to REF001 C "
M: 2022-04-23 17:39:31.846 D-Star, received network header from M0ITB /INFO to CQCQCQ via REF001 C
M: 2022-04-23 17:39:38.759 D-Star, received network end of transmission from M0ITB /INFO to CQCQCQ , 7.1 seconds, 0% packet loss, BER: 0.0%
M: 2022-04-23 17:40:00.867 D-Star link status set to "Linking to REF001 C "
M: 2022-04-23 17:40:01.151 D-Star link status set to "Linked to REF001 C "
M: 2022-04-23 17:40:03.065 D-Star, received network header from M0ITB /INFO to CQCQCQ via REF001 C
M: 2022-04-23 17:40:09.976 D-Star, received network end of transmission from M0ITB /INFO to CQCQCQ , 7.1 seconds, 0% packet loss, BER: 0.0%
M: 2022-04-23 17:40:32.008 D-Star link status set to "Linking to REF001 C "
M: 2022-04-23 17:40:32.290 D-Star link status set to "Linked to REF001 C "
M: 2022-04-23 17:40:34.211 D-Star, received network header from M0ITB /INFO to CQCQCQ via REF001 C
M: 2022-04-23 17:40:41.121 D-Star, received network end of transmission from M0ITB /INFO to CQCQCQ , 7.1 seconds, 0% packet loss, BER: 0.0%
M: 2022-04-23 17:41:03.219 D-Star link status set to "Linking to REF001 C "
M: 2022-04-23 17:41:03.507 D-Star link status set to "Linked to REF001 C "
M: 2022-04-23 17:41:05.414 D-Star, received network header from M0ITB /INFO to CQCQCQ via REF001 C
M: 2022-04-23 17:41:12.324 D-Star, received network end of transmission from M0ITB /INFO to CQCQCQ , 7.1 seconds, 0% packet loss, BER: 0.0%
M: 2022-04-23 17:41:34.408 D-Star link status set to "Linking to REF001 C "
M: 2022-04-23 17:41:34.697 D-Star link status set to "Linked to REF001 C "
M: 2022-04-23 17:41:36.607 D-Star, received network header from M0ITB /INFO to CQCQCQ via REF001 C
M: 2022-04-23 17:41:43.519 D-Star, received network end of transmission from M0ITB /INFO to CQCQCQ , 7.1 seconds, 0% packet loss, BER: 0.0%
M: 2022-04-23 17:42:05.599 D-Star link status set to "Linking to REF001 C "
M: 2022-04-23 17:42:05.887 D-Star link status set to "Linked to REF001 C "
M: 2022-04-23 17:42:07.795 D-Star, received network header from M0ITB /INFO to CQCQCQ via REF001 C
M: 2022-04-23 17:42:14.710 D-Star, received network end of transmission from M0ITB /INFO to CQCQCQ , 7.1 seconds, 0% packet loss, BER: 0.0%
M: 2022-04-23 17:42:36.794 D-Star link status set to "Linking to REF001 C "
M: 2022-04-23 17:42:37.075 D-Star link status set to "Linked to REF001 C "
M: 2022-04-23 17:42:38.985 D-Star, received network header from M0ITB /INFO to CQCQCQ via REF001 C
M: 2022-04-23 17:42:45.898 D-Star, received network end of transmission from M0ITB /INFO to CQCQCQ , 7.1 seconds, 0% packet loss, BER: 0.0%
M: 2022-04-23 17:43:07.957 D-Star link status set to "Linking to REF001 C "
M: 2022-04-23 17:43:08.239 D-Star link status set to "Linked to REF001 C "
M: 2022-04-23 17:43:10.142 D-Star, received network header from M0ITB /INFO to CQCQCQ via REF001 C
M: 2022-04-23 17:43:17.057 D-Star, received network end of transmission from M0ITB /INFO to CQCQCQ , 7.1 seconds, 0% packet loss, BER: 0.0%
M: 2022-04-23 17:43:39.084 D-Star link status set to "Linking to REF001 C "
M: 2022-04-23 17:43:39.361 D-Star link status set to "Linked to REF001 C "
M: 2022-04-23 17:43:41.264 D-Star, received network header from M0ITB /INFO to CQCQCQ via REF001 C
M: 2022-04-23 17:43:48.177 D-Star, received network end of transmission from M0ITB /INFO to CQCQCQ , 7.1 seconds, 0% packet loss, BER: 0.0%
M: 2022-04-23 17:44:10.201 D-Star link status set to "Linking to REF001 C "
M: 2022-04-23 17:44:10.489 D-Star link status set to "Linked to REF001 C "
M: 2022-04-23 17:44:12.394 D-Star, received network header from M0ITB /INFO to CQCQCQ via REF001 C
M: 2022-04-23 17:44:
AF6VN
Posts: 821
Joined: Fri Jul 20, 2018 1:15 am

Re: Help with Dstar.

Post by AF6VN »

I don't know ICOM gear but...

The fact that it says "network header" implies that there is something out there that is sending packets other than your radio (in contrast this is my sending a reflector LINK command [though I was already linked to that reflector, so apparently to return activity] followed by sending an INFO command from a D74)

Code: Select all

M: 2022-04-24 02:47:28.988 D-Star, received RF header from AF6VN   /D74A to REF030CL
M: 2022-04-24 02:47:30.341 D-Star, received RF end of transmission from AF6VN   /D74A to REF030CL, 1.5 seconds, BER: 0.0%
M: 2022-04-24 02:47:53.703 D-Star, received network header from KO4ZPZ  /ID52 to CQCQCQ   via REF030 C
M: 2022-04-24 02:47:55.432 D-Star, received network end of transmission from KO4ZPZ  /ID52 to CQCQCQ  , 1.8 seconds, 0% packet loss, BER: 0.0%
M: 2022-04-24 02:48:03.397 D-Star, received RF header from AF6VN   /D74A to        I
M: 2022-04-24 02:48:04.727 D-Star, received RF end of transmission from AF6VN   /D74A to        I, 1.5 seconds, BER: 0.0%
M: 2022-04-24 02:48:06.795 D-Star, received network header from AF6VN   /INFO to CQCQCQ   via REF030 C
M: 2022-04-24 02:48:13.754 D-Star, received network end of transmission from AF6VN   /INFO to CQCQCQ  , 7.0 seconds, 0% packet loss, BER: 0.0%
Actually changing reflector shows me

Code: Select all

M: 2022-04-24 02:55:00.957 D-Star, received RF header from AF6VN   /D74A to REF001CL
M: 2022-04-24 02:55:00.962 D-Star link status set to "Linking to REF001 C "
M: 2022-04-24 02:55:01.121 D-Star link status set to "Linked to REF001 C  "
M: 2022-04-24 02:55:02.295 D-Star, received RF end of transmission from AF6VN   /D74A to REF001CL, 1.5 seconds, BER: 0.0%
M: 2022-04-24 02:55:02.880 D-Star, received RF header from AF6VN   /D74A to REF001CL
M: 2022-04-24 02:55:04.239 D-Star, received RF end of transmission from AF6VN   /D74A to REF001CL, 1.5 seconds, BER: 0.0%
If your log had been showing RF headers, I'd suspect your radio was configured for either a reflector link command, or the info command, and was relinking every time you hit the PTT. But those would show RF header, not something on the network repeatedly sending an INFO status response to your hotspot. I'd suspect something is also sending LINK commands (followed by INFO -- as I don't get an automatic INFO status after a link change).

A link command issued via the dashboard shows

Code: Select all

M: 2022-04-24 03:03:22.812 D-Star link status set to "Linking to REF030 C "
M: 2022-04-24 03:03:22.917 D-Star link status set to "Linked to REF030 C  "
No sign of either RF or Network headers! That matches your log IF the reflector/D-Star connection keeps dropping and coming back up. (rebooting my system and checking the log does not show an initial LINK status, apparently that lived through the reboot). Still no answer for the immediately following INFO status being sent by the reflector

--
AF6VN
Dennis L Bieber
Post Reply