Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Issue transmitting with Pseudo APRS-IS Server plug-in
Hi,
I installed the?Pseudo APRS-IS Server plug-in and I can successfully connect and receive packets using the Python aprslib client. However when I try to transmit a packet, I can see the packet in the raw messages log of YAAC but no actual transmission is happening. I have both option checkboxes checked and successfully logged in as an authenticated user. I have a single port setup (Direwolf) and have enabled transmission, I can send beacon and messages from YAAC with no issues, problem is when connecting to the pseudo APRS-IS server. Any suggestions on how to send messages from a Python script? Thanks, Vassilis |
Greetings.
When you set up the Pseudo-APRS-IS plugin, are you sure you updated its configuration to enable "Forward authorized transmissions from client through YAAC's upstream connection"? If that isn't checked, APRS packets from sub-clients of YAAC won't be sent onwards. And you have to use a valid passcode for the callsign specified by your sub-client, or the packets won't be forwarded either; I'm assuming the sub-clients are using your same callsign, but different SSID, so the same passcode used for your upstream Internet connection can be used in the sub-clients. Also, incorrectly formatted packets won't go on upstream either, so make sure every packet you're injecting is compliant with the APRS Protocol Specification. If your sub-client's packets show up in YAAC's Raw Packets display in magenta (sort of hot pink) text, that means there's some sort of syntax error in the packets. Hope this helps. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of vas22 <vassilis@...> Sent: Sunday, November 26, 2023 2:19 PM Hi, I installed the Pseudo APRS-IS Server plug-in and I can successfully connect and receive packets using the Python aprslib client. However when I try to transmit a packet, I can see the packet in the raw messages log of YAAC but no actual transmission is happening. I have both option checkboxes checked and successfully logged in as an authenticated user. I have a single port setup (Direwolf) and have enabled transmission, I can send beacon and messages from YAAC with no issues, problem is when connecting to the pseudo APRS-IS server. Any suggestions on how to send messages from a Python script? Thanks, Vassilis |
Hello Andrew and thank you for the quick response!
I confirmed that I have the right options (both available options) selected and I am using the a valid APRS passcode for my callsign. Tried different SSIDs on the client as well as the same I am using in YAAC to no avail.? I ended up patching the plugin with the following code and got it to send messages over the RF port (and receive them on my HT/APRSDroid). I might be still be doing something else wrong, as I suspect this patch is not necessary. File: ConnectedAprsClient.java 393a394,403
>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?// Patch to send to RF ports as well
>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?System.out.println("Scanning for RF ports");
>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?for (PortConnector pc : PortManager.getPortList()) {
>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?if (pc.hasCapability(Connector.CAP_RF) && pc.hasCapability(Connector.CAP_XMT_PACKET_DATA)) {
>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?System.out.println("Found a capable RF port, sending");
>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?TransmittingConnector tc = (TransmittingConnector)pc;
>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?tc.sendFrame(frame);
>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?}
>? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?}
|
You're correct, this patch shouldn't be necessary. What it does is bypass all the checks for valid packets, and also bypass the ability to forward to the APRS-IS if the YAAC instance has an upstream APRS-IS connection. So, the question is, why aren't you transmitting without this patch?
I did find a bug in core YAAC that would prevent the packet from being sent, but the packet logic needs to be worked a little more, since right now such sub-client packets are treated as neither I-gate packets nor RF packets, so I have to ensure sub-client I-gated packets are properly converted to RF format when coming from a sub-client and pushed regardless of whether the recipient is known from RF (Tx I-gating rules). Watch for the next build of YAAC, with a new version of the pseudo-APRS-IS plugin as well. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] <[email protected]> on behalf of vas22 <vassilis@...> Sent: Monday, November 27, 2023 2:37 PM To: [email protected] Subject: Re: [yaac-users] Issue transmitting with Pseudo APRS-IS Server plug-in [Edited Message Follows] Hello Andrew and thank you for the quick response! I confirmed that I have the right options (both available options) selected and I am using the a valid APRS passcode for my callsign. Tried different SSIDs on the client as well as the same I am using in YAAC to no avail. I ended up patching the plugin with the following code and got it to send messages over the RF port (and receive them on my HT/APRSDroid). I might be still be doing something else wrong, as I suspect this patch is not necessary. File: ConnectedAprsClient.java 393a394,403 // Patch to send to RF ports as well |
to navigate to use esc to dismiss