Post 25th Jan Changes

[M0GWC]

Apologies for possibly wasting time but I am very confused!
For the past 18 months I have had no issues, but after the 25/26th January overnight update I noticed I was no
longer sending regular d-prs from my Zumspot.
System configuration: Pi-Star 4.1.3 Dashboard 20210128
ZumSpot firmware 1.52.
If I load a new card with 4.1.2 and a dashboard of 20200520 all is good, soon as I upgrade to the latest dashboard
I get my problem back - what am I doing wrong??

I have managed to make the change from RadioID back to QRZ but could find no mention regarding d-prs, I have rechecked
the APRS setup and there is no change in the configuration.
Any help much appreciated.
73 Graham M0GWC

[MW0MWZ]

I have released a new ircDDBGateway, probably there is some additional work for me to do - hold tight and I'll look into it.

[g7kbr]

Hi all

i am running Pi-star 4.0.0-RC$ dashboard 20210128. It would seem the recent update has stopped D-Star network working. It shows N0-D-star Network and is highlighted in RED. This has only just happed, I checked the IRCDDBGateway setting and all was ok.

Anyone else have this issue? DMR and YSF is ok.

[G8SEZ]

Hi all

i am running Pi-star 4.0.0-RC$ dashboard 20210128. It would seem the recent update has stopped D-Star network working. It shows N0-D-star Network and is highlighted in RED. This has only just happed, I checked the IRCDDBGateway setting and all was ok.

Anyone else have this issue? DMR and YSF is ok.

You're running an old pre-release version, that is not going to help.

You would be better off creating a backup and then creating a new image on a new microSD card. Run a few update and upgrade cycles from an SSH prompt until all of the OS and Pi-Star is up to date then restore your backup, asking for help with a version from 2019 is not going to give you good results. Recent changes expect to have up-to-date systems to run on.

[M0GWC]

Regarding the possible SD card corruption, I did wonder so loaded a new card, all well until
I forced the dashboard update and problem returned.
Graham
M0GWC

[g7kbr]

Hi all

i am running Pi-star 4.0.0-RC$ dashboard 20210128. It would seem the recent update has stopped D-Star network working. It shows N0-D-star Network and is highlighted in RED. This has only just happed, I checked the IRCDDBGateway setting and all was ok.

Anyone else have this issue? DMR and YSF is ok.

You're running an old pre-release version, that is not going to help.

You would be better off creating a backup and then creating a new image on a new microSD card. Run a few update and upgrade cycles from an SSH prompt until all of the OS and Pi-Star is up to date then restore your backup, asking for help with a version from 2019 is not going to give you good results. Recent changes expect to have up-to-date systems to run on.

Many thanks for your words of wisdom. The plan at some point is to update the build. But the unit is not accessible at the moment. I should of disabled the auto update. As it’s seems my issue is down to the new features etc.

Once again thank you.


Sent from my iPhone using Tapatalk

[M1DNS]

i am running Pi-star 4.0.0-RC$ dashboard 20210128.

Pistar 4.0 held at RC and never made it into a full release. Its most prob. as a result of the recent updates of ircddbgateway and dstarrepeater.

As others recommend update to 4.1 (currently 4.1.3) as soon as you get opertuanty.

Sent from my SM-G935F using Tapatalk

[W3KIT]

Apologies for possibly wasting time but I am very confused!
For the past 18 months I have had no issues, but after the 25/26th January overnight update I noticed I was no
longer sending regular d-prs from my Zumspot.
System configuration: Pi-Star 4.1.3 Dashboard 20210128
ZumSpot firmware 1.52.
If I load a new card with 4.1.2 and a dashboard of 20200520 all is good, soon as I upgrade to the latest dashboard
I get my problem back - what am I doing wrong??

I have managed to make the change from RadioID back to QRZ but could find no mention regarding d-prs, I have rechecked
the APRS setup and there is no change in the configuration.
Any help much appreciated.
73 Graham M0GWC

I think I have the same issue. Normally I would see W3KIT-B updated. Not so with the newer Dashboard.
I made a new fresh card with just version 4.1.2 and dashboard 20200520 then keyed up my ID-51, I see W3KIT-2 (my ID-51 SSID) updated and few minuets later I see W3KIT-B updated.

With a newer dashboard when I keyed up I see the following RAW message on APRS.FI, not sure if it mean anything.
----
2021-01-29 08:41:01 EST: W3KIT-2>API51,DSTAR*,qAS,N1IG-G:/134059h3902.81N/07702.51W[092/001/A=000244
2021-01-29 08:43:50 EST: W3KIT-2>API51,DSTAR*,qAS,N1IG-G:/134101h3902.81N/07702.51W[092/000/A=000246
2021-01-29 15:11:37 EST: W3KIT-2>API51,DSTAR*,qAS,KC3PRI-G:/201135h3902.81N/07702.47W[108/000/A=000421
---
Now with fresh version 4.1.2 and dashboard 20200520 I see the following.
---
2021-01-29 16:52:56 EST: W3KIT-2>API51,DSTAR*,qAR,W3KIT-B:/215254h3902.81N/07702.48W[145/000/A=000443
2021-01-29 16:59:57 EST: W3KIT-2>API51,DSTAR*,qAR,W3KIT-B:/215946h3902.81N/07702.48W[145/000/A=000423
2021-01-29 17:10:07 EST: W3KIT-2>API51,DSTAR*,qAR,W3KIT-B:/221004h3902.82N/07702.48W[145/000/A=000426
---

No, big issue here really as I normally I disabled APRS/DPRS in ircDDBGateway anyway. But when I saw the post I though I'd check it out and see.

73, Kit

[W3KIT]

Just to follow up my post above.

With fresh version 4.1.2 and dashboard 20200520, W3KIT-B updating to aprs.fi every 20 min or so. And W3KIT-2 updated whenever I talk.
----
2021-01-29 17:12:06 EST: W3KIT-B>APDG02,TCPIP*,qAC,W3KIT-BS:!3902.83ND07702.48W&/A=000010RNG0001 440 Voice 438.20000MHz +0.0000MHz
2021-01-29 17:33:26 EST: W3KIT-B>APDG02,TCPIP*,qAC,W3KIT-BS:!3902.83ND07702.48W&/A=000010RNG0001 440 Voice 438.20000MHz +0.0000MHz
2021-01-29 17:54:36 EST: W3KIT-B>APDG02,TCPIP*,qAC,W3KIT-BS:!3902.83ND07702.48W&/A=000010RNG0001 440 Voice 438.20000MHz +0.0000MHz
2021-01-29 18:15:47 EST: W3KIT-B>APDG02,TCPIP*,qAC,W3KIT-BS:!3902.83ND07702.48W&/A=000010RNG0001 440 Voice 438.20000MHz +0.0000MHz
2021-01-29 18:36:46 EST: W3KIT-B>APDG02,TCPIP*,qAC,W3KIT-BS:!3902.83ND07702.48W&/A=000010RNG0001 440 Voice 438.20000MHz +0.0000MHz
2021-01-29 18:57:47 EST: W3KIT-B>APDG02,TCPIP*,qAC,W3KIT-BS:!3902.83ND07702.48W&/A=000010RNG0001 440 Voice 438.20000MHz +0.0000MHz
---

With version 4.1.3 and dashboard (20210129) - all dead in the water. W3KIT-2 not updating and 20 min came and went - no W3KIT-B updates.

73, Kit

[Kt7az]

We have several repeaters running the 4.0.0.RC- at remote locations on mountain tops. All of which have stopped functioning with the eror showing “ No D-Star Network”. I wish we were given an EOL time frame on this. Winter is not a good time of year to go to these sites where the only way to fix this is going to these sites. Hope it can be fixed with the daily updates at least till spring.

KT7AZ