New Beta 2023 11 19

[N1LSJ]

As many of the other radios only have a single RX/TX circuit (Like Anytone 878) those radios must switch over to the APRS frequency to
send a status update, so it must be some very short interruption.

I'd think the right thing to do is to delay the beacon if the user had transmitted recently and receiving presently in case they are in the midst of a QSO. I don't know what algorithm other radios use?

[TA1ECA]

Hi,

The problem here is could/will trigger collisions, as it couldn't check the frequency before beaconing.


Cheers.
---
Daniel

I didn't know there was such a feature in OpenGD77. I was used to making sure that the channel was empty to make APRS transmission by pressing the PTT while on the APRS channel.
I really wonder what features OpenGD77 has that I don't know about.
I feel great gratitude to the software developers who spent their own time to develop these wonderful software.

Kind regards,
Emre

[F1RMB]

Nope, only automatic beaconing modes check the frequency before transmitting. In manual mode, that task is up to the operator (in your exemple, in PTT mode, you pressed the key, you maybe spoke, and now you release the PTT a beacon will (maybe) be send.

EDIT: correction, only PTT mode doesn't check for frequency activity before beaconing.

Cheers.
---
Daniel

[N1LSJ]

This update broke manual APRS for me. When I press PTT it just transmits as long as I hold down the PTT - no "squawk", just the count-up numbers and the battery % going down.. I checked that APRS is still in "manual" mode and the APRS seems to be set up correctly.

[F1RMB]

This update broke manual APRS for me. When I press PTT it just transmits as long as I hold down the PTT - no "squawk", just the count-up numbers and the battery % going down.. I checked that APRS is still in "manual" mode and the APRS seems to be set up correctly.

Screenshot at 2023-11-25 08-30-19.png (34.02 KiB) Viewed 4584 times

Maybe it's time to really read the manual.

[SA0BUX]

What was the "CW Id bug in Hotspot mode" ?

An OM on the Facebook group said that the bug was still there.

[F1RMB]

What was the "CW Id bug in Hotspot mode" ?

An OM on the Facebook group said that the bug was still there.

On some condition, STM32 based tranceivers were exiting the hotspot mode in a DIGITAL non working state.
Nothing related to the stuff posted on FB, where the guy posted a log where MMDVMHost just triggered only ONE CWID, and it's not up to the modem to send CW identification by itself, it's MMDVMHost job, modem is passive here.

Hence, better to check on the MMDVMHost side (old/outdated or buggy version, IDK).
There is a lot of strange, probably/mostly PEBCAK, problems there...

[N1LSJ]

Screenshot at 2023-11-25 08-30-19.png
Maybe it's time to really read the manual.

I thought I had the Beaconing beta loaded before this beta but I guess I didn't - sorry about that and "Thanks!"

[oe7abh]

Thanks to all the contributors!
OpenGD77 firmware -> the best thing that can happen to a Chinese device.

73 Alfred OE7ABH
http://tyrofly.at/

[VK3KYY]

This version has now been superseded

See

viewtopic.php?f=19&t=3533