Keyboard Shortcuts
Likes
- Linuxham
- Messages
Search
Re: flamp v2.2.12
Robert:
|
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: --
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: |
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
¿ªÔÆÌåÓýatIndex of /alpha/flrigChange 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 73, David, W1HKJ
|
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.
¿ªÔÆÌåÓýPlease modify this file: src/dialogs/fl_digi.cxxline 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. |
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 FLAMP.prefs
FLAMP.prefs
8F4F_HH-AZ-RR-240430-2000Z-TXID_BAD.k2s
8F4F_HH-AZ-RR-240430-2000Z-TXID_BAD.k2s
![]()
Screenshot 2024-05-08 225912.png
|
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 |