Hello Cassie,
Alright everyone. The initial setup is done I think. Both rig
setups are able to receive packets off 144.39 and are able to do
a transmit test with -x a.
?
Hooray!
Awesome.? Good work.
?
Now that both rigs are set up, I want to test transmission of
packets to eachother- basically I want to send a packet with rig
a, and have direwolf on rig b receive it. I saw in your set up
guide that you recommended the following beacon:
PBEACON delay=00:15 every=1 SYMBOL=/- lat=37^20.00N lon=121^00.00W power=4 height=20 gain=6 comment="was KI6ZHD Change me, CA" via=WIDE1-1
My plan is to add this to the config file for rig a (with an
obvious change in my location and call sign) and then I expect
rig a would be able to receive it? Would that be the best way to
go about doing this?
Sure.. that will work though I would now recommend you learn a bit
about how APRS works, how the different "WIDE" constructs work
(WIDE1-1, vs WIDE2-1), etc. as they are important.? Beyond that,
DIrewolf is really intended to be an APRS "server" but not really a
client.? When I say "client", I mean say show a map with all the
learned stations and their locations, send messages, interact with
services like APRS/email gateways, APRS/Winlink gateways, etc.?
There are several APRS clients out there that are multi-platform and
they don't have to run on the same machine as Direwolf.? I have a
short list of some of the possibilities here:
??
Beyond using AX.25 packet radio with APRS, there are also classic
AX.25 packet terminal clients too:
??
--David
KI6ZHD
