mirror of
https://github.com/richonguzman/LoRa_APRS_iGate.git
synced 2026-11-03 04:02:20 +01:00
Specify IS server #243
Assignees
adam (Adam Wojcieszonek)
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: adam/LoRa_APRS_iGate#243
Reference in new issue
Block a user
I am running a HelTec ESP32 LoRa V3 SX1262 board running the IGate (Dec 2025) firmware.
I tried changing the IS server to an IP address on my local network where I run a "local IS server" for testing.
Server: xx.x.x.x (local network) Port: 14590
The connection is made, but the firmware then get stuck with the LCD showing:
____ "Connected!
____ loading ...."
The server that is listening on that port shows the connection, so it made it past the APRS-IS connection part, but whatever comes right after that does not load. A local tracker that transmits is not transferred to the attached server.
NOTE: Changing back to server: noam.aprs2.net and port 14580 as the only changes, the device works as expected.
Igate is expecting to receive "verified" when trying to log into server to work with it.
See about to output some "verified" packet back to the igate to continue
With the local server settings, the USB port reports:
But the LCD screen shows
____ "Connected!
____ loading ...."
With noam.aprs2.net the USB port shows:
Robert Giuliano
KB8RCO
please explain the process of this "custom" server of yours...
maybe there is another important issue missing:
the aprs-is servers send packets to be recognized with "#" as the start of it ...
so all packets from server to igate should have the "#" as a start and then "verified" in it to complete the process.
The server is a part of APRSIS32 (wiki: http://aprsisce.wikidot.com/)
I would expect that if the issue was with the data coming from the server, it would just ignore things from the server and do nothing.
Instead, the IGate firmware connects, but then appears to get hung-up on loading settings after that.
latest firmware from 2 days ago should go on with all the process if the verification fails...
The verification didn't fail. The connection is made.
The software is Version: 2025-12-22
Is there something newer?
BTW: Thanks for the extremely quick replies and direct feedback!
I appreciate you working with me on it.
So
What do you expect from this? To send all Rx packets to the server/app?
Is this is yes: why don't you use it as tnc which should work right away without any mods
I have 2 HelTec ESP32 LoRa V3 SX1262 boards. One is configured as a tracker that will be used on a High Altitude Balloon for a local school science project. I was using the other as an IGATE for testing. I was trying to use a local IGATE because I had the tracker set to beacon very fast and didn't want to use a common frequency.
I have proven the concept out at slower rates using the setup with NOAM.APRS2.NET:14580.
But during the flight, the idea was to get 3 LoRa IGates running on a different frequency and interfacing with a local server (using APRSIS32).
Going to have to pause this for the Holidays.
I tried connecting another device to APRSIS32's local server and it appears to provide the "#"
APRSIS32 2024/09/05 17:14
logresp CALLSIGN verified, server KB8RCO
logresp CALLSIGN verified, server KB8RCO
Digging a bit deeper ...
Now I am getting a "Bind Error" from APRSIS32.
I don't remember seeing that in the APRSIS32 log before.
It might be on APRSIS32 side of things.
I connected Direwolf APRS as a client (KB8RCO-11) to my "Local APRS-IS server" (KB8RCO) and used the IGATE debug feature to view as much information as possible.
Here is what it reports:
Next I tried using the IPv4 address in the LoRa IGate using KB8RCO-10, but it still stopped at
On the APRS-IS Local Server side it reports:
It also receives a position reports from the LoRa IGate, so there is some communication.
Also running is a LoRa tracker (your tracker firmware) as KB8RCO-7
so where are the "disconnection" problem?
it seems to be working , right?
NOT working. It is not a disconnect problem. It is more of a "Lock-up" problem.
Right after the LoRa board connects to the local server.
NOTHING happens after that connection to the APRS-IS server. Display "LOCKS" showing "Connected! ! Loading ..."
A video of the working device shows:
Change just the APRS-IS settings (address and port)
above steps 1, 2, 3 happen, but that is all.
Display doesn't change from that state. Local APRS-IS seems to accept the information starts sending the board data.
But the board does not sent anything to the local APRS-IS.
I already posted the output for the ESP32 LoRa V3 serial output.
Since the next display seems t come from APRS_IS_Utils::checkStatus(), I assume the miscommunication is in there.
nothing will be sent to the APRS-IS as you changed the server and port.
so if you don't enable your PC app to send it to aprs-is servers, it will only get to your app and not aprs-is.
The issue with the screen stoping to update any new info needs to be addressed differently:
is Digipeater enabled?
is TNC enabled?
Nothing is sent to MY LOCAL APRS-IS server that it is directly connected to.
The serial (debug) has no other entries, and the display just shows "Connected! ! loading ..."
so the firmware is "STUCK" somewhere after print "Connected! ! loading ..." to the display.
all this steps are after the Wifi connection process:
NTP_Utils::setup();
SYSLOG_Utils::setup();
WX_Utils::setup();
WEB_Utils::setup();
TNC_Utils::setup();
MQTT_Utils::setup();
Utils::checkRebootMode();
APRS_IS_Utils::firstConnection();
SLEEP_Utils::checkSerial();
please validate that all of them are disabled...
but as i check this.... maybe the aprs_is::firstConnection is not being fully processed with your "special" local aprs-server
so check this as packets validations in the communication between iGate and your server:
"verified" is expected for the igate to understand that the aprs-is (fake or real) has been achieved.
all packets that the igate expect to hear from aprs-is (or your server) must be without any "#" at the start of the string/line.
I am not sure how to do that. I have only programmed the board through the website.
I am running this on Linux . I did download Visual Code Wtudio, installed platformio, and downloaded the code from github.
I've never used Visual Code Studio before, so not sure how to open the project and compile it.
by validation of this:
NTP_Utils::setup();
SYSLOG_Utils::setup();
WX_Utils::setup();
WEB_Utils::setup();
TNC_Utils::setup();
MQTT_Utils::setup();
Utils::checkRebootMode();
APRS_IS_Utils::firstConnection();
SLEEP_Utils::checkSerial();
over the WebUI configuration page:
Just set Repeater Mode: OFF
Eco Mode: OFF (Normal mode - WiFi and Serial output enabled)
Sent those setting to the board through the web-gui.
Same result.
Unfortunately, I have to stop for the night.
I have an appointment I must go to.
Again, thanks for all your patience.
i have many questions:
is your app enabled to be used as a "fake" APRS-IS
or should you just use this app as a TNC connecting to the LoRa iGate?
can you "again" explain me the use case of it?
I will give the TNC connection a try.
Unfortunately, I will have my family here for a late Christmas celebration.
That means my radio room becomes a guest bedroom, and I cannot run more test until they leave (Jan 5).
I may get a little time tomorrow morning, but not sure how much
Thanks for all your help this far. More to come in the future.
Ok
Let me know any new findings
Using the KISS TNC function is working perfectly!
Thanks for you help and patience!
awesome news... it was easy than to fight the other way ;)