I didn't. I just made sure i changed install directory to match where I put the 2.5.3, so it would overwrite the exe file. all that is in the appdata stays as is Dave Garber VE3WEJ /

Dave, thanks for the advice. Did you have to do an uninstall for 2.5.3 and complete reinstall of 2.5.2?? Any issues with 2.5.2? I upgraded directly from 2.4 so missed any incremental changes on the

i went back to 2.5.2 until fixed... Dave Garber VE3WEJ / VE3IE icloud.com@groups.io> wrote:

Qrz.com has a section for skeds in the forums

Scott, The only sites like this of which I have knowledge are by N5TM VHF Chat & ON4KST. You can find them with Google. These are specialized for low bands & VHF UHF bands. I’m sure there are

I just upgraded to 2.5.3 and have exact same problem and error message as Buddy WB4OMG with my IC-7300 and Win 10 laptop. I followed Mike W9MDB instructions and downloaded and installed new hamlib

I am looking for a website for making some skeds with some local (CT/MA/RI) states that are too close to me (PA). Where is a good website for making schedules like this? Sorry for the off thread.

Hi Ed, You have interpreted each of the displayed quantities correctly. -- 73, Joe, K1JT

I have a number of counties I have worked that have not QSL'd. How do I change their status to "not worked" so if a station from that location appears highlighted in the default purple color? --

My note describing the coding of the LDPC modes, FST4/FST4W, FT8, FT4 and MSK144 has now been elevated from Draft to final version. Thanks to those readers who sent back helpful comments The

You can do it from a command line if power on is supported for your rig. First find your model number...example here for the 7300 assuming you are running Windows. rigctl-wjstx -l | find "7300" 

Bringing a new computer online. Need the file which will power on the rig at program startup. Tom, WA9AFM

Sorry to report... I'm running version 2.5.3 69f9ec and just now I had HR5/F2JD crash the app as it went to log the QSO again.

hi folks: I started playing with the echo mode today and had good success. Is there a reference somewhere that describes the headers in the table that is generated during echo mode, namely UTC

The only thing "wrong" is that the *CLUSTER SOFTWARE* /ASSUMES/ that any spot not in the "phone" bands is CW unless the spot contains the mode in its comments. The better software includes the

Unfortunately, the worldwide DX spotting network has never included the spotted station's "mode" as an always-present data item in each spot - like callsign or frequency. SpotCollector, a component

The structure of a cluster spot, "^" delinted text, does not have facility for recording the mode, thus determining the mode is left to guessing based on frequency or by extracting from spot notes.

How on earth is the logic of declaring what mode a report is purely on the basis of frequency ever going to have any accuracy? Folks can run CW on pretty much ALL frequencies, and FT users are

Joe, I agree that the RBN can be pretty "brain dead", but I'm having trouble swallowing the idea that a CW-decoding system is somehow locking onto and identifying an FT/x mode signal as CW. There has

The cluster networks "assume" operating mode based on frequency. They do not have sufficient "smarts" to differentiate between modes when the SPOTTER does not include the MODE in the comments. IOW,