Date   

Re: DRAWS Pi HAT and GPS module for sale - $100

Chui K9CHU
 

:thumbs-up:

Same question...and dibs too.

:)

I have one on back order...

73 de K9CHU

On Wed, Apr 22, 2020, 10:01 PM Bob <625446forwork@...> wrote:
What version board is it and is it still available? Thx Bob


Re: Routing to RMS gateway via digipeater with axparms? #ax25

Basil Gunn
 

This is a paclink-unix question.
Answer:

wl2kax25 -c <someRMSGateway> <someDigipeater>
wl2kax25 -c WC7EC-10 KH7RFI-7

If there are no other dash args other than -c you do not need to include it.
This will work as well.

wl2kax25 <someRMSGateway> <someDigipeater>
wl2kax25 WC7EC-10 KH7RFI-7

/Basil n7nix

Jay S <jaystagnone@gmail.com> writes:

I need to route my email through a digipeater (KH7RFI-7) to reach an
RMS gateway (WC7EC-10). I tried the following:

sudo axparms -route add> udr0 WC7EC-10 KF7RFI-7

I then created an email in mutt, and used the
command:

wl2kax25 -c WC7EC-10

At the same time I am monitoring with
listen -s in another term window. It appears that I am still trying to
connect directly to the gateway, not via the digipeater. udr0: fm
KI7JS to WC7EC-10 ctl SABM+ (repeated 7 times, then "connection timed
out" from wl2kax25)

What am I doing wrong? I suspect the route command is wrong. Or maybe I should reboot or restart ax25?

FWIW I can use the same system to connect to another gateway
directly. I can also drive to a place I can reach wc7ec and it works
OK. I can also see beacons from KF7RFI when monitoring with listen -a.

Thanks,
Jay KI7JS


Routing to RMS gateway via digipeater with axparms? #ax25

Jay S
 

I need to route my email through a digipeater (KH7RFI-7) to reach an RMS gateway (WC7EC-10). I tried the following:
    sudo axparms -route add udr0 WC7EC-10 KF7RFI-7
I then created an email in mutt, and used the command:
    wl2kax25 -c WC7EC-10
At the same time I am monitoring with listen -s in another term window. It appears that I am still trying to connect directly to the gateway, not via the digipeater.
    udr0: fm KI7JS to WC7EC-10 ctl SABM+ (repeated 7 times, then "connection timed out" from wl2kax25)

What am I doing wrong? I suspect the route command is wrong. Or maybe I should reboot or restart ax25?

FWIW I can use the same system to connect to another gateway directly. I can also drive to a place I can reach wc7ec and it works OK. I can also
see beacons from KF7RFI when monitoring with listen -a. 

Thanks,
Jay KI7JS


Re: mheard not working. Help debugging? #draws #ax25

Jay S
 

Mheard is working now on my draws system.

I had fixed the duplicate call sign in /etc/ax25/axports. However I had not rebooted. Alternatively I could have restarted ax25 service by running ax25-stop and ax25-start. Once I rebooted I got the output below.

To summarize, the original issue was that I saw no output or error message from mheard even though it was obvious that ax25 packets were being received. The problem was caused by a duplicate ssid in /etc/ax25/axports. It was fixed by editing /etc/ax25/axports and changing the second ssid (on line 6) to something different and then restarting ax25 or rebooting. The offending lines were:
    udr0        KI7JS-10            9600    255     2       Winlink port
    udr1        KI7JS-10             9600    255     2       Direwolf port  (I had to change this to KI7JS-11 to fix it)

Thanks for the help, Basil!

Jay KI7JS

pi@drawspi1:~ $ mheard
Callsign   Port    Packets   Last Heard
JUNIPR     udr0          3   2020-04-25 09:25:10
N7AWM      udr0          4   2020-04-25 09:25:00
DIXIE-1    udr0          2   2020-04-25 09:24:43
KM7LJ      udr0          2   2020-04-25 09:24:24
TROUT      udr0          1   2020-04-25 09:24:18


Re: mheard not working. Help debugging? #draws #ax25

Basil Gunn
 

You are using the default alsa settings which most likely will NOT work
for you. You need to determine your alsa settings so that your deviation is
set properly. Also which ham-made parts cable are you using?

When you have time post your output from the listen command:
use listen -a

also console output of both:

ax25-status
ax25-status -d

You previously stated you used listen -d c
In the version of listen I am using '-d' is not a valid argument.
$ listen -v
listen: 2.0.1

Thanks,
/Basil

Jay S <jaystagnone@gmail.com> writes:

Thanks!

OK, I changed the second ki7js-10 to ki7js-11. I am using the left connector, hooked up through a ham-made-parts cable to an old Alinco 110.

Here's the script output:

pi@drawspi1:~/n7nix/debug $ ./ax25-showcfg.sh

=== Display kissparms & ax25dev-parms
port: 0, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: 3000, t2 timeout: 1000
port: 1, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: 3000, t2 timeout: 1000
== kissparms from /etc/ax25/ax25-upd
$KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
$KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
$KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
$KISSPARMS -p ${PORTNAME_2} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
$KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY

===== ax.25 config
Found directory: /proc/sys/net/ax25/ax0
ax25_default_mode: 0
backoff_type: 0
connect_mode: 2
dama_slave_timeout: 180000
extended_window_size: 32
idle_timeout: 900000
ip_default_mode: 0
maximum_packet_length: 255
maximum_retry_count: 6
protocol: 0
standard_window_size: 2
t1_timeout: 3000
t2_timeout: 1000
t3_timeout: 300000

Found directory: /proc/sys/net/ax25/ax1
ax25_default_mode: 0
backoff_type: 0
connect_mode: 2
dama_slave_timeout: 180000
extended_window_size: 32
idle_timeout: 900000
ip_default_mode: 0
maximum_packet_length: 255
maximum_retry_count: 6
protocol: 0
standard_window_size: 2
t1_timeout: 3000
t2_timeout: 1000
t3_timeout: 300000

===== ALSA Controls for Radio Transmit =====
LO Driver Gain L:[-6.00dB] R:[-6.00dB]
PCM L:[-25.00dB] R:[-25.00dB]
DAC Playback PT L:[P3] R:[P3]
LO Playback CM [Full Chip]

===== ALSA Controls for Radio Receive =====
ADC Level L:[0.00dB] R:[0.00dB]
IN1 L:[Off] R:[Off]
IN2 L:[10 kOhm] R:[10 kOhm]
CM L:[10 kOhm] R:[10 kOhm]

===== Port baudrate
DireWolf: udr0 speed: 1200, udr1 speed: 1200
AX.25: udr0 speed: 1200, udr1 speed: 1200

===== axports
udr0 KI7JS-10 9600 255 2 Winlink port
udr1 KI7JS-11 9600 255 2 Direwolf port

===== ax25d.conf
[KI7JS-10 VIA udr0]
NOCALL * * * * * * L
default * * * * * * - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
#
[KI7JS VIA udr0]
NOCALL * * * * * * L
default * * * * * * - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d

===== wl2k.conf
paclink-unix ax25 port: ax25port=udr0

pi@drawspi1:~/n7nix/debug $ mheard
Callsign Port Packets Last Heard
pi@drawspi1:~/n7nix/debug $ mheard


Re: mheard not working. Help debugging? #draws #ax25

Jay S
 

Thanks!

OK, I changed the second ki7js-10 to ki7js-11. I am using the left connector, hooked up through a ham-made-parts cable to an old Alinco 110. 

Here's the script output:

pi@drawspi1:~/n7nix/debug $ ./ax25-showcfg.sh
 
 === Display kissparms & ax25dev-parms
port: 0, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: 3000, t2 timeout: 1000
port: 1, speed: 1200, slottime: 200, txdelay: 500, t1 timeout: 3000, t2 timeout: 1000
 == kissparms from /etc/ax25/ax25-upd
        $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_2} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
        $KISSPARMS -p ${PORTNAME_1} -f no -l 100 -r 32 -s $SLOTTIME -t $TXDELAY
 
 ===== ax.25 config
Found directory: /proc/sys/net/ax25/ax0
ax25_default_mode: 0
backoff_type: 0
connect_mode: 2
dama_slave_timeout: 180000
extended_window_size: 32
idle_timeout: 900000
ip_default_mode: 0
maximum_packet_length: 255
maximum_retry_count: 6
protocol: 0
standard_window_size: 2
t1_timeout: 3000
t2_timeout: 1000
t3_timeout: 300000
 
Found directory: /proc/sys/net/ax25/ax1
ax25_default_mode: 0
backoff_type: 0
connect_mode: 2
dama_slave_timeout: 180000
extended_window_size: 32
idle_timeout: 900000
ip_default_mode: 0
maximum_packet_length: 255
maximum_retry_count: 6
protocol: 0
standard_window_size: 2
t1_timeout: 3000
t2_timeout: 1000
t3_timeout: 300000
 
 
 ===== ALSA Controls for Radio Transmit =====
LO Driver Gain  L:[-6.00dB]     R:[-6.00dB]
PCM             L:[-25.00dB]    R:[-25.00dB]
DAC Playback PT L:[P3]          R:[P3]
LO Playback CM  [Full Chip]
 
 ===== ALSA Controls for Radio Receive =====
ADC Level       L:[0.00dB]      R:[0.00dB]
IN1             L:[Off]         R:[Off]
IN2             L:[10 kOhm]     R:[10 kOhm]
CM              L:[10 kOhm]     R:[10 kOhm]
 
===== Port baudrate
DireWolf: udr0 speed: 1200, udr1 speed: 1200
AX.25:    udr0 speed: 1200, udr1 speed: 1200
 
===== axports
udr0        KI7JS-10            9600    255     2       Winlink port
udr1        KI7JS-11             9600    255     2       Direwolf port
 
 ===== ax25d.conf
[KI7JS-10 VIA udr0]
NOCALL   * * * * * *  L
default  * * * * * *  - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U
#
[KI7JS VIA udr0]
NOCALL   * * * * * *  L
default  * * * * * *  - pi /usr/local/bin/wl2kax25d wl2kax25d -c %U -a %d
 
 ===== wl2k.conf
paclink-unix ax25 port: ax25port=udr0

pi@drawspi1:~/n7nix/debug $ mheard
Callsign   Port    Packets   Last Heard
pi@drawspi1:~/n7nix/debug $ mheard
 
 


Re: mheard not working. Help debugging? #draws #ax25

Basil Gunn
 

Can anyone suggest a few troubleshooting steps I can take? Thanks.
Look at file: /etc/ax25/axports and fix your duplicate call sign
problem.
Which DRAWS connector are you using? Left connector corresponds to
device udr0.

Tune your radio to the 2M APRS frequency, 144.390 so you will have
traffic.

Run this script and copy the console output in an email.
cd
cd n7nix/debug
./ax25-showcfg.sh

/Basil n7nix


Jay S <jaystagnone@gmail.com> writes:

Mheard prints nothing except a header with "Callsign Port Packets Last
heard". There are no error messages. I looked
at/var/ax25/mheard/mheard.dat and it is a zero-length file.

I think ax25 is otherwise working. I can use beacon or listen on the
APRS frequency, and see packets coming in. I can send APRS beacons
from another radio and see them displayed with listen -d c. I get a
message as follows when I run listen: "axconfig: duplicate callsign
KI7JS-10 in line 6 of axports file" but it shows traffic coming in
from the radio.

Can anyone suggest a few troubleshooting steps I can take? Thanks.


mheard not working. Help debugging? #draws #ax25

Jay S
 

Mheard prints nothing except a header with "Callsign   Port   Packets    Last heard". There are no error messages. I looked at /var/ax25/mheard/mheard.dat and it is a zero-length file.

I think ax25 is otherwise working. I can use beacon or listen on the APRS frequency, and see packets coming in. I can send APRS beacons from another radio and see them displayed with listen -d c. I get a message as follows when I run listen: "axconfig: duplicate callsign KI7JS-10 in line 6 of axports file" but it shows traffic coming in from the radio.

Can anyone suggest a few troubleshooting steps I can take? Thanks.


Re: DRAWS Pi HAT and GPS module for sale - $100

Bob
 

What version board is it and is it still available? Thx Bob


Re: N1MM network mode, Field Day and TCP/IP over AX.25

David M
 

The current ARRL Field Day rules don't support a Class A club group outside of a 1000 foot diameter circle. 


Re: N1MM network mode, Field Day and TCP/IP over AX.25

Eric Grumling
 

>Does this sound like HAMwan @ 9600 baud?
>What am I missing?

That's basically what I'd like to try. We're a little too spread out and too many hills to effectively build a pure HSMM-MESH style network but maybe have elements of that too. Pretty much anything that will work. I know most of the members have 9600 baud capable radios, many have an extra Raspberry Pi (or 4) and some have 3 GHz data radios. Between all that we should be able to cobble together some sort of WAN. I'm also looking at 900 MHz telemetry radios (56Kbps) borrowed from the drone world, but that might be even more difficult since I think they're set up for point to point and limited to 1 Watt LOS.


Re: N1MM network mode, Field Day and TCP/IP over AX.25

Eric Grumling
 

There's some discussion about modifying the rules for this year due to the unprecedented situation. In a normal year the club has 3 stations + GOTA/Satellite and schedules operators to run 24X7. I think the idea being floated is that we'd operate under the club call for a scheduled time from our personal station, so this might all be more trouble than it's worth. But just trying to see what's possible since I've been asked to handle the network piece of things.


Re: N1MM network mode, Field Day and TCP/IP over AX.25

Andrew P.
 

Wouldn't that kind of networking violate the Field Day rules requiring all stations be within a 1000-foot circle?


-------- Original message --------
From: Eric Grumling <eric@...>
Date: 4/19/20 14:36 (GMT-05:00)
To: udrc@nw-digital-radio.groups.io
Subject: [draws and udrc] N1MM network mode, Field Day and TCP/IP over AX.25

Our club is looking at different options for this year's Field Day since we have no intention of collecting at our usual 3A campsite. Most of us will probably be operating from home using our own callsigns, but there's some discussion of using N1MM's network mode and forming a multi-user multi-station group using the club call. I'm pretty well versed in networking N1MM on a LAN, and can probably get a VPN set up (to simplify setup for non-network savvy members) for everyone to use. However it might be interesting to see what might be possible using all radio instead of Internet and VPN tunnels. The club repeater sites are connected via a 3GHz WAN that could also be utilized if members have direct LOS with the repeater sites (not many do). 

With that in mind, what is the possibility of running 9600 baud TCP/IP using a Raspberry Pi and UDRC/soundcard modem? That way we could keep things all radio and maybe get some infrastructure built for longer term projects. I'll have to see how much network traffic is generated by N1MM of course, but the idea would be similar to a Cradlepoint style cellular modem, where the logging PC could join a WiFi hotspot or Ethernet port on the Pi, which would then act like a router. Would JNOS or Direwolf do this? Ideally I'd build a standard image for the club, and probably build a few stations too. Club members who want to join the network would need to supply a 70 CM radio with 9600 baud input and we'd probably have to set nodes at the repeater sites.

Good idea or waste of time?


Re: N1MM network mode, Field Day and TCP/IP over AX.25

Basil Gunn
 

With that in mind, what is the possibility of running 9600 baud TCP/IP
using a Raspberry Pi and UDRC/soundcard modem?
Yes lately we have been testing the 9600 baud packet part a great deal &
it works very well.

the logging PC could join a WiFi hotspot or Ethernet port on the Pi,
which would then act like a router. Would JNOS or Direwolf do this?
Since the udrc/DRAWS has is enumerated as network devices (AX0 & AX1) it
should be possible. I am not interested in using JNOS.

I'll start playing with this in my copious amounts of socially separated
time. :)

What exactly is your criteria for success. Ping'ing each station? Fill
in your vision a little more.

Does this sound like HAMwan @ 9600 baud?
What am I missing?

/Basil n7nix


Eric Grumling <eric@grumling.com> writes:

Our club is looking at different options for this year's Field Day since we have no intention of collecting at our usual 3A campsite. Most of us will probably be operating from home using our own callsigns, but there's some discussion of using N1MM's network mode and forming a multi-user multi-station group using the club call. I'm pretty well versed in networking N1MM on a LAN, and can probably get a VPN set up (to simplify setup for non-network savvy members) for everyone to use. However it might be interesting to see what might be possible using all radio instead of Internet and VPN tunnels. The club repeater sites are connected via a 3GHz WAN that could also be utilized if members have direct LOS with the repeater sites (not many do).

With that in mind, what is the possibility of running 9600 baud TCP/IP using a Raspberry Pi and UDRC/soundcard modem? That way we could keep things all radio and maybe get some infrastructure built for longer term projects. I'll have to see how much network traffic is generated by N1MM of course, but the idea would be similar to a Cradlepoint style cellular modem, where the logging PC could join a WiFi hotspot or Ethernet port on the Pi, which would then act like a router. Would JNOS or Direwolf do this? Ideally I'd build a standard image for the club, and probably build a few stations too. Club members who want to join the network would need to supply a 70 CM radio with 9600 baud input and we'd probably have to set nodes at the repeater sites.

Good idea or waste of time?


N1MM network mode, Field Day and TCP/IP over AX.25

Eric Grumling
 

Our club is looking at different options for this year's Field Day since we have no intention of collecting at our usual 3A campsite. Most of us will probably be operating from home using our own callsigns, but there's some discussion of using N1MM's network mode and forming a multi-user multi-station group using the club call. I'm pretty well versed in networking N1MM on a LAN, and can probably get a VPN set up (to simplify setup for non-network savvy members) for everyone to use. However it might be interesting to see what might be possible using all radio instead of Internet and VPN tunnels. The club repeater sites are connected via a 3GHz WAN that could also be utilized if members have direct LOS with the repeater sites (not many do). 

With that in mind, what is the possibility of running 9600 baud TCP/IP using a Raspberry Pi and UDRC/soundcard modem? That way we could keep things all radio and maybe get some infrastructure built for longer term projects. I'll have to see how much network traffic is generated by N1MM of course, but the idea would be similar to a Cradlepoint style cellular modem, where the logging PC could join a WiFi hotspot or Ethernet port on the Pi, which would then act like a router. Would JNOS or Direwolf do this? Ideally I'd build a standard image for the club, and probably build a few stations too. Club members who want to join the network would need to supply a 70 CM radio with 9600 baud input and we'd probably have to set nodes at the repeater sites.

Good idea or waste of time?


Functional End-User Operation Directions

Ed Bloom, KD9FRQ
 

I am looking for some more formalized End-User Directions to keep on the thumb drive, and print for the Go Bag/Box.

What I am looking for is how to swap ports from 0 to 1 should the port 0 fail on the hat (as a precaution) and how to make the needed baseline setting changes to Xastir runs off of Port 1 as default and let the Pac-Link side run off of Port 0.

As it stands now, Xastir sees the Port 0 and I need to move it.


Re: #DRAWS oddity, GPS and ALSA headaches #draws

Jack Spitznagel
 

Hi Basil,

Well, I finally got a chance to do a "multiswap" to see what hardware is
working and what is not with this DRAWS system.

Previously determined that the GPS antenna we have discussed was bad by
swapping on to a good DRAWS/Pi unit that was working fine with another
antenna. Ordered a replacement which arrived last week.

Finally got some time to reconfigure so... before putting the new GPS
antenna on the DRAWS unit that had the antenna failure, I tested both DRAWS
boards with a good Pi3B+ and the remaining good GPS antenna that I have. I
was worried because there had been some heating that took place when the GPS
antenna failed.

The DRAWS board that had the antenna go bad apparently also has a bad GPS
chip:

-When I was testing it a week ago or so with the good antenna from my GO
kit, it "seemed OK", but was very sluggish getting a fix and there seemed to
be a lot of position jitter when it did acquire some satellites. ALSA
indicated the UDRC BCM chip was working. The GPS chip seemed to get a bit
warm, but not alarmingly.

-Today's testing, the DRAWS board in question did not get a fix and no
matter how long after starting the units, no satellites were acquired. ALSA
did appear to work. GPSMON show 4 satellites in the list, but consistently
only shows 00.0000 for coordinates no matter how long I left it.

With the same antenna and same Pi3B+ with the other DRAWS board mounted, the
full GPSMON display comes up immediately and all systems check out. Xastir
runs flawlessly.

I guess this moves to a Brian question... Is the DRAWS board repairable or
swappable for a fee? I most likely am past any reasonable warranty time and
I need this unit for my go kit.

73 and Thanks!

KD4IZ
Jack Spitznagel
FM19oo

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Basil Gunn
Sent: Saturday, April 4, 2020 01:17
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] #DRAWS oddity, GPS and ALSA headaches


Hi Jack,

It also turns out that the original GPS/LNA antenna had gone bad along
with the Pi3B+. It was working before the RPi started into the
overheating problem. So what ever started the heating problem took out
the ability to connect to the DRAWS hat and apparently the GPS antenna...

I tried the GPS antenna from the other DRAWS unit I have in my GO box
and it came right up. Just ordered another from you.
I found these also work:
https://www.amazon.com/gp/product/B00LXRQY9A/ref=ppx_yo_dt_b_search_asin_tit
le

Note: The Pi4 B+ really needs a fan... runs 55 to 60C without, 35-37C
with.
Had a 12V microfan sitting in the junk box, wired it in, and the Pi
stays cool now.
Yes I agree. Pi4's run cool enough when laying naked on my bench but as soon
as you put them into any kind of enclosure they heat up.

I have a case on back order. Does it have a place for a fan mount?
Don't know. Bryan or John need to answer that.

Jack - kd4iz


Re: #aprs #aprs

Paul Noa
 

Thanks Basil,
I am on my way now:
12 17:13:53 EDT, host: asawizard, gps: Ok, bat: +0.00V Seq: 3
Location: 30°06.48' N 81°28.84' W - locator EM90GC25HW - show map - static map
7.3 miles Southwest bearing 229° from Palm Valley, Saint Johns County, Florida, United States [?]
8.8 miles Southwest bearing 228° from Sawgrass, Saint Johns County, Florida, United States
18.7 miles Southeast bearing 146° from Jacksonville, Duval County, Florida, United States
59.6 miles Northeast bearing 58° from Gainesville, Alachua County, Florida, United States
Last position: 2020-04-12 17:13:57 EDT (16m16s ago)
2020-04-12 17:13:57 EDT local time at Palm Valley, United States [?]
Device: NW Digital Radio: UDR
Last path: KO4BCZ-15>APUDR1 via WIDE1-1,qAO,K4GDG-10 (good)
Positions stored: 1


Re: #aprs #aprs

Basil Gunn
 

Curiously NWDR's name was in there that's when I knew I didn't know
how to send a message!!
btest.sh script defaults to sending a message

'btest.sh -p' sends a location beacon

$ ./btest.sh -h
*** Running as user: pi ***
Usage: btest.sh [-P <port>][-s <num>][-p][-m][-v][-h]
-P <portname> | --portname <portname> eg. udr0
-s <num> | --sid <num> set sid in callsign, number 0-15
-p | --position send a position beacon
-m | --message send a message beacon (default)
-g | --gps verify gps is working
-v | --verbose display verbose messages
-h | --help display this message

The btest.sh script prints out the beacon command it executes:

$ ./btest.sh

Send a message beacon
Sent: /usr/local/sbin/beacon -c N7NIX-11 -d 'APUDR1 via WIDE1-1' -l -s udr0 :N7NIX :12 13:06:58 PDT N7NIX mesg_beacon test from host testit2 on port udr0 Seq: 1

You should probably read this link
http://www.aprs.org/

/basil n7nix


Re: #aprs #aprs

Paul Noa
 

Thanks Everyone,

My nearest ham friend sent me this he received on his home rig:

KO4BCZ-11 audio level = 26(7/7)   [NONE]   |||||||__
[0.3] KO4BCZ-11>APUDR1,WIDE1-1::KO4BCZ   :11 15:54:28 EDT KO4BCZ
mesg_beacon test from host asawizard on port udr0 Seq: 0"

APRS Message  for "KO4BCZ", Original Balloon (think Ham b, NW Digital Radio's UDR (APRS/Dstar)
11 15:54:28 EDT KO4BCZ mesg_beacon test from host asawizard on port
udr0 Seq: 0"�

[ig] K4GDG-10>APDW14:!3006.64NR08130.47W&K4GDG-10 iGate | DireWolf 1.4
on RPi+RTL-SDR using QSO365 image

Curiously NWDR's name was in there that's when I knew I didn't know how to send a message!!
I will study up on all the information and try again ASAP.

Thanks
Only Perseverance Prevails!
Paul
KO4BCZ

981 - 1000 of 5709