Re: fldigi
Hello Paul, I recommend you take this question to the Fldigi list at linux...@groups.io as you'll get more traction there. Anyway.. I have a laptop running ubuntu 18-10 i have wsjt-x running smoothly BUT fldigi is killing me. Define "killing you". Is it just a lack of PTT? Does anyone have some sample config's for me i have a ft950 with a microham 3 interface. I have hamlib installed and fldigi starts and decodes ok but does no transmit. Please follow http://www.w1hkj.com/doku/doku.php?id=howto:linux_user_group_configuration_for_serial_ports to make sure your login name is in the right Unix groups. There is also reports that with bleeding edge distros like Mint 19.1 that you need to be in the "tty" group as well. You must log out and back in for the changes to go into effect. If your issues persist and after you join the Groups.IO list, post the unique output of dmesg after you plug in the MicroHam3 interface. I hope this mailing list is still alive. This list is barely alive and it mostly covers incoming Linux AX.25 patches coming from developers that are trying to keep things modern but aren't doing any testing. --David KI6ZHD
Re: fldigi setup question
On Thu, Jun 23, 2016 at 12:28:24PM +0300, Apostolos Kefalas wrote: > On Τετ, 2016-06-22 at 21:15 -0400, Haines Brown wrote: > > The SignaLink USB instructions tell me to make sure the software's > > transmit and receive audio card is set to USB Audio CODEC. I go to > > fldigi, Configure, Soundcard. Although PulseAudio is present on the > > computer, not wishing to use PulseAudio for fldigi, I have selected > > PortAudio. I assume I can do this. Am I wrong? > > No you are not wrong... though I can not understand why you want to do > that. Portaudio will use ALSA which will redirect you through > Pulseaudio!!! I'm in process of transitioning from Wheezy to Jessie, from 32bit to 64bit, and part of that will be to replace Pulseaudio with apulse. > Make sure you have installed libportaudio packages. I had libportaudio2 installed. Your point that with PulseAdio installed ALSA ends up using it convinced me that it would be easier to use puseaudio for the time being. So I told fldigi to use PulseAudio. But that leaves me with questions about how to configure pulseaudio. Reading and online searching do not even mention these things and apparently assumes the person knows that to do. Pavucontrol shows I have three output devices: HDA NVidia Digital Stereo, Xonar DX, and the SignaLink USB sound card identified as PCM2904 Audio Codec Analog Stereo. This apparently is the Burr-Brown Stereo USB CODEC used by SignaLink. In pavucontrol Configuration tab. for PCM2904 Audio Codec there is a menu of Analog profiles affecting whether mono, stereo, duplex, input, output, etc. I've no idea at all which to choose. I find strong signals with stereo + mono out or duplex, and so set it to duplex. In pavucontrol input devices there is PCM2904 Audio Codec Analog Stereo, which is set as fall back and channel is locked. This shows some signal. An there is also the device Monitor PCM2904 Audio Codec Analog Stereo. I've no idea what this is. This does not show a signal. In pavucontrol output devices there is PCM2904 audio codec analog stereo. It is not set to default, but its channel is locked with another channel. In pavucontrol, Recording, there are four instances of ALSA plug-in [fldigi] which are locked, show a little signal and are set to capture from PCM2904 Audio Codec rather than from Monitor of PCM904. Again, no idea what "monitor" refers to. Then there is also a Fldigi capture from. I set this also to PCM12904 rater than monitor. It also has a little signal. I've been assuming that Playback tab in pavucontrol refers to transmission and Recording refers to reception. Is this so? My waterfall is still like before. It is black except for a 353 Hz-wide band of noise at 14.071.503. What looks more like a signal at the very left edge of the waterfall (14.070.016) produces garbage output. Haines Brown KB1GRM -- To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: fldigi setup question
On Τετ, 2016-06-22 at 21:15 -0400, Haines Brown wrote: > There was no response to the question of my original post. I assume that > this was because it was too open ended. So I'll be more specific. > > I'm running debian Wheezy with a SignaLink USB sound card and fldigi > software. The transmitter is a K3 tuned to 14.070, TX DATA mode USB. My > computer uses PulseAudio as default. Alsamixer also sees the presence of > SignaLink's USB Audio CODEC, which is un-muted and at 84%. > > The SignaLink USB instructions tell me to make sure the software's > transmit and receive audio card is set to USB Audio CODEC. I go to > fldigi, Configure, Soundcard. Although PulseAudio is present on the > computer, not wishing to use PulseAudio for fldigi, I have selected > PortAudio. I assume I can do this. Am I wrong? No you are not wrong... though I can not understand why you want to do that. Portaudio will use ALSA which will redirect you through Pulseaudio!!! > > PortAudio does not offer an option to choose the Transmit and Receive > audio card, but instead the Capture and Playback card. I set PortAudio > Capture to the SignaLink's USB Audio CODEC card. But the fldigi > PortAudio Playback does have that option. Its options are Xonar DX (my > computer's sound card) HDA NNvidia (motherboard audio chip), iec958, > spdif (a cable?), pulse (PulseAudio?) and default (my computer's Xonar > sound card?). USB Audio CODEC is not a choice. Should it be? Should I > instead use iec958? Make sure you have installed libportaudio packages. > > Pavucontrol sees "ALSA Plugin [fldigi]" for ALSA Capture under Recording > and sees PCM2904 Audio Codec Analog Stereo among Output > Devices. Question: shouldn't what pavucontol sees and the values it sets > be irrelevant? See above!!! > > And the fldigi waterfall is strange. Fldigi is set to PSK31 at > 14070.000. The waterfall sees noise only in a band at its center > (14071.240 to 14071.716) and at its extreme left edge (14070.041). While > the middle region has nothing that looks like signals (unless it itself > is a broadband signal), the left edge looks as though it is close to the > IM distortion of a signal just out of range. Although the central region > has no visible PSK31 signals and I hear no PSK31 warble, it and the > extreme left produce garbage text ("e S tite ate oee o e too="), whether > I set the demodulation for frequency or phase shift. The only effect > changing the demodulation is that with RTTY, the garbage is upper case. > > Please help. > > Haines Brown KB1GRM > > -- > To unsubscribe from this list: send the line "unsubscribe linux-hams" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html signature.asc Description: This is a digitally signed message part
Re: fldigi setup question
There was no response to the question of my original post. I assume that this was because it was too open ended. So I'll be more specific. I'm running debian Wheezy with a SignaLink USB sound card and fldigi software. The transmitter is a K3 tuned to 14.070, TX DATA mode USB. My computer uses PulseAudio as default. Alsamixer also sees the presence of SignaLink's USB Audio CODEC, which is un-muted and at 84%. The SignaLink USB instructions tell me to make sure the software's transmit and receive audio card is set to USB Audio CODEC. I go to fldigi, Configure, Soundcard. Although PulseAudio is present on the computer, not wishing to use PulseAudio for fldigi, I have selected PortAudio. I assume I can do this. Am I wrong? PortAudio does not offer an option to choose the Transmit and Receive audio card, but instead the Capture and Playback card. I set PortAudio Capture to the SignaLink's USB Audio CODEC card. But the fldigi PortAudio Playback does have that option. Its options are Xonar DX (my computer's sound card) HDA NNvidia (motherboard audio chip), iec958, spdif (a cable?), pulse (PulseAudio?) and default (my computer's Xonar sound card?). USB Audio CODEC is not a choice. Should it be? Should I instead use iec958? Pavucontrol sees "ALSA Plugin [fldigi]" for ALSA Capture under Recording and sees PCM2904 Audio Codec Analog Stereo among Output Devices. Question: shouldn't what pavucontol sees and the values it sets be irrelevant? And the fldigi waterfall is strange. Fldigi is set to PSK31 at 14070.000. The waterfall sees noise only in a band at its center (14071.240 to 14071.716) and at its extreme left edge (14070.041). While the middle region has nothing that looks like signals (unless it itself is a broadband signal), the left edge looks as though it is close to the IM distortion of a signal just out of range. Although the central region has no visible PSK31 signals and I hear no PSK31 warble, it and the extreme left produce garbage text ("e S tite ate oee o e too="), whether I set the demodulation for frequency or phase shift. The only effect changing the demodulation is that with RTTY, the garbage is upper case. Please help. Haines Brown KB1GRM -- To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: fldigi audio configuration.
On Sun, Jun 19, 2016 at 10:59:59PM +0300, Apostolos Kefalas wrote: > On Παρ, 2016-06-17 at 09:34 -0400, Haines Brown wrote: > > I'm getting back to ham radio after many years of absence. I'm running > > an Elecraft K3, PSK31 mode, with a Signalink USB sound card feeding into > > fldigi under Debian Wheezy. > > > > First of all I would recommend to install Debian Jessie instead of > Wheezy (which is too old) if this is possible. Thanks for the reply, Apostolos. I'm actually running Devuan Jessie on another disk on the current machine and also on another machine, but want to get fldigi rolling on Wheezy. My ability to get fldigi going on the other disk from the current one is limited by the fact that the Jessie disk is 64 bit and my current Wheezy is 32 bit. This probably precludes chroot. > > My question concerns fldigi audio configuration. Because I happen to > > have PulseAudio installed, I checked Pulse Audio in fldigi audio > > configuration. However, it asks for the sound server string. $ echo > > $PULSE_SERVER returns nothing. How do I obtain the string's value? > > > You don't need any server string except on very special situations, like > remote audio server. Thanks. > > Pavucontrol shows fldigi playback on and fldigi capture from. My K3 > > receiver is set to 14.070.15 and fldigi is set to 14070.00. > > If you are not controlling K3 through fldigi (flrig, hamlib, etc) then > its OK. > > > The sound > > from the K3 speaker sounds like I might be getting some signals and the > > noise produces an occasional random character in fldigi's Rx field, but > > so far no waterfall. That is, I choose default PAL to be dark blue, but > > waterfall area is black > > Open pavucontrol, go to "Input Devices" and select the correct "Port" > where you have connected K3 I've finally got a waterfall. I suspect this was by selecting USB Audio CODEC as default card in alsamixer. In pavucontrol, Input Devices, I see PCM2904 Audio Codec Analog Stereo device. Its levels are high. It is not muted or locked or set to be default. I see nothing about port here. In fldigi. I set Xcvr Freq to 14070.150, the frequency to which the K3 is tuned. In Open List (book icon), I select "14070.000 USB BPSK31 1" When I go to the middle of the waterfall (1500), the frequency field shows 141071.662. That is, it seems fldigi's passband is outside the 20 meter PSK31 band and this is why I get no signals. It seems fldigi not listening to the 20 meter PSK31 band. The waterfall displays sets of simple vertical lines about 220 Hz apart, each pair separated by a weak line about 100 Hz from the left line. Haines -- To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html