+ AA6YQ comments below My radio is not in that page, i add an xml to gain access and control it + Commander does not support the DX-SR8T, for two reasons: 1. I didn't know that the DX-SR8T existed

On Mon, Jun 1, 2020 at 09:55 AM, Bill Somerville wrote: --language=enThanks Bill for your answer. I don't use spaces in the argument. I have tried again and I can't get the interface to be in

Tom, that is good to hear. I have just run a simple test comparing my FT-991 to my FT-891. On the left is a “snip” from Device Manager. I connected DC power to theFT-991, plugged in a

My error Mark was covering IMD (not too good on 3rd) while my mind drifted to TX phase noise (awesome) 73 W5AJ Robert Midland, Texas

For Windows, several of the built-in fonts include a "slashed" zero. Of particular interest are Andale Mono and Consolas - both are mono spaced fonts. Mono spaced fonts are ideal for use with WSJTX

DX-8SR is the seventh transceiver in Commander's list of transceivers. If your installation does not have it, you need to update the Radios.txt file in the Commander directory. I've been using DXLab

I wanted to thank the several people who made excellent and helpful suggestions about how to get my FT891 running WSJTx on a MacBook. It is working splendidly now. I ended up going the Signalink

My radio is not in that page, i add an xml to gain access and control it

A second problem is this impacts the handi-hams that are blind. Their screen readers will see the slashed zero and the letter O and their screen readers will read out NI OH K or NR OH A. Monty

And some more here: http://www.wm8c.com/slashed_zero_fonts.htm 73 -Jim NU0C "Jim Shorney" <jshorney@...> wrote:

Hi Bill and Joe output problem solved - shazaam! receive problem remains. new soundcard, unlike my old one, has no "line-out" port. so I connected playback mode to the new card's speakers port. turns

The problem with this method is the ALT character does not render as an actual zero to any software that is looking for numbers. This can cause unexpected problems. Best to use a font that actually

Making comments about 200-300 watts being excessive power primarily indicates that the person has no real experience in weak signal work on either 160 or 6 meters with WSJT-X modes. Before making such

How to make a “Slashed Ø” for your Callsign Mark R. Henry, WAØWIK Awhile back, someone asked me how I generate a “slashed Ø” when typing my call into an e-mail or other document. Some of

Actually no. Take a look at ARRLs review in Jan 09 QST. They showed TX 3rd order at 25 dB which is pretty bad don’t you think. That was probably due to them running the k3 at a lower dc voltage.

Mark, your comment "K3, which doesn't have the best TX intermod performance" using WSJT "degrades my tx purity to the point it affects decoding..." Nope. The K3 TX IMD was the gold standard for

Personally I think that is excessive. More than 50 watts is unnecessary in most cases. If you have to resort to power then do a better job on your antenna system. My antenna is a random wire in my

The "right" power level is STRONGLY dependent on what band, what you're trying to work, how good your antennas are, and how well you can hear. As I stated in a previous post, I run legal limit for

The most likely cause is that RX noise on the other end of the QSO is higher than on your end. This happens to me almost all the time, even when I'm running legal limit on 6M, or for long haul QSOs on

OMG I thought doing 100 watts sometimes was way over doing it. 300 watts wow. I’m glad that you posted that so I have a naïve idea what people are using for power. 73 Darl NA8W