I do have power out now both locally on the server and remotely. I am not sure but I believe the problem was with the com ports. I ended up installing a few things then reinstalling it and then

I'm stumped and can't find anything about this issue after a lot of googling. I'm on Windows 10 on an ASUS laptop and my rig is an IC-7300. Suddenly, when I attempt to transmit (FT8) with my IC-7300,

Gerry Do you now have power out on transmit - it appeared that was the original problem that you were concerned about? Joel AC8WS

Hi Bill, Yes, it is a bug. I would suggest you test the RC release of ver 2.4 and see if it is in there as well. I had to make special provisions in my Alltext.exe program to accommodate that bug.

Yes the settings are separate. I have the radios working locally with wsjtx and through rsbs1 locally. The radios now work remotely but I am trying to get FLdigi and flrig set up. I have flrig and

So if adding the date to the beginning of a log file takes more than a handful of microseconds, I would be surprised. The bulk of time would be actually taking the underlying unix time (in seconds)

are you settings things separate under the configurations tab?? Dave Garber VE3WEJ / VE3IE

I has not been this way for a long time. It was a bug that was corrected but seems to be still in the version that bill is using. I was running the Windows version and it was corrected in a later RC

this has been this way for quite a while, I would have to look at release notes. but sounds normal. if the date does not change why append with it and slow the process.. Dave Garber VE3WEJ / VE3IE

This issue still exists for Rc4, but apparently only for MSK144. Looks fine for FT8, but not MSK144 210419_070415 1.840 Tx FT8 0 0.0 1612 CQ W8LVN EN62 210419_070445 1.840 Tx FT8 0

Well, my issue was in the RC3 release. I'm now running with RC4, and will see if it iis still there. w8lvn -- --w8lvn--

Probably it will not surprise you that we've done some of this, especially with respect to time of day. It's very easy to show that ionoscatter conditions are best around mid-day and worst around 7

A brief update on progress. PIC code for the later generation enhanced device, the 16F1827, now exists that will turn 13 characters of Plain text, or 17.75 Hex characters into a set of symbols ready

Hi Mark I also have a 6400 and have had similar - mine changes to LSB on 40m downwards - I think due to the turf file on the 6400 assuming that those bands are normally LSB. All other bands work fine.

Hi Mark, this is due to a regression in the TS-200 driver in hamlib, which I assume you are using. It is fixed for the next release, you can either change to "Settings->Radio->None" in WSJT-X and set

Hi Bill, I ran into this problem when I tested some function in my Alltext.exe program that I sued for the same function. I found that when I used WSJT-X 2.3 rc1 (or rc2). The Date and time was only

on the radio settings tab, see if mode is set to data/pkt, your radio may be trying to use bandplan as its setting, this should override it, i think Dave Garber VE3WEJ / VE3IE

Team: I am noticing that under some conditions, the date field is omitted from ALL.TXT for monitored calls, but not for transmissions I make. What is a little more odd, this did happen when switching

Good Evening All, I have been operating WSJT-x for years and have not had this problem before. My FLEX 6400 just started defaulting to LSB on TX on all bands. I am not having the same problem with

Thank you Joe for the data and Jim also makes a very good comment. When I was looking at how weather storm systems affect transatlantic 6m communications, and also during the winter months when we