60 minutes on, 60 minutes off is then also 50% duty cycle? Joe WB9SBD The Original Rolling Ball Clock Idle Tyme

How narrow is a dead carrier? a LOT smaller than 50 hz, so how long can your rig like a CW Key be pressed down and held? Joe WB9SBD

15 seconds On, 15 seconds Off, looks like a 50% duty cycle to me. 73, Carey, WB4HXE -- 73, Carey, WB4HXE

Power out = power out, regardless of bandwidth. Best, Eric (W1EL)

Dan, No. FT8 is virtually 100% duty cycle. It has little to do with transmitted bandwidth. 73, N0AN Hasan

Thanks again Joe. No mic boost on my external sound card. Spatial Sound is off. I uninstalled the program and went to the download page and downloaded the most recent version.

Thats why I run my amp at 50% because of the duty cycle especially during a contest. Thats the exception than the normal operating practice of just running my rig. Also I run at 50% usually and

Hello all= We have all been educated that due to the high duty cycle of FT8, it is wise to not run full power of you rig to avoid burning up the finals. My question relates to the effect of the

The new version of FT8 decoder makes a decode cycle at around 12 seconds, then "digs deeper” and grabs a second decode and a final one at the end. MSK144 is continuous “real time” decoding of

Ed, Two more thoughts. Right click on yourlower right sound icon and open the volume mixer. In the mic settings, under LEVELS, you maysee a microphone boost. Make sure that is off. Look at all

This is a strange problem Ed. That is forsure. MSK144 is decoding all the time in realtime, so as soon as a ping comes in, the text displays immediately, unlike FT8which goes back over a file

Joe, George and all, First: Thanks for all the suggestions and help based on my post! Still no luck. Joe and George basically suggested similar things. I did go into my sound card

On 13/08/2020 5:06 am, Doug wrote: That highlighting is coming from the DT highlighting of JTAlert. That was a bug with MSK144 that was corrected long ago in JTAlert 2.14.3. You

In FT4 and FT8 I have seen WSJT-X colour the time offset if is too great, as a warning that you may lose sync with the dx station. Likely the same for MSK144. Rob VE3RXH

Sounds like something related to your logging or spotting program - don't think WSJT-X is doing that.

Congrats, Ed - you are definitely getting out. I see the results on PSKReporter. Your frequency is well within tolerance, too. Only thing I can think of is that something is interfering with your

Never mind. I upgraded the KX2 firmware to 3.00 and haven't had a problem since.

There is that ... the assumption was that he was making QSOs and based on what was said, the file was not there. Neil, KN3ILZ On 8/13/2020 5:14 AM, F5BU wrote:

Hello, According to the tests I just redo, if there are no log files, they are only created when you log a qso. And with version 2.2.2 you got then an error due to the <eh> field

OK ... two things: 1. the filename is wsjtx_log.adi 2. the program will recreate the file each time its started if its not there. 3. if the file is not there even