RE: [DG] Hampi: How to configure Winlink packet gateway (Yay!)

[Chris Doutre]

Steve,

Update: My station is showing up in aprs.fi! Yay! And in the Winlink map. And in the packet station selection list in RMS Express. Thank you, thank you.
https://aprs.fi/info/a/W7BPD-11

I will bring my system to the meeting this evening. Meanwhile, I spotted something that I thought might be suspect. I am not that familiar with the APRS protocol, but I did not see anything like this in the reference:

Beacon Message: !4850.00N/12232.27W]145.630MHzMy RMS Gateway

That "]" looks weird to me. Even though APRS obviously has the position correctly. In fact, I like the fact that rmsgw uses lat/long instead of grid square. That way, the position displayed is much more accurate (not everyone likes that, but I do).

And does "My RMS Gateway" belong here?

See you tonight. And thanks again for all your amazing "Digital Elmering".

Chris KC9AD


-----Original Message-----
From: nww...@googlegroups.com <nww...@googlegroups.com> On Behalf Of Steve Magnuson
Sent: Monday, October 14, 2019 7:52 PM
To: nww...@googlegroups.com
Subject: Re: [DG] Hampi: How to configure Winlink packet gateway

Still not right. Bring it to the meeting tomorrow. Not sure what the problem is.

Sent from mobile device.

> On Oct 14, 2019, at 7:30 PM, Chris Doutre <c...@doutre.org> wrote:
>
> pi@hampi-9ad:~ $ rmsgw_aci
> channel wl2kgw with callsign W7BPD-11 on interface ax0 up Traceback
> (most recent call last):
> File "/usr/local/etc/rmsgw/updatechannel.py", line 107, in <module>
> winlink_service = ElementTree.parse(service_config_xml)
> File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 1182, in parse
> tree.parse(source, parser)
> File "/usr/lib/python2.7/xml/etree/ElementTree.py", line 647, in parse
> source = open(source, "rb")
> IOError: [Errno 13] Permission denied: '/etc/rmsgw/winlinkservice.xml'
>
> pi@hampi-9ad:~ $ grep rmsgw /var/log/syslog | tail -10 Oct 14 19:28:50
> hampi-9ad rmsgw_aci[3702]: W7BPD-11 - Linux RMS Gateway ACI 2.5.1 Oct
> 14 2019 (CN88ow) Oct 14 19:28:50 hampi-9ad rmsgw_aci[3702]: Channel:
> W7BPD-11 on wl2kgw (145630000 Hz, mode 0) Oct 14 19:28:52 hampi-9ad
> rmsgw_aci[3702]: python script /usr/local/etc/rmsgw/updatechannel.py
> failed, status 1 Oct 14 19:28:52 hampi-9ad rmsgw_aci[3702]: Channel
> Stats: 1 read, 1 active, 0 down, 0 updated, 1 errors pi@hampi-9ad:~ $
>
>
>
> -----Original Message-----
> From: nww...@googlegroups.com <nww...@googlegroups.com> On Behalf Of
> Steve Magnuson
> Sent: Monday, October 14, 2019 6:30 PM
> To: nwwdigi <nww...@googlegroups.com>
> Subject: Re: [DG] Hampi: How to configure Winlink packet gateway
>
> Better, but you entered the frequency wrong when you ran Configure RMS Gateway. You must enter the frequency in Hz, not MHz. Run it again to reconfigure.
>
> Steve
>
>> On Oct 14, 2019, at 6:22 PM, Chris Doutre <c...@doutre.org> wrote:
>>
>> pi@hampi-9ad:~ $ grep rmsgw /var/log/syslog | tail -10 Oct 14
>> 17:17:01 hampi-9ad rmsgw_aci[14155]: Channel: W7BPD-11 on wl2kgw
>> (145.630 Hz, mode 0) Oct 14 17:17:01 hampi-9ad rmsgw_aci[14155]:
>> Channel Stats: 1 read, 1 active, 0 down, 0 updated, 0 errors Oct 14
>> 17:47:01 hampi-9ad
>> CRON[21347]: (rmsgw) CMD (/usr/local/bin/rmsgw_aci >/dev/null 2>&1)
>> Oct 14 17:47:01 hampi-9ad rmsgw_aci[21348]: W7BPD-11 - Linux RMS
>> Gateway ACI 2.5.1 Oct 14 2019 (CN88ow) Oct 14 17:47:01 hampi-9ad
>> rmsgw_aci[21348]: Channel: W7BPD-11 on wl2kgw (145.630 Hz, mode 0)
>> Oct
>> 14 17:47:01 hampi-9ad rmsgw_aci[21348]: Channel Stats: 1 read, 1
>> active, 0 down, 0 updated, 0 errors Oct 14 18:17:02 hampi-9ad
>> CRON[28542]: (rmsgw) CMD (/usr/local/bin/rmsgw_aci >/dev/null 2>&1)
>> Oct 14 18:17:02 hampi-9ad rmsgw_aci[28544]: W7BPD-11 - Linux RMS
>> Gateway ACI 2.5.1 Oct 14 2019 (CN88ow) Oct 14 18:17:02 hampi-9ad
>> rmsgw_aci[28544]: Channel: W7BPD-11 on wl2kgw (145.630 Hz, mode 0)
>> Oct
>> 14 18:17:02 hampi-9ad rmsgw_aci[28544]: Channel Stats: 1 read, 1
>> active, 0 down, 0 updated, 0 errors pi@hampi-9ad:~ $
>>
>> -----Original Message-----
>> From: nww...@googlegroups.com <nww...@googlegroups.com> On Behalf
>> Of Steve Magnuson
>> Sent: Monday, October 14, 2019 5:37 PM
>> To: nww...@googlegroups.com
>> Subject: Re: [DG] Hampi: How to configure Winlink packet gateway
>>
>> Sorry, wrong command:
>>
>> I need the output of this command:
>>
>> grep rmsgw /var/log/syslog | tail -10
>>
>>
>>
>>
>>>> On Oct 14, 2019, at 4:36 PM, Chris Doutre <c...@doutre.org> wrote:
>>>
>>> Hi Steve,
>>>
>>> Well, the output looks a lot cleaner now; I guess I'll wait a while to see if Winlink updates:
>>>
>>> pi@hampi-9ad:~ $ sudo su - rmsgw
>>> pi@hampi-9ad:~ $ rmsgw_aci
>>> channel wl2kgw with callsign W7BPD-11 on interface ax0 up
>>> pi@hampi-9ad:~ $
>>>
>>> -----Original Message-----
>>> From: nww...@googlegroups.com <nww...@googlegroups.com> On Behalf
>>> Of Steve Magnuson
>>> Sent: Monday, October 14, 2019 4:17 PM
>>> To: nww...@googlegroups.com
>>> Subject: Re: [DG] Hampi: How to configure Winlink packet gateway
>>>
>>> Chris,
>>>
>>> I thought I squashed that bug. Here’s the fix:
>>>
>>> Open a Terminal, then run these commands:
>>>
>>> sudo chown rmsgw:rmsgw /etc/rmsgw/*.xml sudo chown rmsgw:rmsgw
>>> /etc/rmsgw/*.xsd sudo chown rmsgw:rmsgw /etc/rmsgw/*.conf
>>>
>>> Then reboot.
>>>
>>> Steve
>>>
>>>> On Oct 14, 2019, at 4:04 PM, Chris Doutre <c...@doutre.org> wrote:
>>>>
>>>> /etc/rmsgw/winlinkservice.xml
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/5A428D30-62D5-4B51-B833-5AAB3184E45F%40gmail.com.
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/000001d582e8%2445be2350%24d13a69f0%24%40doutre.org.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/E2DC853C-C8B6-4450-BADC-A2FE837DC895%40gmail.com.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
>> To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/001201d582f7%24103c2dd0%2430b48970%24%40doutre.org.
>
> --
> You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/2818BEA3-E971-454C-AB92-ABD3BD2E4EB9%40gmail.com.
>
> --
> You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/002201d58300%2483f7ee40%248be7cac0%24%40doutre.org.

--
You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/DD80CD85-2B0A-483B-96A3-0820EFB371EA%40gmail.com.

[Steve Magnuson]

Great, Chris! The step I had you do yesterday to change ownership of the files was not needed (but didn’t hurt). I’m pretty sure that the root problem was the frequency being in MHz and not Hz.

Also, I was having you run the rmsgw_aci tests manually in the wrong way. I had forgotten that the newer rmsgw software does things in a slightly different way, and it was invalid to run the commands in the way I instructed you to do (hence the error messages you were seeing).

As to the Beacon Message: That is transmitted by your radio on 145.630 MHz once an hour. It transmits APRS-formatted data, hence that weird string of characters. This beacon message is not at all related to W7BPD-11’s appearance on aprs.fi. The data posted on aprs.fi is from Winlink, which gets its data (frequency, location code, call sign) from the rmsgw_aci script that runs every half hour. That data is sent over the Internet to Winlink, which then passes it on to aprs.fi.

Run Direwolf on another computer with an attached radio tuned to 145.630 MHz. Once W7BPD-11 beacons, you’ll see Direwolf decode the APRS data in that beacon. The ‘]’ symbol should should decode as “Mail Server” (or similar). You can change the beacon string in the GUI - it's the “Beacon Message” field. As it says at the top of the GUI, go to http://www.aprs.net/vm/DOS/PROTOCOL.HTM for details on formatting this string, including the lat/long format. Note that the frequency in the beacon string is in MHz, not Hz as rmsgw requires in the Frequency field in the GUI.

Steve

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/001201d58370%2432f4af90%2498de0eb0%24%40doutre.org.

[Chris Doutre]

Hi Steve,

Right you are. I ran Direwolf on a second Pi and got this:

W7BPD-11 audio level = 18(8/8) [NONE] |||||||__
[0.3] W7BPD-11>IDENT:!4850.00N/12232.27W]145.630MHzMy RMS Gateway
Position, MAIL/PostOffice(was PBBS)
N 48 50.0000, W 122 32.2700, 145.630 MHz
My RMS Gateway

It looks like "My RMS Gateway" could be anything I want, like "Blaine ACS", or "Sunny Birch Bay", or "Linux RMS Gateway". How about "rmsgw by n7nix"?

Great stuff. Thanks again. 73.
Chris KC9AD


-----Original Message-----
. . .

[Steve Magnuson]

It’s most useful to listeners to provide a short description of the agency providing the service, so Blaine ACS seems most appropriate.

Keep it short! The radio has to transmit it, remember.

Steve

> --
> You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/000401d58398%24e2056650%24a61032f0%24%40doutre.org.