Understood, James.? I'm saying that if you read what is already in the channel and put that into a Memory Write command (button) with flrig, the radio will switch to that memory location and switch from VFO to MCH, if it was in VFO.
?
Yes, it's rewriting the memory, but with the information that was already there.? Assigning that MW command to an flrig command "button" makes it a one-touch effort to go to the channel and switch to memory mode. You'd have to repeat the effort if you ever change memory channel settings, otherwise you'd be writing earlier settings into the memory when using the flrig user button.
?
Win4Yaesu must likewise do a? set of MR/MW commands.?? I don't see any other way to switch from VFO to memory mode.
The only thing I want to achieve is to change memory channels that are programmed in the radio. But sometimes, I am in VFO mode for whatever reason and if I want to get back to being able to change my channels, I have to press the V/M on the radio. I really wish I could figure out what the CAT code is for this purpose. As Peter stated above, the command/code must exist as Win4Yaesu software has this function.
The radio switches to Memory mode and the designated channel upon a write (MW).? You could set command buttons with memory writes by copying the results from a Memory Read (MR) to a command (button), changing the 'MR' response characters to a 'MW'.? It seems to work, but I'd have to be careful not to mangle up my memories.
No trace of a "sticky" PTT issue running Flrig on it's own.? (I
spent a minute clicking the PTT button and no stickyness...)
But..?? I have had one occurrence when using the "Tune" button in
Fldigi 4.2.06.9 (PSK31 mode) and this Flrig alpha.
Only ONE occurrence so far, I've spent some minutes clicking the
tune (or T/R) button in Fldigi, and so far only that one stuck PTT
issue.? (Toggling the "Tune" button, recovered it.)
Could there be a way for Flgidi to check the state of Flrig's
TX/RX condition after Fldigi transitions from Transmit to Receive,
and do something to make things safe or warn the operator??? As it
is generally aware of what Flrig does, as it can key the modem (if
configured to do so) if it sees Fldigi going into the Transmit
state?
Is there a possibility of a race condition, relating to the
polling periods, between Flrig and the Radio, versus Fldigi and
Flrig ?
Related (maybe.)? I recall from the past (but can't find it in
Fldigi's configuration settings) that there is (or used to be) a
setting to delay the modem for a period after going into
Transmit.? Is that so, or has my grey cell created a myth?
So, I got the Channel Up/Down working, but I have to place the 991 into Memory mode, by hand. I've looked through the CAT control commands and for the life of me, I cannot find the command to toggle between V/M mode. Does this command exist?
in which the WEFAX settings are described as any kind of combination between 288/576 and 30,60,120,240 lpm...
at page 7 of the pdf, Kyodo news is quoted as requiring 60 and 120 lpm / 576 IOC setting:
"Next Tokyo station is JJC, it is Kyodo News Agency. Transmission speed is 60 lpm and IOC 576, sometimes 120 lpm when weather charts are posted."
I also wrote to the owner of the internet site and reached to me, indeed confirming that the setting for 576/120 and 60 are needed in order to receive this station... quoting his email:
"Yes, for Kyodo one needs 576/60. Fldigi removed the line setting from its interface at some point, quite a long time ?ago. What I did, was that I created a copy of Fldigi source code and changed hardcoded 120 to 60. So for Kyodo decoding I would simply run a second altered Fldigi. So yes, I can confirm this behavior of a removed lines dropdown, as it really was there before."
I think the best course of action is to permit changing the combination of all those parameter as it was before, also as it is described in the wefax standard in the PDF i linked before - I will do it myself but I'm not a skilled programmer anymore (I was a programmer in the late '90 :) )
I will try to receive some transmission to test them asap!
I see, but those changes broke the reception of a very
interesting radio station (KYODO NEWS). For what I see, this
is a bug - something that was working before, now it isn't. :(
On Fri, Nov 22, 2024 at
2:15?PM Dave, W1HKJ via <w1hkj=[email protected]>
wrote:
Those changes
were made over 4 years ago.? If you need to reinstall an
older version of the software these are available at
73, David, W1HKJ
On 11/22/24 01:01, Asbesto, IW9HGS via wrote:
Hello,?
In FLDigi 4.1.9 that I had on my old computer I was
able to set some things about WEFAX that now are
disappeared in the newer versions...
I have a new laptop, I installed the recent version
of my GNU/Linux OS, and some options are missing.
I don't have anymore the "LPM" setting, the FIR
setting nor the 4 bargraph showing START, PHASE,
IMAGE... and I think also the "skip phase" is
missing.?
The
main problem is the "LPM" setting, because I can't
set it correctly to receive Kyodo News from Japan.
Kyodo
News require IOC576 with 60LPM and I can't set it
What
I receive now is basically a half page, the other
half is cut away and I can't solve this problem.
Is there some way to get back those settings for?WeFax?
I think now it's unusable for KYODO NEWS decoding.?
I see, but those changes broke the reception of a very
interesting radio station (KYODO NEWS). For what I see, this
is a bug - something that was working before, now it isn't. :(
On Fri, Nov 22, 2024 at
2:15?PM Dave, W1HKJ via <w1hkj=[email protected]>
wrote:
Those changes
were made over 4 years ago.? If you need to reinstall an
older version of the software these are available at
73, David, W1HKJ
On 11/22/24 01:01, Asbesto, IW9HGS via wrote:
Hello,?
In FLDigi 4.1.9 that I had on my old computer I was
able to set some things about WEFAX that now are
disappeared in the newer versions...
I have a new laptop, I installed the recent version
of my GNU/Linux OS, and some options are missing.
I don't have anymore the "LPM" setting, the FIR
setting nor the 4 bargraph showing START, PHASE,
IMAGE... and I think also the "skip phase" is
missing.?
The
main problem is the "LPM" setting, because I can't
set it correctly to receive Kyodo News from Japan.
Kyodo
News require IOC576 with 60LPM and I can't set it
What
I receive now is basically a half page, the other
half is cut away and I can't solve this problem.
Is there some way to get back those settings for?WeFax?
I think now it's unusable for KYODO NEWS decoding.?
I see, but those changes broke the reception of a very
interesting radio station (KYODO NEWS). For what I see, this
is a bug - something that was working before, now it isn't. :(
On Fri, Nov 22, 2024 at
2:15?PM Dave, W1HKJ via <w1hkj=[email protected]>
wrote:
Those changes
were made over 4 years ago.? If you need to reinstall an
older version of the software these are available at
73, David, W1HKJ
On 11/22/24 01:01, Asbesto, IW9HGS via wrote:
Hello,?
In FLDigi 4.1.9 that I had on my old computer I was
able to set some things about WEFAX that now are
disappeared in the newer versions...
I have a new laptop, I installed the recent version
of my GNU/Linux OS, and some options are missing.
I don't have anymore the "LPM" setting, the FIR
setting nor the 4 bargraph showing START, PHASE,
IMAGE... and I think also the "skip phase" is
missing.?
The
main problem is the "LPM" setting, because I can't
set it correctly to receive Kyodo News from Japan.
Kyodo
News require IOC576 with 60LPM and I can't set it
What
I receive now is basically a half page, the other
half is cut away and I can't solve this problem.
Is there some way to get back those settings for?WeFax?
I think now it's unusable for KYODO NEWS decoding.?
Will await what you might find re the Fldigi "pre-tone" issue.
Re Flrig.
This is the PTT setup.
The use of CAT for the PTT status GET, also allows Flrig to
correctly indicate the TX/RX state, even if I have used the mic's
own PTT button to transmit voice, if/when needed.
Fldigi is set to NOT key the modem if it sees Flrig indicating TX
from other stimulus, such as WSJTx or QSSTV etc.
As in Fldigi's? Configure | Rig Control | Flrig dialogue.
And this is the Flrig general radio setup...? (Port name created
by UDEV rule.)
All the above has been wonderfully reliable in the past.? (But
there was a sticky button issue in a recent past alpha, but that
related to the user configurable "Extra Command Buttons", not the
PTT.
Anything else you wish to see, tests run etc, just ask.
I see, but those changes broke the reception of a very interesting radio station (KYODO NEWS). For what I see, this is a bug - something that was working before, now it isn't. :(
On Fri, Nov 22, 2024 at 2:15?PM Dave, W1HKJ via <w1hkj=[email protected]> wrote:
Those changes were made over 4
years ago.? If you need to reinstall an older version of the
software these are available at
73, David, W1HKJ
On 11/22/24 01:01, Asbesto, IW9HGS via
wrote:
Hello,?
In FLDigi 4.1.9 that I had on my old computer I was able to
set some things about WEFAX that now are disappeared in the
newer versions...
I have a new laptop, I installed the recent version of my
GNU/Linux OS, and some options are missing.
I don't have anymore the "LPM" setting, the FIR setting nor
the 4 bargraph showing START, PHASE, IMAGE... and I think
also the "skip phase" is missing.?
The
main problem is the "LPM" setting, because I can't set it
correctly to receive Kyodo News from Japan.
Kyodo
News require IOC576 with 60LPM and I can't set it
What
I receive now is basically a half page, the other half is
cut away and I can't solve this problem.
Is there some way to get back those settings for?WeFax? I think now it's unusable
for KYODO NEWS decoding.?
On 11/23/24 12:38, Dave, G?WBX via
groups.io wrote:
Hi.
A minor bug found in Fldigi 4.2.06.09
And I think a more critical bug with Flrig 2.0.05.75
Both built from source on Linux LMDE 6* in the last few days.
(* Based on Debian 12.1 bookworm, a recent clean install.)
First:? Fldigi 4.2.06.09
If in the RsID configuration panel of Fldigi, a "pre signal
tone" is set, then even if the "TxID" button is not active,
Fldigi sends that "Pre Signal" tone every time it goes to
"Transmit", also when invoking the Tune button!
Worse, it does it when Fldigi is in CW mode, AND the TxID
feature is disabled ("TxID" button LED is dark.)
The work-around for now, is to not have a pre-signal tone set.?
(I had 0.2 seconds for some obscure reason.? I know others who
have as much as 1 second in there, for remote auto ATU's to chew
on.)
This may have been present in earlier versions, but I never
came across it before.? Only now when "playing" with things did
I notice it.?? I suspect this is a pure Fldigi issue.
More than likely a logic statement error.? I
will investigate and correct.
Second: Flrig 2.0.05.75
Trying Flrig on it's own. (No instance of Fldigi or other
software that might use it lurking in the background.)
Sometimes, when clicking on the "PTT" button while Flrig and
the radio are in TX, even while ZERO RF is being produced (no
audio being fed to the rig, both drive and power controls are at
minimum, plus it is connected to a Load, not an Antenna.)
The PTT button in Flrig will visually "Depress" when one clicks
on it, and the "LED" goes out, but a second or so later, the
button "releases" (appears to pop out again) with the LED again
lit!? (Presumably after reading the radio's status, as that was
still in the TX state..)
When using Fldigi, and that transitions from TX to RX, the same
problem can occur.? "Cycling" Fldigi's "Tune" button can "unjam"
it (but not always the first time.)? Clicking on the PTT button
in Flrig (that has it's yellow "LED" lit) is a better way, and
usually works the first time, though not always.
The rig here is a Kenwood TS870s, with USB to serial comm's at
57600bd using RTS/CTS handshake as required by the Kenwood, and
DTR for the PTT (Needed for the rig to accept TX audio via the
ACC connector, also muting the front panel Mic.)
That has all been 100% reliable over the years since I figured
out how set it up correctly..
Dave (HKJ) if you need specific tests/trials done, just tell me
what and how etc.
Have you set the PTT/DTR signal to BOTH ??
flrig will then read the PTT state as the last set DTR state.
73, David
Other than the above, it all seems to be working just fine
thanks, so long as I pay attention to what is happening!
And I think a more critical bug with Flrig 2.0.05.75
Both built from source on Linux LMDE 6* in the last few days.
(* Based on Debian 12.1 bookworm, a recent clean install.)
First:? Fldigi 4.2.06.09
If in the RsID configuration panel of Fldigi, a "pre signal tone"
is set, then even if the "TxID" button is not active, Fldigi sends
that "Pre Signal" tone every time it goes to "Transmit", also when
invoking the Tune button!
Worse, it does it when Fldigi is in CW mode, AND the TxID feature
is disabled ("TxID" button LED is dark.)
The work-around for now, is to not have a pre-signal tone set.?
(I had 0.2 seconds for some obscure reason.? I know others who
have as much as 1 second in there, for remote auto ATU's to chew
on.)
This may have been present in earlier versions, but I never came
across it before.? Only now when "playing" with things did I
notice it.?? I suspect this is a pure Fldigi issue.
Second: Flrig 2.0.05.75
Trying Flrig on it's own. (No instance of Fldigi or other
software that might use it lurking in the background.)
Sometimes, when clicking on the "PTT" button while Flrig and the
radio are in TX, even while ZERO RF is being produced (no audio
being fed to the rig, both drive and power controls are at
minimum, plus it is connected to a Load, not an Antenna.)
The PTT button in Flrig will visually "Depress" when one clicks
on it, and the "LED" goes out, but a second or so later, the
button "releases" (appears to pop out again) with the LED again
lit!? (Presumably after reading the radio's status, as that was
still in the TX state..)
When using Fldigi, and that transitions from TX to RX, the same
problem can occur.? "Cycling" Fldigi's "Tune" button can "unjam"
it (but not always the first time.)? Clicking on the PTT button in
Flrig (that has it's yellow "LED" lit) is a better way, and
usually works the first time, though not always.
The rig here is a Kenwood TS870s, with USB to serial comm's at
57600bd using RTS/CTS handshake as required by the Kenwood, and
DTR for the PTT (Needed for the rig to accept TX audio via the ACC
connector, also muting the front panel Mic.)
That has all been 100% reliable over the years since I figured
out how set it up correctly..
Dave (HKJ) if you need specific tests/trials done, just tell me
what and how etc.
Other than the above, it all seems to be working just fine
thanks, so long as I pay attention to what is happening!