Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support APRS Directed Station Queries #112

Open
dranch opened this issue Sep 4, 2017 · 3 comments
Open

Support APRS Directed Station Queries #112

dranch opened this issue Sep 4, 2017 · 3 comments

Comments

@dranch
Copy link
Collaborator

dranch commented Sep 4, 2017

Direwolf 1.4 recognizes APRS station queries but doesn't respond as the "aprs_directed_station_query" function is effectively just a placeholder and no code support exists today. I would be great to add support for the basic commands. Here is a proposal of maybe how they could be supported over time. Just my $0.02 here..

Phase 1 - have Direwolf just respond with "complete response not supported today". Just getting a response will be a big help for users trying to do diagnostics, etc.

Future proposed phases:

Query Type | Query
APRS | General — All stations query | Station’s position and status | phase 2: should be strait forward

APRSD | Directed — Query an individual station for stations heard direct | List of stations heard direct | Could be a Phase3 feature though this is a pretty valuable response

APRSH | Directed — Query if an individual station has heard a particular station | Position of heard station as an APRS Object, plus heard statistics for the last 8 hours | Maybe a phase 4 feature

APRSM | Directed — Query an individual station for outstanding unacknowledged or undelivered
messages | All outstanding messages for the querying station | Maybe a phase 4 feature

APRSO | Directed — Query an individual station for its Objects | Station’s Objects | maybe phase 3

APRSP | Directed — Query an individual station for its position | Station’s position | phase 2: should be strait forward

APRSS | Directed — Query an individual station for its status | Station's status | phase 2: should be strait forward

APRST or
PING? | Directed — Query an individual station for a trace (i.e. path by which the packet was heard) | Route trace | Could be a Phase4 feature though this is a pretty valuable response

IGATE | General — Query all Internet Gateways | IGate station capabilities | phase 2: should be strait forward

WX | General — Query all weather stations | Weather report (and the station’s position if it is not included in the Weather Report) | Maybe phase 3 Seems to be a subset of APRSO

@dranch
Copy link
Collaborator Author

dranch commented Sep 4, 2017

It's worth adding that Direwolf currently digipeats these packets which is probably NOT what we want to have happen. This should be suppressed as part of the phase 1effort

@Tyler-2
Copy link

Tyler-2 commented Jun 9, 2022

Yes please! I didn't even know about these features since Direwolf is kind of my golden standard for APRS, and where I learn.

@craigsned
Copy link

Bump - would be a really useful addition to Direwolf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants