flamp 2.2.12.02 development version posted at
Index of /alpha/flamp
commit
7ca71a5b2a52d5702abc05df2899005c55edbed9
Author: kk5vd <kk5vd@...>
Date:?? Sat May 25 20:36:30 2024 -0500
??? Excess Guardlock Removed
commit 1b8af593b43388174d2f02edd37cc6e434d84a9b
Author: kk5vd <kk5vd@...>
Date:?? Sun May 19 12:36:42 2024 -0700
??? RELAY/OUTPUT FORMAT/GUARD LOCK
?? ?
???? * Remove misplaced '{}' on Relay repeat loops
???? * Simplified some code
???? * Remove exit() code on non fatal code execution.
???? * Remove header modem condition flags for replay files.
???? * Transfer to FLDIGI a few leading '\n' to separated noise
data from FLAMP data
?????? (Cosmetic, FLDIGI receive panel).
73, David, W1HKJ
for
Robert, KK5VD
|
Re: preview of next fldigi version
That is awesome! Thank you!
Will have configuration
controls to allow easily creating a "darkmode" look.
73, David, W1HKJ
--
Bog W7ZDX
|
preview of next fldigi version
Will have configuration
controls to allow easily creating a "darkmode" look.
73, David, W1HKJ
|
Re: flrig 2.0.05.55 development release posted at
no, just trying to indicate a
named file with the xxx
On 5/25/24 11:08, Cliff, AE5ZA wrote:
toggle quoted message
Show quoted text
Dave,
Is you new color scheme named xxx.UI.prefs and in
the .flrig directory?
On May 25, 2024, at 10:53, Dave, G?WBX via
< g8kbvdave@...>
wrote:
Hi.
Well, for me, the changes to Flrig are still messing
things up.
Built fine without errors or warnings, on LMDE 5 (to be
upgraded within the next 80 or so days!)
Now, my choice of colour scheme for the UI is not
applied, resulting in the "default" scheme.
Even more odd, the main version I have configured in my
system menu, has "my" colour scheme still present, I say
odd, because I've been pointing the "new" version at
"my" config' files, thus...
??? $ ./src/flrig --config-dir ~/.flrig/ts-870s
That has not been a problem before, so has anything
changed to cause trouble doing that?
(I do have all the config' files backed up of course.)
Also, the delay when using the extra buttons on the
slide out (or docked) panels, is still present.
Doing some testing, I find that the command associated
with a custom command button is sent when I click on it,
and the rig immediately reacts on the sent command
sent.? The image of the button changes to the "depressed
state" (but looks a bit ragged.)
But, the "button" does not return to the "un-clicked"
state, for some 6.7 seconds!
During which time the entire UI of Flrig is locked up.
(in v2.0.05.05 the clicked on "visually depressed" state
lasts for about half a second.)
This is common to any radio where I have setup some of
those extra buttons to do special tasks, selecting
antenna ports, changing the radio's audio configuration
for use with voice or digital modes, etc.? (In the case
of the old FT-736r, I have just about all of the
available extra buttons configured for something!)
Any "Un-configured" buttons, DO NOT stick and lock the
UI!.. (Making me think, that "there is something funny"
going on after the command has been sent, is Flrig
expecting to receive data from the radio after a custom
command is sent perhaps?)? Also, all the "usual
functions" in the main UI work without issue.? (When the
UI is not locked waiting for a custom configured button
to unstick!)
This is the third time I've mentioned this, and heard
nothing from anyone either confirming or not my
findings, while I do see my messages appearing in the
group feed, so who have I annoyed this time?? ;-)
73 to All.
??? Dave G0WBX.
--
Created on and sent from a Unix like PC running and
using free and open source software:
|
Re: flrig 2.0.05.55 development release posted at
Dave,
Is you new color scheme named xxx.UI.prefs and in the .flrig directory?
toggle quoted message
Show quoted text
On May 25, 2024, at 10:53, Dave, G?WBX via < g8kbvdave@...> wrote:
Hi.
Well, for me, the changes to Flrig are still messing things up.
Built fine without errors or warnings, on LMDE 5 (to be upgraded within the next 80 or so days!)
Now, my choice of colour scheme for the UI is not applied, resulting in the "default" scheme.
Even more odd, the main version I have configured in my system menu, has "my" colour scheme still present, I say odd, because I've been pointing the "new" version at "my" config' files, thus...
??? $ ./src/flrig --config-dir ~/.flrig/ts-870s
That has not been a problem before, so has anything changed to cause trouble doing that?
(I do have all the config' files backed up of course.)
Also, the delay when using the extra buttons on the slide out (or docked) panels, is still present.
Doing some testing, I find that the command associated with a custom command button is sent when I click on it, and the rig immediately reacts on the sent command sent.? The image of the button changes to the "depressed state" (but looks a bit ragged.)
But, the "button" does not return to the "un-clicked" state, for some 6.7 seconds!
During which time the entire UI of Flrig is locked up.
(in v2.0.05.05 the clicked on "visually depressed" state lasts for about half a second.)
This is common to any radio where I have setup some of those extra buttons to do special tasks, selecting antenna ports, changing the radio's audio configuration for use with voice or digital modes, etc.? (In the case of the old FT-736r, I have just about all of the available extra buttons configured for something!)
Any "Un-configured" buttons, DO NOT stick and lock the UI!.. (Making me think, that "there is something funny" going on after the command has been sent, is Flrig expecting to receive data from the radio after a custom command is sent perhaps?)? Also, all the "usual functions" in the main UI work without issue.? (When the UI is not locked waiting for a custom configured button to unstick!)
This is the third time I've mentioned this, and heard nothing from anyone either confirming or not my findings, while I do see my messages appearing in the group feed, so who have I annoyed this time?? ;-)
73 to All.
??? Dave G0WBX.
--
Created on and sent from a Unix like PC running and using free and open source software:
|
Re: flrig 2.0.05.55 development release posted at
Hi.
Well, for me, the changes to Flrig are still messing things up.
Built fine without errors or warnings, on LMDE 5 (to be upgraded within the next 80 or so days!)
Now, my choice of colour scheme for the UI is not applied, resulting in the "default" scheme.
Even more odd, the main version I have configured in my system menu, has "my" colour scheme still present, I say odd, because I've been pointing the "new" version at "my" config' files, thus...
??? $ ./src/flrig --config-dir ~/.flrig/ts-870s
That has not been a problem before, so has anything changed to cause trouble doing that?
(I do have all the config' files backed up of course.)
Also, the delay when using the extra buttons on the slide out (or docked) panels, is still present.
Doing some testing, I find that the command associated with a custom command button is sent when I click on it, and the rig immediately reacts on the sent command sent.? The image of the button changes to the "depressed state" (but looks a bit ragged.)
But, the "button" does not return to the "un-clicked" state, for some 6.7 seconds!
During which time the entire UI of Flrig is locked up.
(in v2.0.05.05 the clicked on "visually depressed" state lasts for about half a second.)
This is common to any radio where I have setup some of those extra buttons to do special tasks, selecting antenna ports, changing the radio's audio configuration for use with voice or digital modes, etc.? (In the case of the old FT-736r, I have just about all of the available extra buttons configured for something!)
Any "Un-configured" buttons, DO NOT stick and lock the UI!.. (Making me think, that "there is something funny" going on after the command has been sent, is Flrig expecting to receive data from the radio after a custom command is sent perhaps?)? Also, all the "usual functions" in the main UI work without issue.? (When the UI is not locked waiting for a custom configured button to unstick!)
This is the third time I've mentioned this, and heard nothing from anyone either confirming or not my findings, while I do see my messages appearing in the group feed, so who have I annoyed this time?? ;-)
73 to All.
??? Dave G0WBX.
--
Created on and sent from a Unix like PC running and using free and open source software:
|
Re: flrig 2.0.05.55 development release posted at
Phil,
For testing, rename the .flrig directory in your home directory and try .55 again. It works FB with my 7300 here.
toggle quoted message
Show quoted text
On May 25, 2024, at 10:03, Philip Rose, GM3ZZA via < gm3zza@...> wrote:
When I tried this flrig immediately launched a display showing "closing" but then just locked up. REverted to .51 for now.
73 Phil GM3ZZA
|
Re: flrig 2.0.05.55 development release posted at
On Sat, May 25, 2024 at 04:03 PM, Philip Rose, GM3ZZA wrote:
When I tried this flrig immediately launched a display showing "closing" but
then just locked up. REverted to .51 for now.
73 Phil GM3ZZA
FWIW - this is the trace file I had - the close_down is when I killed the process. Phil.
|
Re: flrig 2.0.05.55 development release posted at
When I tried this flrig immediately launched a display showing "closing" but then just locked up. REverted to .51 for now.
73 Phil GM3ZZA
|
On 24/05/2024 18:24, Brian Morrison ,G8SEZ via groups.io wrote: On Fri, 24 May 2024 08:35:27 -0700
"Philip Rose, GM3ZZA via groups.io" <gm3zza@...>
wrote:
flrig version 2.0.05.45 Maybe 2.0.05.51 will be different? Thanks Brian. .51 show the same thing happening. set_pbt_inner and set_pbt_outer are still being sent to the rig. Phil GM3ZZA
|
Thanks Cliff,
I was reading too much into the documentation. I had assumed "use
xcvr data" overrode both read and restore and not just read. I
can't see a use case for restoring without having read.
73 Phil GM3ZZA
On 24/05/2024 16:55, Cliff, AE5ZA
wrote:
toggle quoted message
Show quoted text
Phil,
Try unchecking the individual boxes for parameters
on the Restore config page. Those items are the ones that are
restored when you quit flrig.
On May 24, 2024, at 10:39, Philip Rose, GM3ZZA
via < gm3zza@...>
wrote:
What I've also noticed is that when I close
flrig it changes the rig to the state before it was
started, which is not what I want. For example I was
tuned to 10 MHz it change to 24 MHz
Phil.
|
flrig 2.0.05.55 development release posted at
Index of /alpha/flrig
- fixes to reported UI scheme configuration bugs
- improved CI-V echo detection on Windows OS
73, David, W1HKJ
|
I am sorry Vladimir, but the
macro parser does not include conditional execution.? That is an
interesting idea.
David
On 5/24/24 11:55, Vladimir, RW6AVK
wrote:
toggle quoted message
Show quoted text
Hi David!
How can I implement a macros, for example?
IF <MODEM:FELDHELL>
THEN <EQSL>?
Is it possible to process a condition in a macro?
TNX
|
On Fri, 24 May 2024 08:35:27 -0700 "Philip Rose, GM3ZZA via groups.io" <gm3zza@...> wrote: flrig version 2.0.05.45 Maybe 2.0.05.51 will be different? -- Brian G8SEZ
|
Hi David!
How can I implement a macros, for example?
IF <MODEM:FELDHELL> THEN <EQSL>?
Is it possible to process a condition in a macro?
TNX
|
Phil,
Try unchecking the individual boxes for parameters on the Restore config page. Those items are the ones that are restored when you quit flrig.
toggle quoted message
Show quoted text
On May 24, 2024, at 10:39, Philip Rose, GM3ZZA via < gm3zza@...> wrote:
What I've also noticed is that when I close flrig it changes the rig to the state before it was started, which is not what I want. For example I was tuned to 10 MHz it change to 24 MHz
Phil.
|
What I've also noticed is that when I close flrig it changes the rig to the state before it was started, which is not what I want. For example I was tuned to 10 MHz it change to 24 MHz
Phil.
|
I have been having a lot of inconvenience with the filter settings changing even though I change them back.
I have got a fairly repeatable situation now that changes FIL1 CW from 400~1600 to 350~1550 when I start Flrig.
What I see in the trace file is (first commands being sent across:
15:17:39.136 : getID()
15:17:39.136 : WriteBuffer: FE FE 94 E0 19 00 FD
15:17:39.138 : ReadBuffer [2.100000 msec]:
15:17:39.139 : ReadBuffer [0.005000 msec]: FE FE E0 94 19 00 94 FD
15:17:39.139 : set_pbt_outer()
15:17:39.139 : WriteBuffer: FE FE 94 E0 14 08 01 89 FD
15:17:39.141 : ReadBuffer [2.127000 msec]: FE FE E0 94 FB FD
15:17:39.142 : S: FE FE 94 E0 14 08 01 89 FD R: FE FE E0 94 FB FD
15:17:39.142 : set_pbt_inner()
15:17:39.142 : WriteBuffer: FE FE 94 E0 14 07 01 89 FD
15:17:39.144 : ReadBuffer [2.122000 msec]:
15:17:39.145 : ReadBuffer [0.004000 msec]: FE FE E0 94 FB FD
15:17:39.145 : S: FE FE 94 E0 14 07 01 89 FD R: FE FE E0 94 FB FD
I have the box "Use xcvr data" checked so I do not expect to see any values being updated. The above case was one that didn't change my setting: in the case where the setting was changed the values sent to the IC-7300 were 0179 rather than 0189.
flrig version 2.0.05.45
73 Phil GM3ZZA
|
Re: FLRIG - Is it possible to lock down the USB port?
Hi Gary / team,
Glad you are working with MacOS - MacLogger does check for the right ports (and will keep them constant, as long as you do not reboot).? I use a MacMini (with Arm Silicon) as well as a iMac - my advice is, leave the MacMini on 24/7.
My use case is to have FLRig manage rig control (and I have 3 HF rigs - so 3 configs) - I use RumLog, and the JS8Call interface i believe is the same as JT8.? In the Logs, I manually set the output levels.? Frankly, it's not that critical, but nice for future?reference
(and I use Gridtracker to pump the contact data over to CloudLog and other on-line logs (Clublog, HRD, QRZ, and LOTW).
Sadly, macOS does not have 'udev rules' - which I use (on linux) to interrogate the attached devices, create symbolic links, and bind to predictable ports.? On my other OS's, I just FLrig for rig control as well - and scripts to assign the correct audio devices
to each rig.
Fun stuff - 73's - share what you develop!
Glenn
WA6BJQ
toggle quoted message
Show quoted text
Hi, Glenn.
?
I’m running Sonoma 14.5.
?
That’s a shame that I can’t assign a specific port for FLRIG or, rather, that what the Mac Mini sees changes from one to the other.? Still, it is a small thing and easily corrected in moments.
?
My next challenge will be setting up logging.? I’ve installed MacLoggerDX but am not using it for rig control, simply as a logger.? The problem I’m having with that is MLDX is receiving the information from
both FLDIGI and JS8CALL but logging 0W instead of the 40W I’m using.? I suppose I could just use MLDX for rig control but from what I’ve seen that is problematic when also using digital modes.
?
Oh, well, I’ve just recently begun my transition to Mac OS and the Mac Mini as my daily driver so hopefully, in time, I’ll get this all figured out.
?
Thanks for the reply.
?
73,
Gary
?
Hi Gary....
Are you using macOS (the cu.SLAB seems to suggest that)... macOS does not 'wire' a USB port to? a specific port (on reboot).??
I use 'em all - and normally, I use Linux and have routines to assign to specific ports based on the ID from the serial connection from the rig.
Either way - the Mac rocks on rig control / logging - the FL series is great, and you can throw in RumLog, CloudLog, GridTracker, WSJT-x/JTD-x, et.al.
73's,
Since mmoving over from Windows and a computer with a "real" serial port, I have noticed that sometimes FLRIG fails to init because it is looking for the incorrect port.? For example, sometimes it is set to /dev/cu.SLAB_USBtoUART and
I have to change it to /dev/cu.SLAB_USBtoUART2 and other times, if it is already set to /dev/cu.SLAB_USBtoUART2, I have to set it to /dev/cu.SLAB_USBtoUART.? In both situations, after I make the update and click Init everything works great.
Radio is FTdx10 connected to computer via USB cable
(another USB cable is providing Port Audio to a SignaLink USB)
Computer is M1 Mac-mini running Sonoma 14.5
FLRIG is rev 2.0.05.45
FLDIGI is rev 4.2.05.15
I have another question about logging in FLDIGI, but I'll save that for another day.? Baby steps and all that.
:-)
Thanks!
Gary
WA4YMZ FM05pp
|
flamp 2.2.12.01 development version posted at
Index of /alpha/flamp
??? RELAY/OUTPUT FORMAT/GUARD LOCK
???? * Remove misplaced '{}' on Relay repeat loops
???? * Simplified some code
???? * Remove exit() code on non fatal code execution.
???? * Remove header modem condition flags for replay files.
???? * Transfer to FLDIGI a few leading '\n' to separated noise
data from FLAMP data
?????? (Cosmetic, FLDIGI receive panel).
73, David,? W1HKJ
for Robert, KK5VD
|
Dave, W1HKJ
Bogmonte, W7ZDX
Philip Rose, GM3ZZA
Glenn Jensen, WA6BJQ