¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: Fldigi 4.2.05.20 - Aborting fldigi due to a fatal error.

 

Perfect. Thanks Dave!


Re: flamp v2.2.12

 

Are you a member of the winfldigi? Going to move it there as they allow message posting to a single person.
Robert


Re: flamp v2.2.12

 

Robert:

Cray, not hardly ?. Too much power consumption, just simple Celeron N5105¡¯s for radio work on Linux Mint boxes. The Windows box (not connected to a radio) is an 11th generation i7, pretty mainstream.?


My friend who tested the Alpha versions is also running a vanilla N5105 on Windows.?


I will certainly try the code for either yours or the ¡°flamp-test¡± when available (provided I can remember how to compile it ?).?


de KI4DKS (Tom)


Re: flamp v2.2.12

 

I beginning to think your are running a vic-20 or Cray computer. I'll push the code to SF and provide the git path (command) to download it. Both versions operate correctly on my machine, but not yours (windows) I wondering if we have a race condition. Need to run a few more tests. Note: the Test version runs correctly on MacOSX also.

Robert


Re: Fldigi 4.2.05.20 - Aborting fldigi due to a fatal error.

 

Dave

I dual boot LMDE 6 and Mint 21.3. I have not gotten any fatal errors but fldig does seem to run much better on Mint 21.3.


Bog W7ZDX?

On Fri, May 10, 2024, 09:17 Dave, G?WBX via <g8kbvdave=[email protected]> wrote:
FYI:

Same initial "problem" seen here on LMDE 5 when shutting down Fidigi
that was previously invoked from a command line.? (The Fatal Error
message) using either "File | Exit", or the UI window top right "x" button.

Likewise, I'd seen it in a previous version, but ignored it as the
program was exiting anyway.

The change to line 1647 in fl_digi.cxx has fixed the issue.

Thanks.

Dave G0WBX.


--
Created on and sent from a Unix like PC running and using free and open source software:







--

Bog W7ZDX


Re: Fldigi 4.2.05.20 - Aborting fldigi due to a fatal error.

 

¿ªÔÆÌåÓý

Thank your for the report Dave.

David, W1HKJ

On 5/10/24 11:17, Dave, G?WBX via groups.io wrote:

FYI:

Same initial "problem" seen here on LMDE 5 when shutting down Fidigi that was previously invoked from a command line.? (The Fatal Error message) using either "File | Exit", or the UI window top right "x" button.

Likewise, I'd seen it in a previous version, but ignored it as the program was exiting anyway.

The change to line 1647 in fl_digi.cxx has fixed the issue.

Thanks.

Dave G0WBX.




Re: Fldigi 4.2.05.20 - Aborting fldigi due to a fatal error.

 

FYI:

Same initial "problem" seen here on LMDE 5 when shutting down Fidigi that was previously invoked from a command line.? (The Fatal Error message) using either "File | Exit", or the UI window top right "x" button.

Likewise, I'd seen it in a previous version, but ignored it as the program was exiting anyway.

The change to line 1647 in fl_digi.cxx has fixed the issue.

Thanks.

Dave G0WBX.


--
Created on and sent from a Unix like PC running and using free and open source software:


flrig 2.0.05.48 development test version posted

 

¿ªÔÆÌåÓý

at

Index of /alpha/flrig

Change list since 2.0.5 is very long.? Time to release 2.0.6, so no change requests other than bug fixes please.

Date:?? Fri May 10 07:05:16 2024 -0500

??? G90 read smeter
????? * correct number of read bytes from 8 to 9

Date:?? Thu May 2 07:06:42 2024 -0500

??? ic7610 PBT
????? * correct methods to set/get pbt values
??????? segmentation fault occuring in digi set/get

Date:?? Mon Apr 29 16:20:46 2024 -0500

??? TCP-IP read response
????? * add timeout to loop / wait for response

Date:?? Tue Apr 23 08:48:01 2024 -0500

??? fdm duo
????? * update / cleanup of FDM Duo transceiver class
??????? . correct SWR computation
??????? . move VECTOR initializations to correct method
????? * correct power out scale to 1000 vice 100
????? * add get/set cw_spot_tone

Date:?? Sat Apr 20 07:37:38 2024 -0500

??? 991/A auto start
????? * fix power on sequence

Date:?? Tue Apr 16 15:56:53 2024 -0500

??? Auto Notch Label
????? * change default vector of labels

Date:?? Tue Apr 16 12:36:00 2024 -0500

??? ts570 ptt

Date:?? Fri Apr 19 09:59:19 2024 -0500

??? FT890 status
????? * change read info from 28 to 18 chars
??????? . correct vfo value parsing
????? * add read 5 status bytes
??????? . parse vfo A/B
??????? . parse split
??????? . parse ptt
????? * add read power out

Date:?? Fri Apr 12 07:41:19 2024 -0500

??? Cannot connect logic
????? * retain serial port assignment if transceiver fails to
??????? respond to initialization
????? * improve alert message to provide hint as to probable cause

Date:?? Mon Apr 8 08:30:56 2024 -0500

??? Serial readbuffer
????? * modify Windows ReadBuffer method to more closely match
??????? Linux ReadBuffer method.

Date:?? Sat Apr 6 16:21:36 2024 -0500

??? TS890
????? * Correct errors in mode/bandwidth
????? * Correct get/set split method

Date:?? Tue Apr 23 05:30:23 2024 -0500

??? Mode fast set/get
????? * improved UI display of mode / bw set/get
????? * faster response to xmlrpc request for mode / bw

Date:?? Fri Apr 5 13:43:15 2024 -0500

??? BW fast set/get
????? * improved set/get processing of transceiver bandwidth

Date:?? Fri Apr 5 08:34:41 2024 -0500

??? UI update
????? * set/get/display MODE, BANDWIDTH, FREQ

Date:?? Sun Apr 7 13:55:36 2024 -0500

??? XML label access
????? * change all C style label string arrays to C++ vectors
??????? make both the array and current label value accessible
??????? via XML cmds
????? * XML cmd additions
??????? . get_agc
??????? . incr_agc
??????? . both return post command agc value

Date:?? Wed Apr 3 18:21:52 2024 -0500

??? xml-tcp-serial
????? * fix for grungy tcp-serial drivers.

Date:?? Sat Mar 30 06:45:18 2024 -0500

??? Win32 com port search
????? * improved search for active serial ports.

Date:?? Fri Mar 29 12:20:07 2024 -0500

??? Win32 zusec overflow
????? * 32-bit Windows version is overflowing zusec()
??????? Causing timeouts when timeout is set to 50ms.

Date:?? Sun Mar 24 07:16:12 2024 -0500

??? FT991A
????? * test for valid return strings to queries

Date:?? Fri Mar 29 08:39:00 2024 -0500

??? QMX
????? * add set time

Date:?? Sat Mar 30 13:54:49 2024 -0500

??? Icom transceivers mode change
????? * change to FM bandwidth decode
????? * change to mode/bandwidth/freq display sequence
????? * use set_FILT when selecting FM/FM-D bandwidths
????? * change xmlrpc command rig.set_bandwidth to select
??????? the nearest available bandwidth.? previously selected
??????? the next largest bandwidth
????? * changes effect:
??????? . 7300

Date:?? Wed Mar 13 09:31:29 2024 -0500

??? IC7610 continued
????? * work on following controls:
??????? . squelch
??????? . mode - code for get mode was bogus
??????? . equalize vfoA / vfoB
??????? . CW break in

Date:?? Sun Mar 10 07:20:28 2024 -0500

??? UI tab color
????? * add restore tab color to ui initialization

Date:?? Sun Mar 10 15:13:27 2024 -0500

??? Xml binary client

Date:?? Sat Mar 9 07:31:38 2024 -0600

??? FT747GX
????? * add to list of supported transceiver.

Date:?? Sun Mar 10 05:55:46 2024 -0500

??? Yaesu Auto ON/OFF
????? * auto ON and OFF sequence updates for
??????? . FT450
??????? . FT450D
??????? . FT710

Date:?? Fri Mar 8 03:37:07 2024 -0600

??? tcpip update
????? * Coded TCP/IP access similarly to a serial port.
????? * Successfully tested both the FT-991 and IC-7300.

Date:?? Sun Mar 3 16:05:02 2024 -0600

??? TCPIP connection
????? * change timeout for VSP type connection

Date:?? Mon Feb 19 06:37:00 2024 -0600

??? Yaesu Xcvr RFgain/squelch
????? * code additions contributed by Steve AG7GN <steve.magnuson@...>
????? * added squelch control methods to
??????? . FT991, FT991A
??????? . FT710
??????? . FT2000
????? * added RFgain control methods to
??????? . FT2000

Date:?? Wed Feb 7 06:13:47 2024 -0600

??? Yaesu binary
????? * avoid std::string out-of-bounds assert failure
??????? when testing for icom echo on binary string return from
??????? a non-Icom transceiver

Date:?? Mon Feb 5 21:44:01 2024 -0600

??? FT747 check
????? * change code which checks for presence of FT747

Date:?? Tue Jan 23 04:49:37 2024 -0600

??? IC7610
????? * Fix reported bugs:
??????? . CW break-in management
??????? . Sub receiver, vfo-B, start and end settings
??????? . Copy vfoA to vfoB
??????? . Dual watch

Date:?? Sun Jan 7 21:03:28 2024 -0600

??? LISTSIZE
????? * gee, someone actually wants more than 200 memory spots

Date:?? Sat Jan 6 07:23:48 2024 -0600

??? Geentoo Linux
????? * fix missing header for clang++ compiler.? Removes dependency
??????? on system header heirarchy.

Date:?? Sat Jan 6 06:50:38 2024 -0600

??? TMD710 update
????? * correct get_vfo code
????? * correct reading of the current transceiver mode (AM FM NFM)
????? * correct selection (read and write) of in used vfo A or B
????? * removed forced dual band mode on startup
????? * Notes:
??????? Transceiver has uses hardware controls for both vfo A and B
??????? squelch settings.? Therefore the startup restore of squelch
??????? will not work.? In "Config" -> "Setup" -> "Restore" menu the
??????? "Squelch" should be unchecked.
??????? Changing frequency band is only possible on the transceiver control
??????? panel. There is no corresponding CAT command.

Date:?? Wed Jan 3 05:08:03 2024 -0600

??? memory sort
????? * add ability to sort memory contents by
??????? FREQ, BW, MODE, or COMMENTS
??????? by clicking on sort list header

Date:?? Sun Jan 7 00:51:09 2024 -0600

??? font browser
????? * change FontBrowser class to use std::list vice
??????? C array of structures

Date:?? Fri Jan 5 18:03:14 2024 -0600

??? meterpair structure
????? * define globally as {float; float;}
????? * FT450D
??????? . change to linear conversion

Date:?? Fri Dec 29 15:45:38 2023 -0600

??? Version 2.0.05

73, David, W1HKJ



Re: flamp v2.2.12

 

Robert:

The version I downloaded (either from W1HKJ or Source Forge) is showing a compile date of:

Sunday, 14 April, 2024, 18:25:56 (computer TZ for this box is Eastern)

With a Hash of:

SHA256: c556bcb11db5a4ce80e1484fe7473e022bf38d08a0c031fb0a5ffb24098bd5dc

de KI4DKS (Tom)


Re: flamp v2.2.12

 

Robert:

My normal OS is Linux Mint.
Hash confirms for both files above.

I updated my Win11 machine to fldigi v4.2.05 per your instructions above.

Your version of flamp appears to function correctly with partial relay.
The flamp-test executable runs, but is aborting any partial relay.

Do you happen to have Linux source for your version, so I can test on my radio computers?

de KI4DKS (Tom)


Re: Fldigi 4.2.05.20 - Aborting fldigi due to a fatal error.

 

That works for me, Dave. Thanks.


Re: flamp v2.2.12

 

Just downloaded FLAMP from Source Forge, Issue present.

DE KI4DKS

FLAMP Relay


DE KI4DKS K

go figure.

Turns out the HASH values for my copy of FLAMP 2.2.12 differs from Source Forges version 2.2.12. Something fishy is going on.
Please standby while I'll investigate further.

Robert


Re: flamp v2.2.12

 

Better yet perform a binary compare with my copy to yours, that way you don't have to execute it.
Robert


Re: Fldigi 4.2.05.20 - Aborting fldigi due to a fatal error.

 

¿ªÔÆÌåÓý

Please modify this file: src/dialogs/fl_digi.cxx

line 1647, was "export, "cabrillo",

change to: "export", "cabrillo", "UDP fields",

recompile and test

David

On 5/9/24 11:53, JColes0727 wrote:

My experience running fldigi version 4.2.05.20 on Linux Mint 21.3 (and the terminal error spew) is very similar to yours.

I didn't realize that fldigi was crashing out instead of closing gracefully until I ran it from the command line. After clicking the Close (X) button, it takes 3 seconds for the window to disappear, but that's also true of version 4.2.05, which exits normally. The crash is odd because the program functions as it should as far as I can tell. On exit there should be nothing for the program to do but end its processes and release the resources it was using.


Re: flamp v2.2.12

 

To clarify, is this issue on Linux and Windows?
Robert


Re: flamp v2.2.12

 

Well FUBAR,

DE KI4DKS

FLAMP Relay

<DATA 72 905F>{8F4F:2}L0c3LsDOqjV4P73UNoaMhZztJmI4HPDaEN3x3FU8fB6juA6roP7nPOVtxI7jbXuW
<DATA 72 8873>{8F4F:4}ZcSu58FeOe14+KjYrwfDfxbcGsdIGmW2gNg+OCKRRiWf/8IHNXWdUumuJoBQSUNL
<DATA 72 C15D>{8F4F:6}T8iHmgUBgC7eqwQfLar30h87qpJJudmqOycIB5WTk1M9gzUH4qt6aATjVJnjZ8ot
<CNTL 10 E8C1>{8F4F:EOF}
<CNTL 10 48CD>{8F4F:EOT}

DE KI4DKS K

If the plot gets any thicker I'm not going to be able to swim in it.

Can you right click on flamp.exe file and from this context menu select CRC SHA -> SHA-256 see if you get the same hash value. You might need to use another option for the SHA-256 hash calculation as this context menu might be from the 7zip install on my machine. I done recall if this is the case.

If you compiled your own version the above would likely fail, recompile with optimization turned off and see if the issue persist.

Name: flamp.exe
Size: 2689536 bytes (2626 KiB)
SHA256: ED1257D69C77FFCBAD6154E11176452D55D03F4C241B4C5012CA6F5FFB454E10


We can perform one more option, going to modify the program to output a bunch of data along the function path see what shows up. I'll post here once I hear back from you.

Robert


Re: Fldigi 4.2.05.20 - Aborting fldigi due to a fatal error.

 

My experience running fldigi version 4.2.05.20 on Linux Mint 21.3 (and the terminal error spew) is very similar to yours.

I didn't realize that fldigi was crashing out instead of closing gracefully until I ran it from the command line. After clicking the Close (X) button, it takes 3 seconds for the window to disappear, but that's also true of version 4.2.05, which exits normally. The crash is odd because the program functions as it should as far as I can tell. On exit there should be nothing for the program to do but end its processes and release the resources it was using.


Re: flamp v2.2.12

 

Robert:

Your response reminded me that I have an "ancient" flamp.prefs file as I haven't needed to reconfigure it for a long time.
I deleted it and "forced" a new one.? I see there is at least one new field.
Regardless, the replacement didn't affect anything.

Here is the information requested...

The "screenshot" is what gets Tx'ed.
I have tested any number of individual block relays, singles and multiples (with both spaces and commas as delimiters) with no difference.
Typical modem is MFSK-32, but I have tried others in testing without any change.

I should add that the Windows machines (running an older version of fldigi) is only used for SDR reception and not connected to a radio.? I "tested" them (after updating flamp to v2.2.12) in order to see if it was a Linux issue.

This evening, I recompiled flamp on one of the three Linux boxes (all are connected to a radio) and still get the "aborted" relay.
I seem to recall that previously the "blocks" field used to persist until AFTER the relay was complete before it was cleared (per the configuration setting).? For v2.2.12, it is cleared BEFORE the Tx even starts.

Thanks for your help.

de KI4DKS


Re: G90 cat cntl in Linux #cat-control #digital #g90

 

I followed the instructions.? Everything looked good.? Dialout was previously setup. My device was ttyusb4.? I pressed the "Test CAT" button.? It was unusually slow, but it eventually allowed the "Test PTT" button.? When it was pressed, I got an error.? ?

--
KE0VCD?
ARES
SATERN
CERT


Re: flamp v2.2.12

 

I see you are using 4.02.05 on Linux and .04 on Windows. Should have see that right from the start. FLAMP required FLDIGI 4.02.04.02 or higher for full functionality, try the latest version of FLDIGI see if that corrects the issue. If not please send the above requested data.

Robert