开云体育

And isn't it coincidental that this problem shows up the first time I ran DireWolf after I did a significant upgrade to my Fedora system.....

________________________________________
From: [email protected] <[email protected]> on behalf of Andrew P. <andrewemt@...>
Sent: Sunday, September 17, 2023 7:51 PM
To: [email protected]
Subject: Re: [direwolf] can't pick correct device on PTT RIG command with latest source

Re: the first issue: when I run the Fedora Core 37's distro install of direwolf 1.6 with the same direwolf.conf file (I am explicitly using the complete absolute file path), everything works perfectly (receive and transmit). And it's the same O/S-installed version of libasound.so.2.0.0, which is odd.

No, I take that back. Direwolf 1.6 managed to transmit my first beacon, but it started the alsa failures on the second beacon transmission attempt.

Andrew, KA2DDO

________________________________________
From: [email protected] <[email protected]> on behalf of David Ranch <direwolf-groupsio@...>
Sent: Sunday, September 17, 2023 7:38 PM
To: [email protected]
Subject: Re: [direwolf] can't pick correct device on PTT RIG command with latest source


Hello Andrew,

It's VERY strange that Direwolf is choosing /dev/ttyS0 when you've configured /dev/ttyUSB5. When you start direwolf, are you possibly loading the wrong direwolf.conf file? Also, is the "apavlin" user in the dialout Unix group? Next, regarding your "Error preparing after bad state: Bad address" error, this is a known issue with bleeding edge versions of ALSA. This is discussed AND fixed per this thread here:

/g/direwolf/topic/99527314#8286

--David
KI6ZHD


On 09/17/2023 02:32 PM, Andrew P. wrote:

Greetings.

I just pulled the latest git clone code for hamlib and direwolf (2023-Sep-17 17:00 US/Eastern time), and rebuilt my copy of direwolf on the dev branch. Now I can't have PTT control over my Icom IC-7100 radio. Every time I start up DireWolf, it reports the following:
---------------------------------------------------------------------------------
Dire Wolf version 1.7 (Sep 17 2023) BETA TEST 7
Includes optional support for: gpsd hamlib cm108-ptt dns-sd
Warning: Could not open 'symbols-new.txt'.
The "new" OVERLAID character information will not be available.

Reading config file /home/apavlin/direwolf.conf
Audio device for both receive and transmit: plughw:1,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Hamlib determined CAT control serial port rate of 0.
User configuration overriding hamlib CAT control speed to 19200.
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Hamlib Rig open error -2: rig_settings_get_path: path=/home/apavlin/.config/hamlib_settings
rig_settings_load_all: settings_file (/home/apavlin/.config/hamlib_settings): No such file or directory
rig_open: cwd=/home/apavlin
rig_open: /home/apavlin/hamlib_settings does not exist
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/ttyS0
serial_setup: tcgetattr
serial_setup: cfmakeraw
serial_setup: cfsetispeed=19200,0x000e
serial_setup: cfsetospeed=19200,0x000e
serial_setup: data_bits=8
serial_setup: parity=0
serial_setup: Handshake=None
serial_setup: tcsetattr TCSANOW
serial_setup: tcsetattr failed: Input/output error
port_open: serial_open(/dev/ttyS0) status=-2, err=Bad file descriptor
rig_open: rs->comm_state==0?=0
1:rig.c(1023):rig_open returning(-2) Invalid configuration

Invalid configuration
-----------------------------------------------------

Note there are long delays between printouts of the "Retrying Hamlib Rig Open" call. Also, the PTT directive in my direwolf.conf file says:

PTT RIG 3070 /dev/ttyUSB5 19200

but the above error messages are complaining about /dev/ttyS0. My system doesn't have a motherboard serial port, and I can access /dev/ttyUSB5 with the rigctl command (although it has other issues). There is no rigctld daemon running on my Fedora Core 37 system, uname reports:
Linux 6.4.15-100.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Sep 7 00:23:27 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

There is only one CHANNEL defined in my direwolf.conf file.

Before I installed a local copy of the latest hamlib, building the latest DireWolf would successfully start and receive packets successfully, but it would fail with dozens of errors trying to transmit (and it still didn't key the transmitter):
------------------------------------------------------------------------
[0L] KA2DDO>APJYC1,WIDE1-1:=4003.35N/07527.42W? YAAC development<0x0d>
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.
-------------------------------------------------------------------------

Any suggestions as to what went wrong?

Andrew, KA2DDO