Re: [wsjt-devel] WSJTX Bug - RSTR / RSTS will be logged incorrectly..

is incorrect. Is it > a big could be but that is why there is an op present too make sure it is > correct. > > On Nov 18, 2019 11:19 AM, Dwayne Sinclair wrote: > > > > > > In the above example I am NA6US and I am working XE2JS. At reception of RR73

[wsjt-devel] RTTY

great tool for RTTY. From an implementation perspective it may be possible to run interval and interval less with RTTY with the WSJT-X UI. Regards Dwayne Sinclair NA6US Redondo Beach, CA ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net

[wsjt-devel] WSJT-X on Local and Remote Stations - Nasty Automatic Transmit Enable

I was working WSJT-X F&H mode on both my local (DM03) and remote station (CN95) Both WSJT-X were in Hound mode. Local station was on standby monitoring same band. I started working the Fox from CN95 and when the Fox responded to my callsign, WSJT-X on DM03 automatically Enabled TX and tried to

Re: [wsjt-devel] WSJT-X on Local and Remote Stations - Nasty Automatic Transmit Enable

pen to abuse. -D > On Nov 5, 2021, at 4:13 PM, Bill Somerville via wsjt-devel > wrote: > > On 05/11/2021 22:34, Dwayne Sinclair via wsjt-devel wrote: >> I was working WSJT-X F&H mode on both my local (DM03) and remote station >> (CN95) Both WSJT-X were in Hound

Re: [wsjt-devel] TX..RX with different radios

I have done this a few times just to prove to myself that TX is not an issue - Better receive is where I would get the best improvement in WSJT-X. Both Mac and Windows have native and third party capability to split Audio so TX can go one direct and RX the other. WSJT-X TX and CAT Control can be

[wsjt-devel] TX..RX with different radios

Sure… All the LOTW awards come with rules. Here are the rules for DXCC: http://www.arrl.org/dxcc-rules You can have a split transmitter and receiver but it needs to be within 500M of each other... a) All stations used to make contacts for a specific DXCC award

Re: [wsjt-devel] TX..RX with different radios

vel > wrote: > > On 8/24/2022 12:57 PM, Dwayne Sinclair via wsjt-devel wrote: >> Sure… All the LOTW awards come with rules. > > LOTW does not issue awards. It is ONLY a worldwide log book that the issuers > of awards can consult to document QSOs. Some issuers of awards ar

[wsjt-devel] Q65 T/R Cycle Submode Tracking

There are technical discussions and associated websites that describes the optimal submode for the various T/R Cycles - T/R 15 Seconds Submode A T/R 30 Seconds Submode B T/R 60 Seconds Submode C T/R 120 Seconds Submode D T/R 300 Seconds Submode E Would it be possible to add a switch to setting t

Re: [wsjt-devel] Q65 T/R Cycle Submode Tracking

number > of factors are in play. Have you read the Q65 Quick Start Guide? > > 73 > > Charlie DL3WDG > > On Mon, 6 Feb 2023 at 20:03, Dwayne Sinclair via wsjt-devel > mailto:wsjt-devel@lists.sourceforge.net>> > wrote: >> There are technical discussions and

Re: [wsjt-devel] 3Y0J strange F/H operation

There is no question the Expedition messed up with F&H. Simple as that. Add it to the list of lessons learned for subsequent expeditions. Regards Dwayne AB6A > On Feb 15, 2023, at 8:04 AM, David Kjellquist via wsjt-devel > wrote: > > Unlike WSJT-X, JTDX software allows F&H on either odd or ev

Re: [wsjt-devel] 3Y0J strange F/H operation

I agree with you 100% but that does not take away the fact there was abundant confusion for many ops. Just watching this play out, you would see almost the same amount of ops transmitting odd as well as even attempting to respond. In my humble opinion, they should have been using F&H and even.

[wsjt-devel] Q65 Doppler Mode / Flex Radio 6400 (with 2 Slices only)

There is a nasty bug which destroyed two EME sessions for me. Not sure where the problem lies (WSJT-X/Hamlib/Flex etc) … If SmartSDR 3.4 has two Slices active when starting WSJT-X, enabling Q65 Doppler Tracking will cause CAT to fail. CAT turns from Green to Orange and stops responding to WSJT-

[wsjt-devel] Is call3.txt still used in current versions of WSJT-X?

Is call3.txt no longer used or only used for some modes such as JT65? I have seen comments to suggest call3.txt has been depreciated in latest versions of WSJT-X but nothing I could see in release notes. Q65 documents detail when setting up scheduled QSO’s, to fill in the DX CALL and generate m

[wsjt-devel] Truncated Waterfall Display "Feature"

Last night, I met an operator who was struggling with EME on 23CM after abandoning EME on the 70CM band. As soon as he started up WSJT-X, I noted his waterfall display was set to Bins/Pixel 2 instead of 5/6 and less than 1500Hz was displayed on the screen. All decodes 1500Hz and up were not deco

Re: [wsjt-devel] Truncated Waterfall Display "Feature"

portant to make sure his receiver > bandwidth is wide enough to pass the signal at that frequency. > > 73, Russ K2TXB > > -----Original Message- > From: Dwayne Sinclair via wsjt-devel > Sent: Wednesday, April 5, 2023 11:35 AM > To: WSJT software development > Cc:

Re: [wsjt-devel] Truncated Waterfall Display "Feature"

I agree but it is not intuitive that Start Hz is an option in the controls, but end Hz is controlled by Bin Pixels and how far the op stretches the window. 73 Dwayne AB6A > On Apr 5, 2023, at 10:13 AM, Reino Talarmo via wsjt-devel > wrote: > > Perhaps also reading User Guide 6.2. Wide Graph

Re: [wsjt-devel] Truncated Waterfall Display "Feature"

Just to add, It would seem to be the intuitive fix would be Start and End Hz as options in the controls or Settings Menu defaulting to 0Hz and 3000Hz and not affected by Bin/Pixel setting or how far the window is stretched. 73 Dwayne AB6A > On Apr 5, 2023, at 10:19 AM, Dwayne Sinclair wr

[wsjt-devel] macOS - Is there a "quick" way of updating Hamlib on MacOS implementation?

I have seen Windows instructions to replace a Hamlib dll to get the latest version of Hamlib. Is there the same capability on macOS so we can test and validate Hamlib issues without having to compile WSJT-X? Regards Dwayne AB6A ___ wsjt-devel mailing

Re: [wsjt-devel] macOS - Is there a "quick" way of updating Hamlib on MacOS implementation?

0dylib%20placement%20MacOS.png?dl=0 > > > All the above assumes you installed the WSJT-X .dmg file from the Sourceforge > website and that you have not compiled WSJT-X on your own. > > Let me know if you have any further questions. > >> On Jun 12, 2023, at 1:38 PM,

[wsjt-devel] Q65-15A Broken?

There have been ongoing reports from various operators best summarized in the post attached that Q65-15A is “broken”. What is current consensus on this and if it is broken, is there any plans to address the issues? https://www.bobatkins.com/radio/Q65-15_eme_II.html Regards Dwayne AB6A

Re: [wsjt-devel] Q65-15A Broken?

why? > > Are you (or they?) talking about EME? If so, are you aware that the Q65-15x > submodes are not supposed to work for EME. The 2.5 s EME delay is too large. > >-- 73, Joe, K1JT > >> On 1/22/2024 2:04 PM, Dwayne Sinclair via wsjt-devel wrote: >> There ha

Re: [wsjt-devel] Q65-15A Broken?

Yes - many of us are already using Q65-30B on 23CM EME. Looking for “faster” ;) Regards Dwayne AB6A > On Jan 22, 2024, at 12:44 PM, Lance Collister, W7GJ via wsjt-devel > wrote: > > There is the 30 second option... > > On 1/22/2024 20:36:37, Dwayne Sinclair via wsjt-deve

Re: [wsjt-devel] Q65-15A Broken?

e many times more EME activity than at > present, so that very fast QSOs were desirable in contests, and if nearly > everybody had many dB's to spare on the EME path, something like Q65-15A > might be desirable. As things stand, our advice is to use Q65-30B for EME on >

[wsjt-devel] EME Doppler Control without Monitoring Enabled + Q65-20M

Our recent discussion on UHF/SHF (23cm) EME Q65 confirmed today the fastest mode available is Q65-30B. WSJT-X does an outstanding job of doppler control and can be used to control doppler for CW QSO’s via configuring Preferences/Radio/Mode to None so that the mode of the transceiver (in CW mode)

Re: [wsjt-devel] Release Candidate WSJT-X 2.7.0-rc4

The Darwin disk image for RC4 is corrupt. Only has a 281 byte file size. Dwayne AB6A > On Mar 11, 2024, at 7:57 AM, Joe Taylor via wsjt-devel > wrote: > > Dear WSJT-X Users, > > We are pleased to announce that Release Candidate WSJT-X 2.7.0-rc4 is ready > for download and use by beta testers