|
1) How does one share the sound devices?
2) How does one avoid collisions over rig control ports?
3) how does one ensure separate?fldigi.files space?
Thanks in advance!
|
I have setup 2 instances of FLDigi one VHF one HF.
I used a signalink for one instance and internal card for the other, so I can't think of a way to share one card easily.
For setup I created two separate folders with different names, made a copy of all the folders in each directory, changed the default port for flmsg on one, and used the command line options to direct the desktop shortcut to the correct file.
|
kd8ftr:
Thanks for replying.
So this is using two different transceivers.
My need is to run two modes simultaneously?on one transceiver/one frequency. ? So I believe i would have to be able to share the card AND disambiguate the CAT control com port.
I have setup 2 instances of FLDigi one VHF one HF.
I used a signalink for one instance and internal card for the other, so I can't think of a way to share one card easily.
For setup I created two separate folders with different names, made a copy of all the folders in each directory, changed the default port for flmsg on one, and used the command line options to direct the desktop shortcut to the correct file.
|
Use Flrig to control the two fldigi setups. Search the web, there are some doc. on how to do it.
kd8ftr:
Thanks for replying.
So this is using two different transceivers.
My need is to run two modes simultaneously?on one transceiver/one frequency. ? So I believe i would have to be able to share the card AND disambiguate the CAT control com port. I have setup 2 instances of FLDigi one VHF one HF.
I used a signalink for one instance and internal card for the other, so I can't think of a way to share one card easily.
For setup I created two separate folders with different names, made a copy of all the folders in each directory, changed the default port for flmsg on one, and used the command line options to direct the desktop shortcut to the correct file.
--
|
This is a strange problem you're trying to solve. Do you really need to run two modes on the same transceiver at the same time? You do realize that will cause problems when one mode wants to transmit and the other mode is in the middle of reception, since no conventional amateur transceiver is full-duplex. How are you going to coordinate the need to transmit versus receive? It's a lot more than just figuring how to share the CAT port. Now, if this is receive-only, then you can use various sound mixing applications to create virtual sound cards for the two instances of fldigi (assuming you have figured out how to get them to use different configuration subdirectories). You might want to figure out those higher-level issues. Andrew, KA2DDO ________________________________________ From: [email protected] < [email protected]> on behalf of John W Totzke - W0JWT - MO <jwtotzke@...> Sent: Saturday, July 27, 2024 12:35 PM To: [email protected]Subject: Re: [nbems] Can one run two instances of FLDIGI at the same time? Use Flrig to control the two fldigi setups. Search the web, there are some doc. on how to do it. On Sat, Jul 27, 2024 at 11:32?AM Don Rolph via groups.io<> <don.rolph@...<mailto: [email protected]>> wrote: kd8ftr: Thanks for replying. So this is using two different transceivers. My need is to run two modes simultaneously on one transceiver/one frequency. So I believe i would have to be able to share the card AND disambiguate the CAT control com port. On Sat, Jul 27, 2024 at 12:29?PM kd8ftr via groups.io<> <kd8ftr@...<mailto: [email protected]>> wrote: I have setup 2 instances of FLDigi one VHF one HF. I used a signalink for one instance and internal card for the other, so I can't think of a way to share one card easily. For setup I created two separate folders with different names, made a copy of all the folders in each directory, changed the default port for flmsg on one, and used the command line options to direct the desktop shortcut to the correct file. -- 73, AB1PH Don Rolph -- John W. Totzke W?JWT
|
Okay, as long as you are transmitting 2 at one time, it may work fine. It goes without saying that you won't be able to send one and receive the other at the same time.
Still use 2 directories, a different port for flmsg, rig, amp, or arq on one file.
Vox shouldn't interfere. Other methods of PTT could clash if trying to use separate methods. I would suggest setting up for whichever mode has a longer transmit to do PTT keying. Then activate your second mode which should just send audio.
|
John W0JWT
thanks for you reply.
I looking at:
.
it appears that I can?run both?instances?simultaneously only if I have independent sound cards.
I believe that FLRIG would allow for sharing?of rig control.
Does anyone?have hints on sharing?the sound card?
Thanks!
On Sat, Jul 27, 2024 at 12:35?PM John W Totzke - W0JWT - MO via <jwtotzke= [email protected]> wrote:
Use Flrig to control the two fldigi setups. Search the web, there are some doc. on how to do it.
kd8ftr:
Thanks for replying.
So this is using two different transceivers.
My need is to run two modes simultaneously?on one transceiver/one frequency. ? So I believe i would have to be able to share the card AND disambiguate the CAT control com port. I have setup 2 instances of FLDigi one VHF one HF.
I used a signalink for one instance and internal card for the other, so I can't think of a way to share one card easily.
For setup I created two separate folders with different names, made a copy of all the folders in each directory, changed the default port for flmsg on one, and used the command line options to direct the desktop shortcut to the correct file.
--
--
|
Hi Don
I often run two instances of fldigi using the same audio device
(Icom 9100) I also can concurrently run wsjt-x and qsstv. CAT is
shared via flrig. I do of course QSY for the latter modes. The 2nd
fldigi instance is mainly for RX only but it does allow TX.
Pulseaudio and Pipewire under Linux quite happily share the audio
channels. I assume Windows has a similar feature.
In the config the 2nd fldigi instance has "Flrig PTT keys modem"
under rig control checked. I don't use it this way, but I can (for
example) TX two separate modes on the same frequency with (say)
different audio offsets.
My main fldigi command start is;
/usr/local/bin/fldigi --home-dir /home/user/.fldigi
My main fldigi command start is;
/usr/local/bin/fldigi --home-dir /home/user/.fldigi.rxonly
The configs also differ in the TCP ports used for flamp I/O. No
doubt flmsg would need a similar setup. I don't think flarq can be
setup that way though.
TX/RX contention would be an issue. I have not looked into that.
Perhaps PSM (under fldigi) could be used to detect the "other
modem" in the same bandpass and thus stall the TX for a while.
wsjt-x needed some features disabled so it wouldn't do automatic
CAT things.
Cheers Bob VK2YQA
On 28/7/24 02:32, Don Rolph wrote:
toggle quoted message
Show quoted text
kd8ftr:
Thanks for replying.
So this is using two different transceivers.
My need is to run two modes simultaneously?on one
transceiver/one frequency. ? So I believe i would have to be
able to share the card AND disambiguate the CAT control com
port.
I have setup 2 instances of FLDigi one VHF one HF.
I used a signalink for one instance and internal card
for the other, so I can't think of a way to share one card
easily.
For setup I created two separate folders with different
names, made a copy of all the folders in each directory,
changed the default port for flmsg on one, and used the
command line options to direct the desktop shortcut to the
correct file.
--
|
Thank you Bob.? I wil?test.
Hi Don
I often run two instances of fldigi using the same audio device
(Icom 9100) I also can concurrently run wsjt-x and qsstv. CAT is
shared via flrig. I do of course QSY for the latter modes. The 2nd
fldigi instance is mainly for RX only but it does allow TX.
Pulseaudio and Pipewire under Linux quite happily share the audio
channels. I assume Windows has a similar feature.
In the config the 2nd fldigi instance has "Flrig PTT keys modem"
under rig control checked. I don't use it this way, but I can (for
example) TX two separate modes on the same frequency with (say)
different audio offsets.
My main fldigi command start is;
/usr/local/bin/fldigi --home-dir /home/user/.fldigi
My main fldigi command start is;
/usr/local/bin/fldigi --home-dir /home/user/.fldigi.rxonly
The configs also differ in the TCP ports used for flamp I/O. No
doubt flmsg would need a similar setup. I don't think flarq can be
setup that way though.
TX/RX contention would be an issue. I have not looked into that.
Perhaps PSM (under fldigi) could be used to detect the "other
modem" in the same bandpass and thus stall the TX for a while.
wsjt-x needed some features disabled so it wouldn't do automatic
CAT things.
Cheers Bob VK2YQA
On 28/7/24 02:32, Don Rolph wrote:
kd8ftr:
Thanks for replying.
So this is using two different transceivers.
My need is to run two modes simultaneously?on one
transceiver/one frequency. ? So I believe i would have to be
able to share the card AND disambiguate the CAT control com
port.
I have setup 2 instances of FLDigi one VHF one HF.
I used a signalink for one instance and internal card
for the other, so I can't think of a way to share one card
easily.
For setup I created two separate folders with different
names, made a copy of all the folders in each directory,
changed the default port for flmsg on one, and used the
command line options to direct the desktop shortcut to the
correct file.
--
|
Oh and to explain my PSM suggestion Don.
PSM is "kind of " like the old AX25 FM squelch detect where the
TX wont key whilst a valid signal is still in the RX passband. It
does this by "buffering" the outbound signal and asserting PTT
only when the RF channel is clear. It can also add the usual
slot/persist delay numbers to reduce hidden TX problems.
I used it in the past with fldigi when I setup some auto
responding notification scripts. Simple command stuff like "send
me a picture", or "what is your current GPS output". PSM let me
send a reply as soon as the channel was clear rather than using a
fixed delay.
For your particular case the TX audio also needs to appear in the
RX stream. The simplest way to do that is to just enable the
transceiver monitor. If that isn't available a local audio
software loopback will probably work.
Cheers Bob
On 28/7/24 03:20, Don Rolph wrote:
toggle quoted message
Show quoted text
Thank you Bob.? I wil?test.
Hi Don
I often run two instances of fldigi using the same audio
device (Icom 9100) I also can concurrently run wsjt-x and
qsstv. CAT is shared via flrig. I do of course QSY for the
latter modes. The 2nd fldigi instance is mainly for RX
only but it does allow TX.
Pulseaudio and Pipewire under Linux quite happily share
the audio channels. I assume Windows has a similar
feature.
In the config the 2nd fldigi instance has "Flrig PTT keys
modem" under rig control checked. I don't use it this way,
but I can (for example) TX two separate modes on the same
frequency with (say) different audio offsets.
My main fldigi command start is;
/usr/local/bin/fldigi --home-dir /home/user/.fldigi
My main fldigi command start is;
/usr/local/bin/fldigi --home-dir /home/user/.fldigi.rxonly
The configs also differ in the TCP ports used for flamp
I/O. No doubt flmsg would need a similar setup. I don't
think flarq can be setup that way though.
TX/RX contention would be an issue. I have not looked
into that. Perhaps PSM (under fldigi) could be used to
detect the "other modem" in the same bandpass and thus
stall the TX for a while.
wsjt-x needed some features disabled so it wouldn't do
automatic CAT things.
Cheers Bob VK2YQA
On 28/7/24 02:32, Don Rolph wrote:
kd8ftr:
Thanks for replying.
So this is using two different transceivers.
My need is to run two modes simultaneously?on one
transceiver/one frequency. ? So I believe i would
have to be able to share the card AND disambiguate
the CAT control com port.
I have setup 2 instances of FLDigi one VHF one
HF.
I used a signalink for one instance and
internal card for the other, so I can't think of a
way to share one card easily.
For setup I created two separate folders with
different names, made a copy of all the folders in
each directory, changed the default port for flmsg
on one, and used the command line options to
direct the desktop shortcut to the correct file.
--
--
|
toggle quoted message
Show quoted text
Oh and to explain my PSM suggestion Don.
PSM is "kind of " like the old AX25 FM squelch detect where the
TX wont key whilst a valid signal is still in the RX passband. It
does this by "buffering" the outbound signal and asserting PTT
only when the RF channel is clear. It can also add the usual
slot/persist delay numbers to reduce hidden TX problems.
I used it in the past with fldigi when I setup some auto
responding notification scripts. Simple command stuff like "send
me a picture", or "what is your current GPS output". PSM let me
send a reply as soon as the channel was clear rather than using a
fixed delay.
For your particular case the TX audio also needs to appear in the
RX stream. The simplest way to do that is to just enable the
transceiver monitor. If that isn't available a local audio
software loopback will probably work.
Cheers Bob
On 28/7/24 03:20, Don Rolph wrote:
Thank you Bob.? I wil?test.
Hi Don
I often run two instances of fldigi using the same audio
device (Icom 9100) I also can concurrently run wsjt-x and
qsstv. CAT is shared via flrig. I do of course QSY for the
latter modes. The 2nd fldigi instance is mainly for RX
only but it does allow TX.
Pulseaudio and Pipewire under Linux quite happily share
the audio channels. I assume Windows has a similar
feature.
In the config the 2nd fldigi instance has "Flrig PTT keys
modem" under rig control checked. I don't use it this way,
but I can (for example) TX two separate modes on the same
frequency with (say) different audio offsets.
My main fldigi command start is;
/usr/local/bin/fldigi --home-dir /home/user/.fldigi
My main fldigi command start is;
/usr/local/bin/fldigi --home-dir /home/user/.fldigi.rxonly
The configs also differ in the TCP ports used for flamp
I/O. No doubt flmsg would need a similar setup. I don't
think flarq can be setup that way though.
TX/RX contention would be an issue. I have not looked
into that. Perhaps PSM (under fldigi) could be used to
detect the "other modem" in the same bandpass and thus
stall the TX for a while.
wsjt-x needed some features disabled so it wouldn't do
automatic CAT things.
Cheers Bob VK2YQA
On 28/7/24 02:32, Don Rolph wrote:
kd8ftr:
Thanks for replying.
So this is using two different transceivers.
My need is to run two modes simultaneously?on one
transceiver/one frequency. ? So I believe i would
have to be able to share the card AND disambiguate
the CAT control com port.
I have setup 2 instances of FLDigi one VHF one
HF.
I used a signalink for one instance and
internal card for the other, so I can't think of a
way to share one card easily.
For setup I created two separate folders with
different names, made a copy of all the folders in
each directory, changed the default port for flmsg
on one, and used the command line options to
direct the desktop shortcut to the correct file.
--
--
|
Hi Don,
I am running a Raspberry Pi 4b and Yaesu FT710.? The radio is tuned to 7.110.? On the Pi I am running flrig for cat, two instances of FLDIGI, one for contestia 4/250 at?+900 and one for FSQ at?+1500 also JS8CALL and Commstat.??
I JUST got this working and it is on a Pi so I won't be much help for Windows but it can be done.? Previously I had something similar working on Ubuntu and digi?+ js8 on windows but on windows digi was "listen only", I couldn't make the speakers talk to the radio.? The audio is 90% of the magic.? I am using pulseaudio on pi and ubuntu.??
Thank you Bob.? I wil?test.
Hi Don
I often run two instances of fldigi using the same audio device
(Icom 9100) I also can concurrently run wsjt-x and qsstv. CAT is
shared via flrig. I do of course QSY for the latter modes. The 2nd
fldigi instance is mainly for RX only but it does allow TX.
Pulseaudio and Pipewire under Linux quite happily share the audio
channels. I assume Windows has a similar feature.
In the config the 2nd fldigi instance has "Flrig PTT keys modem"
under rig control checked. I don't use it this way, but I can (for
example) TX two separate modes on the same frequency with (say)
different audio offsets.
My main fldigi command start is;
/usr/local/bin/fldigi --home-dir /home/user/.fldigi
My main fldigi command start is;
/usr/local/bin/fldigi --home-dir /home/user/.fldigi.rxonly
The configs also differ in the TCP ports used for flamp I/O. No
doubt flmsg would need a similar setup. I don't think flarq can be
setup that way though.
TX/RX contention would be an issue. I have not looked into that.
Perhaps PSM (under fldigi) could be used to detect the "other
modem" in the same bandpass and thus stall the TX for a while.
wsjt-x needed some features disabled so it wouldn't do automatic
CAT things.
Cheers Bob VK2YQA
On 28/7/24 02:32, Don Rolph wrote:
kd8ftr:
Thanks for replying.
So this is using two different transceivers.
My need is to run two modes simultaneously?on one
transceiver/one frequency. ? So I believe i would have to be
able to share the card AND disambiguate the CAT control com
port.
I have setup 2 instances of FLDigi one VHF one HF.
I used a signalink for one instance and internal card
for the other, so I can't think of a way to share one card
easily.
For setup I created two separate folders with different
names, made a copy of all the folders in each directory,
changed the default port for flmsg on one, and used the
command line options to direct the desktop shortcut to the
correct file.
--
--
--
richard
kd8noa
|
Hey Don:? If the question of running two instances / versions of FLDIGI at the same time is related to being able to do FLDIGI and FSQ "simultaneously" then the answer may be to use FLDIGI for FLDIGI/FLAMP messages and the FSQ Call program for FSQ.
?
N6OPE
|
KF8NOA,
Excellent piec of work.? Thanks for letting me know.
On Sat, Jul 27, 2024 at 5:40?PM richard7298 via <richard7298= [email protected]> wrote: Hi Don,
I am running a Raspberry Pi 4b and Yaesu FT710.? The radio is tuned to 7.110.? On the Pi I am running flrig for cat, two instances of FLDIGI, one for contestia 4/250 at?+900 and one for FSQ at?+1500 also JS8CALL and Commstat.??
I JUST got this working and it is on a Pi so I won't be much help for Windows but it can be done.? Previously I had something similar working on Ubuntu and digi?+ js8 on windows but on windows digi was "listen only", I couldn't make the speakers talk to the radio.? The audio is 90% of the magic.? I am using pulseaudio on pi and ubuntu.??
Thank you Bob.? I wil?test.
Hi Don
I often run two instances of fldigi using the same audio device
(Icom 9100) I also can concurrently run wsjt-x and qsstv. CAT is
shared via flrig. I do of course QSY for the latter modes. The 2nd
fldigi instance is mainly for RX only but it does allow TX.
Pulseaudio and Pipewire under Linux quite happily share the audio
channels. I assume Windows has a similar feature.
In the config the 2nd fldigi instance has "Flrig PTT keys modem"
under rig control checked. I don't use it this way, but I can (for
example) TX two separate modes on the same frequency with (say)
different audio offsets.
My main fldigi command start is;
/usr/local/bin/fldigi --home-dir /home/user/.fldigi
My main fldigi command start is;
/usr/local/bin/fldigi --home-dir /home/user/.fldigi.rxonly
The configs also differ in the TCP ports used for flamp I/O. No
doubt flmsg would need a similar setup. I don't think flarq can be
setup that way though.
TX/RX contention would be an issue. I have not looked into that.
Perhaps PSM (under fldigi) could be used to detect the "other
modem" in the same bandpass and thus stall the TX for a while.
wsjt-x needed some features disabled so it wouldn't do automatic
CAT things.
Cheers Bob VK2YQA
On 28/7/24 02:32, Don Rolph wrote:
kd8ftr:
Thanks for replying.
So this is using two different transceivers.
My need is to run two modes simultaneously?on one
transceiver/one frequency. ? So I believe i would have to be
able to share the card AND disambiguate the CAT control com
port.
I have setup 2 instances of FLDigi one VHF one HF.
I used a signalink for one instance and internal card
for the other, so I can't think of a way to share one card
easily.
For setup I created two separate folders with different
names, made a copy of all the folders in each directory,
changed the default port for flmsg on one, and used the
command line options to direct the desktop shortcut to the
correct file.
--
--
--
richard
kd8noa
|
John W Totzke - W0JWT - MO