Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Direwolf
- Messages
Search
|
Re: Easy-Digi CODEC not installing
Your Easy Digi has two types of connections to your Pi - audio connections and a PTT connection. As Rob mentioned, the one showing up as ttyUSB0 is the serial adapter, for the PTT connection. How are you connecting the audio from the Easy Digi to your Pi? Depending on exactly which Easy Digi variant you have, it likely came with two audio cables, so what are those connected to? On a Pi, you'll want a USB sound card for that, which will show up separately in lsusb. Martin. KD6YAM On Sun, Dec 12, 2021 at 1:07 PM Fred Bouwman <bouwmanf@...> wrote: I am having trouble adding a sound card. My Easy-Digi is not adding the CODEC sound card to the Pi when I plug in the USB. A Signalink works fine on the same Pi. The Pi seems to see the device, lsusb sees it and ls /dev shows it is added as ttyUSB0, but it will not appear in the sound card dropdown in Audio Device Settings. I am running Stretch on a Pi 3B. Does anyone know how I can resolve this? Thanks for your help.? |
|
Re: Easy-Digi CODEC not installing
If it is showing as /dev/ttyUSB0, it is showing up as a serial communication port (Like Windows COM#), not a sound card. These are very different devices. Robert Giuliano
On Sunday, December 12, 2021, 04:07:09 PM EST, Fred Bouwman <bouwmanf@...> wrote:
I am having trouble adding a sound card. My Easy-Digi is not adding the CODEC sound card to the Pi when I plug in the USB. A Signalink works fine on the same Pi. The Pi seems to see the device, lsusb sees it and ls /dev shows it is added as ttyUSB0, but it will not appear in the sound card dropdown in Audio Device Settings. I am running Stretch on a Pi 3B. Does anyone know how I can resolve this? Thanks for your help.?
|
|
Easy-Digi CODEC not installing
I am having trouble adding a sound card. My Easy-Digi is not adding the CODEC sound card to the Pi when I plug in the USB. A Signalink works fine on the same Pi. The Pi seems to see the device, lsusb sees it and ls /dev shows it is added as ttyUSB0, but it will not appear in the sound card dropdown in Audio Device Settings. I am running Stretch on a Pi 3B. Does anyone know how I can resolve this? Thanks for your help.?
|
|
Re: Receiving Messages
You might create an APRS (aprsd) service. Python/aprsd/aprslib. I think direwolf is the kiss modem at the bottom of it all. wm6h |
|
Re: Transmit timing error: PTT is on 4005 mSec too long. Direwolf 1.6
#hamlib
Yes, there are no errors now and it transmits fine.?
|
|
Re: Transmit timing error: PTT is on 4005 mSec too long. Direwolf 1.6
#hamlib
开云体育Once you got the CAT communications working again, did your "transmit timing error" go away? --David KI6ZHD On 12/10/2021 11:24 AM, Doug via
groups.io wrote:
Thanks for the reply.? I rebuilt my Direwolf after reloading hamlib libraries.? That did not fix the issue.? I changed my CI-V baud setting for my radio from? 19200 to 9600...and changed it back to 19200, and it will now transmit again.? I have no idea why that worked, but your reply gave me some clues. |
|
Re: Transmit timing error: PTT is on 4005 mSec too long. Direwolf 1.6
#hamlib
Thanks for the reply.? I rebuilt my Direwolf after reloading hamlib libraries.? That did not fix the issue.? I changed my CI-V baud setting for my radio from? 19200 to 9600...and changed it back to 19200, and it will now transmit again.? I have no idea why that worked, but your reply gave me some clues.
73, Doug - KI5SBM |
|
Re: Transmit timing error: PTT is on 4005 mSec too long. Direwolf 1.6
#hamlib
When this Transmit Timing Error was reported in the past, it seemed to be caused by a hamlib failure.? We see hamlib errors in this case: Hamlib Error: rig_set_ptt command for channel 0 PTT Communication bus error???????? Hamlib Error: rig_set_ptt command for channel 0 PTT Communication bus error? That might be the cause of the other error. Let's try to fix that. What do you have for the PTT line in the configuration file? |
|
Re: Transmit timing error: PTT is on 4005 mSec too long. Direwolf 1.6
#hamlib
Does anyone know what causes this error?
|
|
Re: Receiving Messages
开云体育This sort of thing is handled in my YAAC program by plugin extensions. For example, I have a MADISpost application that extracts only weather messages and creates a log file for consumption by the Weather Service processors. The sounds plugin generates different kinds of sound effects based on the type of event that occurred, where a text message addressed to your station is one of the supported events.So you could easily write a plugin to accept only text messages addressed to you, extract the actual comment message text, and do something with it. This is why I implemented the feature for digitally-signed text messages, so you could confirm the identity of the sender before accepting such a message. Hope that helps.? Andrew, KA2DDO author of YAAC ("Yet Another APRS Client") https://www.ka2ddo.org/ka2ddo/YAAC.html -------- Original message --------
From: Don Rolph <don.rolph@...> Date: 12/9/21 15:35 (GMT-05:00) To: [email protected] Subject: Re: [direwolf] Receiving Messages I might add that the approach being experimented with in the ATGP projects team is that messaging (and other human centric activities) would be handled by a client communicating with the packet APRS beaconing/digipeating/packet handling layer. On Dec 9, 2021, at 2:22 PM, David Ranch <direwolf-groupsio@...> wrote:
|
|
Re: Receiving Messages
开云体育I might add that the approach being experimented with in the ATGP projects team is that messaging (and other human centric activities) would be handled by a client communicating with the packet APRS beaconing/digipeating/packet handling layer.On Dec 9, 2021, at 2:22 PM, David Ranch <direwolf-groupsio@...> wrote:
|
|
Re: Receiving Messages
开云体育Generally speaking, Direwolf does not support real APRS messaging at this time.? There is a Github issue tracking this feature enhancement here: ?? Maybe you can add your specific use case there and it can be considered if/when messaging gets implemented.? Until then, there are a few other things you might consider: ? - One workaround approach: ? - Other Linux programs that I understand support APRS messaging that could possibly be leveraged with your project: ? ? ? ? ? ? ???? ? (java) ???? ???? --David KI6ZHD On 12/09/2021 10:39 AM, charlie gale
wrote:
I'm familiar with using COMMENTCMD to insert data into a comment and send it, including sending it as a message to a specific user. I'd like to go the other direction - receive a message and use it to trigger some function on the computer. Is there an easy way to take a message addressed to my specific call and append it to a file or execute a command, or something? I suspect I could use the TEE command and dump everything heard and then parse what I get and purge the rest on a regular basis, but I was hoping for something a bit more streamlined. Thanks for any ideas! |
|
Re: HRoT - retained messages not delivered
开云体育Just as a quick follow up, I didn't search for what "HRoT" stood for but it evidently is this: ?? I can't say I ever heard about this project before and it's already 2yrs old!? @wb2osz: Should questions for that effort be directed to this Direwolf list?? Maybe there is some other Groups.IO list the user to send this message to? --David KI6ZHD On 12/09/2021 10:34 AM, David Ranch
wrote:
|
|
Receiving Messages
I'm familiar with using COMMENTCMD to insert data into a comment and send it, including sending it as a message to a specific user. I'd like to go the other direction - receive a message and use it to trigger some function on the computer. Is there an easy way to take a message addressed to my specific call and append it to a file or execute a command, or something? I suspect I could use the TEE command and dump everything heard and then parse what I get and purge the rest on a regular basis, but I was hoping for something a bit more streamlined. Thanks for any ideas!
|
|
Re: HRoT - retained messages not delivered
开云体育Hello Tom, I don't completely understand what you're specific issue with Direwolf is here. Assuming when you say MOSQUITTO, you're talking about the MQTT client/server solution, Direwolf has no native support for that so any issue you have here would be external to Direwolf.? Next, if you're talking about APRS messaging... Direwolf's support of messaging is very thin and messages aren't actually stored in Direwolf.. they are just relayed and either acknowledged by the recipient APRS stack or the originator APRS stack will continue to retry to send multiple times before it times out. --David KI6ZHD On 12/09/2021 08:36 AM, HB9EYZ wrote:
Following setup: DireWolf, KISSutil, HRoT, MOSQUITTO, all running on a Raspberry. |
|
HRoT - retained messages not delivered
HB9EYZ
Following setup: DireWolf, KISSutil, HRoT, MOSQUITTO, all running on a Raspberry.
'Sub' via APRS or via mosquitto_sub works fine. Also 'pub' using the same ways. Using 'pub' via APRS does not set the 'retain' flag. Using the -r parm in mosquitto_pub is possible. But the retained messages are only delivered to a new connected mosquitto_sub with the appropriate topics. When using a new 'sub' via APRS, the retained messages are not delivered.? Any idea how to bring this up and running? Thanks Tom, HB9EYZ |
|
Re: Transmit timing error: PTT is on 4005 mSec too long. Direwolf 1.6
#hamlib
Here's more info from -o
Dire Wolf version 1.6 Includes optional support for:? hamlib cm108-ptt Reading config file direwolf.conf Audio device for both receive and transmit: plughw:2,0? (channels 0 & 1) Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate. Channel 1: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate. Hamlib determined CAT control serial port rate of 19200. Note: PTT not configured for channel 1. (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 ...??????????????????????????????????????????????????? DCD 0 = 1 DCD 1 = 1???????????????????????????????????????????????????????????????????????????????????????????????????????? Attached to KISS TCP client application 0...????????????????????????????????????????????????????????????????????? Ready to accept KISS TCP client application 1 on port 8001 ...??????????????????????????????????????????????????? KISS protocol set hardware "TNC:", port 0???????????????????????????????????????????????????????????????????????? KISS protocol set hardware "MODEM:", port 0?????????????????????????????????????????????????????????????????????? KISS Set Hardware unrecognized command: MODEM. KISS protocol set hardware "MODEML:", port 0 KISS Set Hardware unrecognized command: MODEML. KISS protocol set hardware "MODEMBW:", port 0 KISS Set Hardware unrecognized command: MODEMBW. PTT 0 = 1 Hamlib Error: rig_set_ptt command for channel 0 PTT Communication bus error?????????????????????????????????????????????????????????????????????????????????????????? [0L] KI5SBM>APRS,WIDE1-1:=/>+!27d]\r? #,/W2 <0x0d> Transmit timing error: PTT is on 4010 mSec too long. PTT 0 = 0 Hamlib Error: rig_set_ptt command for channel 0 PTT Communication bus error??? |
Fred Bouwman
to navigate to use esc to dismiss