Elecraft KX3 CAT's strange behaviour

[EA3GCV]

Hello Vit,

According to my own experience with VSPE (I use VSPE 64) I always created the splitter with 9600 bauds. Using higher baud rates I have experienced many problems (like the one you describe). As you can see, connecting directly to the native COM port, all is working well. So I suggest you to use 9600 bauds in your splitter port. (8 start bits and 1 stop bits).

VSPE can handle up to 4 applications at once. But I have experienced similar problems as yours when using many programs. Every computer is a world and you need to find out the best setup works for you. Believe me, I do remote sessions with many users and what is working for one user it's not working for others!

I use OmniRIG because Swislsog, JTDX and MixW are supporting OmniRig. From the VSPE side, OmniRig counts as a single program so I have 3 more programs left to share with this virtual port. OmniRig will send the CAT info to all programs and maybe you will avoid this flashing problem.

It's very important to know that if you are running Swisslog as administrator, you will also have to force OmniRig to run as administrator otherwise it won't be able to communicate. Golden rule: all programs linked with Swisslog must be run with the same privileges: Either all with standard privileges or all with administrator privileges.

If you don't want to try OmniRig, try to set 9600 baud rate as the default splitter COM port speed and try again. I have configured many computers with VSPE with 9600 bauds and all work perfectly.

Best 73