[wsjt-devel] 2.6.0-GA BandAct column colored background
When I started using WSJT-X 2.6.0-GA, I checked the Settings, General tab "Start new decode periods at top" checkbox. After functioning as it should for many hours, I experienced an anomaly. The *background color* of all decoded lines in the Band Activity column became *RED* for all 15 second decode sequences that followed. The red background issue continued until I right clicked on the column and selected "Erase". This action cleared the problem. The following day the same thing occurred, but the background color now was YELLOW. Erasing all data in the column again corrected the anomaly. Other than this infrequent issue, WSJT-X version 2.6.0-GA is working fine. Since the newly improved decoding code was added to JT9.exe, I have noticed a larger number of decodes per fifteen second FT8 period. I use deep decode with Ap enabled. On packed 20, 15 and 20M bands Saturday morning, with loads of Europeans on the air, I am consistently decoding between 50 and 60 decodes per sequence, over 200 lines per minute. I often see 3 to 7 decodes, all marked with "a7" on the far right side of the line. on what appears to be a 4th pass to decode the most current WAV file. So far, I'm very happy with the performance of WSJT-X version 2.6.0 . 73, Rich - K1HTV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] 2.6.0-rc5 "Start new decode at top" anomaly
Reino, Thanks for the info. I had been using the scrolling method. I was getting annoyed at double clicking on a station in the Band Activity column, only to have additional decodes push up the list, resulting in a different station to be selected, so I gave the "Start decode at top" option a try. The right-click, erase in the Band Activity column is easy and solves the problem. After 64 years in this great hobby, I'm still having fun chasing and working DX. Running 75 Watts, my FT8 DXCC total stands at 285 countries. Take care and thanks for your contributions answering questions of WSJT-X users. My main focus now is helping blind Hams around the world get on the air using FT8, FT4 & MSK144 using a program called QLog, created by Sam, W2JDB. You can read about it on my and Sam's QRZ page. Thanks again for your help. 73, Rich - K1HTV www.qrz.com/db/K1HTV = = = Hi Rich, This is a long known problem and no solution in the program found. You may erase the band activity window at regular intervals and it continues fine or restore operation. You may erase both displays with the Erase button or click in the Band activity window and select Erase from the drop down list.73, Reino OH3mA From: Richard V Zwirko via wsjt-devel [mailto:wsjt-...@li...] Sent: 1. joulukuutata 2022 18:52 To: WSJT-X Development Group Cc: Richard V Zwirko Subject: [wsjt-devel] 2.6.0-rc5 "Start new period at top" anomaly Using the new WSJT-X Version 2.6.0-rc5, with the Settings, General tab, "Start new period decodes at top" checkbox checked, as expected, the display of decoded FT8 spots started fine. Each decoding cycle displayed properly from the top down. However, within an hour, the top-down display of spots stopped. When I scrolled back, the spots from the just decoded cycle were there. I unchecked the "Start new period decodes at top" checkbox and then checked OK. After a few decode periods with decodes being appended to the bottom of the last decodes, I rechecked the checkbox, but as soon as the next decode cycle was decoded, no spots were displayed. Again, the decodes could be seen by scrolling back the Activity column data. The only way to get WSJT-X to display decodes again from the top down was to restart 2.6.0-rc5. After about another hour of displaying properly, as I started to compose this report, the top-down non-display problem developed again. Only a restart of 2.6.0-rc5 would get the "Start new decodes at the top" working again. 73, Rich - K1HTV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] 2.6.0-rc5 "Start new period at top" anomaly
Using the new WSJT-X Version 2.6.0-rc5, with the Settings, General tab, "Start new period decodes at top" checkbox checked, as expected, the display of decoded FT8 spots started fine. Each decoding cycle displayed properly from the top down. However, within an hour, the top-down display of spots stopped. When I scrolled back, the spots from the just decoded cycle were there. I unchecked the "Start new period decodes at top" checkbox and then checked OK. After a few decode periods with decodes being appended to the bottom of the last decodes, I rechecked the checkbox, but as soon as the next decode cycle was decoded, no spots were displayed. Again, the decodes could be seen by scrolling back the Activity column data. The only way to get WSJT-X to display decodes again from the top down was to restart 2.6.0-rc5. After about another hour of displaying properly, as I started to compose this report, the top-down non-display problem developed again. Only a restart of 2.6.0-rc5 would get the "Start new decodes at the top" working again. 73, Rich - K1HTV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Multiple 2.6.0-rc4 Hound bugs
wsjt-devel@lists.sourceforge.net *Multiple 2.6.0-rc4 Hound bugs* In the past few days, on two different occasions, while working ZL7/K5WE, I experienced a number of anomalies in the Hound mode. I was using WSJT-X version 2.6.0-rc4 in the FT8 mode with the "H" Hound button active (Red background). While on 18.091 MHz, after transmitting a number of Tx1 messages of "ZL7/K5WE K1HTV FM18" the Fox answered me, sending calls and reports at 21:22:15. That's when I noticed what appeared to be the first bug.* Instead of WSJT-X moving my Tx tone frequency to the Fox's transmit frequency, it remained higher in the band at 1736 Hz. *. My first thought was that the DX station may be using a WSJT-X clone. At 21:22:45 the 2nd bug was experienced. When I received the Fox's Tx2 message of calls and a dB report,* instead of WSJT-X auto sequencing and switching to my Tx3 message of calls and R-Report, I continued to send the Tx1 message of calls and grid.* By the time I noticed this bug, 6 seconds had passed and at 21:22:51 I manually switched to my Tx3 message of calls and R-Report. The ZL7 didn't copy my truncated, short message, so my Tx3 message was transmitted again at 21:23:15. Here is the captured data from the "Rx Frequency" column. 212215 Tx 1736 ~ K1HTV FM18 212230 -2 0.3 373 ~ K1HTV -14 212245 Tx 1740 ~ K1HTV FM18 212251 Tx 1740 ~ K1HTV R-15 212300 -1 0.3 373 ~ ZL7/K5WE RR73 Chatham Is. 212300 2 0.3 313 ~ K1HTV -14 212315 Tx 1740 ~ K1HTV R-15 212330 3 0.3 374 ~ CX7BBR -19 212330 7 0.3 314 ~ ZL7/K5WE RR73 Chatham Is. 212400 -3 0.3 373 ~ ZL7/K5WE RR73 Chatham Is. When I received the RR73 message at 21:23:30, the third bug occurred. *Instead of the red "Enable Tx" going gray, my transmissions continued and my Tx3 message was resent to the Fox.* I had to manually click the "Halt Tx" button. Finally, a 4th bug occurred. *After receiving the RR73 message from the Fox, the WSJT-X "Log QSO" screen did not pop up.* I had to manually click the "Log QSO" button and hit Enter to log the QSO. I verified that the settings "Prompt me to log QSO" checkbox was checked. This same problem had occurred the day before when I worked ZL7/K5WE on FT8 20 Meters. I wonder if anyone else has experienced these anomalies with 2.6.0-rc4? 73, Rich - K1HTV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Watchdog timer for F/H?
If you chase DXpeditions using the Fox/Hound mode, you are probably aware that you need to toggle the Tx Enable button Off and then On before the 90 second timeout period. If you don't, after 90 seconds the Tx Enable turns off and you stop transmitting. Many, if not most of us, have been caught by the timeout timer before we could reset it. When set up as a Hound F/H, how about converting the WatchDog timer in the lower right corner of the WSJT-X main screen to a 90 second countdown timer? The WD timer is of no use when running as a Hound. If this suggestion can be implemented in a future version of WSJT-X, how about being able to reset the 90 second timer by clicking on the WD box? And to really be helpful, how about sending a series of beeps to the default sound card speaker for the last 5 or 10 seconds of the 90 second timeout period. Comments? 73, Rich - K!HTV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Tx4 response anomaly
I noticed an anomaly in WSJT-X Version 2.3.0-rc1. I believe that It may have been reported in earlier versions, but the anomaly still occurs. Near the end of an FT8 QSO the station being worked sends his Tx4 report of calls and RR73. On my end, WSJT-X responds with a Tx5 message of 'Calls and 73'. However, the other station, not copying my 73, resends his Tx4, RR73 message. Since my Enable Tx is now off, in order to for me to respond to his Tx4 message with another Tx5 ‘Calls and 73’ message, I double click on the stations ‘calls & RR73’ message from him in either the 'Rx Frequency' or 'Band Activity' columns. The problem is that instead of me transmitting the proper Tx5 ‘73’ message, WSJT-X sends a Tx3 message of Calls plus R-report. Is there any reason why WSJT-X cannot be changed to respond with the proper Tx5 message when the operator double clicks on the received Tx4 message? 73, Rich – K1HTV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
