Hi!
After the latest Pi-Star upgrade, there's no sending of callsign/ID to the station. Nothing appears, like in analog mode.
Pure YSF reflectors work fine.
Tested on my Yaesu FT-70D.
No identification in YSF2DMR after the latest Pi-Star upgrade.
Re: No identification in YSF2DMR after the latest Pi-Star upgrade.
The issue started with this commit:
When the binaries are reverted to a previous version, everything works again.
Code: Select all
commit d915d044c3564116deb3b2d0d2e21d81c9221035 (HEAD, origin/master, origin/HEAD, master)
Author: root <root@pi-star>
Date: Tue Feb 2 16:44:34 2021 +0000
update YSF stack
Re: No identification in YSF2DMR after the latest Pi-Star upgrade.
I suspect that I just need to enable the APRSGateway option for YSFGateway (similar to ircDDBGateway) to cure this.
Re: No identification in YSF2DMR after the latest Pi-Star upgrade.
Chased this around for a while and finally came up with;
APRS can be made to work just fine - and in fact this is fixed 4.1.4 for YSFGateway too now...
When using any of the DMR2xxx modes, the meta data (callsigns etc) is not decoded by the radio, although voice appears to be fine.
For the sake of ruling out some other options, I tested against the newest MMDVMHost / DGIdGateway / YSFGateway / YSF2DMR software - and its not that I am missing something.
The issue occurs in the current YSFGateway - looking into it...
APRS can be made to work just fine - and in fact this is fixed 4.1.4 for YSFGateway too now...
When using any of the DMR2xxx modes, the meta data (callsigns etc) is not decoded by the radio, although voice appears to be fine.
For the sake of ruling out some other options, I tested against the newest MMDVMHost / DGIdGateway / YSFGateway / YSF2DMR software - and its not that I am missing something.
The issue occurs in the current YSFGateway - looking into it...
Re: No identification in YSF2DMR after the latest Pi-Star upgrade.
After chasing this around for a while, its not the new YSFGateway, now looking at the MMDVM_CM code....
Re: No identification in YSF2DMR after the latest Pi-Star upgrade.
Fixed - update, head to the config page, press apply (even without making a change) and that will sort it out
Re: No identification in YSF2DMR after the latest Pi-Star upgrade.
Thank you very much!
Re: No identification in YSF2DMR after the latest Pi-Star upgrade.
Same problem with DM2YSF and own call showing up in place of others. Can you do the same for DM@YSF?
Re: No identification in YSF2DMR after the latest Pi-Star upgrade.
Hello !
I don't see callsigns on Yaesu FT991A via YSF00002 on 4.1.4.
With fresh install pistar 4.1.2 and restore configs from 4.1.4 i can see callsigns.
After update (pistar-daily or /usr/local/sbin/pistar-daily.cron) it's broken too.
And i see callsign in latest 4.1.4 via another reflectors (not YSF00002).
In MMDVMHost Configuration enabled only YSFMode and YSF2DMR.
73!
I don't see callsigns on Yaesu FT991A via YSF00002 on 4.1.4.
With fresh install pistar 4.1.2 and restore configs from 4.1.4 i can see callsigns.
After update (pistar-daily or /usr/local/sbin/pistar-daily.cron) it's broken too.
And i see callsign in latest 4.1.4 via another reflectors (not YSF00002).
In MMDVMHost Configuration enabled only YSFMode and YSF2DMR.
73!
Code: Select all
# cat /proc/device-tree/model
Raspberry Pi 3 Model B Plus Rev 1.3
# pistar-mmdvmhshatflash | tail -3
Selected Modem: STM32-DVM / MMDVM_HS - Raspberry Pi Hat (GPIO)
Connected Hardware: MMDVM_HS_Hat-v1.4.6 20180720 14.7456MHz ADF7021 FW by CA6JAU GitID #10c725c
TCXO Value: 14.7456MHz