dl9sau
commented
8 months ago Hello,
it's a better idea to contact me directly instead of opening a github ticket. But since you made this topic public, please let me first point out (for all other readers in the world ;) that fixed stations are recommended to use a beacon interval of 30-60 minutes.
I see your booted message at findu.com http://findu.com/: http://findu.com/cgi-bin/raw.cgi?call=OH2LAK-15&time=1
-> Per se, the aprs-is connection works.
In the web interface you may see that he sends this beacon to aprsis. (This is the part "aprsis_status = "OK, toAPRSIS: " + s_data;");
At http://findu.com/cgi-bin/errors.cgi I don't see your callsign. That's good.
You wrote, that RF to aprsis works correctly. Your own becacon and received-packets-over-lora go the same way: via the function send_to_aprsis(). Thus it's not really understandable, that your own beacon does not work, but the stuff you gate from RF works.
So my first question is: did you try another aprs server (i.e. euro.aprs2.net http://euro.aprs2.net/)? I ask because I never used igates.aprs.fi http://igates.aprs.fi/ and know anybody who used it. Perhaps there's a compatibility issue.
My next question (and I think it's the more important one): did you check your aprs symbol table / symbol code settings?
APRS symbol code and APRS symbol-table is really confusing - but these words are defined by the APRS standard.
Let's look at a working beacon: DB0LY-10>APLOX1,Q,qAU,DB0LY:!5312.72NL01316.47E&LoRa-APRS iGATE 433.775MHz Firmware SQ9MDD/DL9SAU/DL3EL ..and the code in prepareAPRSFrame(), that builds the frame above, is:
outString += (may_add_dao_extension ? aprsLatPresetDAO : aprsLatPreset);
outString += aprsSymbolTable;
outString += (may_add_dao_extension ? aprsLonPresetDAO : aprsLonPreset);
outString += aprsSymbol;-> Ok, first is symbolTable, second is symbol. In the case of db0ly: "L" is symbolTable, and "&" is symbol.
In your settings I read: | "aprs_s_table":"&",
"aprs_symbol":"L",
-> _____ "&" is symbolTable, and "L" is symbol in your setting.
I think this is the cause the packets are dropped.
Read more about aprs symbols at http://www.aprs.org/symbols/symbols-new.txt There you also find the definition of "L& - Lora Igate"
Compare it in that document with "/[ = Human" http://findu.com/cgi-bin/raw.cgi?call=DL9SAU-12&time=1 20231025100509,DL9SAU-12>APLOX1-1,qAU,DB0FRI-10:=5330.57N/00733.40E[229/000/145.500MHz d023/Thomas D23. LoRa 70cm; KISS-Test !W75! _____^SymTable ^SymCode
Btw, it is not a bug not prevent a user from configuring not-yet defined icons (as long as they are not reserved characters due to the spec). Else software would need to be recompiled if in the future new icons are invented and become valid.
In your settings we see a (correct) password. It would be wise to change it, but it's unchangeable by design. You're lost :-S
vy 73,
- Thomas dl9sau
Am 25.10.2023 um 09:38 schrieb oh2lak @.***>:
Using the TTGO-T-Beam with @dl9sau fork firmware, for some reason the location beacon of the TTGO-T-Beam LoRa iGate itself does not go to APRS-IS I can verify that connection to APRS-IS is functioning as packets do reach IS by observing e.g. https://aprs.fi/?c=raw&call=OH2LAK-15 and the igate is relaying from LoRa to APRS-IS successfully. The specific settings which should make the own beacon go to APRS-IS is enabled. Here's a list of variety of parameters I think have something to do with this topic; { "tx_aprsis_bc":true, "tx_aprsis_sm":true, "aprs_callsign":"OH2LAK-15", "aprs_relay_path":"WIDE1-1", "aprs_s_table":"&", "aprs_symbol":"L", "aprs_objnam":"", "aprs_comment":"Lora Digi/iGate 433.775", "aprs_lat_p":"60-11.4299N", "aprs_lon_p":"024-45.7920E", "pos_amb":0, "aprs_blist":"", "aprs_fb_interv":300, "aprs_fixed_beac":true, "aprsis_en":true, "aprsis_srv_h":"igates.aprs.fi", "aprsis_srv_p":14580, "aprsis_fltr":"", "aprsis_call":"", [..] "aprsis_2rf":1, } — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
OH2LAK
Using the TTGO-T-Beam with @DL9SAU fork firmware, for some reason the location beacon of the TTGO-T-Beam LoRa iGate itself does not go to APRS-IS
I can verify that connection to APRS-IS is functioning as packets do reach IS by observing e.g. https://aprs.fi/?c=raw&call=OH2LAK-15 and the igate is relaying from LoRa to APRS-IS successfully.
The specific settings which should make the own beacon go to APRS-IS is enabled. Here's a list of variety of parameters I think have something to do with this topic;
{ "tx_aprsis_bc":true, "tx_aprsis_sm":true, "aprs_callsign":"OH2LAK-15", "aprs_relay_path":"WIDE1-1", "aprs_s_table":"&", "aprs_symbol":"L", "aprs_objnam":"", "aprs_comment":"Lora Digi/iGate 433.775", "aprs_lat_p":"60-11.4299N", "aprs_lon_p":"024-45.7920E", "pos_amb":0, "aprs_blist":"", "aprs_fb_interv":300, "aprs_fixed_beac":true, "aprsis_en":true, "aprsis_srv_h":"igates.aprs.fi", "aprsis_srv_p":14580, "aprsis_fltr":"", "aprsis_call":"", "aprsis_pw":"20397", "aprsis_2rf":1, }