Add support for YAAC #105

New Issue

2026-10-05T05:36:27+02:00

adam commented

2026-10-05 05:36:27 +02:00

Hello,

here is another multiplatform client that would be great to get to work with the LORA module.
I tried to set it up like the other examples here but i can't get it to connect neither bia TCP/IP nor via Serial.

https://www.ka2ddo.org/ka2ddo/YAACdocs/config_kissovertcp.html

Hello, here is another multiplatform client that would be great to get to work with the LORA module. I tried to set it up like the other examples here but i can't get it to connect neither bia TCP/IP nor via Serial. https://www.ka2ddo.org/ka2ddo/YAACdocs/config_kissovertcp.html

adam closed this issue

2026-10-05 05:36:27 +02:00

adam commented

2026-10-05 05:36:28 +02:00

there is Serial output and also KISS output (TNC2 encapsulated)

did both not work?

there is Serial output and also KISS output (TNC2 encapsulated) did both not work?

adam commented

2026-10-05 05:36:29 +02:00

yea i tried both options and nothing happens.

yea i tried both options and nothing happens.

adam commented

2026-10-05 05:36:30 +02:00

Here is a screenshot from the serial option

![Screenshot from 2024-07-19 16-59-35](https://github.com/user-attachments/assets/bc6f8183-6f79-4062-9467-a214d7bd5169) Here is a screenshot from the serial option

adam commented

2026-10-05 05:36:30 +02:00

will try to write the YAAC dev to know what I should do.

will try to write the YAAC dev to know what I should do.

adam commented

2026-10-05 05:36:31 +02:00

Could you please try two variants, for both the TNC Option must be switched on in the iGate. I assume you run LINUX on your computer.

KISS over TCP: Enter IP from iGate, Port 8001, enter Callsign, enable Transmit, disable TEMP1-1, enable WIDE1-1, disable Beacon, Protocol RAW AX25
Serial Option: Device name /tmp/tnc, Baud 115200, enter Callsign, enable Transmit, disable TEMP1-1, enable WIDE1-1, disable Beacon, Protocol RAW AX25
Then go to a console and enter socat PTY,link=/tmp/tnc TCP:ip_of_iGate:8001 &

Could you please try two variants, for both the TNC Option must be switched on in the iGate. I assume you run LINUX on your computer. 1) KISS over TCP: Enter IP from iGate, Port 8001, enter Callsign, enable Transmit, disable TEMP1-1, enable WIDE1-1, disable Beacon, Protocol RAW AX25 2) Serial Option: Device name /tmp/tnc, Baud 115200, enter Callsign, enable Transmit, disable TEMP1-1, enable WIDE1-1, disable Beacon, Protocol RAW AX25 Then go to a console and enter `socat PTY,link=/tmp/tnc TCP:ip_of_iGate:8001 &`

adam commented

2026-10-05 05:36:32 +02:00

as 3rd option (but this is not your origin question), you can run XAstir as APRS Client with socat out of option 2:

as 3rd option (but this is not your origin question), you can run XAstir as APRS Client with socat out of option 2: ![UqTQkW3ozxdaAUVU](https://github.com/user-attachments/assets/1dd4dc36-8975-4873-bc5d-9ccc13151688)

adam commented

2026-10-05 05:36:32 +02:00

it does seem that either the tcp/ip or the serial worked as i was receiving stations however when i try to send out any beacons nothing shows up on aprs.fi. The lora-aprs module does show up regularly sending beacons but nothing appears from YAAC.

Would the socat method then also theortically work for PAT?

it does seem that either the tcp/ip or the serial worked as i was receiving stations however when i try to send out any beacons nothing shows up on aprs.fi. The lora-aprs module does show up regularly sending beacons but nothing appears from YAAC. Would the socat method then also theortically work for PAT?

adam commented

2026-10-05 05:36:33 +02:00

it does seem that either the tcp/ip or the serial worked as i was receiving stations however when i try to send out any beacons nothing shows up on aprs.fi. The lora-aprs module does show up regularly sending beacons but nothing appears from YAAC.

Would the socat method then also theortically work for PAT?

so you receive from TNC but can send from TNC into LORA?

this is another scenario

> it does seem that either the tcp/ip or the serial worked as i was receiving stations however when i try to send out any beacons nothing shows up on aprs.fi. The lora-aprs module does show up regularly sending beacons but nothing appears from YAAC. > > Would the socat method then also theortically work for PAT? so you receive from TNC but can send from TNC into LORA? this is another scenario

adam commented

2026-10-05 05:36:34 +02:00

at the moment. I am not entirely sure. there are not that many APRS stations around me to test if i am receiving and on which interface that is. I will need to try again

at the moment. I am not entirely sure. there are not that many APRS stations around me to test if i am receiving and on which interface that is. I will need to try again

adam commented

2026-10-05 05:36:34 +02:00

it does seem that either the tcp/ip or the serial worked as i was receiving stations however when i try to send out any beacons nothing shows up on aprs.fi. The lora-aprs module does show up regularly sending beacons but nothing appears from YAAC.

Would the socat method then also theortically work for PAT?

Take care not to mix up things:
When the iGate runs in TNC mode you can access it via Port 8001. This makes sense if either

the iGate is not connected to APRS-IS and you want to see the stations on the map of XAstir or YAAC RX from the iGate
if the iGate is or is not connected to APRS-IS and you want to send and receive messages through the iGates SSID via XAstir
if the iGate is connected to APRS-IS and you additionally want to see the output RX from the iGate

In all cases the functionality of connection to aprsis, digipeating, beaconing, ... shall be done via the iGate from Ricardo configurable in the webUI

> it does seem that either the tcp/ip or the serial worked as i was receiving stations however when i try to send out any beacons nothing shows up on aprs.fi. The lora-aprs module does show up regularly sending beacons but nothing appears from YAAC. > > Would the socat method then also theortically work for PAT? Take care not to mix up things: When the iGate runs in TNC mode you can access it via Port 8001. This makes sense if either - the iGate is not connected to APRS-IS and you want to see the stations on the map of XAstir or YAAC RX from the iGate - if the iGate is or is not connected to APRS-IS and you want to send and receive messages through the iGates SSID via XAstir - if the iGate is connected to APRS-IS and you additionally want to see the output RX from the iGate In all cases the functionality of connection to aprsis, digipeating, beaconing, ... shall be done via the iGate from Ricardo configurable in the webUI

adam commented

2026-10-05 05:36:35 +02:00

Would the socat method then also theortically work for PAT?

Basically yes, socat "emulates" a serial KISS interface to PAT and a TCP KISS interface to the iGate

> Would the socat method then also theortically work for PAT? Basically yes, socat "emulates" a serial KISS interface to PAT and a TCP KISS interface to the iGate

adam commented

2026-10-05 05:36:36 +02:00

at the moment. I am not entirely sure. there are not that many APRS stations around me to test if i am receiving and on which interface that is. I will need to try again

With socat and the "&" at the end you see the received frames from iGate <-> Client in the terminal

> at the moment. I am not entirely sure. there are not that many APRS stations around me to test if i am receiving and on which interface that is. I will need to try again With socat and the "&" at the end you see the received frames from iGate <-> Client in the terminal

adam commented

2026-10-05 05:36:36 +02:00

yes, the lora-aprs module is transmitting correctly to aprs.fi the basic hardware installation works without any issues.

yes the ideal would be to be able to connect to the APRS-IS network via the hardware module, and then use YAAC or similar to send beacons, receive stations, send messages etc.

At the moment I am simply not sure if the TCP/IP is working or the Serial Variant is working, if anything is really working at all.
All I can say is that at one point some additional station data did appear on YAAC. However I am certainly not able to transmit anything into the APRS-IS network from YAAC or similar

yes, the lora-aprs module is transmitting correctly to aprs.fi the basic hardware installation works without any issues. yes the ideal would be to be able to connect to the APRS-IS network via the hardware module, and then use YAAC or similar to send beacons, receive stations, send messages etc. At the moment I am simply not sure if the TCP/IP is working or the Serial Variant is working, if anything is really working at all. All I can say is that at one point some additional station data did appear on YAAC. However I am certainly not able to transmit anything into the APRS-IS network from YAAC or similar

adam commented

2026-10-05 05:36:37 +02:00

yes, the lora-aprs module is transmitting correctly to aprs.fi the basic hardware installation works without any issues.

ok

yes the ideal would be to be able to connect to the APRS-IS network via the hardware module, and then use YAAC or similar to send beacons, receive stations, send messages etc.

ok except the beaconing. This should be done through the iGates configuration

At the moment I am simply not sure if the TCP/IP is working or the Serial Variant is working, if anything is really working at all. All I can say is that at one point some additional station data did appear on YAAC. However I am certainly not able to transmit anything into the APRS-IS network from YAAC or similar

Socat and XAstir are working perfect with the configs I sent you, I have this running in test-setup

> yes, the lora-aprs module is transmitting correctly to aprs.fi the basic hardware installation works without any issues. > ok > yes the ideal would be to be able to connect to the APRS-IS network via the hardware module, and then use YAAC or similar to send beacons, receive stations, send messages etc. > ok except the beaconing. This should be done through the iGates configuration > At the moment I am simply not sure if the TCP/IP is working or the Serial Variant is working, if anything is really working at all. All I can say is that at one point some additional station data did appear on YAAC. However I am certainly not able to transmit anything into the APRS-IS network from YAAC or similar Socat and XAstir are working perfect with the configs I sent you, I have this running in test-setup

adam commented

2026-10-05 05:36:38 +02:00

In terms of sending a beacon from YAAC. Would it not be possible to set the LORA board with callsign:5 and then send a beacon from YAAC with callsign:15

In terms of sending a beacon from YAAC. Would it not be possible to set the LORA board with callsign:5 and then send a beacon from YAAC with callsign:15

adam commented

2026-10-05 05:36:38 +02:00

sure, but what is the sense behind ?

Pure sending a beacon to RF or APRS-IS would work, but the way back (if someone wants to drop you a message would be broken up.
For this case you would need to connect to APRS-IS via YAAC and use the iGate as pure hardware lora module. All "intelligence" would have to be done by YAAC. There are more elegant solutions.

Maybe you explain what you are targeting, then we can help you to find a suitable solution.

sure, but what is the sense behind ? Pure sending a beacon to RF or APRS-IS would work, but the way back (if someone wants to drop you a message would be broken up. For this case you would need to connect to APRS-IS via YAAC and use the iGate as pure hardware lora module. All "intelligence" would have to be done by YAAC. There are more elegant solutions. Maybe you explain what you are targeting, then we can help you to find a suitable solution.

adam commented

2026-10-05 05:36:39 +02:00

so if i am supposed to data transfered when using socat, I don't see anything.
So there is still some issue

so if i am supposed to data transfered when using socat, I don't see anything. So there is still some issue

adam commented

2026-10-05 05:36:39 +02:00

![Screenshot from 2024-07-19 18-20-31](https://github.com/user-attachments/assets/bdf04c1c-02ff-4a9f-bcfd-ce622a13f911)

adam commented

2026-10-05 05:36:40 +02:00

so if i am supposed to data transfered when using socat, I don't see anything. So there is still some issue

How do you try to transfer data ?

> so if i am supposed to data transfered when using socat, I don't see anything. So there is still some issue How do you try to transfer data ?

adam commented

2026-10-05 05:36:41 +02:00

I am not sure what you mean, which data exactly? isn't this simply supposed to show any data sent from YAAC when using the serial tnc option?

I am not sure what you mean, which data exactly? isn't this simply supposed to show any data sent from YAAC when using the serial tnc option?

adam commented

2026-10-05 05:36:41 +02:00

I tried using YAAC with the LoRa Digi/IGate and it worked fine with TCP KISS.
Of course, you need to "Select APRS Server" in the LoRa Digi/IGate configuration.

Here is another approach to provide a bridge between LoRa APRS and the existing regular APRS RF network.
https://github.com/wb2osz/direwolf-doc/blob/main/APRS-LoRa-VHF-APRS-Bridge.pdf

73,
John WB2OSZ

I tried using YAAC with the LoRa Digi/IGate and it worked fine with TCP KISS. Of course, you need to "Select APRS Server" in the LoRa Digi/IGate configuration. Here is another approach to provide a bridge between LoRa APRS and the existing regular APRS RF network. [https://github.com/wb2osz/direwolf-doc/blob/main/APRS-LoRa-VHF-APRS-Bridge.pdf ](https://github.com/wb2osz/direwolf-doc/blob/main/APRS-LoRa-VHF-APRS-Bridge.pdf ) 73, John WB2OSZ

adam commented

2026-10-05 05:36:42 +02:00

then something may be wrong with my network @wb2osz becuase nothing seems to work as expected.
the kissutil does seem to connect but i don't know much more after that.

then something may be wrong with my network @wb2osz becuase nothing seems to work as expected. the kissutil does seem to connect but i don't know much more after that.

adam commented

2026-10-05 05:36:43 +02:00

so if i am supposed to data transfered when using socat, I don't see anything. So there is still some issue

could you try to start socat with -v option ? Then it should show you more

> so if i am supposed to data transfered when using socat, I don't see anything. So there is still some issue could you try to start socat with -v option ? Then it should show you more

adam commented

2026-10-05 05:36:43 +02:00

nothing at all.
I even enabled the syslog option and there is only one entry
APRSIS TX / StartUp_Status / https://github.com/richonguzman/LoRa_APRS_iGate 2024.06.15
nothing more is being written to the logs.
Sending and receiving packets to and from the module itself is fine and the module and it's SSID can be found on aprs-fi.

nothing at all. I even enabled the syslog option and there is only one entry APRSIS TX / StartUp_Status / https://github.com/richonguzman/LoRa_APRS_iGate 2024.06.15 nothing more is being written to the logs. Sending and receiving packets to and from the module itself is fine and the module and it's SSID can be found on aprs-fi.

adam commented

2026-10-05 05:36:44 +02:00

ah finally some data appeared on the socat -v output, although the syslog is still just one entry

ah finally some data appeared on the socat -v output, although the syslog is still just one entry

adam commented

2026-10-05 05:36:45 +02:00

ok, syslog is not working when on TNC mode, so this is normal.
When you RX or TX data it could be read in clear-text in the 1st digit of every line...

ok, syslog is not working when on TNC mode, so this is normal. When you RX or TX data it could be read in clear-text in the 1st digit of every line...

adam commented

2026-10-05 05:36:45 +02:00

in any case the data that appears on the syslog output is only what is being sent from YAAC, nothing else. So the data is still not reaching the lora module for some reason.

in any case the data that appears on the syslog output is only what is being sent from YAAC, nothing else. So the data is still not reaching the lora module for some reason.

adam commented

2026-10-05 05:36:46 +02:00

basic question, in iGate config, have you:

Section "Station", Symbol, set to "Red Diamond with L", entered valid callsign
Section "APRS-IS", enable "Enable APRS-IS connection" and "Gate APRS-IS Messages to RF"
Section "Beaconing", enable "Send our beacon to APRS-IS"
Section "LoRa", enable "Enable LoRa-TX" and "Enable LoRa-RX" and set to same freq

?

basic question, in iGate config, have you: - Section "Station", Symbol, set to "Red Diamond with L", entered valid callsign - Section "APRS-IS", enable "Enable APRS-IS connection" and "Gate APRS-IS Messages to RF" - Section "Beaconing", enable "Send our beacon to APRS-IS" - Section "LoRa", enable "Enable LoRa-TX" and "Enable LoRa-RX" and set to same freq ?

adam commented

2026-10-05 05:36:47 +02:00

Yes, this is why the iGate works and send packages to aprs.fi without an issue. There is something else happening when trying to connect to the igate either via serial or tcp/ip which doesn't seem to work

Yes, this is why the iGate works and send packages to aprs.fi without an issue. There is something else happening when trying to connect to the igate either via serial or tcp/ip which doesn't seem to work

adam commented

2026-10-05 05:36:47 +02:00

what is the callsign and ssid which is on iGate and YAAC ?

what is the callsign and ssid which is on iGate and YAAC ?

adam commented

2026-10-05 05:36:48 +02:00

i'd rather not provide my callsign, in any case the callsign with the iGate ssid is clearly visible on aprs.fi.

i'd rather not provide my callsign, in any case the callsign with the iGate ssid is clearly visible on aprs.fi.

adam commented

2026-10-05 05:36:49 +02:00

please have a look on https://www.findu.com/cgi-bin/raw.cgi?call=CALLSIGN and replace your callsign and ssid in this link.

The link is RAW APRS_IS data.
Check if something was TX from the iGate which looks like what you wanted to have.

please have a look on https://www.findu.com/cgi-bin/raw.cgi?call=CALLSIGN and replace your callsign and ssid in this link. The link is RAW APRS_IS data. Check if something was TX from the iGate which looks like what you wanted to have.

adam commented

2026-10-05 05:36:49 +02:00

its interesting because now of all of a sudden the two ssid's from YAAC just appeared on APRS.fi. So I really don't know what is going on

its interesting because now of all of a sudden the two ssid's from YAAC just appeared on APRS.fi. So I really don't know what is going on

Sign in to join this conversation.

main

Batt-comment-fix

IS2-mod

test-RP

updates-before-4.0.4

LoRa-Settings-fix

Tbeam1W

gps-sleep-fix

setPower-LoRa

supreme-update

aprspacketlib-message-update

payload-message-fix

sendCommentAfterXBeacons

map-html-security-fix

commit-update

WiFi-Password-error-management

rxDate-on-RX-Packets-in-webui

mDNS-update-fix

GPS-BAUD-RATE-AUTO-DETECT

update-CAD-timeout

Digipeater-updates-Morifef

solar-light-gateway-update

oled-screen-timeout-fix-in-AP-mode

newboard230926-3

ntp-update-change

new-Board-Indonesia

revision-loop-wifi

RP2350-add

limpieza-de-nombres-de-placas

new-board-RAK3312-RAK3112

further-fixes-v106

clean-parts-of-APRSPacketLib

aprspacketlib-105

fixes-geoscott

tnc-with-tnc2-update

TestPRJohnRokicki

24px-symbols

better-symbols

icons-on-map

preconfig-v4

geokscott-fix

query-answer-tacticall-fix

new-digi-mode

map_test1

CAD_1

richonguzman-patch-19

RPC-LoRa-DigiGate-1W

richonguzman-patch-18

lora32_GPS-add

richonguzman-patch-17

Tbeam-AXP192-and-sx1262-915-add

new-json

stackTraceFixOta

SP_V3.2.2

backBefore-FIX-OTA

RadioLib-moved-to-7.6.0

clean-saveNewDigiEcoModeConfig

VEXT-CTRL-fix

new-board_9M2IBR_ESP32

justCleanBeforeV3-2

blackList-update

25segBufferHash

backToDigi1

betterCleaningCode

digi-correction

masDigiBackUp

correccionCPU

moreHeltecV2

digiBackUpFix-plus-tactical

digi-backup-fix

Tactical

Heltec-v4

elegantOta-3.1.7

decodingFix

richonguzman-patch-16

heltec-Wireless-Paper-v1.2

HELTEC-Vision-Master-E290

APRS-IS-passcode-blocking-fix

newDeco

TXCO-fix

INA219-2

radiolib-excludes

add-AHT20

more-mods-aprspacketlib

richonguzman-patch-15

mqtt-beacon-fix

TNC-mas

NTP-server-fix

RxTxv3131

RxTxFreq

startup-delay

Freq-Beacon-Selection

self-mqtt-beacon

Op-defined-ntp_server

richonguzman-patch-14

richonguzman-patch-13

richonguzman-patch-12

richonguzman-patch-11

richonguzman-patch-10

richonguzman-patch-9

richonguzman-patch-8

richonguzman-patch-7

WirelessBridge

before3.1.2

newOTA

config-size-correction

LoRaHAM_V2

richonguzman-patch-6

richonguzman-patch-5

before3.1-2

tnc-name-fix

before3.1

heltec_paper_v12

more-Lora-posibilities

mqttVersionUpdate

mqtt-Fix

mqtt-Add

sleeperSyslog

coreTest

statusChange

acdMod

gpsPressureCorrection

corrections20250726

tncBuffer

richonguzman-patch-4

richonguzman-patch-3

richonguzman-patch-2

richonguzman-patch-1

UEM9

UEM8

HTCT62-fix1

UEM7

QRP-LG-Plus

QRP-LG-Plus-sleep

UEM6-1

UEM6

UEM5

UEM4

UEM3

UEM2

UEM1

timestamp-decoding

NewPR_LB5JJ

ethernet_001

updateMods_PETRKR

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/LoRa_APRS_iGate#105