Keyboard Shortcuts
Likes
- KM4ACK-Pi
- Messages
Search
Re: More GPS Winlink Bookworm woes
OK finally getting back to the issue of winlink gateways not being shown in Pat when I'm in the Pat mailbox and click on Connect, then select Alias, none of my pre-selected aliases are shown. To recap, in the previous email you suggested: "well check line 6 on patmenu2/FA-functions" I have made what I **think** are the correct changes, but I still have the same issue. Here is the original and the changed line 6 that you mention: Original: CONFIG=$XDG_CONFIG_HOME/pat/config.json Changed to: CONFIG=$XDG_CONFIG_HOME/.config/pat/config.json I have attached a screenshot of my alias select list. Thank you!! ? -- Mike WB8ERJ Geeze! What is he up to now? On Sat, Feb 24, 2024 at 12:32?AM Kelly K7MHI via <kellykeeton=[email protected]> wrote: haha, well check line 6 on patmenu2/FA-functions |
Re: EES Hotspot Domain ?
If you have just a bunch of hosts try adding them into `/etc/hosts` and
toggle quoted message
Show quoted text
your system should resolve them. Otherwise dnsmasq is one way to go. There are a few DNS resolvers someone could use. I think the final setup depends if you setup static ip addresses or if there is a DHCP server somewhere around that internet-less network then. On windows that file is somewhere C:\Windows\System32 not sure on windows cause I haven't one in reach right now. -dominic Dan Hurd W5DMH <dan@...> wrote: On Sat, Mar 2, 2024 at 04:35 AM, Herbert Crosby wrote: --
A seed grows with no sound, but a tree falls with a huge noise. Destruction has noise, but creation is quiet. This is the power of silence. Grow silently. - Confucius |
Re: EES Hotspot Domain ?
On Sat, Mar 2, 2024 at 04:35 AM, Herbert Crosby wrote:
Noip.com. ddns setup is the easiest.That would be if you were NOT running a Hotspot, my question is regarding running a Hotspot, there is no internet involved.? You need a local DNS to provide the domain, thinking DNSMasq is probably the correct solution but I am not 100% sure how to implement it and I don't want to break the great work Jason has done with BAP.? |
EES Hotspot Domain ?
I'm pretty sure there is a way to create a "domain" for your EES server when you are running on HotSpot, just not sure how to do it.? Currently, ? will get users to the Emergency Email Server.? I believe there is a way to assign a domain instead of the IP address.... like : ? Anyone here know how to implement that?? |
Here are the results of ?cat /etc/ax25/axports
rob@pi41:~/pi-build $ cat /etc/ax25/axports
# /etc/ax25/axports
#
# The format of this file is:
#
# name callsign speed paclen window description
#
?
#1 OH2BNS-1 1200 255 2 144.675 MHz (1200 ?bps)
#2 OH2BNS-9 38400 255 7 TNOS/Linux ?(38400 bps)
wl2k KK6JNI 1200 255 7 Winlink
? Rob KK6JNI |
Re: Build-a-Pi Update-Tool problem ?
#bap
BAP is no longer being developed. Give 73Linux a try which can be installed on top of BAP.
73Linux is very similar to BAP but also supports x86 machines. -- 73, de KM4ACK
|
|
|
Re: Hello a quick question
Use 73Linux instead of BAP. You'll have better luck. There are some known issues though with Wayland. Conky doesn't work. VARA won't install with 73 but Kelly has a great write up on how to get it going. /g/KM4ACK-Pi/message/12128
-- 73, de KM4ACK
|
|
|
Build-a-Pi Update-Tool problem ?
#bap
My?problem?with getting the ¡°Unable to establish connection with remote: No AX:25 ports configured¡± error in the Pat mailbox window in Chrome is continuing after reboots. So I decided to check to see if I needed any updates to BAP. (This is on the RPi 8GB that I am?setting up for my new IC-705.) I ran the Build-a-Pi Update-Tool and it said I needed these four updates: ? ?Direwolf ? ?VARIM ? ?Xastir ? ?PACKETSEARCH I thought that was odd, since those are the same four that the Build-a-Pi Update-Tool updated when I began the setup process to use this RPi with the IC-705. So I ran the update and there were no obvious errors shown. But after I rebooted and ran the Build-a-Pi Update-Tool again, the same four apps still show as ¡°Update Needed¡±. So maybe they were never updated ? Is this a known issue? How can I find out which versions the Build-a-Pi Update-Tool is trying to update to?
?
|
Re: Strange Direwolf YACC and XASTIR error: rig_set_ptt command for channel 0 PTT
Yes, I'm seeing lots of packets and decoding them. The map in XASTER fills right up, the one in YAAC doesn't show any. If I look in the decode texts, it is loaded with stations, except for mine. The audio in Direwolf is running around 50-68. I'm not certain what you mean by "Step one is rx packet with good success" Is that a question, then if so, I would say there are plenty of packets decoding.
It is really odd that YAAC isn't showing any real connection with Direwolf, it doesn't show any raw packets in that list or radio lists, etc. There must be some link missing between YAAC and Direwolf. XASTIR is closer to working correctly. It show stations on the map, and show lots of raw packets. The only thing it doesn't show is my K1YPP-7 packets from my handheld. There must be some parameter that I am just totally missing, but what? My Igate function is picking up my K1YPP-7, yet NI4CE-10, which is I think about 20-30 miles away, does. If I look at the RAW packets on aprs.fi for K1YPP-10, it mostly looks good, I do see a few dups in red, but I don't think that is causing any of my current problems, I suspect you can see those as well. Thanks for throwing out suggestions, it is really close at this point. Dennis, K1YPP |
Re: Strange Direwolf YACC and XASTIR error: rig_set_ptt command for channel 0 PTT
Step one is rx packet with good success?
|
Re: Strange Direwolf YACC and XASTIR error: rig_set_ptt command for channel 0 PTT
I tried the "PTT RIG 2? localhost:12345" and it complained with the error: "Retrying Hamlib Rig open..."
So far, in direwolf.conf I have tried all of the following, or some variation: #
#PTT COM1 RTS
#PTT COM1 RTS -DTR
#PTT /dev/ttyUSB0 RTS
#PTT RIG 2 localhost:4532
#PTT RIG 2 localhost:7342
#PTT RIG 2 localhost:12345
#PTT /dev/ttyUSB0 RTS -DTR
# PTT is a symlink for /dev/ttyUSB0
PTT RIG 1020 /dev/PTT 4800
#PTT RIG 1020 /dev/ttyAMA0 4800
The only one that seems to work is the /dev/PTT, where PTT is a symlink for /dev/ttyUSB0. On the good news front, I did find that somewhere along the line I had turned off the beacon for the Igate. Once I uncommented (#) that, the beacon is now running in both XASTIR or YAAC, I now see K1YPP-10 showing up in aprs.fi. However, I don't see K1YPP-7 showing up from my FT5-D sends out a beacon. I am seeing beacons from other stations in the area showing up on the map. They also show up in the little window in the lower-left corner of XASTIR, all except my own, that doesn't show up. If I go out on my deck with the FT5-D and its small antenna, I do show up in aprs.fi via a superstation about 20 miles away, but my Igate just 100 ft away doesn't capture it. Oh, the big red error message only showed up once in Direwolf when using YAAC, but shows up often when using XASTIR. See the first post for that error. Here is the current config file for Direwolf: dennis@raspberrypi:~ $ cat direwolf.conf
?
ADEVICE? plughw:3,0
?
CHANNEL 0
#
MYCALL K1YPP-10
#
MODEM 1200
#MODEM 9600
#
#PTT COM1 RTS
#PTT COM1 RTS -DTR
#PTT /dev/ttyUSB0 RTS
#PTT RIG 2 localhost:4532
#PTT RIG 2 localhost:7342
#PTT RIG 2 localhost:12345
#PTT /dev/ttyUSB0 RTS -DTR
# PTT is a symlink for /dev/ttyUSB0
PTT RIG 1020 /dev/PTT 4800?
#(The one above is the one that currently sorta works) #PTT RIG 1020 /dev/ttyAMA0 4800
?
AGWPORT 8000
KISSPORT 8001
PBEACON delay=1? every=30 overlay=S symbol="digi" lat=27^15.27N long=082^30.52W power=5 height=15 gain=1 comment="Sarasota FL" via=WIDE1-1
?
#? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?#
#? ? ? ? ? ? ?APRS DIGIPEATER PROPERTIES? ? ? ? ? ? ? ? ? ? #
#? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?#
DIGIPEAT 0 0 ^WIDE[3-7]-[1-7]$|^TEST$ ^WIDE[12]-[12]$ TRACE
# tried above with and without TRACE
IGSERVER noam.aprs2.net
?
# You also need to specify your login name and passcode.
IGLOGIN K1YPP-10 12675
?
PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=R lat=27^15.127N long=082^30.52W
#PBEACON sendto=IG delay=0:30 every=60:00 symbol="igate" overlay=T lat=42^37.14N long=071^20.83W ?
# To relay messages from the Internet to radio, you need to add
# one more option with the transmit channel number and a VIA path.
?
IGTXVIA 0 WIDE1-1,WIDE2-1
?
IGTXLIMIT 6 10
?
So, in summary, what I know so far is -The FT-817nd is responding to Direwolf commands via CAT, -aprs.fi sees the K1YPP-10 beacons, -YAAC is communicating with Direwolf, but doesn't show any stations, including my K1YPP-7, but does show ONLY K1YPP-10 on the map -The big red error message is still there in XASTIR, but seems to be rare in YAAC. -My local transmit isn't making it through the Igate and doesn't appear to show up in Direwolf at all. Anyway, that is the quick summary. I'm open to any suggestions, this is really frustrating. Thanks Dennis, K1YPP Sarasota, FL |
Re: Strange Direwolf YACC and XASTIR error: rig_set_ptt command for channel 0 PTT
I've also noticed that YACC doesn't any longer populate the map with stations heard, just my k1ypp-10. That did work, but now, does not. However, XASTIR still populates the map but has that constant error going by in Direwolf. Is this any kind of clue to anything?
Dennis, K1YPP |