Re: Question about fldigi submode logging / testing feedback on fldigi 4.2.06
Not sure if this will go directly to you or the group so I separated it out.? If anyone else sees this, please feel free to deleted it immediately.? Or not.? You¡¯re call.?
?
?
I¡¯m used to name confusion.? About 30 years ago I was working in Order Fulfillment for a large commercial computer company based in Massachusetts. (I was in one of our NC facilities.) ?One day I started getting
emails asking me for specifics about a new project engineering was working on but, since my job responsibility had nothing to do with that function, I looked in the address book to see if I could figure out who the intended recipient was so I could forward
it to them.? It turns out that there was an engineer with the same name.? I forwarded the email to him (copying the original sender) and, over time as we continued to receive each other¡¯s emails, we developed an online friendship.? The biggest surprise was
when we were discussing what we were going to do over the weekend and one of us, not sure who, mentioned doing some antenna work.? It was then when we realized we not only shared a name but also a hobby.
?
Eventually, he told me he was going to another company and the misrouted emails ceased.? A few years later that company bought my company, but by then he had retired so we never experienced getting each other¡¯s
emails again.
?
Anyways, just a small anecdote about how, even in such a large community, we run up on people with whom we have similarities, even sharing a name.
?
Gary Rogers in North Carolina.
?
This is gonna be confusing :)
Gary, all are welcome to use the zip file. Just download, open the zip file and drag it to your applications folder and double click. It should open without additional steps.
toggle quoted message
Show quoted text
On Nov 16, 2024, at 10:09?PM, Gary WA4YMZ via groups.io <wa4ymz@...> wrote:
?
I tried but after receiving the ¡°we couldn¡¯t verify¡± message the only options I had were to cancel out or delete the app.? I think that there may be an issue with my Mac mini since I tried to open the previously
installed and working version that required hoop-jumping (4.2.05.15) using the work around, which was working a few weeks ago, ?but now I just get the Terminal opening and its expected message, but everything hangs after that.? I¡¯m using an M1 Mini running
15.0.1
BTW, if you do decide to bite the bullet and enroll in the Developer program, I¡¯m sure there will be many of us who will gladly chip in to cover the cost.
I clicked on the zip file icon and that took me to your DropBox.? Are you sharing that file with just Dave or with the wider group?? Thanks.
Thank you Gary.? Perhaps it is time for me to fultill the Apple Developer requirements.
David
On 11/13/24 15:23, Gary Rogers, KO3F via??wrote:
Dave, I took the liberty of using my Apple Developer ID to re-sign Fldigi-4.2.06.05.dmg, sending it through the Apple notarization tool and stapling the approval to the app. This should permit MacOS 15 users to open and run the app without
all the extra steps. Its in my dropbox here:?
I¡¯m happy to help with signing and notarizing Fldigi apps for Mac going forward, if desired.
On Nov 13, 2024, at 3:38?PM, Barry, PC1K via??<barry@...>wrote:
Thanks Phil,
Helpful background info, much appreciated!
73 de PC1K
On 13-11-2024 21:14, Philip Rose, GM3ZZA via??wrote:
I joined the ADIF community after the introduction of SUBMODE, version 3 I think. But from some of the discussion, I understand it was an attempt to get a handle on the growing proliferation
of new modes. MODE was an attempt at being limited to modulation technique, and SUBMODE defining the coding.?
So modes like LSB became MODE=SSB, SUBMODE=LSB. And the digital modes similarly. At the time MODE=LSB became deprecated, and allowed to be imported from files created? by unmaintained legacy
apps, but all apps being developed should export it as MODE=SSB, SUBMODE=LSB.?
With the new HELL modes, unfortunately there is no legacy mode to deprecate.?
The Mode change is still occasionally raises its head in the ADIF discussion forum. Most users want to see a single QSO field 'Mode'. And to that extent all SUBMODE values are unique as a 'recommended
' enumeration list. Any app can maintain a single field in its internal database as long as it gets exported as two fields.
It's a can of worms. For my logging app I accept both strict and deprecated values for the mode. And export strict.?
73 Phil GM3ZZA
On 13 November 2024, at 17:35, "Barry, PC1K via?"?<barry@...>?wrote:
Unfortunately just lost my Apple silicon mac last week.
>?but this change was forced upon us by the current ADIF
I know, because I started the discussion, my aim was to make logging more consistent. Before the change I have seen a FSKH105 QSO logged as HELL, FSKH105 and FSKHELL, this causes confirmations not
to happen. In addition LoTW refuses to log FSKH105 (sometimes) as it is not ADIF compliant. This is being worked on in the next ADIF release.
When I look at the ADIF specification, it does not say one can use a submode in the mode field, this is how fldigi implemented it before, and funny enough is also what??does:
Exports as follows:
QRZLogbook download for pc1k
??? Date: Wed Nov 13 17:22:32 2024
??? Bookid: 354929
??? Records: 1
??? <ADIF_VER:5>3.1.1
????<PROGRAMID:10>QRZLogbook
????<PROGRAMVERSION:3>2.0
??? <eoh>
<time_on:4>1721
<my_lon:11>E004 12.400
<eqsl_qsl_sent:1>N
<app_qrzlog_status:1>N
...
<my_lat:11>N052 03.700
<cqz:2>14
<qso_date:8>20241113
<cont:2>EU
<freq:7>7.07498
<tx_pwr:2>20
<lotw_qsl_rcvd:1>N
<mode:7>FSKHELL?????? <- it is not ADIF compliant
<qsl_rcvd:1>N
<app_qrzlog_logid:10>1177766696
<dxcc:3>263
...
<band_rx:3>40m
<eor>
I wonder why submode was added to the ADIF standard??
A good fix for fldigi IMHO would be to also have submode in the logbook.adi and preferably in the UI. So I can still know if a QSO was made in FELD HELL or FSKHELL, because these modes have different
characteristics. I don't need the submode to reflect in?, even though that would be nice. This we did not discuss before implementing
the change in fldigi 4.2.06.
?
Maybe I made everything worse by starting the discussion, if the submode field is not implemented in many applications. In any case thanks for your help, fldigi is great!
73 de PC1K
?
?
On 13-11-2024 17:12, Dave, W1HKJ wrote:
I will look again at the code, but this change was forced upon us by the current ADIF specification.
David
On 11/12/24 22:08, Barry, PC1K via??wrote:
Hello,?
Today I got around to testing fldigi 4.2.06, specifically:?
With this patch, when I log a QSO in FSKH105, fldigi logs HELL in the mode field, which is correct.?
However the submode field, is not in logbook.adi, nor do I see it anywhere else in the UI. This means that all Hell contacts will be logged as HELL regardless of submode. Is there a way to configure fldigi so that it stores the submode to logbook.adi and preferably
show the submode in the UI??
Thanks, Barry?
?
|
Re: Question about fldigi submode logging / testing feedback on fldigi 4.2.06
Thanks, Gary.
?
I grabbed the zip file, decompressed it, moved it to the Applications folder, then launched it (FLRIG was already running).? It asked me if I was OK with it accessing the microphone and I said yes.? Within
minutes I was on 20M copying signals.? Since then I have shut down the program and FLRIG, power cycled the Mini, and brought it back up again with no issues, including not having to answer the microphone question.? Excellent!
?
Hi, Dave.
?
I¡¯ve only been on with this version of fldigi but so far everything is looking great!? Note that I¡¯m not a power user so I¡¯ll defer to those who are more experienced, but for now all is great!? Thanks.
?
Gary, WA4YMZ
?
?
This is gonna be confusing :)
Gary, all are welcome to use the zip file. Just download, open the zip file and drag it to your applications folder and double click. It should open without additional steps.
toggle quoted message
Show quoted text
On Nov 16, 2024, at 10:09?PM, Gary WA4YMZ via groups.io <wa4ymz@...> wrote:
?
I tried but after receiving the ¡°we couldn¡¯t verify¡± message the only options I had were to cancel out or delete the app.? I think that there may be an issue with my Mac mini since I tried to open the previously
installed and working version that required hoop-jumping (4.2.05.15) using the work around, which was working a few weeks ago, ?but now I just get the Terminal opening and its expected message, but everything hangs after that.? I¡¯m using an M1 Mini running
15.0.1
BTW, if you do decide to bite the bullet and enroll in the Developer program, I¡¯m sure there will be many of us who will gladly chip in to cover the cost.
I clicked on the zip file icon and that took me to your DropBox.? Are you sharing that file with just Dave or with the wider group?? Thanks.
Thank you Gary.? Perhaps it is time for me to fultill the Apple Developer requirements.
David
On 11/13/24 15:23, Gary Rogers, KO3F via??wrote:
Dave, I took the liberty of using my Apple Developer ID to re-sign Fldigi-4.2.06.05.dmg, sending it through the Apple notarization tool and stapling the approval to the app. This should permit MacOS 15 users to open and run the app without
all the extra steps. Its in my dropbox here:?
I¡¯m happy to help with signing and notarizing Fldigi apps for Mac going forward, if desired.
On Nov 13, 2024, at 3:38?PM, Barry, PC1K via??<barry@...>wrote:
Thanks Phil,
Helpful background info, much appreciated!
73 de PC1K
On 13-11-2024 21:14, Philip Rose, GM3ZZA via??wrote:
I joined the ADIF community after the introduction of SUBMODE, version 3 I think. But from some of the discussion, I understand it was an attempt to get a handle on the growing proliferation
of new modes. MODE was an attempt at being limited to modulation technique, and SUBMODE defining the coding.?
So modes like LSB became MODE=SSB, SUBMODE=LSB. And the digital modes similarly. At the time MODE=LSB became deprecated, and allowed to be imported from files created? by unmaintained legacy
apps, but all apps being developed should export it as MODE=SSB, SUBMODE=LSB.?
With the new HELL modes, unfortunately there is no legacy mode to deprecate.?
The Mode change is still occasionally raises its head in the ADIF discussion forum. Most users want to see a single QSO field 'Mode'. And to that extent all SUBMODE values are unique as a 'recommended
' enumeration list. Any app can maintain a single field in its internal database as long as it gets exported as two fields.
It's a can of worms. For my logging app I accept both strict and deprecated values for the mode. And export strict.?
73 Phil GM3ZZA
On 13 November 2024, at 17:35, "Barry, PC1K via?"?<barry@...>?wrote:
Unfortunately just lost my Apple silicon mac last week.
>?but this change was forced upon us by the current ADIF
I know, because I started the discussion, my aim was to make logging more consistent. Before the change I have seen a FSKH105 QSO logged as HELL, FSKH105 and FSKHELL, this causes confirmations not
to happen. In addition LoTW refuses to log FSKH105 (sometimes) as it is not ADIF compliant. This is being worked on in the next ADIF release.
When I look at the ADIF specification, it does not say one can use a submode in the mode field, this is how fldigi implemented it before, and funny enough is also what??does:
Exports as follows:
QRZLogbook download for pc1k
??? Date: Wed Nov 13 17:22:32 2024
??? Bookid: 354929
??? Records: 1
??? <ADIF_VER:5>3.1.1
????<PROGRAMID:10>QRZLogbook
????<PROGRAMVERSION:3>2.0
??? <eoh>
<time_on:4>1721
<my_lon:11>E004 12.400
<eqsl_qsl_sent:1>N
<app_qrzlog_status:1>N
...
<my_lat:11>N052 03.700
<cqz:2>14
<qso_date:8>20241113
<cont:2>EU
<freq:7>7.07498
<tx_pwr:2>20
<lotw_qsl_rcvd:1>N
<mode:7>FSKHELL?????? <- it is not ADIF compliant
<qsl_rcvd:1>N
<app_qrzlog_logid:10>1177766696
<dxcc:3>263
...
<band_rx:3>40m
<eor>
I wonder why submode was added to the ADIF standard??
A good fix for fldigi IMHO would be to also have submode in the logbook.adi and preferably in the UI. So I can still know if a QSO was made in FELD HELL or FSKHELL, because these modes have different
characteristics. I don't need the submode to reflect in?, even though that would be nice. This we did not discuss before implementing
the change in fldigi 4.2.06.
?
Maybe I made everything worse by starting the discussion, if the submode field is not implemented in many applications. In any case thanks for your help, fldigi is great!
73 de PC1K
?
?
On 13-11-2024 17:12, Dave, W1HKJ wrote:
I will look again at the code, but this change was forced upon us by the current ADIF specification.
David
On 11/12/24 22:08, Barry, PC1K via??wrote:
Hello,?
Today I got around to testing fldigi 4.2.06, specifically:?
With this patch, when I log a QSO in FSKH105, fldigi logs HELL in the mode field, which is correct.?
However the submode field, is not in logbook.adi, nor do I see it anywhere else in the UI. This means that all Hell contacts will be logged as HELL regardless of submode. Is there a way to configure fldigi so that it stores the submode to logbook.adi and preferably
show the submode in the UI??
Thanks, Barry?
?
|
Can¡¯t help you with the ChatGPT hallucination thing.
However, the crossover path does not look like a Windows thing.
Also, the path seems to double up on the backlash.
Not sure if that helps any, but thought I¡¯d toss it out there.
Enjoy!
73, Willie N1JBJ
toggle quoted message
Show quoted text
On Nov 17, 2024, at 10:17?AM, Joel Black - W4JBB via groups.io <joel.b.black@...> wrote:
? I may have stated this before (I'm getting older and I'm not sure who I've told what stories ;) ), but my coding experience comes from plugging what I want to do in Google and now ChatGPT.
?
I have both Flrig and Fldigi compiled and working. I also have CrossOver (I already had a sub for my Mac) installed with a few apps in it for which there are no good Linux replacements. What I would like to do is write a script that starts Flrig, Fldigi, and a program from CrossOver called AlertCenter. I have the script written so that it starts Flrig, Fldigi, and CrossOver but it won't start the program I'm trying to start (the program *does* start if I manually start it in CrossOver).
If it helps, here's the final version of script after it not running successfully on previous attempts:
#!/bin/bash
?
flrig &
?
fldigi &
?
CROSSOVER_PATH="/opt/cxoffice/bin/crossover"
?
BOTTLE_NAME="SHARES_AlertCenter"
?
EXE_PATH="C:\\AlertCenter\\AlertCenter.exe"
?
"$CROSSOVER_PATH" run "$BOTTLE_NAME" "$EXE_PATH" &
?
I tried what I do on my Mac - copy the shortcut of the program in CrossOver to a text editor. In macOS, that copies the shortcut; in Linux, it copied the desktop information for the program. If the shortcut is in there, I couldn't decipher it.
?
I also tried to create a script with just the single program and I get the same result - CrossOver starts but the program does not. I can also run the script and, after everything's up and running, I just double-click the program inside the CrossOver window. I can do that but I'd rather have them all start when I run the script.
I have checked my paths and everything seems correct I just cannot make that final step. Am I missing something or cannot I just not do what I've intended to do?
?
Regards,
Joel, W4JBB
?
|
I may have stated this before (I'm getting older and I'm not sure who I've told what stories ;) ), but my coding experience comes from plugging what I want to do in Google and now ChatGPT.
?
I have both Flrig and Fldigi compiled and working. I also have CrossOver (I already had a sub for my Mac) installed with a few apps in it for which there are no good Linux replacements. What I would like to do is write a script that starts Flrig, Fldigi, and a program from CrossOver called AlertCenter. I have the script written so that it starts Flrig, Fldigi, and CrossOver but it won't start the program I'm trying to start (the program *does* start if I manually start it in CrossOver).
If it helps, here's the final version of script after it not running successfully on previous attempts:
#!/bin/bash
?
flrig &
?
fldigi &
?
CROSSOVER_PATH="/opt/cxoffice/bin/crossover"
?
BOTTLE_NAME="SHARES_AlertCenter"
?
EXE_PATH="C:\\AlertCenter\\AlertCenter.exe"
?
"$CROSSOVER_PATH" run "$BOTTLE_NAME" "$EXE_PATH" &
?
I tried what I do on my Mac - copy the shortcut of the program in CrossOver to a text editor. In macOS, that copies the shortcut; in Linux, it copied the desktop information for the program. If the shortcut is in there, I couldn't decipher it.
?
I also tried to create a script with just the single program and I get the same result - CrossOver starts but the program does not. I can also run the script and, after everything's up and running, I just double-click the program inside the CrossOver window. I can do that but I'd rather have them all start when I run the script.
I have checked my paths and everything seems correct I just cannot make that final step. Am I missing something or cannot I just not do what I've intended to do?
?
Regards,
Joel, W4JBB
?
|
Re: flrig 2.0.05 remote xml_client
Hi, I can confirm similar behaviour with a Kenwood TS590S.
?
So, flrig 2.0.05 (compiled from source) server run on MacOS and client run on MacOS.
?
As I click on "init" in client, client crashes with a well known "send report to apple?" dialog.
?
This is the first report. As I have some more time I will investigate further.
?
Best, Filip YU3FMS
|
Re: Linux Recommendation - Work is a RHEL/Windows Shop
Thanks... I think I'll use Mint until I can get more experience under my belt playing around under the hood.
?
Joel - W4JBB
|
Re: Question about fldigi submode logging / testing feedback on fldigi 4.2.06
This is gonna be confusing :)
Gary, all are welcome to use the zip file. Just download, open the zip file and drag it to your applications folder and double click. It should open without additional steps.
toggle quoted message
Show quoted text
On Nov 16, 2024, at 10:09?PM, Gary WA4YMZ via groups.io <wa4ymz@...> wrote:
Hi, Dave. ? I tried but after receiving the ¡°we couldn¡¯t verify¡± message the only options I had were to cancel out or delete the app.? I think that there may be an issue with my Mac mini since I tried to open the previously installed and working version that required hoop-jumping (4.2.05.15) using the work around, which was working a few weeks ago, ?but now I just get the Terminal opening and its expected message, but everything hangs after that.? I¡¯m using an M1 Mini running 15.0.1 ? BTW, if you do decide to bite the bullet and enroll in the Developer program, I¡¯m sure there will be many of us who will gladly chip in to cover the cost. ? Hi, Gary. ? I clicked on the zip file icon and that took me to your DropBox.? Are you sharing that file with just Dave or with the wider group?? Thanks. ? Gary Rogers, WA4YMZ ? ? Thank you Gary.? Perhaps it is time for me to fultill the Apple Developer requirements.
David On 11/13/24 15:23, Gary Rogers, KO3F via??wrote: Dave, I took the liberty of using my Apple Developer ID to re-sign Fldigi-4.2.06.05.dmg, sending it through the Apple notarization tool and stapling the approval to the app. This should permit MacOS 15 users to open and run the app without all the extra steps. Its in my dropbox here:? I¡¯m happy to help with signing and notarizing Fldigi apps for Mac going forward, if desired. ? On Nov 13, 2024, at 3:38 ?PM, Barry, PC1K via ??<barry@...>wrote: ? Thanks Phil, Helpful background info, much appreciated! 73 de PC1K On 13-11-2024 21:14, Philip Rose, GM3ZZA via??wrote: I joined the ADIF community after the introduction of SUBMODE, version 3 I think. But from some of the discussion, I understand it was an attempt to get a handle on the growing proliferation of new modes. MODE was an attempt at being limited to modulation technique, and SUBMODE defining the coding.? So modes like LSB became MODE=SSB, SUBMODE=LSB. And the digital modes similarly. At the time MODE=LSB became deprecated, and allowed to be imported from files created? by unmaintained legacy apps, but all apps being developed should export it as MODE=SSB, SUBMODE=LSB.? With the new HELL modes, unfortunately there is no legacy mode to deprecate.? The Mode change is still occasionally raises its head in the ADIF discussion forum. Most users want to see a single QSO field 'Mode'. And to that extent all SUBMODE values are unique as a 'recommended ' enumeration list. Any app can maintain a single field in its internal database as long as it gets exported as two fields. It's a can of worms. For my logging app I accept both strict and deprecated values for the mode. And export strict.? 73 Phil GM3ZZA
On 13 November 2024, at 17:35, "Barry, PC1K via?"?<barry@...>?wrote:
Unfortunately just lost my Apple silicon mac last week. >?but this change was forced upon us by the current ADIF I know, because I started the discussion, my aim was to make logging more consistent. Before the change I have seen a FSKH105 QSO logged as HELL, FSKH105 and FSKHELL, this causes confirmations not to happen. In addition LoTW refuses to log FSKH105 (sometimes) as it is not ADIF compliant. This is being worked on in the next ADIF release. When I look at the ADIF specification, it does not say one can use a submode in the mode field, this is how fldigi implemented it before, and funny enough is also what??does:
Exports as follows:
QRZLogbook download for pc1k
??? Date: Wed Nov 13 17:22:32 2024
??? Bookid: 354929
??? Records: 1
??? <ADIF_VER:5>3.1.1
????<PROGRAMID:10>QRZLogbook
????<PROGRAMVERSION:3>2.0
??? <eoh>
<time_on:4>1721
<my_lon:11>E004 12.400
<eqsl_qsl_sent:1>N
<app_qrzlog_status:1>N
...
<my_lat:11>N052 03.700
<cqz:2>14
<qso_date:8>20241113
<cont:2>EU
<freq:7>7.07498
<tx_pwr:2>20
<lotw_qsl_rcvd:1>N
<mode:7>FSKHELL?????? <- it is not ADIF compliant
<qsl_rcvd:1>N
<app_qrzlog_logid:10>1177766696
<dxcc:3>263
...
<band_rx:3>40m
<eor>
I wonder why submode was added to the ADIF standard?? A good fix for fldigi IMHO would be to also have submode in the logbook.adi and preferably in the UI. So I can still know if a QSO was made in FELD HELL or FSKHELL, because these modes have different characteristics. I don't need the submode to reflect in?, even though that would be nice. This we did not discuss before implementing the change in fldigi 4.2.06. ? Maybe I made everything worse by starting the discussion, if the submode field is not implemented in many applications. In any case thanks for your help, fldigi is great! 73 de PC1K ? ? On 13-11-2024 17:12, Dave, W1HKJ wrote: I will look again at the code, but this change was forced upon us by the current ADIF specification.
David On 11/12/24 22:08, Barry, PC1K via??wrote: Hello,?
Today I got around to testing fldigi 4.2.06, specifically:?
With this patch, when I log a QSO in FSKH105, fldigi logs HELL in the mode field, which is correct.?
However the submode field, is not in logbook.adi, nor do I see it anywhere else in the UI. This means that all Hell contacts will be logged as HELL regardless of submode. Is there a way to configure fldigi so that it stores the submode to logbook.adi and preferably show the submode in the UI??
Thanks, Barry?
?
?
?
|
FLRIG 2.x not usable on my new Mac mini M4 with my Yaesu FT-991A
Good morning (German time).
?
I know that this problem is not new and I found several posts here from the past.
But I could not find any real solution.
?
What I can say is that 1.4.7 works fine and 1.4.8 and up does not.?
If I try to start one of them then all I get is the "spinning ball" and after some time macOS asks me to kill the app.
?
I tried to remove the .flrig directory to see if it helps to start new, but it makes no difference.
?
?I am happy that 1.4.7 works, but of course ... you know ...
?
73,
Peter
?
|
Re: Question about fldigi submode logging / testing feedback on fldigi 4.2.06
Hi, Dave.
?
I tried but after receiving the ¡°we couldn¡¯t verify¡± message the only options I had were to cancel out or delete the app.? I think that there may be an issue with my Mac mini since I tried to open the previously
installed and working version that required hoop-jumping (4.2.05.15) using the work around, which was working a few weeks ago, ?but now I just get the Terminal opening and its expected message, but everything hangs after that.? I¡¯m using an M1 Mini running
15.0.1
?
BTW, if you do decide to bite the bullet and enroll in the Developer program, I¡¯m sure there will be many of us who will gladly chip in to cover the cost.
?
Hi, Gary.
?
I clicked on the zip file icon and that took me to your DropBox.? Are you sharing that file with just Dave or with the wider group?? Thanks.
?
Gary Rogers, WA4YMZ
?
?
Thank you Gary.? Perhaps it is time for me to fultill the Apple Developer requirements.
David
toggle quoted message
Show quoted text
On 11/13/24 15:23, Gary Rogers, KO3F via groups.io wrote:
Dave, I took the liberty of using my Apple Developer ID to re-sign Fldigi-4.2.06.05.dmg, sending it through the Apple notarization tool and stapling the approval to the app. This should permit MacOS 15 users to open and run the app without
all the extra steps. Its in my dropbox here:
I¡¯m happy to help with signing and notarizing Fldigi apps for Mac going forward, if desired.
?
On Nov 13, 2024, at 3:38?PM, Barry, PC1K via groups.io
<barry@...> wrote:
?
Thanks Phil,
Helpful background info, much appreciated!
73 de PC1K
On 13-11-2024 21:14, Philip Rose, GM3ZZA via??wrote:
I joined the ADIF community after the introduction of SUBMODE, version 3 I think. But from some of the discussion, I understand it was an attempt to get a handle on the growing proliferation
of new modes. MODE was an attempt at being limited to modulation technique, and SUBMODE defining the coding.?
So modes like LSB became MODE=SSB, SUBMODE=LSB. And the digital modes similarly. At the time MODE=LSB became deprecated, and allowed to be imported from files created? by unmaintained legacy
apps, but all apps being developed should export it as MODE=SSB, SUBMODE=LSB.?
With the new HELL modes, unfortunately there is no legacy mode to deprecate.?
The Mode change is still occasionally raises its head in the ADIF discussion forum. Most users want to see a single QSO field 'Mode'. And to that extent all SUBMODE values are unique as a 'recommended
' enumeration list. Any app can maintain a single field in its internal database as long as it gets exported as two fields.
It's a can of worms. For my logging app I accept both strict and deprecated values for the mode. And export strict.?
73 Phil GM3ZZA
On 13 November 2024, at 17:35, "Barry, PC1K via?"?<barry@...>?wrote:
Unfortunately just lost my Apple silicon mac last week.
>?but this change was forced upon us by the current ADIF
I know, because I started the discussion, my aim was to make logging more consistent. Before the change I have seen a FSKH105 QSO logged as HELL, FSKH105 and FSKHELL, this causes confirmations not
to happen. In addition LoTW refuses to log FSKH105 (sometimes) as it is not ADIF compliant. This is being worked on in the next ADIF release.
When I look at the ADIF specification, it does not say one can use a submode in the mode field, this is how fldigi implemented it before, and funny enough is also what??does:
Exports as follows:
QRZLogbook download for pc1k
??? Date: Wed Nov 13 17:22:32 2024
??? Bookid: 354929
??? Records: 1
??? <ADIF_VER:5>3.1.1
????<PROGRAMID:10>QRZLogbook
????<PROGRAMVERSION:3>2.0
??? <eoh>
<time_on:4>1721
<my_lon:11>E004 12.400
<eqsl_qsl_sent:1>N
<app_qrzlog_status:1>N
...
<my_lat:11>N052 03.700
<cqz:2>14
<qso_date:8>20241113
<cont:2>EU
<freq:7>7.07498
<tx_pwr:2>20
<lotw_qsl_rcvd:1>N
<mode:7>FSKHELL?????? <- it is not ADIF compliant
<qsl_rcvd:1>N
<app_qrzlog_logid:10>1177766696
<dxcc:3>263
...
<band_rx:3>40m
<eor>
I wonder why submode was added to the ADIF standard??
A good fix for fldigi IMHO would be to also have submode in the logbook.adi and preferably in the UI. So I can still know if a QSO was made in FELD HELL or FSKHELL, because these modes have different
characteristics. I don't need the submode to reflect in?, even though that would be nice. This we did not discuss before implementing the change in fldigi 4.2.06.
?
Maybe I made everything worse by starting the discussion, if the submode field is not implemented in many applications. In any case thanks for your help, fldigi is great!
73 de PC1K
?
?
On 13-11-2024 17:12, Dave, W1HKJ wrote:
I will look again at the code, but this change was forced upon us by the current ADIF specification.
David
On 11/12/24 22:08, Barry, PC1K via??wrote:
Hello,?
Today I got around to testing fldigi 4.2.06, specifically:?
With this patch, when I log a QSO in FSKH105, fldigi logs HELL in the mode field, which is correct.?
However the submode field, is not in logbook.adi, nor do I see it anywhere else in the UI. This means that all Hell contacts will be logged as HELL regardless of submode. Is there a way to configure fldigi so that it stores the submode to logbook.adi and preferably
show the submode in the UI??
Thanks, Barry?
?
?
?
|
Re: Linux Recommendation - Work is a RHEL/Windows Shop
At work we ran CentOS 7, and now Rocky. Private cloud, tens of thousands of compute nodes netboot Flatcar Container Linux for K8 workloads, most of the other stuff around it is CentOS/Rocky.
?
If you are an RHEL shop, Rocky or one of the other "RHEL like" flavors might be a good starting point.
?
Otherwise Debian based systems and their derivatives are fairly common in ham radio circles.
?
Debian is my personal preference at home for Linux.
|
Re: DigiRig, flrig, and a Yaesu FT-747GX
Yeah the strangest thing is that I have cat control through JS8Call and WSJT-X working fine?
|
Re: DigiRig, flrig, and a Yaesu FT-747GX
Fair enough.
I could not get the repo download (of flrig) working.? But to test
connectivity, I tried JTDX with my FTdx10 (not Flrig/Flrig -
worked just fine, even though flrig did not (as a standalone).? My
next step was to compile and install flrig (from source - also
fldigi), rebooted, and this seemed to be my solution on the Pi.
JTDX actually confirmed connectivity / CAT operations.? Using the
GUI and command line audio mixers, I was able to access and test
each audio subsystem (I have three ham rigs, and a commercial
mixer .. on USB ports).? Ringing out new installations.
These things can be frustrating - you will get it.
73,
Glenn
On 11/16/24 06:51, Riley Gossling,
KF0QMQ via groups.io wrote:
toggle quoted message
Show quoted text
Thanks for the reply. Yes, I am part of the dialout group. I
did the chmod command also and no change. I don't believe it's a
permission issue since I have this same setup working with other
programs.
|
Re: DigiRig, flrig, and a Yaesu FT-747GX
Thanks for the reply. Yes, I am part of the dialout group. I did the chmod command also and no change. I don't believe it's a permission issue since I have this same setup working with other programs.
|
Re: DigiRig, flrig, and a Yaesu FT-747GX
Riley,
I may have missed it.. but - did you add your login alias to the dialout group?
sudo usermod -a -G dialout $USER = *sudo usermod -a -G dialout gjensen* (my alias being gjensen)
and sudo chmod 666 /dev/ttyUSB1 - must do on all ports that touch ham software (i.e. /dev/ttyUSB5 (CI-V)
?
Went through this just last night - on a Raspberry Pi 5 - accessing the system from a VNC server.
73,
Glenn
WA6BJQ
On 11/15/24 11:25, Riley Gossling,
KF0QMQ via groups.io wrote:
Yes, I believe WSJT-X uses Hamlib.
?
Getting flrig to work is what I'm trying to do. I cannot get
it to communicate with my radio.
|
Re: DigiRig, flrig, and a Yaesu FT-747GX
Thank you for taking the time to help me troubleshoot this. I see other people seem to have had luck with the digirig and flrig, so I am going to continue trying to figure it out.
|
Re: DigiRig, flrig, and a Yaesu FT-747GX
Is it possible that this cable works fine with software using hamlib but not flrig? I would have thought if it worked for one it would work for the other.
?
I have not had the change to try another computer.
|
Re: DigiRig, flrig, and a Yaesu FT-747GX
whether I use /dev/ttyUSB0 for /dev/serial/by-id/... I get the same results. One thing I meant to mention is that when I click init the audio on my radio stops for a split second and I see the "CAT" symbol on the radio come on for about a second then turn back off.
|
Re: DigiRig, flrig, and a Yaesu FT-747GX
I would like to note that selecting /dev/ttyUSB0 results in the same issue.
|
Re: DigiRig, flrig, and a Yaesu FT-747GX
I've attached debug_log and trace here. The output of that command is:
?
[ 1479.789733] usb 1-5.1: SerialNumber: 0e2a0f816687ed11965525d7a603910e ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
[ 1479.796135] cp210x 1-5.1:1.0: cp210x converter detected ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
[ 1479.798963] usb 1-5.1: cp210x converter now attached to ttyUSB0 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
[ 1479.875170] usb 1-5.2: new full-speed USB device number 10 using xhci_hcd ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
[ 1479.966047] usb 1-5.2: New USB device found, idVendor=0d8c, idProduct=0012, bcdDevice= 1.00 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
[ 1479.966079] usb 1-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
[ 1479.966094] usb 1-5.2: Product: USB Audio Device ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
[ 1479.966106] usb 1-5.2: Manufacturer: C-Media Electronics Inc. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
[ 1479.990453] input: C-Media Electronics Inc. USB Audio Device as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.2/1-5.2:1.3/0003:0D8C:0012.0003/input/input14 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
[ 1480.042983] hid-generic 0003:0D8C:0012.0003: input,hidraw0: USB HID v1.00 Device [C-Media Electronics Inc. USB Audio Device] on usb-0000:00:14.0-5.2/input3 ? ? ?
|
Re: DigiRig, flrig, and a Yaesu FT-747GX
Well I have installed 2.0.05.81 and mimic'd you settings exactly, with no luck. Not sure if it helps, but this is the trace when I click init:
?
04:07:47.433 : closeRig()
04:07:47.434 : close serial port
04:07:47.434 : ClosePort(): fd = 14
04:07:47.439 : serial port closed
04:07:47.439 : clear frequency list
04:07:47.440 : initialize title bar
04:07:47.440 : start tranceiver serial port
04:07:47.442 : /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_0e2a0f816687ed11965525d7a603910e-if00-port0 opened: fd = 14
04:07:47.447 : D: startXcvrSerial:?
Serial port:
? ? Port ? ? : /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_0e2a0f816687ed11965525d7a603910e-if00-port0
? ? Baud ? ? : 4
? ? Stopbits : 2
? ? Retries ?: 2
? ? Timeout ?: 50
? ? Loop ? ? : 250
? ? RTSCTS ? : 0
? ? CATptt ? : 0
? ? RTSptt ? : 0
? ? DTRptt ? : 0
? ? RTS+ ? ? : 0
? ? DTR+ ? ? : 0
04:07:47.448 : initialize transceiver
04:07:47.449 : selrig->initialize()
04:07:47.449 : init_rig()
04:07:47.449 : selrig->check()
04:07:47.449 : get info S: ? ?R: ?
04:07:47.449 : WriteBuffer: ?00 00 00 00 10
04:07:47.602 : ReadBuffer [51.143000 msec]:?
04:07:47.604 : S: ?00 00 00 00 10 ?R: ?
04:07:47.604 : FAILED
|
Gary WA4YMZ
Joel Black - W4JBB
Glenn Jensen, WA6BJQ