[Dx4win] DX4WIN mode problem with Flex6000

[radioart at frontiernet.net]

Hello Paul,

First I must say, I have been a DX4WIN customer for over 15 years and am very happy with DX4WIN.  Currently my radio of choice is the Flex6500 and with this new radio there seems to be some features of DX4WIN that are not working as with the Flex5000A... I hope you will resolve this problems so I can continue to be a devoted customer....  (The new Flex6000 series can 
transmit/receive on any slice/VFO, which I think is causing this problem)

I have experienced three problems using DX4WIN 8.05 with my new Flex6500 V1.0.0 via the SCAT interface Flex provides.

 
The first is; when I have a QSO on VFOB (which means I've selected TX on Slice_B) and am ready to log the contact I notice the band and freq are correct for TXB but the mode is what ever RXA is set to (the other VFO or Slice_A)...  So I have to make RXA the same mode as TXB for the DX4WIN log book to have the proper mode for the QSO....  With the Flex6000 you can have up to 8 RX/TX slices so logging the correct mode for the slice your on is going to get worse in the future.

Second, when I double-click on a DX spot with a QSX frequency my 6500 jumps to the correct frequencies but the TXB VFO (slice_B) mode is not the same as the RXA (Slice_A) mode.  That is, DX4WIN set the DX listening mode correctly but did not set the transmitting mode correctly so I'm listening to CW but transmitting in SSB....


The third problem is only a  nuisance issue, I cannot connect DX4WIN (F9) to the radio unless I have 
VFO/Slice_B open as well as VFO/Slice_A open.  For some reason DX4WIN 
looks for VFOB when it opens up and not VFOA.  Other Logging programs 
only require  VFOA to be open ( I was told this was the case by one of Flex's API developers).


Paul,  I would sincerely appreciate it if you could resolve at least the first 2 issues.


Kind Regards,

 Dennis KØEOO