WebChat Will Not Launch In Browser

[Randall Luebke]

Yesterday I setup my DigiPi as a DigiPeater, and then an IGate.  Both worked perfectly.  With the iGate activated, I then toggled on WebChat.  I then tried to open a WebChat session on my browser, Edge, and it failed.  I tried again with Chrome and got the same error.  This is the browser error message.  

Internal Server Error

The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.

[Randall Luebke]

This is the Syslog:

Mar 26 12:18:20 digipi systemd[1]: Starting webchat.service - webchat...
Mar 26 12:18:21 digipi systemd[1]: Started webchat.service - webchat.
Mar 26 12:18:27 digipi webchat.sh[3775]:  * Serving Flask app 'aprsd_webchat_extension'
Mar 26 12:18:27 digipi webchat.sh[3775]:  * Debug mode: off
Mar 26 12:19:03 digipi webchat.sh[3775]: 2026-03-26 12:19:03.471 | Thread-2 (process_request_thread) | ERROR    | Exception on / [GET] | flask.app:log_exception:875
Mar 26 12:19:03 digipi webchat.sh[3775]: Traceback (most recent call last):
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/usr/lib/python3.13/threading.py", line 1014, in _bootstrap
Mar 26 12:19:03 digipi webchat.sh[3775]:     self._bootstrap_inner()
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    └ <function Thread._bootstrap_inner at 0x764d4938>
Mar 26 12:19:03 digipi webchat.sh[3775]:     └ <Thread(Thread-2 (process_request_thread), started daemon 1904210912)>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/usr/lib/python3.13/threading.py", line 1043, in _bootstrap_inner
Mar 26 12:19:03 digipi webchat.sh[3775]:     self.run()
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    └ <function Thread.run at 0x764d47f8>
Mar 26 12:19:03 digipi webchat.sh[3775]:     └ <Thread(Thread-2 (process_request_thread), started daemon 1904210912)>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/usr/lib/python3.13/threading.py", line 994, in run
Mar 26 12:19:03 digipi webchat.sh[3775]:     self._target(*self._args, **self._kwargs)
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    │        │    │        │    └ {}
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    │        │    │        └ <Thread(Thread-2 (process_request_thread), started daemon 1904210912)>
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    │        │    └ (<socket.socket fd=6, family=2, type=1, proto=0, laddr=('10.0.0.40', 8055), raddr=('10.0.0.21', 53759)>, ('10.0.0.21', 53759))
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    │        └ <Thread(Thread-2 (process_request_thread), started daemon 1904210912)>
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    └ <bound method ThreadingMixIn.process_request_thread of <werkzeug.serving.ThreadedWSGIServer object at 0x74a8ff48>>
Mar 26 12:19:03 digipi webchat.sh[3775]:     └ <Thread(Thread-2 (process_request_thread), started daemon 1904210912)>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/usr/lib/python3.13/socketserver.py", line 697, in process_request_thread
Mar 26 12:19:03 digipi webchat.sh[3775]:     self.finish_request(request, client_address)
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    │              │        └ ('10.0.0.21', 53759)
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    │              └ <socket.socket fd=6, family=2, type=1, proto=0, laddr=('10.0.0.40', 8055), raddr=('10.0.0.21', 53759)>
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    └ <function BaseServer.finish_request at 0x74ecb118>
Mar 26 12:19:03 digipi webchat.sh[3775]:     └ <werkzeug.serving.ThreadedWSGIServer object at 0x74a8ff48>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/usr/lib/python3.13/socketserver.py", line 362, in finish_request
Mar 26 12:19:03 digipi webchat.sh[3775]:     self.RequestHandlerClass(request, client_address, self)
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    │                   │        │               └ <werkzeug.serving.ThreadedWSGIServer object at 0x74a8ff48>
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    │                   │        └ ('10.0.0.21', 53759)
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    │                   └ <socket.socket fd=6, family=2, type=1, proto=0, laddr=('10.0.0.40', 8055), raddr=('10.0.0.21', 53759)>
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    └ <class 'werkzeug.serving.WSGIRequestHandler'>
Mar 26 12:19:03 digipi webchat.sh[3775]:     └ <werkzeug.serving.ThreadedWSGIServer object at 0x74a8ff48>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/usr/lib/python3.13/socketserver.py", line 766, in __init__
Mar 26 12:19:03 digipi webchat.sh[3775]:     self.handle()
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    └ <function WSGIRequestHandler.handle at 0x74e38a28>
Mar 26 12:19:03 digipi webchat.sh[3775]:     └ <werkzeug.serving.WSGIRequestHandler object at 0x74a39c90>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/home/pi/.aprsd-venv/lib/python3.13/site-packages/werkzeug/serving.py", line 398, in handle
Mar 26 12:19:03 digipi webchat.sh[3775]:     super().handle()
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/usr/lib/python3.13/http/server.py", line 436, in handle
Mar 26 12:19:03 digipi webchat.sh[3775]:     self.handle_one_request()
Mar 26 12:19:03 digipi webchat.sh[3775]:     │    └ <function BaseHTTPRequestHandler.handle_one_request at 0x74ed5208>
Mar 26 12:19:03 digipi webchat.sh[3775]:     └ <werkzeug.serving.WSGIRequestHandler object at 0x74a39c90>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/usr/lib/python3.13/http/server.py", line 424, in handle_one_request
Mar 26 12:19:03 digipi webchat.sh[3775]:     method()
Mar 26 12:19:03 digipi webchat.sh[3775]:     └ <bound method WSGIRequestHandler.run_wsgi of <werkzeug.serving.WSGIRequestHandler object at 0x74a39c90>>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/home/pi/.aprsd-venv/lib/python3.13/site-packages/werkzeug/serving.py", line 370, in run_wsgi
Mar 26 12:19:03 digipi webchat.sh[3775]:     execute(self.server.app)
Mar 26 12:19:03 digipi webchat.sh[3775]:     │       │    │      └ <Flask 'aprsd_webchat_extension'>
Mar 26 12:19:03 digipi webchat.sh[3775]:     │       │    └ <werkzeug.serving.ThreadedWSGIServer object at 0x74a8ff48>
Mar 26 12:19:03 digipi webchat.sh[3775]:     │       └ <werkzeug.serving.WSGIRequestHandler object at 0x74a39c90>
Mar 26 12:19:03 digipi webchat.sh[3775]:     └ <function WSGIRequestHandler.run_wsgi.<locals>.execute at 0x749b63e8>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/home/pi/.aprsd-venv/lib/python3.13/site-packages/werkzeug/serving.py", line 331, in execute
Mar 26 12:19:03 digipi webchat.sh[3775]:     application_iter = app(environ, start_response)
Mar 26 12:19:03 digipi webchat.sh[3775]:                        │   │        └ <function WSGIRequestHandler.run_wsgi.<locals>.start_response at 0x749b62f8>
Mar 26 12:19:03 digipi webchat.sh[3775]:                        │   └ {'wsgi.version': (1, 0), 'wsgi.url_scheme': 'http', 'wsgi.input': <_io.BufferedReader name=6>, 'wsgi.errors': <_io.TextIOWrap...
Mar 26 12:19:03 digipi webchat.sh[3775]:                        └ <Flask 'aprsd_webchat_extension'>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/home/pi/.aprsd-venv/lib/python3.13/site-packages/flask/app.py", line 1536, in __call__
Mar 26 12:19:03 digipi webchat.sh[3775]:     return self.wsgi_app(environ, start_response)
Mar 26 12:19:03 digipi webchat.sh[3775]:            │    │        │        └ <function WSGIRequestHandler.run_wsgi.<locals>.start_response at 0x749b62f8>
Mar 26 12:19:03 digipi webchat.sh[3775]:            │    │        └ {'wsgi.version': (1, 0), 'wsgi.url_scheme': 'http', 'wsgi.input': <_io.BufferedReader name=6>, 'wsgi.errors': <_io.TextIOWrap...
Mar 26 12:19:03 digipi webchat.sh[3775]:            │    └ <flask_socketio._SocketIOMiddleware object at 0x74a8f6a8>
Mar 26 12:19:03 digipi webchat.sh[3775]:            └ <Flask 'aprsd_webchat_extension'>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/home/pi/.aprsd-venv/lib/python3.13/site-packages/flask_socketio/__init__.py", line 42, in __call__
Mar 26 12:19:03 digipi webchat.sh[3775]:     return super().__call__(environ, start_response)
Mar 26 12:19:03 digipi webchat.sh[3775]:                             │        └ <function WSGIRequestHandler.run_wsgi.<locals>.start_response at 0x749b62f8>
Mar 26 12:19:03 digipi webchat.sh[3775]:                             └ {'wsgi.version': (1, 0), 'wsgi.url_scheme': 'http', 'wsgi.input': <_io.BufferedReader name=6>, 'wsgi.errors': <_io.TextIOWrap...
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/home/pi/.aprsd-venv/lib/python3.13/site-packages/engineio/middleware.py", line 74, in __call__
Mar 26 12:19:03 digipi webchat.sh[3775]:     return self.wsgi_app(environ, start_response)
Mar 26 12:19:03 digipi webchat.sh[3775]:            │    │        │        └ <function WSGIRequestHandler.run_wsgi.<locals>.start_response at 0x749b62f8>
Mar 26 12:19:03 digipi webchat.sh[3775]:            │    │        └ {'wsgi.version': (1, 0), 'wsgi.url_scheme': 'http', 'wsgi.input': <_io.BufferedReader name=6>, 'wsgi.errors': <_io.TextIOWrap...
Mar 26 12:19:03 digipi webchat.sh[3775]:            │    └ <bound method Flask.wsgi_app of <Flask 'aprsd_webchat_extension'>>
Mar 26 12:19:03 digipi webchat.sh[3775]:            └ <flask_socketio._SocketIOMiddleware object at 0x74a8f6a8>
Mar 26 12:19:03 digipi webchat.sh[3775]: > File "/home/pi/.aprsd-venv/lib/python3.13/site-packages/flask/app.py", line 1511, in wsgi_app
Mar 26 12:19:03 digipi webchat.sh[3775]:     response = self.full_dispatch_request()
Mar 26 12:19:03 digipi webchat.sh[3775]:                │    └ <function Flask.full_dispatch_request at 0x7576f9d8>
Mar 26 12:19:03 digipi webchat.sh[3775]:                └ <Flask 'aprsd_webchat_extension'>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/home/pi/.aprsd-venv/lib/python3.13/site-packages/flask/app.py", line 919, in full_dispatch_request
Mar 26 12:19:03 digipi webchat.sh[3775]:     rv = self.handle_user_exception(e)
Mar 26 12:19:03 digipi webchat.sh[3775]:          │    └ <function Flask.handle_user_exception at 0x7576f898>
Mar 26 12:19:03 digipi webchat.sh[3775]:          └ <Flask 'aprsd_webchat_extension'>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/home/pi/.aprsd-venv/lib/python3.13/site-packages/flask/app.py", line 917, in full_dispatch_request
Mar 26 12:19:03 digipi webchat.sh[3775]:     rv = self.dispatch_request()
Mar 26 12:19:03 digipi webchat.sh[3775]:          │    └ <function Flask.dispatch_request at 0x7576f988>
Mar 26 12:19:03 digipi webchat.sh[3775]:          └ <Flask 'aprsd_webchat_extension'>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/home/pi/.aprsd-venv/lib/python3.13/site-packages/flask/app.py", line 902, in dispatch_request
Mar 26 12:19:03 digipi webchat.sh[3775]:     return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)  # type: ignore[no-any-return]
Mar 26 12:19:03 digipi webchat.sh[3775]:            │    │           │    │              │    │            └ {}
Mar 26 12:19:03 digipi webchat.sh[3775]:            │    │           │    │              │    └ 'index'
Mar 26 12:19:03 digipi webchat.sh[3775]:            │    │           │    │              └ <Rule '/' (OPTIONS, HEAD, GET) -> index>
Mar 26 12:19:03 digipi webchat.sh[3775]:            │    │           │    └ {'static': <function Flask.__init__.<locals>.<lambda> at 0x74a70618>, 'location': <function location at 0x74a77488>, 'index':...
Mar 26 12:19:03 digipi webchat.sh[3775]:            │    │           └ <Flask 'aprsd_webchat_extension'>
Mar 26 12:19:03 digipi webchat.sh[3775]:            │    └ <function Flask.ensure_sync at 0x7576fac8>
Mar 26 12:19:03 digipi webchat.sh[3775]:            └ <Flask 'aprsd_webchat_extension'>
Mar 26 12:19:03 digipi webchat.sh[3775]:   File "/home/pi/.aprsd-venv/lib/python3.13/site-packages/aprsd_webchat_extension/cmds/webchat.py", line 400, in index
Mar 26 12:19:03 digipi webchat.sh[3775]:     latitude = float(CONF.aprsd_webchat_extension.latitude)
Mar 26 12:19:03 digipi webchat.sh[3775]:                      └ <oslo_config.cfg.ConfigOpts object at 0x760a05f0>
Mar 26 12:19:03 digipi webchat.sh[3775]: ValueError: could not convert string to float: '33.30.08'

[Craig]

Hi Randall,

The lat/lon values you entered were oddly formatted,  "33.30.08", we're
looking for a decimal equivalent like -123.456 .

You can either "sudo remount; nano config/aprsd/aprsd.conf" and fix the
file directly (and reboot), or re-Initialize.


if it helps,
-craig
KM6LYW

[Randall Luebke]

I have been using my DigiPi for a few months now as a WinLink RMS, with the lat/lon I input via initialization as

33.30.08

-117.42.52

Does WinLink not use these values and it only uses the Gridsquare instead , so it worked?

Regardless, how should these values be formatted, and is there a way to reinitialize without reflashing?

[Craig]

Right, Winlink uses grid square.

Re-initialize is not possible without reflashing.  You'll find your
values are cached in your
web-browser form data.  It's much faster the second time - just dont'
forget to change
your lat/lon :)

-craig
KM6LYW

[Randall Luebke]

You were correct, Craig.  I re-flashed and then re-initialized with the correct Lat/Lon.  I am able to successfully transmit APRS messages to my iGate and receive Ack's and proper responses.  I can toggle-on APRS Chat and launch the web page.  All good so far.  However, when I try to transmit a message via APRS Chat, my sound card stops working.  The only way to fix it is to reboot the DigiPi.  How to I remedy this problem. 

BTW, once I get this working properly, I am going to build a go-kit similar to the one you recently posted in your YouTube video.  I'm going to travel with it, and yes, I will send you photos when done.

[Craig]

great work!

it sounds like it jams on first transmit?  that's always RF on the cables, got ferrite beads?  or a large steel nail?

Remind me what rig/interface you're using?

cool,
-craig
KM6LYW

--
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/2b759d5b-a0d6-4e2f-b10e-2b26a678d95fn%40googlegroups.com.

[Craig]

Okay, Let's look at PktLog to see what's going on

On 3/26/26 8:29 PM, Randy Luebke wrote:

My radio is a Baofeng AR5-RM and an AIOC sound card. I have 2 ferrites, on 5 inch cable connecting the AIOC to the DigiPi. This setup worked perfectly for months for WinLink. It also seems to work as an APRS iGate. I have lots of ferrites, so if adding more is your best option, I can readily try it. 

[Randall Luebke]

I had room for one my magnet on the cable running between my DigiPi and the AIOC.  After adding that ferrite and tried another transmission.  Once again, it turned off the sound card.  From my Packet Log after my attempt to send a message.

Mar 27 14:29:42 digipi systemd[1]: Starting webchat.service - webchat...
Mar 27 14:29:43 digipi systemd[1]: Started webchat.service - webchat.
Mar 27 14:29:49 digipi webchat.sh[3010]:  * Serving Flask app 'aprsd_webchat_extension'
Mar 27 14:29:49 digipi webchat.sh[3010]:  * Debug mode: off
Mar 27 14:30:03 digipi kernel: usb usb1-port1: disabled by hub (EMI?), re-enabling...
Mar 27 14:30:03 digipi kernel: usb 1-1: USB disconnect, device number 7
Mar 27 14:30:04 digipi kernel: usb 1-1: new full-speed USB device number 8 using dwc2
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 5 - ChHltd set, but reason is unknown
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 6 - ChHltd set, but reason is unknown
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 4 - ChHltd set, but reason is unknown
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 0 - ChHltd set, but reason is unknown
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 2 - ChHltd set, but reason is unknown
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 7 - ChHltd set, but reason is unknown
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 3 - ChHltd set, but reason is unknown
Mar 27 14:30:04 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:04 digipi kernel: usb 1-1: device descriptor read/64, error -71
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 6 - ChHltd set, but reason is unknown
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 4 - ChHltd set, but reason is unknown
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 0 - ChHltd set, but reason is unknown
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 2 - ChHltd set, but reason is unknown
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 7 - ChHltd set, but reason is unknown
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 3 - ChHltd set, but reason is unknown
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 5 - ChHltd set, but reason is unknown
Mar 27 14:30:05 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:05 digipi kernel: usb 1-1: device descriptor read/64, error -71
Mar 27 14:30:06 digipi kernel: usb 1-1: new full-speed USB device number 9 using dwc2
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 4 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 0 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 2 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 7 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 3 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 5 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 6 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: usb 1-1: device descriptor read/64, error -71
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 0 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 1 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 2 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 7 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 3 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 5 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 6 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: dwc2_hc_chhltd_intr_dma: Channel 4 - ChHltd set, but reason is unknown
Mar 27 14:30:06 digipi kernel: dwc2 3f980000.usb: hcint 0x00000002, intsts 0x04200029
Mar 27 14:30:07 digipi kernel: usb 1-1: device descriptor read/64, error -71
Mar 27 14:30:07 digipi kernel: usb usb1-port1: attempt power cycle
Mar 27 14:30:08 digipi systemd[1]: Stopped target sound.target - Sound Card.

[Craig]

Yup, RF on cable/device, 

EMI == Electro Magnetic Inteference,

On 3/27/26 7:33 AM, Randall Luebke wrote:

Mar 27 14:30:03 digipi kernel: usb usb1-port1: disabled by hub (EMI?), re-enabling...

relocate antenna? Pi should not be near-field broadside to the antenna.  choose
a different length USB cable?  anything but 19" or factor or multiple.


cool,
-craig
KM6LYW

[Randall Luebke]

Because I want to keep my Go-Box build as compact as possible, can I move the antenna instead of increasing the distance of the Pi from my radio?

[Craig]

sure thing, we're moving into operation best-practices here.  Ensure tight coax connections or coax
will radiate.  Try different USB cables as all shielding is not the same.  add a counterpoise to the
antenna so the USB cable doesn't become "the other half of the antenna"

There shouldn't be any metal in the antenna near-field (2 meters) broad-side, this includes
the pi and all wiring.

cool,
-craig
KM6LYW

--

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/26e4ca10-f3ef-4a30-b423-37336adb0d8en%40googlegroups.com.

[Craig]

yes, I like the rollup jpoles, especially if you're slinging it into a tree (or lashing it to a fiberglass fishing pole).

The one in your link doesn't appear to have a ferrite bead at the feedpoint.

If you're buying new, checkout N9TAX rollups on ebay.

cool,
-craig
KM6LYW

On 3/27/26 9:27 AM, Randy Luebke wrote:

The antenna I am using is one of those long, like 30+ inches, folding antennas.  The ones the feel/sound like they have a tape measure inside.  It’s probably all metal! 

 

I will try a counterpoise first, as that is a simple fix.  If that doesn't work, I will try a different antenna AND I will also try moving the current antenna.  One last question of you today before I go about my experimentation, Craig.  In your videos you often suggest a folding J-Pole antenna, like this one: Slim Jim Antenna 2 Meter 70Cm VHF/UHF New Dual Band K5BJM  Base or Portable | eBay  Aren’t these just metal wire with a plastic coating?

 

Thank you for all you do, BTW.  I was chatting with Jason KM4ACK all the way in Tennessee via my APRS.fi iOS App and your DigiPi today.  Very cool!

[WA4SKI]

As usual, Craig, you were 100% correct.  It was RF killing webchat and actually disconnecting my sound card as well.   I place a ferrite on the connection point to my antenna, wrapping the coax around it about 5 times.  I also placed a ferrite on the power cord coming from my wall transformer, which also had a ferrite built into the cord.  Now, I'm digipeating like a bandit and Webchat works as well.  I have 3 questions:

1. When I send a message to WXBOT, for example, I receive a response to my iPhone's APRS.fi App.  I do not see a response in my webchat.  If I send a text message using SMS via Webchat, my phone get's the message.  However, when I reply Webchat does not see my reply, but my APRS.fi App does. This is not what I would expect in a "Chat".  I would expect a back-forth conversation.  So, question #1, is this normal behavior?

2. When I send a message, I would like it to go out from my HT's callsign, WA4SKI-7.  If I send the message out via Webchat is it going out at my base callsign, WA4SKI, or my Digipeater callsign WA4SKI-2?

3.  How do I change the signaling message coming from my Digipeater.  Right now it's send out some something about Digipeater.org.  I would like to signal that this Digipeater is tactical and that it can and will change locations from time to time.  How do I make that update?

4.  When I initialized my DigiPi, I indicated I wanted it to start up as an iGATE.  Now, I want to change this and have it always starting as a Digipeater.  Do I have to reinitialize again, or can I make that change via Linux.

[Craig]

Great job!

the aprs.fi app connects to the internet, replies are assured.  it gets confusing real
quick if you have two devices using your callsign.  aprs.fi app will also ack a packet
and make it so you're radio will never hear re-transmits.

DigiPi WebChat *ONLY* listens to RF (configurable in ~/config/aprs/aprsd.conf).
Click PktLog and look for lines with "audio level" in them - those are actual received
packets.

DigiPi WebChat uses your base callsign since that's where you the operator 
are listening.  The automated-control operations get the SSID/suffix.  suffi?  suffexes?
I need to look, but webchat ssid should be defined in config/aprs/aprsd.conf as well.

digipeater beacon string is defined in direwolf.digipeater.conf .  your "static" location
is defined in localize.env .   APRS Tracker will beacon a positioned provided by a GPS.

Startup service is defined on the Initialize page, and poked into /etc/systemd/system/digipi-boot.service.
comment out "online.sh" and uncomment "digipeater"

good questions!
-craig
KM6LYW

To view this discussion visit https://groups.google.com/d/msgid/digipi/f219e25f-8497-4d0f-8553-01462e739325n%40googlegroups.com.

[Randall Luebke]

Yea, so, Craig.... you are way too smart for me. :)  That said, please help me one item at a time.

I have multiple beacons setup.  One for my HT, one for my iPhone, one for my iPad and one for my base callsign, each with a unique SSID.  I have been switching among them when I message from the App, as I want a respond to the appropriate SSID.  That seems to be working well as I can message the App using WA4SKI-3 (my UV-Pro) and the replies come back to my UV-Pro which is confirmed by the plesent "ding' on the radio and a little banner propping up on the UV-Pro's screen.   As far as "best practices" for APRS.fi then, should I always only message via TNC to mitigate the issues you mentioned about acks?

My RF received levels are very low, in the 30's.  But I hear a ton of them.  Do I need to turn up the volume?  If yes, am I turning up the Capture or the Audio Out?

Finally, I'm using a Baofeng AR-5RM and it does not have a GPS.  I would like to change my positions manually.  I'm a Linux neophyte.  If you would, please provide me with the "sudo nano" stuff to change the GPS as well as the startup. 

BTW, your DidigiPi is amazing and I'm proud to be a Patreon.  Thank you for your encouragement and support.  I'm learning so much!  

[Craig]

Heh, Randall, I admire the tenacious curiosity here!  inline,

On 3/31/26 10:11 AM, Randall Luebke wrote:
> Yea, so, Craig.... you are way too smart for me. :)  That said, please
> help me one item at a time.
>
> I have multiple beacons setup.  One for my HT, one for my iPhone, one
> for my iPad and one for my base callsign, each with a unique SSID.  I
> have been switching among them when I message from the App, as I want
> a respond to the appropriate SSID.  That seems to be working well as I
> can message the App using WA4SKI-3 (my UV-Pro) and the replies come
> back to my UV-Pro which is confirmed by the plesent "ding' on the
> radio and a little banner propping up on the UV-Pro's screen. As far
> as "best practices" for APRS.fi then, should I always only message via
> TNC to mitigate the issues you mentioned about acks?

right, I would never have multiple messaging systems using the same
callsign, they
will ack each other, unexpected/unreliable results.  It's also like
having the same IP
address on the internet in two places, just leads to tears.

>
> My RF received levels are very low, in the 30's.  But I hear a ton of
> them.  Do I need to turn up the volume?  If yes, am I turning up the
> Capture or the Audio Out?

you can click Audio, then press F4 for "capture" and yah, maybe tweak
it, but
20 to 80 is just fine in my experience.  50 is a good target if you want
something
to do.

>
> Finally, I'm using a Baofeng AR-5RM and it does not have a GPS.  I
> would like to change my positions manually.  I'm a Linux neophyte.  If
> you would, please provide me with the "sudo nano" stuff to change the
> GPS as well as the startup.

Shell
password: raspberry
sudo remount
sudo nano localize.env   (edit the NEWLAT/NEWLON lines)

>
> BTW, your DidigiPi is amazing and I'm proud to be a Patreon. Thank you
> for your encouragement and support.  I'm learning so much!

Thanks! that means a lot to me, It's great to see people sharing what
they know and
learning what they don't.  I get a lot from you guys too.

-craig
KM6LYW

[Randall Luebke]

Everything has been running smoothly for several days now.  I'm hitting other digipeaters 60 miles north and south of me, all from a funky 40-inch foldable antenna hanging in my 2nd story bedroom closet.  Amazing.

FYI, I am new to ham radio.  I bought my first radio about a year ago, with the idea of being able to stay in touch with my family in an emergency. Then, I jumped with both feet deep into the ham rabbit hole.  About 9 months ago I got my technician's license.  I've since joined ARRL and two local RACES groups.  Now, I own 8 radios.  I've setup a Mesh Node that tunnels into our local Sheriff's department emergency services.  Then, with your help and the genius of your DigiPi, I'm running a APRS digipeater as well as a WinLink Packet RMS.

Thank you for all your help and support and guidance, and please.....keep it up!

[Craig]

Thanks for the report Randall!  Great work - It escalates quickly
doesn't it?  :)

Have fun,
-craig
KM6LYW

[Randall Luebke]

Sorry, one last request for support on this.  I did not follow your instructions on how to edit the file for  /etc/systemd/system/digipi-boot.service.  Intead of adding/removing a # sign, I deleted the command that will start up the iGate automatically.  What is it so I can add it back into the file.  TX

[Craig]

Right, I wasn't abundantly clear, only one command shouldn't have a # sign prefix.
The pound sign effectively removes the line from the file (makes it a comment).

So, if you want DigiPi to boot as a Digipeater, remove the pound sign from "digipeater"
and add a pound sign to "online.sh"

/etc/systemd/system/digipi-boot.service

[Unit]
Description=DigiPi initial boot service
After=default.target

[Service]
Type=simple
#Wait for boot process to complete, not just start
ExecStartPre=sleep 10
#ExecStart=systemctl start digipeater
#ExecStart=systemctl start tracker
#ExecStart=systemctl start node
#ExecStart=systemctl start winlinkrms
ExecStart=systemctl start tnc
#ExecStart=systemctl start tnc300b
#ExecStart=systemctl start wsjtx
#ExecStart=systemctl start js8call
#ExecStart=systemctl start fldigi
#ExecStart=systemctl start sstv
#ExecStart=/home/pi/online.sh
#ExecStart=systemctl start node
ExecStartPost=systemctl start pat
Restart=no

--

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/26f42523-9590-40cb-928a-60589b4f5c31n%40googlegroups.com.