Keyboard Shortcuts
Likes
- Linuxham
- Messages
Search
flrig color configuration
¿ªÔÆÌåÓýI am working on the color / scheme selection dialogs for flrig.? The result will no doubt pass the Abe Lincoln test, "You can please some of the people..."This dark scheme will be possible with the changes: 73, David, W1HKJ |
||||||||||||||||||||||||||||||||||||||||||
Re: [winfldigi] Fldigi "not working" with QMX - two issues solved
Cliff, AE5ZA
¿ªÔÆÌåÓýBob,Interesting suggestions. I've been using a QDX for some time and it does pretty much all the modes it should do with little config changes. Rise/Fall - 80/60, Min. Samples 180, TX Shift - 0. Tried your suggestions on the QMX and no go. The Audio processing was changed in item #12 in QMX Firmware update 007. From then on it was broken except for a few modes like Thor as Dave indicated by his testing. The new 018 firmware didn't change anything for digital modes including unable to use TxID without it killing TX after the ID. 73, Cliff, AE5ZA
|
||||||||||||||||||||||||||||||||||||||||||
Re: [winfldigi] Fldigi "not working" with QMX - two issues solved
¿ªÔÆÌåÓýHi Dave, more to help with your testing rather than the L-R issue. The TX "failure" for such MFSK audio as
Olivia/Contestia/Thor/MFSK/Domino/IKFP/FSQ/RSID is "fixed" by
reducing the QDX (and I assume QMX) minimum samples from the 480
default to something like 120-180. I also reduce the rise/fall
times (2/40) to stop the raise cosine PTT inhibit, otherwise the
TX chops on and off. FM picture sub modes are generally not pretty
with random like line shifts. Minimum samples at 120 is however not low enough for Thor 56 or faster/wider. I have a series of command buttons on flrig to change this and the audio level as needed. The TX audio still sounds a little ragged, but I have had some
successful Olivia 8/250 QSO's VK>EU. One day I'll do some SDR
s/n threshold testing to see of there is any decode degradation. Cheers Bob VK2YQA
On 16/5/24 23:38, Dave, W1HKJ wrote:
|
||||||||||||||||||||||||||||||||||||||||||
Re: [winfldigi] Fldigi "not working" with QMX - two issues solved
¿ªÔÆÌåÓýWell, that is bad news.? Installed 1.00.018 and just started to test when the QMX went up in smoke.? Literally !! Stinks !!? I now have one available for parts.? Anyone want one for the price of the postage?David On 5/16/24 11:09, Dave wrote:
Board revision V1, firmware 1.00.017. |
||||||||||||||||||||||||||||||||||||||||||
Re: Next version FLdigi
¿ªÔÆÌåÓýWould be simple to export the fldigi NOTES field as COMMENT field.? Or external program could perform the field renaming.David On 5/16/24 10:06, Vladimir, RW6AVK
wrote:
Good day David. |
||||||||||||||||||||||||||||||||||||||||||
Re: Next version FLdigi
¿ªÔÆÌåÓýNOTES is an available field for export// These ADIF fields are not in the fldigi QSO database /* ??????? {COMMENT,????? 256,?? "COMMENT",????? NULL},??????????????? // comment field for QSO ??????? {ADDRESS,????? 256,?? "ADDRESS",????? NULL},??????????????? // contacted stations mailing ad dress ??????? {PFX,????????? 20,??? "PFX",????????? NULL},??????????????? // WPA prefix ??????? {PROP_MODE,??? 100,?? "PROP_MODE",??? NULL},??????????????? // propogation mode ??????? {QSL_MSG,????? 256,?? "QSL_MSG",????? NULL},??????????????? // personal message to appear on ?qsl card ??????? {QSL_RCVD,???? 4,???? "QSL_RCVD",???? NULL},??????????????? // QSL received status ??????? {QSL_SENT,???? 4,???? "QSL_SENT",???? NULL},??????????????? // QSL sent status ??????? {QSL_VIA,????? 20,??? "QSL_VIA",????? NULL},??????????????? // QSL via this person ??????? {RX_PWR,?????? 8,???? "RX_PWR",?????? NULL},??????????????? // power of other station in watts ??????? {SAT_MODE,???? 20,??? "SAT_MODE",???? NULL},??????????????? // satellite mode ??????? {SAT_NAME,???? 20,??? "SAT_NAME",???? NULL},??????????????? // satellite name }; David On 5/16/24 10:06, Vladimir, RW6AVK
wrote:
Good day David. |
||||||||||||||||||||||||||||||||||||||||||
Re: flrig 2.0.05.50 development release posted at
Hi again.
Re:- flrig 2.0.05.50 development release posted Built with no errors/warnings on LMDE 5, 64 bit.? (Mint without the Ubuntu Influence.) There is still a problem with the additional buttons, but this version does eventually return control to the user, but it takes some 10 to 15 seconds to regain control after clicking (or right clicking) on one of those buttons "That actually do something"... "Empty" buttons, (nothing specified to send to the radio) return control to the user almost instantly. Ver 2.0.05.05 did not have this issue. 73. Dave G0WBX. -- Created on and sent from a Unix like PC running and using free and open source software: |
||||||||||||||||||||||||||||||||||||||||||
Re: [winfldigi] Fldigi "not working" with QMX - two issues solved
¿ªÔÆÌåÓýGood morning Jindra,After receiving your email solutions I put my QMX on line and retested.? My findings are not the same as yours. Issue #1: my QMX expects to receive the audio on the LEFT channel and not the RIGHT channel. The audio drive to the QMX must be of sufficient amplitude for the QMX to detect the audio frequency.? Set the OS audio output to provide maximum drive and then set this control to 0 dB: Testing the QMX into a dummy load and listening and decoding on an FT-710 with flrig/fldigi; the various digital modes behave thuslyL
Any attempt at transmiting a leading RsID signal results in a loss of transmission immediately after the RsID signal. Issue #2:? use flrig with fldigi The "RF" control is simply a gain control for the QMX transceiver.? It provides a very wide range of input signal amplification.? I usually set mine between 80 and 90 depending on the band and antenna in use. 73, David On 5/16/24 02:37, ok4rm wrote:
Issue #1: QMX is in TX mode, but there is no output despite fldigi generating signal |
||||||||||||||||||||||||||||||||||||||||||
flrig 2.0.05.50 development release posted at
¿ªÔÆÌåÓýIndex of /alpha/flrigSee readme.txt for complete list of changes after 2.0.05. See flrig-2.0.05.50.png for view of changes in dialog(s).? Note that user interface changes has been split into system and color dialogs.? Enable tooltips and hover the mouse over various controls on any of the dialogs for control operation hints. Please report discrepancies, hidden features, bugs to this forum. 73, David, W1HKJ |
||||||||||||||||||||||||||||||||||||||||||
Re: #fldigi Exception when closing
#fldigi
I have just tried a reboot of my machine, hoping I may have had some hangover from the TCP/IP connection to my logger. Started flrig and fldigi ONLY and I get the same error.
toggle quoted message
Show quoted text
Phil. On 15/05/2024 15:31, Philip Rose, GM3ZZA via groups.io wrote:
I get an exception when I close fldigi. |
||||||||||||||||||||||||||||||||||||||||||
#fldigi Exception when closing
#fldigi
I get an exception when I close fldigi.
I have my own logging program that I connect fldigi to (Logbook->Connect to Server). If I close fldigi without disconnecting the logger I get the below exception (I also get it if I do disconnect the logger). It is probably something I need to do when fldigi connects to my logger. I actually seem to get the exception whether or not I connect my logger. The command I use to launch fldigi is: PULSE_SINK=alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo.2 PULSE_SOURCE=alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo.2 /usr/local/bin/fldigi --config-dir ~/.ic7300 Thread 12 "fldigi" received signal SIGUSR2, User defined signal 2. [Switching to Thread 0x7f35ee3fe6c0 (LWP 1278591)] __GI___pthread_sigmask (how=1, newmask=<optimized out>, oldmask=0x0) at ./nptl/pthread_sigmask.c:43 43 ./nptl/pthread_sigmask.c: No such file or directory. (gdb) bt #0 __GI___pthread_sigmask (how=1, newmask=<optimized out>, oldmask=0x0) at ./nptl/pthread_sigmask.c:43 #1 0x000055e41b369b94 in n3fjp_loop(void*) (args=<optimized out>) at logbook/n3fjp_logger.cxx:2769 #2 0x00007f35f06a8134 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442 #3 0x00007f35f07287dc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 (gdb) The stack notes from fldigi:* Stack trace: /usr/local/bin/fldigi(+0x3a83f4)[0x560cc47f43f4] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e1a)[0x7faf3c8a8e1a] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e85)[0x7faf3c8a8e85] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa90d8)[0x7faf3c8a90d8] /lib/x86_64-linux-gnu/libstdc++.so.6(_ZSt20__throw_length_errorPKc+0x40)[0x7faf3c8a01e9] /usr/local/bin/fldigi(+0x2308cb)[0x560cc467c8cb] /usr/local/bin/fldigi(+0x23b1c5)[0x560cc46871c5] /usr/local/bin/fldigi(+0x5612af)[0x560cc49ad2af] /usr/local/bin/fldigi(+0x4e25e8)[0x560cc492e5e8] /usr/local/bin/fldigi(+0x4e0383)[0x560cc492c383] /usr/local/bin/fldigi(+0x4e02c9)[0x560cc492c2c9] /usr/local/bin/fldigi(+0x596e84)[0x560cc49e2e84] /usr/local/bin/fldigi(+0x5915a2)[0x560cc49dd5a2] /usr/local/bin/fldigi(+0x591625)[0x560cc49dd625] /usr/local/bin/fldigi(+0x5afd29)[0x560cc49fbd29] /usr/local/bin/fldigi(+0x4df3c9)[0x560cc492b3c9] /usr/local/bin/fldigi(+0x4df3ed)[0x560cc492b3ed] /usr/local/bin/fldigi(main+0x1bc4)[0x560cc4555444] /lib/x86_64-linux-gnu/libc.so.6(+0x2724a)[0x7faf3ca4624a] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x7faf3ca46305] /usr/local/bin/fldigi(+0x10ef21)[0x560cc455af21] * Version information: fldigi 4.2.05.16 Copyright (C) 2007-2010 Dave Freese, Stelios Bounanos, and others. License GPLv3+: GNU GPL version 3 or later <>following This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. * Build information: Build information: built : Fri May 3 15:16:59 BST 2024 by philip@chinook on x86_64-pc-linux-gnu for x86_64-pc-linux-gnu configure flags: compiler : gcc version 12.2.0 (Debian 12.2.0-14) compiler flags : -I$(srcdir) -I$(srcdir)/include -I$(srcdir)/irrxml -I$(srcdir)/libtiniconv -I$(srcdir)/fileselector -I$(srcdir)/xmlrpcpp -I$(srcdir)/mbedtls -pthread -I/usr/local/include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_THREAD_SAFE -D_REENTRfollowingANT -I/usr/include/opus -I/usr/include/x86_64-linux-gnu -D_REENTRANT -I/usr/local/include -I/usr/include/libusb-1.0 -I/usr/include/libpng16 -pipe -Wall -fexceptions -O2 --param=max-vartrack-size=0 -I$(srcdir)/xmlrpcpp --param=max-vartrack-size=0 -DNDEBUG linker flags : -lportaudio -lasound -lm -lpthread -L/usr/local/lib -lfltk_images /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so -lfltk -lm -lpthread -lXinerama -lXfixes -lXcursor -L/usr/lib/x86_64-linux-gnu -lpangoxft-1.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lharfbuzz -lfontconfig -lfreetype -lXft -lpangocairo-1.0 -lcairo -lgtk-3 -lgdk-3 -lgio-2.0 -lX11 -lXft -lXrender -lwayland-cursor -lwayland-client -lxkbcommon -ldbus-1 -lfontconfig -ldl -lX11 -lsndfile -lsamplerate -lpulse-simple -lpulse -pthread -L/usr/local/lib -lhamlib -lpng16 -ludev libraries : FLTK 1.4.0 libsamplerate 0.2.2 libsndfile 1.2.0 PortAudio 19 PulseAudio 16.1 Hamlib 4.6~git Runtime information: system : Linux chinook 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64 libraries : libsamplerate-0.2.2 (c) 2002-2008 Erik de Castro Lopo libsndfile-1.2.0 PortAudio V19.6.0-devel, revision 396fe4b6699ae929d3a685b3ef8a7e97396139a4 1246720 Pulseaudio 16.1.0 Hamlib 4.6~git * Stack trace: /usr/local/bin/fldigi(+0x3a83f4)[0x560cc47f43f4] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e1a)[0x7faf3c8a8e1a] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e85)[0x7faf3c8a8e85] /lib/x86_64-linux-gnu/libstdc++.so.6(+0xa90d8)[0x7faf3c8a90d8] /lib/x86_64-linux-gnu/libstdc++.so.6(_ZSt20__throw_length_errorPKc+0x40)[0x7faf3c8a01e9] /usr/local/bin/fldigi(+0x2308cb)[0x560cc467c8cb] /usr/local/bin/fldigi(+0x23b1c5)[0x560cc46871c5] /usr/local/bin/fldigi(+0x5612af)[0x560cc49ad2af] /usr/local/bin/fldigi(+0x4e25e8)[0x560cc492e5e8] /usr/local/bin/fldigi(+0x4e0383)[0x560cc492c383] /usr/local/bin/fldigi(+0x4e02c9)[0x560cc492c2c9] /usr/local/bin/fldigi(+0x596e84)[0x560cc49e2e84] /usr/local/bin/fldigi(+0x5915a2)[0x560cc49dd5a2] /usr/local/bin/fldigi(+0x591625)[0x560cc49dd625] /usr/local/bin/fldigi(+0x5afd29)[0x560cc49fbd29] /usr/local/bin/fldigi(+0x4df3c9)[0x560cc492b3c9] /usr/local/bin/fldigi(+0x4df3ed)[0x560cc492b3ed] /usr/local/bin/fldigi(main+0x1bc4)[0x560cc4555444] /lib/x86_64-linux-gnu/libc.so.6(+0x2724a)[0x7faf3ca4624a] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x7faf3ca46305] /usr/local/bin/fldigi(+0x10ef21)[0x560cc455af21] * Version information: fldigi 4.2.05.16 Copyright (C) 2007-2010 Dave Freese, Stelios Bounanos, and others. License GPLv3+: GNU GPL version 3 or later <> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. * Build information: Build information: built : Fri May 3 15:16:59 BST 2024 by philip@chinook on x86_64-pc-linux-gnu for x86_64-pc-linux-gnu configure flags: compiler : gcc version 12.2.0 (Debian 12.2.0-14) compiler flags : -I$(srcdir) -I$(srcdir)/include -I$(srcdir)/irrxml -I$(srcdir)/libtiniconv -I$(srcdir)/fileselector -I$(srcdir)/xmlrpcpp -I$(srcdir)/mbedtls -pthread -I/usr/local/include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_THREAD_SAFE -D_REENTRANT -I/usr/include/opus -I/usr/include/x86_64-linux-gnu -D_REENTRANT -I/usr/local/include -I/usr/include/libusb-1.0 -I/usr/include/libpng16 -pipe -Wall -fexceptions -O2 --param=max-vartrack-size=0 -I$(srcdir)/xmlrpcpp --param=max-vartrack-size=0 -DNDEBUG linker flags : -lportaudio -lasound -lm -lpthread -L/usr/local/lib -lfltk_images /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so -lfltk -lm -lpthread -lXinerama -lXfixes -lXcursor -L/usr/lib/x86_64-linux-gnu -lpangoxft-1.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lharfbuzz -lfontconfig -lfreetype -lXft -lpangocairo-1.0 -lcairo -lgtk-3 -lgdk-3 -lgio-2.0 -lX11 -lXft -lXrender -lwayland-cursor -lwayland-client -lxkbcommon -ldbus-1 -lfontconfig -ldl -lX11 -lsndfile -lsamplerate -lpulse-simple -lpulse -pthread -L/usr/local/lib -lhamlib -lpng16 -ludev libraries : FLTK 1.4.0 libsamplerate 0.2.2 libsndfile 1.2.0 PortAudio 19 PulseAudio 16.1 Hamlib 4.6~git Runtime information: system : Linux chinook 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64 libraries : libsamplerate-0.2.2 (c) 2002-2008 Erik de Castro Lopo libsndfile-1.2.0 PortAudio V19.6.0-devel, revision 396fe4b6699ae929d3a685b3ef8a7e97396139a4 1246720 Pulseaudio 16.1.0 Hamlib 4.6~git |
||||||||||||||||||||||||||||||||||||||||||
Re: [winfldigi] FLDIGI keeps deleting my log
On Mon, May 13, 2024 at 01:53 PM, Dave, W1HKJ wrote:
Can someone else please verify.Good day David. I've been using the version?fldigi 4.2.05.17?since day one. There were no problems with log. Worked actively from 1 to 10?May, sending via UDP. After Alpha?.17 was not updated - I'm waiting for the release. (Windows-7 x86) |
||||||||||||||||||||||||||||||||||||||||||
Re: [winfldigi] flrig: User Interface settings issues - Tested on 2.0.05.49
¿ªÔÆÌåÓýTim,I find your haughty attitude disengaging.? Let me be a little frank with you.
73, David, W1HKJ
On 5/13/24 20:19, Tim wrote:
|
||||||||||||||||||||||||||||||||||||||||||
Re: [winfldigi] FLDIGI keeps deleting my log
¿ªÔÆÌåÓýI've completed my testing of fldigi 4.2.05.21 and cannot duplicate the reported problem.? The fldigi logbook data file, default:? <fldigi data folder>/logs/logbook.adif *, remains intact whether adding, modifying, or deleting logbook records.Can someone else please verify.? Thank you. latest development release is at * <fldigi data folder> ? on Windows: USER_HOME_FOLDER\fldigi.files ? on Linux & MacOS: USER_HOME_FOLDER/.fldigi 73, David, W1HKJ On 5/13/24 08:03, Dave, W1HKJ wrote:
Thank you for the report.? The UDP log export introduced this bug to the code.? I will look into this immediately. |
||||||||||||||||||||||||||||||||||||||||||
Re: [winfldigi] FLDIGI keeps deleting my log
¿ªÔÆÌåÓýThank you for the report.? The UDP log export introduced this bug to the code.? I will look into this immediately.In the meantime, cease from using the latest fldigi development test version and vall back to version 2.0.5 David On 5/12/24 22:41, Dave Garber wrote:
|
||||||||||||||||||||||||||||||||||||||||||
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. |