Why does my logger follow last turned freq dial instead of active transmitter?

James Charlton

I am using a 6600m with an N3FJP logger.  The radio is running V3.1.12.51.  The radio and the logging PC are hardwired to my router with Cat5 cables.  I also have an  amp and two antenna switches that connect to the radio via three USB cables.

In normal operation with only slice A active, the logger displays the selected frequency.  If only slice B is active, the logger displays that frequency.  It's when I have both slices on the radio's screen that something strange happens.

In that case, the logger shows the frequency selected by the last knob touched, regardless of which TX button is red,  For example, let's say slice A is on 20m and it's TX button is red(selected) and slice B is on 40m and its TX button is white (not selected).  Also, let's say that the logger is displaying slice As frequency.  If I ever so slightly turn the Slice B tuning knob, the logger immediately displays the Slice B frequency even though that TX button is not red.

Turning the slice A tuning knob will cause the logger to immediately display the Slice A frequency.  The amp and antenna switches don't follow the logger frequency, they follow the TX buttons only.

I don't know when this started,maybe it has been this way since I got the radio.  It may even be a feature(?).  Anyway, I suspect it is related to the CAT configuration which I know nothing about because that part worked when I first plugged the radio in.

On the radio, looking at the menu/usb cables window shows three USB cables and no CAT cables.
Opening that little SmartSDR CAT v3.1.12 program shows a number of CAT connections all indicating slice A and several different COMs.  The N3FJP logger is using its FLEX api with com5 selected.

Is there some configuration or settings that can make the logger display the TX frequency and not that of the last knob turned?
Thanks in advance for any suggestions,
Jim  AD0AB 

David Decoons, wo2x

David Decoons, wo2x

James Charlton

VE3DZP

James Charlton

Gary,
Thanks, I'll try that.

Steven WA8Y

Do you have a CAT (COM#) for Slice B, Slice C, etc?

VE3DZP

David Decoons, wo2x

I am working on a hardware solution which might fit the bill.

I have ordered an FTDI NMC null modem USB A male to USB A male cable. This would connect from the back of the radio to the logging PC. 

On the radio side set up the cable for CAT and follow TX slice. Set baud to 9600 and enable auto report.

On the PC side check Device Manager to see the COM port number the cable creates. Set up the logging program as Flex Radio 6000 series (depending on logging program) and select the COM port number created by the cable. Now frequency info from the radios slice set to TX will be sent to the logging program.

I have ordered one of the cables from Amazon and will have it Tuesday to test.

For those that don't have any free USB ports on the radio you can use a USB 2.0 hub to expand the number of USB ports on the radio.

73
Dave wo2x

James Charlton

Hi All,

I reposted this same question because I know quite a bit about the problem now.

As far as I can tell, the problem is with N3FJP. Scott Davis is very responsive, but he says that the FLEX API rig interface for his ACL Logger uses the Flex DLL and his logger takes whatever the DLL sends it. According to Scott, the DLL must be changed to send the Transmit slice freq, not the active slice.

I am not sure that he is correct. That's why I re-asked the question to see if anyone has the N3FJP logger working correctly.

There is a second rig interface in the N3FJP logger called Flex Radio. It can be set up to log the transmit frequency properly, but the DX spotter interaction with the radio is lost. The DX spotter interaction depends on the API.

Right now, unless someone has a magic solution to the problem I can configure the logger to correctly log the frequency of the transmit slice but not have DX spotter connection to the radio or, I can have good DX spotter interaction, but risk logging the incorrect transmit frequency. Of course, the third choice is to use a different logger.

Thanks in advance for any help,

Jim Charlton AD0AB