Re: fldigi 4.2.06.07 posted at

开云体育

Notarized versions of Fldigi-4.2.06.07 and Flarq-4.3.9 for MacOS 15 are here:

fldigi 4.2.06.07 posted at

开云体育

Note:
? - added SCAMP mode
? - added additional time scales to fmt mode; 4, 8, 16, 24 and 48 hour

? -? MacOS users on MacOS > 13.x.x will have to ignore the "malicious" software warning during first execution.
???? Should only require a single response to the "use microphone" dialog.

Re: DigiRig, flrig, and a Yaesu FT-747GX

#53656

开云体育

?Turn off all other serial access to the transceiver/digirig before starting and configuraing flrig.? Suggest rebooting the computer before starting flrig.

reboot computer
turn on transceiver
start flrig
configure flrig

start WSJT-X and set up to use "flrig" as the transceiver interface
start JS8Call and configure similar to WSJT-X

The will allow fldigi, JS8Call, and WSJT-X to operate simultaneously, all with transceiver control via flrig.

73, David, W1HKJ

On 11/16/24 09:13, Riley Gossling, KF0QMQ via groups.io wrote:

Show quoted text

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

#53655

Can you explain what that means please?

Show quoted text

On Tue, Nov 19, 2024, 7:21?AM N5VMO Pat via <n5vmo00=[email protected]> wrote:

Remember to do NULL MODEM PIN SWAP on the RS-232 ( DB-9 ) on PINS?2 and 3 SWAP ....... VERY IMPORTANT?on FT-637's =)? ?I know I have one as well ..... bought a NULL MODEM ADAPTOR form mine and leave it on the rig and saves buying a special cable sometimes?hard to find =)

RS-232 configuration in Digirig 1.9

--
73's Pat? N5VMO

Re: DigiRig, flrig, and a Yaesu FT-747GX

#53654

Remember to do NULL MODEM PIN SWAP on the RS-232 ( DB-9 ) on PINS?2 and 3 SWAP ....... VERY IMPORTANT?on FT-637's =)? ?I know I have one as well ..... bought a NULL MODEM ADAPTOR form mine and leave it on the rig and saves buying a special cable sometimes?hard to find =)

Show quoted text

RS-232 configuration in Digirig 1.9

--

73's Pat? N5VMO

Re: DigiRig, flrig, and a Yaesu FT-747GX

#53653

I have not tried that. I would like to exhaust all other options before opening it up and modifying it, since the logic levels selection works fine with other software.

Re: DigiRig, flrig, and a Yaesu FT-747GX

#53650

I believe so, but I can try messing with them again.?

?

I'm using a Digirig with homemade cables.

?

https://forum.digirig.net/t/cable-for-yaesu-ft-747/4282

Re: DigiRig, flrig, and a Yaesu FT-747GX

#53648

A note, the tiny10 installation was on the same computer I had been trying to get working with linux, the windows 11 installation was a different computer.

Re: DigiRig, flrig, and a Yaesu FT-747GX

#53647

Alright I've tried installing the latest flrig software on both tiny10 (a stripped-down version of windows 10) and actual windows 11 and I get the same errors.

?

This leads me to believe the issue is with my Digirig setup, but I know others have used their digirig with flrig and I don't have any issues with WSJT-X or JS8Call.

?

Any other ideas?

Re: Scripting Assistance

#53643

Sorry... I'm trying to write a script that starts a program that was installed in a CrossOver Bottle. I can get the script to start CrossOver but I cannot get the script to start the program that's been installed in the Bottle.

?

Joel, W4JBB

Re: Scripting Assistance

#53642

I dont understand what you're trying to achieve.

flamp not connecting to fldigi

#53641

I'm running a Linux Mint box with fldigi 4.2.06 and flamp 2.2.14. fldigi is set to start flamp, which it does. Regardless of which program starts first, flamp shows NOT CONNECTED status. It's working fine on another system running on a Raspberry Pi 4. I've tried reinstalling and restarting from new flamp config file. Obviously, I'm missing something but have no idea what. Any suggestions appreciated!

Re: Linux Recommendation - Work is a RHEL/Windows Shop

#53640

Mint is just fine.. or Ubuntu as well - I use them both.

It's not a matter of experience per se - it's one of preference.? You can really get under the covers with any distro.

73,

Glenn

WA6BJQ

Show quoted text

On Sun, Nov 17, 2024 at 6:47?AM Joel Black - W4JBB via <joel.b.black=[email protected]> wrote:

Thanks... I think I'll use Mint until I can get more experience under my belt playing around under the hood.

?

Joel - W4JBB

Re: Scripting Assistance

#53639

Sorry, I may have caused some confusion...

?

I am trying to write the scripts on my Linux laptop. I was only giving an example of what I had successfully done on my Mac.

?

Joel, W4JBB

Re: FLRIG 2.x not usable on my new Mac mini M4 with my Yaesu FT-991A

#53638

I have the exact same problem, never found a solution. 1.4.7 works but not 1.4.8 and above. Have compiled the software but with no success - beach ball still keeps spinning.

?

BTW! I have an Intel Mac

Re: Scripting Assistance

#53635

Maybe try using the open command on macOS:

?

open -a /Path/To/Application.app

?

That is how I open macOS applications from shell scripts.

?

Another approach might be Apple Script, which can be exported into a self contained app for convenience. I've had mixed results with Apple Script, probably because I dont have much experience with it.

?

You can also create macOS application bundles with nothing more than a shell script in it, so you have a nice icon to click. It's simply a folder structure, with a couple files in the right places. (That is all application bundles are anyway, the OS makes them appear as a single icon, if you move/drag it somewhere, the whole underlying folder structure and files with-in it are moved).

?

- Lonney

?

On Sun, Nov 17, 2024 at 06:17 AM, Joel Black - W4JBB wrote:

Show quoted text

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?

Re: Scripting Assistance

#53634

ChatGPT is generally pretty good at helping write shell, python, powershell etc. I learned a lot from it by asking for examples of how to do things, then implementing them in my scripts, and sometimes getting it to help me troubleshoot things. I learn best by seeing practical examples.

?

I got ChatGPT to write the Python that I used to process and fix about a year ago. With out it, I would not have gotten anywhere with it. Another good example is the I used in my using the JS8 digi mode, no way in the world I could have written that on my own to that level.

?

Yes this "AI" is not AI, it doesn't comprehend anything, its simply predictive text on steroids which is why it makes stuff up - much like auto correct incorrectly corrects things. At least understand what it is, and what it isn't :-)

?

On Sun, Nov 17, 2024 at 08:56 AM, William Smith, N1JBJ wrote:

Show quoted text

Can’t help you with the ChatGPT hallucination thing.

fldigi manual logging PWR field always 0

#53633

开云体育

Hello All,

When I manually log in fldigi the Pwr field always resets to 0. When I use the button it works normally. See attached video. For now I work-around using

sed -i 's/<TX_PWR:1>0/<TX_PWR:2>20/g' /home/bar/.fldigi/logs/logbook.adif

I am missing something?

73 de PC1K

simplescreenrecorder-2024-10-28_13.33.39.mp4

Re: Question about fldigi submode logging / testing feedback on fldigi 4.2.06

#53632

Circle back to the original topic, after giving it some thought.

If it is too much work to implement submodes in fldigi, I would prefer to revert to the old situation. It is better to log submode FSKH105 as mode. Compared to the current fix, which would log all different HELL modes as HELL.

With the old way, I can script myself out of it, currently:

sed -i 's/FSKH105/FSKHELL/g' /home/bar/.fldigi/logs/logbook.adif

Similar I could sed the mode and submode into the log.

The fix in 4.2.06 would mean manual work to modify the log. As there is no way to determine if a QSO was in Feld Hell or FSKH105.

Remember that FSKH105 is proposed to be added to ADIF, which would mean I do not have to use sed at all. Ignoring submode as mode, which I don't care about too much.

Anyways, my 2 cents.

Show quoted text

On 2024-11-17 18:13, Gary WA4YMZ via groups.io wrote:
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
From: [email protected] <[email protected]> on behalf of Gary Rogers, KO3F via groups.io <cgaryrogers190@...>
Date: Sunday, November 17, 2024 at 4:43?AM
To: [email protected] <[email protected]>
Subject: Re: [linuxham] 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.
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
From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> on behalf of Dave, W1HKJ via groups.io<><w1hkj@...<mailto:w1hkj@...>>
Date: Wednesday, November 13, 2024 at 5:31?PM
To: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>
Subject: Re: [linuxham] Question about fldigi submode logging / testing feedback on fldigi 4.2.06
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 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:
[cid:part1.hWVkIuxB.1KKZGwLO@...]
fldigi-4.2.06.05.zip<>
dropbox.com<>
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@...><mailto:barry@...>wrote:
Thanks Phil,
Helpful background info, much appreciated!
73 de PC1K
On 13-11-2024 21:14, Philip Rose, GM3ZZA via groups.io<> 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 groups.io<>" <barry@...><mailto:barry@...> wrote:
Unfortunately just lost my Apple silicon mac last week.

but this change was forced upon us by the current ADIFI 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 QRZ.com<> does:
[cid:part1.NbzJrSKB.1BzNYTIt@...]
[cid:part2.OvrD5o3j.NKn6Hj8k@...]
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 QRZ.com/LoTW<>, 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 groups.io<> 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