Re: Error using kiss interface

#8537

Radio is about 2 feet above my computer.? I've already set the radio to low power (5 watts).? What's strange is I don't have this problem doing igate->RF and RF->gate and I was using 50 watts then.? I'm having the same issue after adding some ferrite beads to the USB cable.

Stephen Atkins

VE6CPU/VE6STA/VE6SU

Sent with secure email.

Show quoted text

------- Original Message -------
On Tuesday, August 15th, 2023 at 3:49 PM, David Ranch <direwolf-groupsio@...> wrote:

How close is your radio to your computer + sound device? It would be best to get some distance between the two ideally in the vertical plane. Also consider lowering your RF power to help with any RFI issues.

--David
KI6ZHD

On 08/15/2023 01:16 PM, Stephen Atkins via groups.io wrote:

So to answer my own question. I tried using soundmodem and got the same results. It seems I'm getting some RF or something in to my USB cable between my computer and my SignaLink which is causing the USB port to reset. I've got some RF chokes I'll try putting in line to see if that helps.

Stephen Atkins

VE6CPU/VE6STA/VE6SU

Sent with secure email.

------- Original Message -------
On Tuesday, August 15th, 2023 at 1:34 PM, Stephen Atkins via groups.io <ve6cpu@...> wrote:

Hello everyone.

I'm trying to use Direwolf using ax.25 to connect to my packet bbs over RF. The packet bbs is bpq32 and I can get everything to work when I connect locally. It's running on a Windows 10 machine.

Direwolf is running on my Linux box and was being used as an iGate with no issues. I removed all of the aprs/igate from the config so it wouldn't beacon at the moment, everything else stayed the same. I run "direwolf -p -t 0" first, then use kissattach to attache to the /dev/pts/? port. From there I run "call VE6CPU CICNOD v VE6CIC-14" to try and connect to my bbs. It says it sends a packet but I don't hear one and it doesn't key the transmitter. After a few seconds it tries sending again and it does actually tx this time. On the third tx it gives the following. I've included all out put from the time I start direwolf.

Dire Wolf DEVELOPMENT version 1.7 E (Mar 3 2022)
Includes optional support for: gpsd hamlib cm108-ptt dns-sd

Reading config file direwolf.conf

Audio device for both receive and transmit: plughw:2,0 (channel 0)

Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.

Note: PTT not configured for channel 0. (Ignore this if using VOX.)

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 Zues'

Virtual KISS TNC is available on /dev/pts/4

Created symlink /tmp/kisstnc -> /dev/pts/4

DNS-SD: Avahi: Service 'Dire Wolf on Zues' successfully registered.

Invalid transmit channel 8 from KISS client app.

Are you using AX.25 for Linux? It might be trying to use a modified

version of KISS which uses the channel field differently than the

original KISS protocol specification. The solution might be to use

a command like "kissparms -c 1 -p radio" to set CRC none mode.

Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:

sudo /sbin/modprobe -q mkiss crc_force=1

<<< Data frame from KISS client application, port 8, total length = 25

000: 80 86 92 86 9c 9e 88 e0 ac 8a 6c 86 a0 aa 62 ac ..........l...b.

010: 8a 6c 86 92 86 7d 3f 04 a6 .l...}?..

Invalid transmit channel 2 from KISS client app.

Are you using AX.25 for Linux? It might be trying to use a modified

version of KISS which uses the channel field differently than the

original KISS protocol specification. The solution might be to use

a command like "kissparms -c 1 -p radio" to set CRC none mode.

Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:

sudo /sbin/modprobe -q mkiss crc_force=1

<<< Data frame from KISS client application, port 2, total length = 25

000: 20 86 92 86 9c 9e 88 e0 ac 8a 6c 86 a0 aa 62 ac .........l...b.

010: 8a 6c 86 92 86 7d 3f da 0c .l...}?..

[0L] VE6CPU-1>CICNOD,VE6CIC-14:(SABM cmd, p=1)

Audio output start error.

Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Audio write error retry count exceeded.

Audio output start error.

Bad address

The above errors repeats at least a dozen times and will repeat everytime it tries to send a packet. Should also mention it does actually send that packet and bpq32/soundmodem on the other machine sees the packet.

I did try modprobing mkiss with the suggested paramaters (after rmmod), but the same message comes up. Any idea what's happening?

Thanks for the help.

Stephen Atkins

VE6CPU/VE6STA/VE6SU

Sent with secure email.

Re: Error using kiss interface

#8536

开云体育

How close is your radio to your computer + sound device?? It would be best to get some distance between the two ideally in the vertical plane.? Also consider lowering your RF power to help with any RFI issues.

--David
KI6ZHD

On 08/15/2023 01:16 PM, Stephen Atkins via groups.io wrote:

Show quoted text

So to answer my own question.? I tried using soundmodem and got the same results.? It seems I'm getting some RF or something in to my USB cable between my computer and my SignaLink which is causing the USB port to reset.? I've got some RF chokes I'll try putting in line to see if that helps.

Stephen Atkins

VE6CPU/VE6STA/VE6SU

Sent with secure email.

------- Original Message -------
On Tuesday, August 15th, 2023 at 1:34 PM, Stephen Atkins via groups.io <ve6cpu@...> wrote:

Hello everyone.

I'm trying to use Direwolf using ax.25 to connect to my packet bbs over RF.? The packet bbs is bpq32 and I can get everything to work when I connect locally.? It's running on a Windows 10 machine.

Direwolf is running on my Linux box and was being used as an iGate with no issues.? I removed all of the aprs/igate from the config so it wouldn't beacon at the moment, everything else stayed the same.? I run "direwolf -p -t 0" first, then use kissattach to attache to the /dev/pts/? port.? From there I run "call VE6CPU CICNOD v VE6CIC-14" to try and connect to my bbs.? It says it sends a packet but I don't hear one and it doesn't key the transmitter.? After a few seconds it tries sending again and it does actually tx this time.? On the third tx it gives the following.? I've included all out put from the time I start direwolf.

Dire Wolf DEVELOPMENT version 1.7 E (Mar ?3 2022)
Includes optional support for: ?gpsd hamlib cm108-ptt dns-sd

Reading config file direwolf.conf

Audio device for both receive and transmit: plughw:2,0 ?(channel 0)

Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.

Note: PTT not configured for channel 0. (Ignore this if using VOX.)

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 Zues'

Virtual KISS TNC is available on /dev/pts/4

Created symlink /tmp/kisstnc -> /dev/pts/4

DNS-SD: Avahi: Service 'Dire Wolf on Zues' successfully registered.

Invalid transmit channel 8 from KISS client app.

Are you using AX.25 for Linux? ?It might be trying to use a modified

version of KISS which uses the channel field differently than the

original KISS protocol specification. ?The solution might be to use

a command like "kissparms -c 1 -p radio" to set CRC none mode.

Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:

sudo /sbin/modprobe -q mkiss crc_force=1

<<< Data frame from KISS client application, port 8, total length = 25

? 000: ?80 86 92 86 9c 9e 88 e0 ac 8a 6c 86 a0 aa 62 ac ?..........l...b.

? 010: ?8a 6c 86 92 86 7d 3f 04 a6 ? ? ? ? ? ? ? ? ? ? ? .l...}?..

Invalid transmit channel 2 from KISS client app.

Are you using AX.25 for Linux? ?It might be trying to use a modified

version of KISS which uses the channel field differently than the

original KISS protocol specification. ?The solution might be to use

a command like "kissparms -c 1 -p radio" to set CRC none mode.

Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:

sudo /sbin/modprobe -q mkiss crc_force=1

<<< Data frame from KISS client application, port 2, total length = 25

? 000: ?20 86 92 86 9c 9e 88 e0 ac 8a 6c 86 a0 aa 62 ac ? .........l...b.

? 010: ?8a 6c 86 92 86 7d 3f da 0c ? ? ? ? ? ? ? ? ? ? ? .l...}?..

[0L] VE6CPU-1>CICNOD,VE6CIC-14:(SABM cmd, p=1)

Audio output start error.

Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Error preparing after bad state: Bad address

Audio write error retry count exceeded.

Audio output start error.

Bad address

The above errors repeats at least a dozen times and will repeat everytime it tries to send a packet.? Should also mention it does actually send that packet and bpq32/soundmodem on the other machine sees the packet.

I did try modprobing mkiss with the suggested paramaters (after rmmod), but the same message comes up.? Any idea what's happening?

Thanks for the help.

Stephen Atkins

VE6CPU/VE6STA/VE6SU

Sent with secure email.

Re: Error using kiss interface

#8535

So to answer my own question.? I tried using soundmodem and got the same results.? It seems I'm getting some RF or something in to my USB cable between my computer and my SignaLink which is causing the USB port to reset.? I've got some RF chokes I'll try putting in line to see if that helps.

Stephen Atkins

VE6CPU/VE6STA/VE6SU

Sent with secure email.

Show quoted text

------- Original Message -------
On Tuesday, August 15th, 2023 at 1:34 PM, Stephen Atkins via groups.io <ve6cpu@...> wrote:

Hello everyone.

I'm trying to use Direwolf using ax.25 to connect to my packet bbs over RF.? The packet bbs is bpq32 and I can get everything to work when I connect locally.? It's running on a Windows 10 machine.

Direwolf is running on my Linux box and was being used as an iGate with no issues.? I removed all of the aprs/igate from the config so it wouldn't beacon at the moment, everything else stayed the same.? I run "direwolf -p -t 0" first, then use kissattach to attache to the /dev/pts/? port.? From there I run "call VE6CPU CICNOD v VE6CIC-14" to try and connect to my bbs.? It says it sends a packet but I don't hear one and it doesn't key the transmitter.? After a few seconds it tries sending again and it does actually tx this time.? On the third tx it gives the following.? I've included all out put from the time I start direwolf.

Dire Wolf DEVELOPMENT version 1.7 E (Mar ?3 2022)
Includes optional support for: ?gpsd hamlib cm108-ptt dns-sd

Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,0 ?(channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Note: PTT not configured for channel 0. (Ignore this if using VOX.)
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 Zues'
Virtual KISS TNC is available on /dev/pts/4
Created symlink /tmp/kisstnc -> /dev/pts/4
DNS-SD: Avahi: Service 'Dire Wolf on Zues' successfully registered.
Invalid transmit channel 8 from KISS client app.

Are you using AX.25 for Linux? ?It might be trying to use a modified
version of KISS which uses the channel field differently than the
original KISS protocol specification. ?The solution might be to use
a command like "kissparms -c 1 -p radio" to set CRC none mode.
Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:
sudo /sbin/modprobe -q mkiss crc_force=1

<<< Data frame from KISS client application, port 8, total length = 25
? 000: ?80 86 92 86 9c 9e 88 e0 ac 8a 6c 86 a0 aa 62 ac ?..........l...b.
? 010: ?8a 6c 86 92 86 7d 3f 04 a6 ? ? ? ? ? ? ? ? ? ? ? .l...}?..
Invalid transmit channel 2 from KISS client app.

Are you using AX.25 for Linux? ?It might be trying to use a modified
version of KISS which uses the channel field differently than the
original KISS protocol specification. ?The solution might be to use
a command like "kissparms -c 1 -p radio" to set CRC none mode.
Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:
sudo /sbin/modprobe -q mkiss crc_force=1

<<< Data frame from KISS client application, port 2, total length = 25
? 000: ?20 86 92 86 9c 9e 88 e0 ac 8a 6c 86 a0 aa 62 ac ? .........l...b.
? 010: ?8a 6c 86 92 86 7d 3f da 0c ? ? ? ? ? ? ? ? ? ? ? .l...}?..
[0L] VE6CPU-1>CICNOD,VE6CIC-14:(SABM cmd, p=1)
Audio output start error.
Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Audio write error retry count exceeded.
Audio output start error.
Bad address

The above errors repeats at least a dozen times and will repeat everytime it tries to send a packet.? Should also mention it does actually send that packet and bpq32/soundmodem on the other machine sees the packet.

I did try modprobing mkiss with the suggested paramaters (after rmmod), but the same message comes up.? Any idea what's happening?

Thanks for the help.

Stephen Atkins
VE6CPU/VE6STA/VE6SU

Sent with secure email.

Error using kiss interface

#8534

Hello everyone.

I'm trying to use Direwolf using ax.25 to connect to my packet bbs over RF.? The packet bbs is bpq32 and I can get everything to work when I connect locally.? It's running on a Windows 10 machine.

Direwolf is running on my Linux box and was being used as an iGate with no issues.? I removed all of the aprs/igate from the config so it wouldn't beacon at the moment, everything else stayed the same.? I run "direwolf -p -t 0" first, then use kissattach to attache to the /dev/pts/? port.? From there I run "call VE6CPU CICNOD v VE6CIC-14" to try and connect to my bbs.? It says it sends a packet but I don't hear one and it doesn't key the transmitter.? After a few seconds it tries sending again and it does actually tx this time.? On the third tx it gives the following.? I've included all out put from the time I start direwolf.

Dire Wolf DEVELOPMENT version 1.7 E (Mar ?3 2022)

Includes optional support for: ?gpsd hamlib cm108-ptt dns-sd

Reading config file direwolf.conf

Audio device for both receive and transmit: plughw:2,0 ?(channel 0)

Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.

Note: PTT not configured for channel 0. (Ignore this if using VOX.)

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 Zues'

Virtual KISS TNC is available on /dev/pts/4

Created symlink /tmp/kisstnc -> /dev/pts/4

DNS-SD: Avahi: Service 'Dire Wolf on Zues' successfully registered.

Invalid transmit channel 8 from KISS client app.

Are you using AX.25 for Linux? ?It might be trying to use a modified

version of KISS which uses the channel field differently than the

original KISS protocol specification. ?The solution might be to use

a command like "kissparms -c 1 -p radio" to set CRC none mode.

Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:

sudo /sbin/modprobe -q mkiss crc_force=1

<<< Data frame from KISS client application, port 8, total length = 25

? 000: ?80 86 92 86 9c 9e 88 e0 ac 8a 6c 86 a0 aa 62 ac ?..........l...b.

? 010: ?8a 6c 86 92 86 7d 3f 04 a6 ? ? ? ? ? ? ? ? ? ? ? .l...}?..

Invalid transmit channel 2 from KISS client app.

Are you using AX.25 for Linux? ?It might be trying to use a modified

version of KISS which uses the channel field differently than the

original KISS protocol specification. ?The solution might be to use

a command like "kissparms -c 1 -p radio" to set CRC none mode.

Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:

sudo /sbin/modprobe -q mkiss crc_force=1

<<< Data frame from KISS client application, port 2, total length = 25

? 000: ?20 86 92 86 9c 9e 88 e0 ac 8a 6c 86 a0 aa 62 ac ? .........l...b.

? 010: ?8a 6c 86 92 86 7d 3f da 0c ? ? ? ? ? ? ? ? ? ? ? .l...}?..

[0L] VE6CPU-1>CICNOD,VE6CIC-14:(SABM cmd, p=1)

Audio output start error.

Bad address

Error preparing after bad state: Bad address

Audio write error retry count exceeded.

Audio output start error.

Bad address

The above errors repeats at least a dozen times and will repeat everytime it tries to send a packet.? Should also mention it does actually send that packet and bpq32/soundmodem on the other machine sees the packet.

I did try modprobing mkiss with the suggested paramaters (after rmmod), but the same message comes up.? Any idea what's happening?

Thanks for the help.

Stephen Atkins

VE6CPU/VE6STA/VE6SU

Sent with secure email.

Re: Anyone Successfully Running NOAACAP?

#8533

Rusty,
I have one more idea--maybe for you the?myResend = 0 line in /etc/noaacap.conf is causing this situation.? Perhaps your station has already sent it once, and having myResend=0 would direct it to not send another.? For my use case, myResend = 3 is needed.

Why the INFOCMD error?? From what I can tell, it is because direwolf's CBEACON is expecting to receive a string of text to assemble into a packet, and doesn't receive a useful string from the INFOCMD piece.? I tested by running /usr/local/bin/noaacap.py (called by INFOCMD) a few times in quick succession.? Because I also have an active product, and myResend=3, only every third instance of /usr/local/bin/noaacap.py returns a useful text string.

I would suggest contacting K2IE if you are still having issues with noaacap (which was written initially for aprx, btw).? Hope this helped.

Jon

Re: Anyone Successfully Running NOAACAP?

#8532

开云体育

On 8/15/23 06:37, Jon Dea (AA4JM) wrote:

Chris - W4LUC,

I missed this key part of your post - my apologies:

> sh: 1: /usr/local/bin/noaacap.py: not found

?

Rusty Travis did catch that though -- that python script may have not been copied over to /usr/local/bin.? That directory is owned by the root user, so however noaacap.py gets there, you'll need to use sudo.? Aside from Rusty's approach, one could also install using the noaacap-1.0.deb file and the sudo dkpg and sudo apt-get (or just apt) commands mentioned on the github site (readme section).

Thank you Jon, I carefully followed the README, and "sudo dpkg -i aprx_2.9.0_raspi.deb" followed by"sudo apt -f install" did NOT install /usr/local/bin/noaacap.py, nor the several other required python modules, as I stated. I'm sure Mssr. Chris encountered the same issues as he described his difficulties with the program installation and function.

May I ask why the INFOCMD fails when there is certainly a weather alert for the configured zone? In case it matters:

$ systemctl status aprx
● aprx.service - LSB: start and stop aprx
???? Loaded: loaded (/etc/init.d/aprx; generated)
???? Active: active (exited) since Tue 2023-08-15 01:08:12 PDT; 6h ago
?????? Docs: man:systemd-sysv-generator(8)
??? Process: 385 ExecStart=/etc/init.d/aprx start (code=exited, status=0/SUCCESS)
??????? CPU: 97ms

Aug 15 01:08:11 aprs systemd[1]: Starting aprx.service - LSB: start and stop aprx...
Aug 15 01:08:12 aprs systemd[1]: Started aprx.service - LSB: start and stop aprx.

... and ...

$ grep -Ev "^#|^$" /etc/aprx.conf
mycall CALLSIGN
myloc lat 47yy.2N lon -120xx.2E
<aprsis>
passcode 12345
server??? rotate.aprs2.net
</aprsis>
<logging>
pidfile /var/run/aprx.pid
rflog /home/repeater/aprx-rf.log
aprxlog /home/repeater/aprx.log
</logging>
<interface>
ax25-device? $mycall
tx-ok??????? true? # transmitter enable defaults to false
telem-to-is? true? # set to 'false' to disable
</interface>
<beacon>
beaconmode both
cycle-size 2m
beacon via WIDE2-1 \
?? srccall CALLSIGN \
?? timeout 20 \
?? exec /usr/local/bin/noaacap.py
</beacon>

Re: OM>(callsign)

#8531

开云体育

Yes, if you want to _see_ a filtered view of your traffic, use an APRS client like APRSIS32 or YAAC to monitor your Direwolf instance (through the AGWPE or KISS interface), and do the filtering in that program's user interface displays, not in the data stream flowing through your digipeater.

Direwolf's log output is really meant for debugging your Direwolf setup; it wasn't intended to be a tactical user interface.

The only good reason you would want to use excluding filters in a digipeater or I-gate is for deliberate blacklisting of an offensive station (such as the pirates getting on APRS-IS to send commercial or otherwise illegal traffic, where a transmit-capable I-gate operator wouldn't want to be liable for forwarding the pirate's packets to RF).

Andrew, KA2DDO

author of YAAC

From: [email protected] <[email protected]> on behalf of Russell, KV4S <russelljthomas@...>
Sent: Tuesday, August 15, 2023 8:57:27 AM

makes sense, thank you!

On Tue, Aug 15, 2023 at 12:30?AM Geoffrey Merck <f4fxl@...> wrote:

Yes it can be filtered but you should not do it. It would drop all message traffic that would have been going through your digipeater. Messaging functionality on the network is already impaired because some areas only have receive only igates. Please do not start cutting it out from digipeaters.

--
Geoffrey F4FXL /? KC3FRA
My Direwolf stuff :

_._,_._,

_._,_._,_

Re: Anyone Successfully Running NOAACAP?

#8530

Chris - W4LUC,

I missed this key part of your post - my apologies:

> sh: 1: /usr/local/bin/noaacap.py: not found

?

Rusty Travis did catch that though -- that python script may have not been copied over to /usr/local/bin.? That directory is owned by the root user, so however noaacap.py gets there, you'll need to use sudo.? Aside from Rusty's approach, one could also install using the noaacap-1.0.deb file and the sudo dkpg and sudo apt-get (or just apt) commands mentioned on the github site (readme section).

Rusty - About six months ago I experienced errors like that with products valid for long durations.? I contacted K2IE and, for my situation, he believed that something in the data returned in the expiration time field in the NOAA XML was probably not formatted as expected by the python code.? My situation eventally cleared up, but I did notice that when my errors occurred our local NWS office had been issuing 2 overlapping products of the same criteria & different expiration values.? Some variant of that (or something completely different) could be what is happening here, but I think you may want to contact K2IE & permit him some time to consider this situation.

Jon

Re: OM>(callsign)

#8529

makes sense, thank you!

Show quoted text

On Tue, Aug 15, 2023 at 12:30?AM Geoffrey Merck <f4fxl@...> wrote:

Yes it can be filtered but you should not do it. It would drop all message traffic that would have been going through your digipeater. Messaging functionality on the network is already impaired because some areas only have receive only igates. Please do not start cutting it out from digipeaters.

--
Geoffrey F4FXL /? KC3FRA
My Direwolf stuff :

Re: Anyone Successfully Running NOAACAP?

#8528

开云体育

?I had a similar problem as Mssr. Chris, my diagnostics and solution:

$ sudo cp -v ./noaacap/usr/local/bin/noaacap.py /usr/local/bin/
'./noaacap/usr/local/bin/noaacap.py' -> '/usr/local/bin/noaacap.py'

$ ls -l /usr/local/bin/noaacap.py
-rwxr-xr-x 1 root root 10369 Aug 14 21:14 /usr/local/bin/noaacap.py

$ cat -n ~/direwolf.conf | grep CBEACON
?? 288? CBEACON EVERY=30 VIA=WIDE2-1 INFOCMD="/usr/local/bin/noaacap.py"
?? 300? #CBEACON dest="SPEECH" info="Club meeting tonight at 7 pm."
?? 305? #CBEACON dest="MORSE-6" info="de MYCALL"

$ direwolf -L direwolf.log -T %H:%M:%S -t 0
Dire Wolf DEVELOPMENT version 1.7 G (Jun 15 2023)
...
Traceback (most recent call last):
? File "/usr/local/bin/noaacap.py", line 12, in <module>
??? import pytz
ModuleNotFoundError: No module named 'pytz'
ERROR: Unable to run "/usr/local/bin/noaacap.py"
Unknown error 256
CBEACON, config file line 288, INFOCMD failure.
...

$ apt-cache search pytz
python-arrow-doc - Python library to manipulate dates, times, timestamps: documentation
python3-arrow - Python3 library to manipulate dates, times, and timestamps
python3-django-timezone-field - database and form fields for pytz objects (Python3 version)
python3-pytz-deprecation-shim - Shims to help you safely remove pytz
python3-pytzdata - timezone database for Python
python3-typeshed - collection of library stubs for Python, with static types
tz-converter - Convert the time and date across time zones

Anyway, to make a long story short after several module not found errors:

$ sudo apt -y install python3-pytzdata python3-bs4 python3-bsddb3 python3-systemd
...

$ direwolf -L direwolf.log -T %H:%M:%S -t 0
Dire Wolf DEVELOPMENT version 1.7 G (Jun 15 2023)
...
CBEACON, config file line 288, INFOCMD failure.
...

So this was successful, except for the fact that:
$ cat /etc/noaacap.conf
[noaacap]
myTZ??????????? America/Vancouver
myZone????????? WAZ026
myResend??????? 0

?and states:

In light of your excellent guidance, I don't understand why the INFOCMD fails, please?

Re: OM>(callsign)

#8527

Yes it can be filtered but you should not do it. It would drop all message traffic that would have been going through your digipeater. Messaging functionality on the network is already impaired because some areas only have receive only igates. Please do not start cutting it out from digipeaters.

--
Geoffrey F4FXL /? KC3FRA
My Direwolf stuff :

Re: Anyone Successfully Running NOAACAP?

#8526

Chris - W4LUC,

NOAACAP must be working on your RPi - the INFOCMD failure line is what happens when there is nothing on the NOAA alert server meeting the criteria you have set up in the /etc/noaacap.conf file.? Patrick (N3TSZ) touched on this.

When there is an active product on the NOAA server, /usr/local/bin/noaacap.py will run and find it, and build a packet with the pertinent info.? So, what does that look like?? I have examples below from yesterday.? (Side note--I don't use VIA=WIDE2-1 as I have no need for this information to go beyond the 2m simplex reach of my station.? Your situation could be different.)

AA4JM-1>APDW16::NWS_WARN :132300z,Excessive Heat,FLZ647-FLC009-FLZ041-044>046-053-141-144-247{DF000
AA4JM-1>APDW16::NWS_ADVIS:132300z,Heat,FLZ041-044>046-053-141-144-247-347-447-547-647-747{DIV00

Some might ask why the alert is built like this...the answer is that they are meant to be machine readable (e.g. YAAC, APRSIS32, Xastir, likely web apps too) and are coded to a specification to do that.? The Area Specific section to the right of the greater-than sign (>) at shows the details, in particular one could note that the behavior of NOAACAP uses the compressed zones & counties format.

73,
Jon

Re: Anyone Successfully Running NOAACAP?

#8525

Certainly:?https://github.com/K2IE/noaacap

Re: Anyone Successfully Running NOAACAP?

#8524

开云体育

May I ask the link where you downloaded this noaacap, please? It sounds like something I'd like to use here.

On 8/14/23 16:43, Chris - W4LUC via groups.io wrote:

Show quoted text

Hmmmm.... The script not being found shouldn't be part of this, right?

[ig] # aprsc 2.1.14-g5e22b37

[ig] # logresp W4LUC verified, server T2CAEAST

[ig] W4LUC-10>APDW16:!2634.00NR08006.24W&Rcv only IGate

sh: 1: /usr/local/bin/noaacap.py: not found

ERROR: Unable to run "/usr/local/bin/noaacap.py"

Unknown error 32512

CBEACON, config file line 46, INFOCMD failure.

Re: Anyone Successfully Running NOAACAP?

#8523

Hmmmm.... The script not being found shouldn't be part of this, right?

[ig] # aprsc 2.1.14-g5e22b37

[ig] # logresp W4LUC verified, server T2CAEAST

[ig] W4LUC-10>APDW16:!2634.00NR08006.24W&Rcv only IGate

sh: 1: /usr/local/bin/noaacap.py: not found

ERROR: Unable to run "/usr/local/bin/noaacap.py"

Unknown error 32512

CBEACON, config file line 46, INFOCMD failure.

Re: Anyone Successfully Running NOAACAP?

#8521

开云体育

On 8/14/23 16:13, Chris - W4LUC via groups.io wrote:

On Mon, Aug 14, 2023 at 06:39 PM, Rusty Travis wrote:

find / -type f -name direwolf.conf -o -name noaacap.conf 2>/dev/nul

/dev/null actually contained two ell characters

Rusty... Thanks sooo much for that!? I found my files and edited them.? I hope I can see some sort of alert come out of this.

Re: Anyone Successfully Running NOAACAP?

#8520

Every two minutes you should see red text calling out an error on the line number in the direwolf.conf where your CBEACON is. The error is because there is no alert at this time.

Patrick (N3TSZ)

On Monday, August 14, 2023 at 07:16:23 PM EDT, Chris - W4LUC via groups.io <cmaltese@...> wrote:

Hi Jon -?

As there are no current alerts for Palm Beach, FL, is there something I should be seeing in Direwolf that indicates the script is polling or something???

--Thanks / Chris

Re: Anyone Successfully Running NOAACAP?

#8519

Hi Jon -?

As there are no current alerts for Palm Beach, FL, is there something I should be seeing in Direwolf that indicates the script is polling or something???

--Thanks / Chris

Re: Anyone Successfully Running NOAACAP?

#8518

On Mon, Aug 14, 2023 at 06:39 PM, Rusty Travis wrote:

find / -type f -name direwolf.conf -o -name noaacap.conf 2>/dev/nul

Rusty... Thanks sooo much for that!? I found my files and edited them.? I hope I can see some sort of alert come out of this.

--Chris

Re: Anyone Successfully Running NOAACAP?

#8517

开云体育

On 8/13/23 15:09, Chris - W4LUC via groups.io wrote:

I have been trying to implement NOAACAP into an instance of Direwolf
installed on an RPi for the purpose of IGating severe WX warnings for my
county.  I'm currently setup as an RX only node.  The installation of the code went fine.  Where I'm getting
jammed-up is finding the following two files to edit per the
instructions:
"direwolf.conf" and "noaacap.conf".  I have GREPped until my eyes bled and
I can't find them.  Any guidance?  ...

"direwolf.conf" is a symbolic name for whatever configuration file is used when one starts direwolf. When one examines the startup command, whatever yours may be, if it doesn't contain a "-c filename" option, then the default location is either /etc/direwolf.conf or $HOME/direwolf.conf if it exists . If noaacap.conf doesn't exist, then you'll have to create it wherever the instructions state.

A very cheap, easy diagnostic is to copy and paste:

??? find / -type f -name direwolf.conf -o -name noaacap.conf 2>/dev/null

and examine the output, which should be minimal, helping your eyes to clot the bleeding. ;-)