not talking to dxLab commander...w new Cat 1.1.5.0

Dan, make sure there are no conflicts with ports assignment. SSDR CAT automatically creates port 4 and port 14, no matter which ports are already created in your system. It does not seem to be a major bug in SSDR CAT, but it makes you pay special attention to your Com ports assignment. Before launching SSDR CAT and SSDR make sure that you have both ports 4 and 14 available. Otherwise there should be no problem with Commander addressing port 4. You can also try more complex way. Try DDUtil ver.3 and create a couple of VSP pairs with K5FR VSP Manager. DDUtil sees Flex 6K without addressing Com ports, so you can create a random pair, using one port to connect with DDUtil, and second port for Commander. In this case you are not tied to Com 4-14 pair.

Ha, just read this. My win Keyer runs on a FTD com port 4. And will not key the rig, whereas it keys the Flex 5K perfectly. Obviously, I must change/delete that pair of ports that Scat creates. But that is a wonder...how can it create a pair of ports, when both of those ports already exist. I have had the com 4 with my winkeyer. Shouldn't SDRCat see that and NOT interfere? And checking SDRCat, I of course see a port 4 but no port14. Something is amiss

I don't understand either. previous version I had good communication with DXlabs Commander. Now I can't get it to connect. And why I can't send cw to the rig is a mystery. To me, that's a major problem to try and create a port where a normal windows com port already exists. I have a normal Com 4, it's the WinKeyer which works perfectly in PowerSDR and will not work in 'Not so SmartSDR' I do find it interesting that in SmartSDR it lists my Physical Port Com4 and if it did create a com 14, it doesn't show up in the list. I'm assuming that is also related to my loss of connection to DXLabs Commander which is rock solid in PowerSDR.