FM APRS not working on UV390 (Beta 2023 08 09)

[F1RMB]

SK1 is above the PTT button, SK2 is below.

[SA0BUX]

A bit stupid question, sorry, in UV380 what are the sk1 and 2 keys? Is SK1 the one above or the one below?

On RT3S it's the one above the PTT , should be the same on UV380

[VK3KYY]

RT3S is a MD-UV380

[lu2efi]

Your codeplug is working for me on both UV380 and also GD77

Try clearing all your APRS configs and make a new one and do not change anything in that config

Use the latest CPS 2023.08.10.01

It worked! Now I can transmit APRS info both on channels with APRS config associated and on VFO also, and get reported by a nearby iGate.
Thanks Roger

[VK3KYY]

Your codeplug is working for me on both UV380 and also GD77

Try clearing all your APRS configs and make a new one and do not change anything in that config

Use the latest CPS 2023.08.10.01

It worked! Now I can transmit APRS info both on channels with APRS config associated and on VFO also, and get reported by a nearby iGate.
Thanks Roger

OK.

Perhaps clearing the old data fixed it.

[W4TAB]

Hi,

I just installed in on my RT3S and it worked like a charm! I tested it with my base station that is setup as iGate and everything works. I know this is the first step into APRS, if this radio can get to sending messages it is going to be the million dollar radio, dual band, DMR, AND APRS! I will not need another HT, EVER!

Thank you to all the developers for all their time and dedication poured into this project.

[VK3KYY]

Hi,

I just installed in on my RT3S and it worked like a charm! I tested it with my base station that is setup as iGate and everything works. I know this is the first step into APRS, if this radio can get to sending messages it is going to be the million dollar radio, dual band, DMR, AND APRS! I will not need another HT, EVER!

Thank you to all the developers for all their time and dedication poured into this project.

What sort of messages?

The GD77 and UV380 hardware could send other AX25 packets.
Currently there is a packet length limitation on the MD9600, of about 75 bytes, including preamble flags and CRC and end flags etc. Hence why we can't send a comment with the APRS packet on this radio

[W4TAB]

What sort of messages?

The GD77 and UV380 hardware could send other AX25 packets.
Currently there is a packet length limitation on the MD9600, of about 75 bytes, including preamble flags and CRC and end flags etc. Hence why we can't send a comment with the APRS packet on this radio

I was thinking about comments or call sign to direct the message if the packet makes it to an iGate

[VK3KYY]

What sort of messages?

The GD77 and UV380 hardware could send other AX25 packets.
Currently there is a packet length limitation on the MD9600, of about 75 bytes, including preamble flags and CRC and end flags etc. Hence why we can't send a comment with the APRS packet on this radio

I was thinking about comments or call sign to direct the message if the packet makes it to an iGate

Comment text at the end of the APRS packet is already in this release up to 24 characters (not however on the MD9600 yet because of hardware limitations)

Sending the callsign in the comment text seems pointless as the packet data has to contain the senders callsign, so sending again in plain text seems like duplication.

Status text is sent in a separate message and has not been implemented yet. But I can't see any problems with implementing this.

We could also send general message packets, not including the location data, but we would need to write a some sort of CAT type functionality, as its impractical to attempt to type messages on a numeric keypad

And as the firmware can't currently receive APRS, and I don't know for sure whether the hardware audio filters will allow us to ever add APRS Rx, I can't see a use case for this

[VK3KYY]

About callsign in comment field, and SSID already containing the callsign. I know that (including an org I was involved w/ off and on locally) some radios are configured with tactical SSIDs, typically for events use. And thus, some orgs might or might not put callsigns in the comment field instead, as the SSID will not contain the licence callsign. So I guess it depends on the user or the org who manages the APRS operation.

I guess it depends on your country, but here in Canada, it is legal and allowed to use tactical callsign on the SSID in APRS, as long as other method(s) of identification is going to be used.

SSID is not the callsign, it data that is appended / sent after the callsign in the AX25 packet.
Callsign is actually the AX25 data source.
APN000 is the destination (other destinations can be used)

So if you are saying that the source identifier may not be your callsign, and you will put the callsign in the comment, then thats up to your operating environment, but for Ham operation normally your callsign is used as the data source

See the Amateur radio AX25 specification

http://www.tapr.org/pdf/AX25.2.2.pdf

and the APRS specification

http://www.aprs.org/doc/APRS101.PDF

Both specify that for Amateur radio operation the source field is your callsign

The firmware is intended for Amateur Radio use only.