Keyboard Shortcuts
Likes
- Linuxham
- Messages
Search
CTY-3416 Country Files - 13 May 2024
The Country (CTY) Files were updated on 13 May 2024:
For installation instructions, start at: Hover your mouse over the word Contest in the menu, then select the software you are using. To install the file, follow the link to your software at the top of the page. If you are interested in a bigger CTY.DAT for everyday logging, you can get it here: Note that the release notes (and Version Entity) for this larger file are different than what is shown below. There is a separate link to them. As a reminder, there is an RSS feed of the latest country file announcements: Here are the release notes: 13 May 2024 (CTY-3416) VER20240513, Version entity is Central Kiribati, T31 Added/changed Entities/Prefixes/Callsigns: * B7CRA and B9CRA are both China, BY * TO972JO is Martinique, FM * GB0AEL is Northern Ireland, GI * GB0BOA, GB5RB and MM0PLX/P are all Scotland, GM * GB0MFB, GB1SDB and GB8SOS are all Wales, GW * K1LB and N5YJZ are both United States, K in CQ zone 3, ITU zone 6 * KD2DMR, NY9P and WA9FBO are all United States, K in CQ zone 4, ITU zone 7 * KC4YDJ, KI5UXR, KM4IYW, KO4BVP, KO4UMQ, N5VJX, W5BAM, WA2DLN and WB2UBW are all United States, K in CQ zone 4, ITU zone 8 * AA8WZ, K8OSF, K9DY, K9JHR, KB8NXH, KQ6KC, N9FZ and WA6VZN are all United States, K in CQ zone 5, ITU zone 8 * KC5LAF, KO4V and W7CWT are all Hawaii, KH6 * AC9IZ, K1LH, KG5COH and KH6RF are all Alaska, KL * LU2DT/D, LU3EU/D, LU4EV/D, LU5JAH/F, LU5JSB/H, LU7EPT/D, LU7VB/O, LU9DNV/D, LU9JDZ/H and LW3DJC/D are all Argentina, LU * RA9ULL/6, RJ9I/6, UA4FMQ/P and UE79MA are all European Russia, UA * R9XD/9 is Asiatic Russia, UA9 in ITU zone 20 * UA1O/0 is Asiatic Russia, UA9 in CQ zone 19, ITU zone 23 * RL5G/0 is Asiatic Russia, UA9 in CQ zone 19, ITU zone 34 * VK8DNT/4 is Australia, VK in ITU zone 55 * VK2HJ/9 is Norfolk Island, VK9N Removed Entities/Prefixes/Callsigns: * EA1RCI/P in Spain, EA * TO3Z in Guadeloupe, FG * GB0SPD, GB1PAT and GB9SPD in Northern Ireland, GI * GB8FT in Scotland, GM * AB4GG, AD4FL, AI1K, K0FE, K0PLC, K2AMF, K4KSV, K4TNN, K4YO, K5PSN, K6ACV, K8MCN, K8WV, K9KA, K9TWW, KA8VZB, KB4ZFA, KF4TCV, KI4ZRH, KJ4EBE, KO4SKK, N0FIR, N0TR, N2CCG, N7GVV, N7NG, N8JOE, N9JNQ, NY9H, W4YPW, W5EPL, W8HMK, WA4CAX, WB4KUU, WB9WKT, WE4BY, WO0M, WP2C, WR8AA and WX7F in United States, K * KD0VQY and KX4ES in Hawaii, KH6 * AG6PI, KF0EXR, KF7PFN, KI6ZYO, KK6BVH and KK6CAU in Alaska, KL * LU2EE/D, LU7DZV/D and LW6DNF/D in Argentina, LU * PI9TP/J in Netherlands, PA * R24BLIN, R8FF/1, RC9HC/1, RT9K/6 and UA8K/1 in European Russia, UA * R0QAW/9, R2023BA, R4DB/8 and R4FBJ/0/P in Asiatic Russia, UA9 Though I am subscribed to this reflector so that I can make these announcements, I do not see most messages posted to it. If you have any comments or corrections to the country file, please contact me directly. 73 - Jim AD1C -- Jim Reisert AD1C, <jjreisert at alum.mit.edu>, |
Re: flrig 2.0.05.48 development test version posted
Built and working on LMDE 5 64 bit with a real TS-870s as the target.
Seems OK, but there is (like 2.0.05.05) a momentary assertion of the DTR line as the serial port is opened. (I may have omitted to report that, but 2.0.05.05 has been working OK for me for some time now.) I have protection against that (using the radio's TX-Disable feature) but it could key an unprotected radio momentarily if a simple hardware PTT is used, driven from DTR.? (RTS is needed for flow control, and the hardware PTT is "Needed" so the rig will accept TX Audio from the rear accessory port.) However, it crashes and deadlocks the UI when using the companion "Extra Buttons" dialogue, needing a "Kill" from Htop to end. The buttons stay "stuck in" and the entire Flrig UI is frozen.? No excess CPU usage that I can see in that state. The .05 alpha was not a problem. The same happens with the FT736r, also needing Htop to Kill it. Testing .48 alpha with the PCR1000, and all seems well.? Not got an antenna on it at present, but all the controls seem to work, making changes to the background noise as expected. I do not (yet) have any of the extra buttons configured with that RX, so nothing happens when they are pressed.? They also do NOT cause the UI deadlock, so maybe some clash of threads with the other rigs with the serial I/O routines? If you require any specific testing, just give me chapter and verse instructions, and I'll do the tests for you. 73, and thanks for your time and effort etc. Dave G0WBX. -- Created on and sent from a Unix like PC running and using free and open source software: |
Re: #flrig flrig not working with my FT-890 FTDI Programming Cable
#flrig
I tried the new test release flrig-2.0.05.48.
It still works like my previous post. I guess it is still like the last patches you sent. I know you have been busy with fldigi lately. |
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. |