DigiRig & Yaesu FT-2980R Stopped Working
Randall Luebke
Craig
Let's start with the contents of PktLog, that'll tell us if the digirig is healthy. Can you paste PktLog here?
Second, a good test is to boot with everything connected, then start the "APRS Digipeater". Wait
eight seconds and see if it goes into transmit (sends a beacon).
we'll get you sorted,
-craig
KM6LYW
I setup my DigiPi as a WinLink Email Server. Everything worked correctly until it didn't. I've checked the WinLink.org site and it shows my station as active. I'm using a DigiRig Mobile, with the correct DigRig cables. I've unplugged and reconnected everything. I even tried to reflash my DigiPi. I tested the radio with no connections for both sending and receiving. All good. Help! --
You received this message because you are subscribed to the Google Groups "DigiPi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digipi+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/digipi/28b3d4b0-3898-4213-9de7-11156560594dn%40googlegroups.com.
Randall Luebke
Here is the Pktlog followed and the Syslog.
Pktlog:
Reading config file /run/direwolf.digipeater.conf
Line 16: Unexpected character '.' in location "33.30.08"
Line 16: Unexpected character '.' in location "-117.42.52"
Config file: FILTER IG ... on line 30.
Warning! Don't mess with IS>RF filtering unless you are an expert and have an unusual situation.
Warning! The default is fine for nearly all situations.
Warning! Be sure to read carefully and understand "Successful-APRS-Gateway-Operation.pdf" .
Warning! If you insist, be sure to add " | i/180 " so you don't break messaging.
Line 35: Warning - IGFILTER is a rarely needed expert level feature.
If you don't have a special situation and a good understanding of
how this works, you probably should not be messing with it.
The default behavior is appropriate for most situations.
Please read "Successful-APRS-IGate-Operation.pdf".
Audio device for both receive and transmit: default (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate / 3, Tx AX.25.
Initializing GPIO common structure
Opening GPIO line 16 on chip /dev/gpiochip0
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
DNS-SD: Avahi: Announcing KISS TCP on port 8001 as 'Dire Wolf on digipi'
Virtual KISS TNC is available on /dev/pts/1
Created symlink /tmp/kisstnc -> /dev/pts/1
DNS-SD: Avahi: Service 'Dire Wolf on digipi' successfully registered.
Connect to IGate server noam.aprs2.net (2603:c023:4003:5b1b:209f:986:2aba:4c8d) failed.
Connect to IGate server noam.aprs2.net (69.197.140.169) failed.
Connect to IGate server noam.aprs2.net (205.209.228.99) failed.
Connect to IGate server noam.aprs2.net (44.184.136.10) failed.
Connect to IGate server noam.aprs2.net (15.235.87.126) failed.
Connect to IGate server noam.aprs2.net (155.138.131.1) failed.
Connect to IGate server noam.aprs2.net (2001:19f0:b001:999:5400:4ff:feb0:e9a7) failed.
Connect to IGate server noam.aprs2.net (44.26.110.252) failed.
Connect to IGate server noam.aprs2.net (44.25.16.4) failed.
Connect to IGate server noam.aprs2.net (44.135.208.225) failed.
[0L] WA4SKI-2>APDW18,WIDE2-1:!b=]330k?w# ! WA4SKI WIDE1 DigiPi http://digipi.org/<0x20>
Connect to IGate server noam.aprs2.net (2603:c023:4003:5b1b:209f:986:2aba:4c8d) failed.
Connect to IGate server noam.aprs2.net (2001:19f0:b001:999:5400:4ff:feb0:e9a7) failed.
Connect to IGate server noam.aprs2.net (44.26.110.252) failed.
Connect to IGate server noam.aprs2.net (44.135.208.225) failed.
Connect to IGate server noam.aprs2.net (44.25.16.4) failed.
Connect to IGate server noam.aprs2.net (15.235.87.126) failed.
Connect to IGate server noam.aprs2.net (44.184.136.10) failed.
Connect to IGate server noam.aprs2.net (69.197.140.169) failed.
Connect to IGate server noam.aprs2.net (155.138.131.1) failed.
Connect to IGate server noam.aprs2.net (205.209.228.99) failed.
Now connected to IGate server noam.aprs2.net (44.26.110.252)
Check server status here http://44.26.110.252:14501
[ig] # aprsc 2.1.19-g730c5c0
[ig] # logresp WA4SKI-2 verified, server T2LANE
Here is the SysLog:
Jan 27 14:51:20 digipi direwolf.digipeater.sh[25701]: /home/pi/direwatch.py:417: SyntaxWarning: invalid escape sequence '\['
Jan 27 14:51:20 digipi direwolf.digipeater.sh[25701]: search = re.search("^\[\d\.*\d*\] ([a-zA-Z0-9-]*)", line) # snag callsign from unsupported packet
Jan 27 14:51:20 digipi direwolf.digipeater.sh[25701]: /home/pi/direwatch.py:519: SyntaxWarning: invalid escape sequence '\['
Jan 27 14:51:20 digipi direwolf.digipeater.sh[25701]: search = re.search("^\[\d\.*\d*\] (.*)", line)
Jan 27 14:51:20 digipi direwolf.digipeater.sh[25701]: /home/pi/direwatch.py:541: SyntaxWarning: invalid escape sequence '\['
Jan 27 14:51:20 digipi direwolf.digipeater.sh[25701]: search = re.search("^\[\d\.*\d*\] ([a-zA-Z0-9-]*)", line)
Jan 27 14:51:21 digipi direwolf.digipeater.sh[25701]: usage: direwatch.py [-h] -l LOG [-f FONTSIZE] [-t TITLE_TEXT] [-o] [-y LAT]
Jan 27 14:51:21 digipi direwolf.digipeater.sh[25701]: [-x LON] [-s SAVEFILE] [-d DISPLAY]
Jan 27 14:51:21 digipi direwolf.digipeater.sh[25701]: direwatch.py: error: argument -x/--lon: expected one argument
Jan 27 14:51:24 digipi direwolf.digipeater.sh[25674]: + sudo rfcomm --raw watch /dev/rfcomm0 1 socat -d -d tcp4:127.0.0.1:8001 /dev/rfcomm0