APRS dev discussion - Githubissues

sq2mo commented 7 months ago

Configured all values in U.Info, set both MSG and GPS channels and radio is sending the APRS frames which are decoded correctly by direwolf :+1:

Minor stuff that could be fixed:

MySSID and DigiID are probably kept in the RAM, as they vanish after restarting the radio.
For DigiID, I would get rid of the setting, moving the number to AprsDIG. Note that some of the paths like NOGATE or RFONLY do not have the number at all.
Latitude and Longiture get random letters prepended - I've typed in GPS LAT and LON in APRS format of ddmm.mm, including the symbol characters at the end.

Thanks for your good work! Happy to test any next version.

tristanmoney commented 7 months ago

I tested APRS as well. It works quite well but "H" is added after latitude (should be "N" for my location) and "a" is added after longitude (should be W for my location). A great addition to these radios, very excited for the next release. APRS

phdlee commented 7 months ago

Thanks for testing, It's working properly.I'm so happy. 1.problem (bug) for MySSID, DigiID are perhaps that's my mistake, i will ifx it soon 2.So should remove the digiID part? If need DigiID, we can add it into AprsDIG as shown below. For example, if the digi id is 1, add 'AAA-1' <-- to AprsDIG. If don't need Digi ID, it's AAAA Is that right?

3.I need to find out if there is a problem when reading coordinate information from EEProm. If you can take a picture of the entered value and send it to me, I will test the same.

Thanks again Ian KD8CEC

On Mon, Feb 5, 2024 at 1:55 AM sq2mo @.***> wrote:

Configured all values in U.Info, set both MSG and GPS channels and radio is sending the APRS frames which are decoded correctly by direwolf 👍

Minor stuff that could be fixed:

MySSID and DigiID are probably kept in the RAM, as they vanish after restarting the radio.

For DigiID, I would get rid of the setting, moving the number to AprsDIG. Note that some of the paths like NOGATE or RFONLY do not have the number at all.

Latitude and Longiture get random letters prepended - I've typed in GPS LAT and LON in APRS format of ddmm.mm, including the symbol characters at the end.

Thanks for your good work! Happy to test any next version.

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPHBQUF7UDD2BHLZDV3YR64QJAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEYTOMJZGQ3DMMQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

phdlee commented 7 months ago

Thank you for testing. It probably appears to be a program bug. As soon as I fix it, I will upload 0.2C, the bug-fixed version. Thank you again. Ian KD8CEC

On Mon, Feb 5, 2024 at 7:16 AM tristanmoney @.***> wrote:

I tested APRS as well. It works quite well but "H" is added after longitude (should be "N" for my location) and "a" is added after latitude (should be W for my location). A great addition to these radios, very excited for the next release. APRS.png (view on web) https://github.com/phdlee/uvk5cec/assets/54490270/90e75061-92c9-4259-894b-e24294b00b03

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1925943701, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPDXNCNW6R2DJUE6UF3YSACFTAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVHE2DGNZQGE . You are receiving this because you are subscribed to this thread.Message ID: @.***>

jangelor commented 7 months ago

This is great work and development so far. Congratulations! I think it has really good potential in making the Quansheng a very inexpensive radio for APRS. I have some comments on the APRS message format. It is incorrect, and it is being read as a status instead, since it lacks the correct message destination. Here is the format for an APRS message example:

DU2XXR-9>APZIOR,WIDE1-1,WIDE2-1::APRSPH :CQ test message

In this message, these are the elements:

DU2XXR-9 is the originating station, which is my callsign and SSID.
APZIOR is the APRS "tocall" or basically just the identifier of which software I am using. Since you are using an experimental bot, this can be APZxxx where xxx can be your arbitrary identifier (with Z being "experimental"). Currently, you let users set their own tocall, but if you need to save on space, this can be just hardcoded. I recommend using this instead for another setting, as below.
WIDE1-1,WIDE2-1 is the digipath. This basically defines the digipeater path or hops that the message or packet takes. The above means 3 "hops" with the numbers being decremented after each transmit. When it runs out, the packet or message is no longer retransmitted by the digipeaters. I recommend you support two digipaths, so that users can define one for each. The digi SSID you included can be removed, as users have the option to define their own digipath like WIDE1 (this is from the old "paradigm") or something like WIDE1-1 for the first digipath and WIDE2-1 for the second, etc. For simplicity sake, this can be one digipath only like WIDE2-1. But allowing for two (separated by comma) will make it more flexible. This can also be RFONLY (message/packet will not be gated into APRS-Internet Service) or NOGATE which does the same. It can also be a specific digipeater or igate as the path.
::APRSPH : This is the "addressee" or "destination" station that the APRS messaage is addressed to. This is exactly 9 characters, with up to 6 callsign characters, a hyphen, and up to 2 SSIDs, so for example DU2XXR-10. If the callsign+ssid is less than 9 characters, this needs to be filled up with a space. For example ::N2RAC-7 :
:CQ test message. This is now the message content. Maximum is 67 characters. I just used this as an example, since "CQ" is one of the commands to interact with my bot. An APRS user can send a message to another APRS user (as addressed in the addressee field), and this can be any message.

In the APRS spec, there can also be a message ID or paged message. APRS capable radios and software will usually resend a message 5 times, until it is acknowledged or "ACK" by the target station. This can be particularly useful in an RF environment when the station is moving, portable, or located within several digipeater hops. This ensures reliability of message sending. When an ACK is received, the sending radio then stops the message re-sends. This is usually in the format of {XXX or up to a 3-number or character ID after the {. The ACK is formatted as an ackXXX

More information here: https://github.com/stephanelsmith/micro-aprs/blob/master/docs/encdec/README.md

I have not provided additional information on positioning and status, since I am mostly focused on APRS messaging.

Feel free to use my bot to test messages whether they are being received/processed properly: https://aprsph.net . The code to that is here btw: github.com/jangelor/ioreth

phdlee commented 7 months ago

thank you, I learned a lot about APRS today. I modified it by looking at the refrence book about APRS protocol In the future, we will add features little by little as we look at the rule book.

Ian KD8CEC

On Mon, Feb 5, 2024 at 2:09 PM jangelor @.***> wrote:

This is great work and development so far. Congratulations! I think it has really good potential in making the Quansheng a very inexpensive radio for APRS. I have some comments on the APRS message format. It is incorrect, and it is being read as a status instead, since it lacks the correct message destination. Here is the format for an APRS message example:

DU2XXR-9>APZIOR,WIDE1-1,WIDE2-1::APRSPH :CQ test message

In this message, these are the elements:

DU2XXR-9 is the originating station, which is my callsign and SSID.

APZIOR is the APRS "tocall" or basically just the identifier of which software I am using. Since you are using an experimental bot, this can be APZxxx where xxx can be your arbitrary identifier (with Z being "experimental"). Currently, you let users set their own tocall, but if you need to save on space, this can be just hardcoded. I recommend using this instead for another setting, as below.

WIDE1-1,WIDE2-1 is the digipath. This basically defines the digipeater path or hops that the message or packet takes. The above means 3 "hops" with the numbers being decremented after each transmit. When it runs out, the packet or message is no longer retransmitted by the digipeaters. I recommend you support two digipaths, so that users can define one for each. The digi SSID you included can be removed, as users have the option to define their own digipath like WIDE1 (this is from the old "paradigm") or something like WIDE1-1 for the first digipath and WIDE2-1 for the second, etc. For simplicity sake, this can be one digipath only like WIDE2-1. But allowing for two (separated by comma) will make it more flexible. This can also be RFONLY (message/packet will not be gated into APRS-Internet Service) or NOGATE which does the same. It can also be a specific digipeater or igate as the path.

::APRSPH : This is the "addressee" or "destination" station that the APRS messaage is addressed to. This is exactly 9 characters, with up to 6 callsign characters, a hyphen, and up to 2 SSIDs, so for example DU2XXR-10. If the callsign+ssid is less than 9 characters, this needs to be filled up with a space. For example ::N2RAC-7 :

:CQ test message. This is now the message content. Maximum is 67 characters.

In the APRS spec, there can also be a message ID or paged message. APRS capable radios and software will usually resend a message 5 times, until it is acknowledged or "ACK" by the target station. This can be particularly useful in an RF environment when the station is moving, portable, or located within several digipeater hops. This ensures reliability of message sending. When an ACK is received, the sending radio then stops the message re-sends. This is usually in the format of {XXX or up to a 3-number or character ID after the {. The ACK is formatted as an ackXXX

More information here: https://github.com/stephanelsmith/micro-aprs/blob/master/docs/encdec/README.md

I have not provided additional information on positioning and status, since I am mostly focused on APRS messaging.

Feel free to use my bot to test messages whether they are being received/processed properly: https://aprsph.net . The code to that is here btw: github.com/jangelor/ioreth

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1926242049, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPGZ66WBOX7BOIVVD3LYSBSQXAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRWGI2DEMBUHE . You are receiving this because you commented.Message ID: @.***>

phdlee commented 7 months ago

Changed from Version 0.2B to 0.2C.

The URL will remain the same. (Used as is to avoid generating too many release numbers) Thanks for the test.

Ian KD8CEC

On Mon, Feb 5, 2024 at 7:16 AM tristanmoney @.***> wrote:

I tested APRS as well. It works quite well but "H" is added after longitude (should be "N" for my location) and "a" is added after latitude (should be W for my location). A great addition to these radios, very excited for the next release. APRS.png (view on web) https://github.com/phdlee/uvk5cec/assets/54490270/90e75061-92c9-4259-894b-e24294b00b03

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1925943701, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPDXNCNW6R2DJUE6UF3YSACFTAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVHE2DGNZQGE . You are receiving this because you are subscribed to this thread.Message ID: @.***>

jangelor commented 7 months ago

Hi Ian. I can't seem to find the part where APRS is written in the source .gz you provided. Is it in the source here on github?

Angelo DU2XXR

sq2mo commented 7 months ago

Testing 0.2C showed good results.

WIDE1 with DigiID 1 (which is essentially WIDE1-1) works, so does RFONLY, so does generic path of "APRS". I needed to reconfigure lat/lon to decimal format.
I was able to pop up on aprs.fi, with symbol of "/D".

Thoughts for the future:

Don't think two Digi paths are supported yet. As @jangelor pointed, this is a good idea.
For destination call, I've used "APUVK5". You might also want to use some specific value APxxxx, so your software gets identified easily, on both air and APRS-IS. Current standardized device list is here: https://github.com/aprsorg/aprs-deviceid
APRS menu could be reorganized and separated from SSTV/CW functions.
TX-only TNC (serial-to-RF) would be great
EDIT: preamble (shifting tones before the actual frame) could be shorter to save some airtime, 200ms seems a good value

Appreciate your work.

tristanmoney commented 7 months ago

0.2C fixed the APRS positions for me. I had to put in the longitude as "-128.648" to get the "W" at the end. It would be great to be able to change the symbol too, but @phdlee is already doing amazing things here, I'm not going to complain about anything. Awesome work, I will continue to test future releases.

phdlee commented 7 months ago

Thanks for the test. Adding the ability to change icons is a very simple task, but it doesn't leave a lot of programming memory space. I'll make a note. Ian KD8CEC

On Tue, Feb 6, 2024 at 12:05 PM tristanmoney @.***> wrote:

0.2C fixed the APRS positions for me. I had to put in the longitude as "-128.648" to get the "W" at the end. It would be great to be able to change the symbol too, but @phdlee https://github.com/phdlee is already doing amazing things here, I'm not going to complain about anything. Awesome work, I will continue to test future releases. image.png (view on web) https://github.com/phdlee/uvk5cec/assets/54490270/808a0bd1-5757-4639-bb58-0cf50f7e23c0

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1928699703, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPEPRUB2TOLNQCNS2H3YSGMWPAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYGY4TSNZQGM . You are receiving this because you were mentioned.Message ID: @.***>

phdlee commented 7 months ago

The entire source code will be organized and uploaded at Version 1.0.

I am currently studying APRS Message. What is currently in UV-K5 is Status transmission. Reading the information you sent and the APRS regulations to add the message function. Ian KD8CEC

On Tue, Feb 6, 2024 at 12:59 AM jangelor @.***> wrote:

Hi Ian. I can't seem to find the part where APRS is written in the source .gz you provided. Is it in the source here on github?

Angelo DU2XXR

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1927323880, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPB2F7MDVJF5VAXR5FDYSD6XVAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRXGMZDGOBYGA . You are receiving this because you commented.Message ID: @.***>

phdlee commented 7 months ago

Thanks for the test. As jangelor suggested, it would be a good idea to hard code it with APZK5R or APUVK5 to reduce program space.

I will continue to revise it until version 1. Ian KD8CEC

On Tue, Feb 6, 2024 at 6:49 AM sq2mo @.***> wrote:

Testing 0.2C showed good results.

WIDE1 with DigiID 1 (which is essentially WIDE1-1) works, so does RFONLY, so does generic path of "APRS". I needed to reconfigure lat/lon to decimal format.

I was able to pop up on aprs.fi, with symbol of "/D".

Thoughts for the future:

Don't think two Digi paths are supported yet. As @jangelor https://github.com/jangelor pointed, this is a good idea.

For destination call, I've used "APUVK5". You might also want to use some specific value APxxxx, so your software gets identified easily, on both air and APRS-IS. Current standardized device list is here: https://github.com/aprsorg/aprs-deviceid

APRS menu could be reorganized and separated from SSTV/CW functions.

TX-only TNC (serial-to-RF) would be great

Appreciate your work.

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1928155609, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPHHVBACP3UJVZGJDXLYSFHWNAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYGE2TKNRQHE . You are receiving this because you commented.Message ID: @.***>

phdlee commented 7 months ago

The version has been newly released as 0.2E. I just added files to the existing release. If you have time, please test it. Ian KD8CEC

On Tue, Feb 6, 2024 at 12:05 PM tristanmoney @.***> wrote:

0.2C fixed the APRS positions for me. I had to put in the longitude as "-128.648" to get the "W" at the end. It would be great to be able to change the symbol too, but @phdlee https://github.com/phdlee is already doing amazing things here, I'm not going to complain about anything. Awesome work, I will continue to test future releases. image.png (view on web) https://github.com/phdlee/uvk5cec/assets/54490270/808a0bd1-5757-4639-bb58-0cf50f7e23c0

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1928699703, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPEPRUB2TOLNQCNS2H3YSGMWPAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYGY4TSNZQGM . You are receiving this because you were mentioned.Message ID: @.***>

phdlee commented 7 months ago

The version has been newly released as 0.2E. I just added files to the existing release. If you have time, please test it. (Fixed Aprs DST => APK5C1. (Changed from APUVK5) Since it is the same product but comes in several models, we added K5, firmware version C, and INDEX 1.)

Ian KD8CEC

On Tue, Feb 6, 2024 at 6:49 AM sq2mo @.***> wrote:

Testing 0.2C showed good results.

WIDE1 with DigiID 1 (which is essentially WIDE1-1) works, so does RFONLY, so does generic path of "APRS". I needed to reconfigure lat/lon to decimal format.

I was able to pop up on aprs.fi, with symbol of "/D".

Thoughts for the future:

Don't think two Digi paths are supported yet. As @jangelor https://github.com/jangelor pointed, this is a good idea.

For destination call, I've used "APUVK5". You might also want to use some specific value APxxxx, so your software gets identified easily, on both air and APRS-IS. Current standardized device list is here: https://github.com/aprsorg/aprs-deviceid

APRS menu could be reorganized and separated from SSTV/CW functions.

TX-only TNC (serial-to-RF) would be great

Appreciate your work.

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1928155609, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPHHVBACP3UJVZGJDXLYSFHWNAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYGE2TKNRQHE . You are receiving this because you commented.Message ID: @.***>

jangelor commented 7 months ago

Messaging is working very well now!

I used WIDE1 for AprsDP1 and 1 for SSID1 for DigiID, plus WIDE2 for AprsDP2, which made my digipath into WIDE1-1,WIDE2.

ISSUE: I wanted to set it into WIDE1-1,WIDE2-1 (the common standard for portable devices), but if I use WIDE2-1 for AprsDP2, it turns it into WIDE2--1 (with an extra -) for some reason. Perhaps needs to be fixed.

I set DX CALL to APRSPH, which means destination is APRSPH (my own bot at https://aprsph.net)

I made my message into CQ QshTest, which transmitted just that as a message to APRSPH.

My Yaesu FT1D received it

You can see that I got logged into the net as

An issue: I found that the message includes a msgID of {1 at the end of messages. I recommend against this for now until the radio is able to receive messages. That's because with the same msgID, other radios receiving the message might not display a different message sent if it's the same message ID being received (e.g., it's treated as duplicate). Also, receiving stations are forced to send an ack1 upon receiving the message, which is useless because the Quansheng is not able to receive ACKs yet.

I recommend that msgID needs to be incremental for each message sent. This can probably be something manually set (up to 3 digits). Or perhaps for now it can just be taken out because the radio does not receive yet.

Another improvement I can suggest is that when writing an APRS message, the CW MSGs can be used instead of a separate field. For example,

CWMSG1+CWMSG2+CWMSG3+...+CWMSG7

can be used to transmit a message (no spaces, but the user can insert a space in between words). Since there are 10 characters each, this would total to the APRS spec 67 characters (can truncate the last 3 chas from CWMSG7)

For example this can be the setting

CWMSG1 "Hello this" CWMSG2 " is Angelo" CWMSG3 " DU2XXR sen" CWMSG4 "ding an AP" CWMSG5 "RS message" CWMSG6 " from Quan" CWMSG7 "sheng"

A bit painstaking, but would work.

Also, the text input of the radio itself is very difficult, unlike usual APRS capable radios, which at least provide multi-tap capability on the keypad e.g., 2 for A, 222 for C, 33 for E, etc. I wonder if this can be a future feature. This is already done on the "messenger" app on another firmware. SEe https://www.youtube.com/shorts/0DMWYtcDYtM

jangelor commented 7 months ago

OK, I was able to make the digipath WIDE1-1,WIDE2-1 by using "WIDE2 1" (with space) on AprsDP2

I think it's more intuitive to just let the user set AprsDP2 exactly as they want it to, including the hyphen and SSID. For example, WIDE2-2 (with the hyphen).

Perhaps this can also be the same with AprsDP1 and just lose the need for a digiSSID (might save up space for other features/options). Just let us write it as we wish it to appear like WIDE1-1.

So in this case, the entire digpath string would be coming from AprsDP1,AprsDP2.

tristanmoney commented 7 months ago

I was able to send myself a message to PinPoint APRS. Great progress.

@phdlee one of your Youtube videos shows a GPS module plugged into the external mic jack for use with APRS. What model of GPS is it? I would like to order one for testing.

lyusupov commented 7 months ago

@phdlee

Ian, is there any chance to use an externally connected GNSS receiver together with this UV-K5 APRS firmware ? The way like shown on your video :

sq2mo commented 7 months ago

Messages, status and position do work for me just fine. Good work!

Things which could be improved:

preabmle is around 680ms long, could be 3x shorter (screen)
MySSID and DigiID are being set to 0 after radio reboot.

jangelor commented 7 months ago

Preamble can be something user-defined, like with Yaesu radios that provide 100, 150, 200, 250, 300, 400, 500, 750, and 1000 ms delays.

phdlee commented 7 months ago

That's a good idea. If you promise a specific character at the end of the CW message, you can send it up to that point. ex) sheng#! Let's consider increasing the message in version 0.4. It's probably needed for other functions besides APRS. Keyboard input method is currently difficult due to program space. Perhaps it would be possible to separate it into APRS-specific firmware. In order to connect to GPS, the firmware must be released in a separate version.

Ian KD8CEC

Message ID: @.***>

phdlee commented 7 months ago

I thought about it today, and I think I need to remove the DIGI SSID as you said and manage it in TEXT WIDE1 1 or WIDE1-1 (not allow - so i remove '-' char before send AX.25)

On Thu, Feb 8, 2024 at 10:20 AM jangelor @.***> wrote:

OK, I was able to make the digipath WIDE1-1,WIDE2-1 by using "WIDE2 1" (with space) on AprsDP2 image.png (view on web) https://github.com/phdlee/uvk5cec/assets/58649783/e2332d2b-818f-4890-aa17-e90a5077dd6e image.png (view on web) https://github.com/phdlee/uvk5cec/assets/58649783/11a80599-fb00-44b3-a294-0f527ea6c106

I think it's more intuitive to just let the user set AprsDP2 exactly as they want it to, including the hyphen and SSID. For example, WIDE2-2 (with the hyphen).

Perhaps this can also be the same with AprsDP1 and just lose the need for a digiSSID (might save up space for other features/options). Just let us write it as we wish it to appear like WIDE1-1.

So in this case, the entire digpath string would be coming from AprsDP1,AprsDP2.

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1933216047, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPHCDH3MBP4CB4KSKCDYSQR7NAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZTGIYTMMBUG4 . You are receiving this because you were mentioned.Message ID: @.***>

phdlee commented 7 months ago

I bought it at a local market. Anything that supports 9600bps and nmea protocol is possible. In order to connect GPS to UV-K5, we may need to separate it into a separate firmware version that is different from the existing firmware. This is because there is only one connector, and CW-PADDLE, microphone, UART, etc. are used together. Ian KD8CEC

On Thu, Feb 8, 2024 at 12:20 PM tristanmoney @.***> wrote:

I was able to send myself a message to PinPoint APRS. Great progress.

image.png (view on web) https://github.com/phdlee/uvk5cec/assets/54490270/9bdc2045-f7c0-4590-b0a4-bb35a73a5441

@phdlee https://github.com/phdlee one of your Youtube videos shows a GPS module plugged into the external mic jack for use with APRS. What model of GPS is it? I would like to order one for testing.

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1933301604, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPA54ZWY26H7VQAS3WDYSQ773AVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZTGMYDCNRQGQ . You are receiving this because you were mentioned.Message ID: @.***>

phdlee commented 7 months ago

I was reluctant to use GPS because parsing the NMEA protocol took up a lot of program space. However, while looking at the APRS protocol document recently, I found out that GPS data can be transmitted as is. i will probably perform some experiments regarding APRS again in version 0.4. ian KD8CEC

On Thu, Feb 8, 2024 at 1:51 PM Linar Yusupov @.***> wrote:

@phdlee https://github.com/phdlee

Ian, is there any chance to use an externally connected GNSS receiver together with this UV-K5 APRS firmware ? The way like shown on your video https://www.youtube.com/watch?v=VXECf1R-umg&t=7s : image.png (view on web) https://github.com/phdlee/uvk5cec/assets/5849637/f27896dd-99bd-4032-909e-cb78a601dacb

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1933359953, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPDXQRZIGOICLQRY3CDYSRKTJAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZTGM2TSOJVGM . You are receiving this because you were mentioned.Message ID: @.***>

phdlee commented 7 months ago

k~ I will increase the preamble by about 30%. Would you like to try CW-related settings as well? (for testing purposes) I would like to know if CW-related settings are maintained even after rebooting or if they also disappear.

Ian KD8CEC

On Fri, Feb 9, 2024 at 2:16 AM sq2mo @.***> wrote:

Messages, status and position do work for me just fine. Good work!

Things which could be improved:

preabmle is around 680ms long, could be 3x shorter (screen) image.png (view on web) https://github.com/phdlee/uvk5cec/assets/17483811/e2f83dc8-937f-4be9-81e9-dfec54981504

MySSID and DigiID are being set to 0 after radio reboot.

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1934581722, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPC3IXBSCZ3MGT3QCB3YSUCAJAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZUGU4DCNZSGI . You are receiving this because you were mentioned.Message ID: @.***>

sq2mo commented 7 months ago

Would you like to try CW-related settings as well? (for testing purposes) I would like to know if CW-related settings are maintained even after rebooting or if they also disappear.

CW Tone, Dly and WPM from main menu are also not saved across reboots. As well as STVEnc and STV CW.

CT2IRJ commented 7 months ago

I bought it at a local market. Anything that supports 9600bps and nmea protocol is possible. In order to connect GPS to UV-K5, we may need to separate it into a separate firmware version that is different from the existing firmware. This is because there is only one connector, and CW-PADDLE, microphone, UART, etc. are used together. Ian KD8CEC … On Thu, Feb 8, 2024 at 12:20 PM tristanmoney @.> wrote: I was able to send myself a message to PinPoint APRS. Great progress. image.png (view on web) https://github.com/phdlee/uvk5cec/assets/54490270/9bdc2045-f7c0-4590-b0a4-bb35a73a5441 @phdlee https://github.com/phdlee one of your Youtube videos shows a GPS module plugged into the external mic jack for use with APRS. What model of GPS is it? I would like to order one for testing. — Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPA54ZWY26H7VQAS3WDYSQ773AVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZTGMYDCNRQGQ . You are receiving this because you were mentioned.Message ID: @.>

Right.

I'm really interested on the connection between the GPS module and the K5. I have a bunch of Vaisala RS41 radiosondes and some of them have broken sensor booms and I can salvage the GPS units from them

Keep up the good work

73

tristanmoney commented 7 months ago

I wonder if there is another UART on the microcontroller that could be used to solder an internal GPS to? Will try to look this weekend.

Also, if program space is an issue, could the microcontroller be replaced? Maybe find something pin compatible but with more memory.

phdlee commented 7 months ago

There is no unused pin. Only two GPIOs of BK4819 remain (high-speed control is not possible), and the rest are all in use. In particular, some pins serve multiple purposes. (Keypad + FM, etc.) UART0 is connected to a 3.5mm connector and is used for firmware updates, etc. The 3.5mm connector is used to connect various I/Os together. ex) UART0 RX

PTT

The firmware was re-uploaded to version 0.2H. Most of the opinions expressed so far have been reflected. Preamble, text conversion of SSID, etc. If you have time, please test it. Ian KD8CEC

On Fri, Feb 9, 2024 at 12:24 PM tristanmoney @.***> wrote:

It looks like UART0 pins PC3 (TX) and PC4 (RX) are not connected to anything on the MCU: image.png (view on web) https://github.com/phdlee/uvk5cec/assets/54490270/cd74c7d6-103c-4b89-9dc4-5d8b7ae8fe3c

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1935280068, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPEZMPOZTMDMHHFHPT3YSWJF7AVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZVGI4DAMBWHA . You are receiving this because you were mentioned.Message ID: @.***>

phdlee commented 7 months ago

The firmware was re-uploaded to version 0.2H. Most of the opinions expressed so far have been reflected. Preamble, text conversion of SSID, etc. If you have time, please test it. Ian KD8CEC

On Tue, Feb 6, 2024 at 6:49 AM sq2mo @.***> wrote:

Testing 0.2C showed good results.

WIDE1 with DigiID 1 (which is essentially WIDE1-1) works, so does RFONLY, so does generic path of "APRS". I needed to reconfigure lat/lon to decimal format.

I was able to pop up on aprs.fi, with symbol of "/D".

Thoughts for the future:

Don't think two Digi paths are supported yet. As @jangelor https://github.com/jangelor pointed, this is a good idea.

For destination call, I've used "APUVK5". You might also want to use some specific value APxxxx, so your software gets identified easily, on both air and APRS-IS. Current standardized device list is here: https://github.com/aprsorg/aprs-deviceid

APRS menu could be reorganized and separated from SSTV/CW functions.

TX-only TNC (serial-to-RF) would be great

Appreciate your work.

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1928155609, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPHHVBACP3UJVZGJDXLYSFHWNAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYGE2TKNRQHE . You are receiving this because you commented.Message ID: @.***>

phdlee commented 7 months ago

The firmware was re-uploaded to version 0.2H. Most of the opinions expressed so far have been reflected. Preamble, text conversion of SSID, etc. If you have time, please test it. Ian KD8CEC

On Tue, Feb 6, 2024 at 12:59 AM jangelor @.***> wrote:

Hi Ian. I can't seem to find the part where APRS is written in the source .gz you provided. Is it in the source here on github?

Angelo DU2XXR

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1927323880, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPB2F7MDVJF5VAXR5FDYSD6XVAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRXGMZDGOBYGA . You are receiving this because you commented.Message ID: @.***>

sq2mo commented 7 months ago

After a short test, MySSID is still zeroed after reboot.

Regarding the preamble, it was too long and I was advising to make it shorter, i.e. 200ms like in direwolf. Perhaps I was not clear enough, sorry for that.

EDIT: One more thing, when sending a packet with a WIDE1-1 path configured, actual path SSID is incorrect. Direwolf does not recognize it as an AX25 frame.

Example: configured path is WIDE1-1, encoded should be: ae 92 88 8a 62 40 62 instead of the above, it is received as: ae 92 88 8a 62 40 c4

So last digit/SSID decoded is always 'b', when WIDE1-1 is configured in the radio. If path is set to WIDE1 (incorrect in APRS world), payload is: ae 92 88 8a 62 40 80

I'm using 'direwolf -t 0 -d p' to view the payload in hex.

tristanmoney commented 7 months ago

Also getting AX.25 errors with 0.2H. Tried both "WIDE1 1" and "WIDE1-1" in AprsDP1 with the same result.

phdlee commented 7 months ago

It was a bug when using a single Digipeater. This was a problem that occurred when functions were combined to save program memory space, and was corrected and uploaded as version V0.2J. If you have time, please test again Ian KD8CEC

On Sat, Feb 10, 2024 at 12:06 PM tristanmoney @.***> wrote:

Also getting AX.25 errors with 0.2H. Tried both "WIDE1 1" and "WIDE1-1" with the same result. image.png (view on web) https://github.com/phdlee/uvk5cec/assets/54490270/f19ce126-5342-4ab1-8a20-d6affa201a4a

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1936831415, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPFNMTFCWWOHHFKLC7TYS3P4TAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWHAZTCNBRGU . You are receiving this because you were mentioned.Message ID: @.***>

phdlee commented 7 months ago

sq2mo The preamble was reduced to 130 times and uploaded again as v0.2J.

The inability to save your EEPROM seems to be a different problem. Currently, your radio is not storing APRS or anything related to CW. I think you need to check your settings or memory status, not the Aprs function. If possible, would you like to do a Factory Reset and save My SSID without configuring anything? And if possible, please send me a personal email telling me what firmware you used previously. @.***

On Sat, Feb 10, 2024 at 2:39 AM sq2mo @.***> wrote:

After a short test, MySSID is still zeroed after reboot.

Regarding the preamble, it was too long and I was advising to make it shorter, i.e. 200ms like in direwolf. Perhaps I was not clear enough, sorry for that.

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1936327546, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPFKXFCPNYEPOO77FNDYSZNMLAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWGMZDONJUGY . You are receiving this because you were mentioned.Message ID: @.***>

sq2mo commented 7 months ago

@phdlee Now the frame is properly recognized with WIDE1-1 path configured.

After full factory reset, same behavior - MySSID is 0 after reboot. Any other folks have the same problem? If not, it is indeed my EEPROM contents problem...

Preamble is around 870ms currently:

Previous FW was from Egzumer.

CT2IRJ commented 7 months ago

Hi OM's

I've tested v0.2J, and I've succeeded in decoding messages with my TM-D700,

By the way, what is the proper LAT and LON format to be entered? I've tryed various permutation but still cannot get it right.

I've used 39xx.xx and -08xx.xx N39xx.xx / W08xx.xx and 39xx.xxN / 008xx.xxW tryed also with a comma (,) for the decimal but no success...

73 de CT2IRJ

tristanmoney commented 7 months ago

With 0.2J (and previous releases) MySSID is preserved after a power cycle. I am testing with the UV-K5(8) model. @sq2mo maybe your radio has a defect?

Status report, messaging, and position seem to work with 0.2J:

sq2mo commented 7 months ago

@sq2mo maybe your radio has a defect?

Indeed, my UV-K6 is a fallen one, k5prog reads only zeroes from EEPROM. So I am off testing until I fix this or get a new one :(

jangelor commented 7 months ago

Great work. I've shared it on the APRS Users and APRSThursday groups on Facebook for testing. So far, my radio does not lose any settings after a power cycle.

Some additional suggestions

Give several choices for "target" callsign or DX CALL so that one doesn't have to change it all the time.
Give an option to CWM transmit CW MSG 0-4 or CW MSG 5-9 and even SSTV MSG 1 -2 so that user essentially has 4 choices of stored messages to send: MSG (just 10 characters), CWM set 1 (up to 50 characters), CWM set 2 (up to 50 characters), and SSTV msg (up to 20 charactrs).
Lose the "message ID" or the trailing {1 ... this only adds congestion to the APRS network because the receiving radio or device has to send an "ack1" upon receiving a message. Unless there is already a means for the UV-K5 to receive messages and thus ACKs, this has no purpose.

lyusupov commented 7 months ago

@sq2mo

k5prog reads only zeroes from EEPROM.

I had the same issue while doing power up with PTT button active. I found out that the PTT+PowerOn is required for flashing firmware only. To read EEPROM with k5prog utility - just regular PowerOn procedure (by the volume knob) is sufficient.

sq2mo commented 7 months ago

@lyusupov Thanks, I am aware of both programming modes, unfortunately this is something else. Interesting that it's possible to save the channels from radio itself.

Hope to sort this out and continue the testing of so much appreciated APRS FW :)

sq2mo commented 7 months ago

I've been able to cure my radio! Certain EEPROM values seemed to be read only. Too much hacking :)

So now the only major thing for correction is looong preamble length. I am using a status frame to check it, and it's still at 870ms.

For the reference, Direwolf has the preamble set at 300ms and postamble to 100ms:

#define DEFAULT_TXDELAY     30  // *10mS = 300mS
#define DEFAULT_TXTAIL      10  // *10mS = 100mS

phdlee commented 7 months ago

CT2IRJ Sorry for the late reply. I've been building and testing version V0.3HF for a while.

LAT and LON can be entered in the following manner: 39.1111, -08.3333. (You must enter coordinates that we generally know, GPS coordinates that appear on Google Maps) Calculated internally in APRS format

Ian KD8CEC

On Sat, Feb 10, 2024 at 9:35 PM CT2IRJ @.***> wrote:

Hi OM's

I've tested v0.2J, and I've succeeded in decoding messages with my TM-D700,

By the way, what is the proper LAT and LON format to be entered? I've tryed various permutation but still cannot get it right.

I've used 39xx.xx and -08xx.xx N39xx.xx / W08xx.xx and 39xx.xxN / 008xx.xxW tryed also with a comma (,) for the decimal but no success...

73 de CT2IRJ

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1936996791, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPDE42C5NKNEZKWJC33YS5SS5AVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWHE4TMNZZGE . You are receiving this because you were mentioned.Message ID: @.***>

phdlee commented 7 months ago

thank you I found out another one. (MESSAGE ID) However, Message ID is not an option but a default, so 1 was added.

I will make a note of CW MSG5~9 and SSTV MSG 1~2 and add them when program space allows while working on Version 0.4. Since there are people waiting for the stable version, we plan to release the 0.2P version first. (Only the name will be changed.)

If you have any additional ideas, please let me know. I will make a note of it in my Todo List.

On Sun, Feb 11, 2024 at 5:18 AM jangelor @.***> wrote:

Great work. I've shared it on the APRS Users and APRSThursday groups on Facebook for testing. So far, my radio does not lose any settings after a power cycle.

Some additional suggestions

Give several choices for "target" callsign or DX CALL so that one doesn't have to change it all the time.

Give an option to CWM transmit CW MSG 0-4 or CW MSG 5-9 and even SSTV MSG 1 -2 so that user essentially has 3 choices of stored messages to send.

Lose the "message ID" or the trailing {1 ... this only adds congestion to the APRS network because the receiving radio or device has to send an "ack1" upon receiving a message. Unless there is already a means for the UV-K5 to receive messages and thus ACKs, this has no purpose.

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1937111614, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPHTY4MSPE45BMDVY23YS7IY3AVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXGEYTCNRRGQ . You are receiving this because you were mentioned.Message ID: @.***>

phdlee commented 7 months ago

I bought a GPS for about $2, easily available on Aliexpress and not at the local market. Once the GPS module is delivered, we plan to add the APRS function again in Version 0.4 or create an APRS-only version while testing.

Ian KD8CEC

On Thu, Feb 15, 2024 at 4:49 AM sq2mo @.***> wrote:

I've been able to cure my radio! Certain EEPROM values seemed to be read only. Too much hacking :)

So now the only major thing for correction is looong preamble length. I am using a status frame to check it, and it's still at 870ms.

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1944487658, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPCIKUH3TWQKT5A5ECTYTUIM5AVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBUGQ4DONRVHA . You are receiving this because you were mentioned.Message ID: @.***>

CT2IRJ commented 7 months ago

Hi,

thanks Ian, eventually I've managed to figure it out :) It is working. Now, how to interface the GPS module to the K5? I've searched but could not find any info on it.

My plan is to re-use one module recovered for RS-41 radiosondes and place it a) inside an external PTT case, or is space allows (wich I doubt) inside the radio itself.

Thanks for all your work.

73 de CT2IRJ

CT2IRJ Sorry for the late reply. I've been building and testing version V0.3HF for a while. LAT and LON can be entered in the following manner: 39.1111, -08.3333. (You must enter coordinates that we generally know, GPS coordinates that appear on Google Maps) Calculated internally in APRS format Ian KD8CEC … On Sat, Feb 10, 2024 at 9:35 PM CT2IRJ @.> wrote: Hi OM's I've tested v0.2J, and I've succeeded in decoding messages with my TM-D700, By the way, what is the proper LAT and LON format to be entered? I've tryed various permutation but still cannot get it right. I've used 39xx.xx and -08xx.xx N39xx.xx / W08xx.xx and 39xx.xxN / 008xx.xxW tryed also with a comma (,) for the decimal but no success... 73 de CT2IRJ — Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPDE42C5NKNEZKWJC33YS5SS5AVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWHE4TMNZZGE . You are receiving this because you were mentioned.Message ID: @.>

darksidelemm commented 7 months ago

Where is the source code for the more recent releases? (e.g. 0.2P?) I'm keen to have a look at how APRS has been implemented.

phdlee commented 6 months ago

CT2IRJ GPS cannot be connected yet. I only tested it. We are planning to create an APRS-only version so that GPS can be connected. It is planned for 0.4 Version.

Ian KD8CEC

On Thu, Feb 15, 2024 at 11:16 PM CT2IRJ @.***> wrote:

Hi,

thanks Ian, eventually I've managed to figure it out :) It is working. Now, how to interface the GPS module to the K5? I've searched but could not find any info on it.

My plan is to re-use one module recovered for RS-41 radiosondes and place it a) inside an external PTT case, or is space allows (wich I doubt) inside the radio itself.

Thanks for all your work.

73 de CT2IRJ

CT2IRJ Sorry for the late reply. I've been building and testing version V0.3HF for a while. LAT and LON can be entered in the following manner: 39.1111, -08.3333. (You must enter coordinates that we generally know, GPS coordinates that appear on Google Maps) Calculated internally in APRS format Ian KD8CEC … <#m6309206681911512059> On Sat, Feb 10, 2024 at 9:35 PM CT2IRJ @.> wrote: Hi OM's I've tested v0.2J, and I've succeeded in decoding messages with my TM-D700, By the way, what is the proper LAT and LON format to be entered? I've tryed various permutation but still cannot get it right. I've used 39xx.xx and -08xx.xx N39xx.xx / W08xx.xx and 39xx.xxN / 008xx.xxW tryed also with a comma (,) for the decimal but no success... 73 de CT2IRJ — Reply to this email directly, view it on GitHub <#9 (comment) https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1936996791>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPDE42C5NKNEZKWJC33YS5SS5AVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWHE4TMNZZGE https://github.com/notifications/unsubscribe-auth/AE4DZPDE42C5NKNEZKWJC33YS5SS5AVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZWHE4TMNZZGE . You are receiving this because you were mentioned.Message ID: @.>

— Reply to this email directly, view it on GitHub https://github.com/phdlee/uvk5cec/issues/9#issuecomment-1946184006, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE4DZPCPVD5NWYRC7YGWKLLYTYKDFAVCNFSM6AAAAABCY7ZZHWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBWGE4DIMBQGY . You are receiving this because you were mentioned.Message ID: @.***>

CT2IRJ commented 6 months ago

Hi Ian, thanks for repliyng.

You are doing an amazing job. If we can help in any way, please let us know.

73 de CT2IRJ

phdlee / uvk5cec

APRS dev discussion #9