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

I am not familiar with N2FJP logger but it sounds like the logger API is following the active slice instead of either transmit slice or a dedicated slice.

With Ham Radio Deluxe I have COM 9 defined in SmartSDR CAT and it is set to slice A. HRD and HRD Logbook tracks only slice A.

Your issue sounds like it is going to be a setting or the API on the logging program is not set up correctly. Look at N3FJP and see if you can define what the logger tracks via API.

Dave wo2x

David Decoons, wo2x

Here's right from the author's web site -
 
"Flex Radio (via API)
Rig Name = Flex API

Note, no other settings are required with the Flex API option. With this option, my software will track the active slice."

So, whatever slice you make any change to the frequency info is sent to the logger. I would suggest emailing the author and ask that he add an option for the API to track the TX slice instead of active slice.

Dave wo2x

James Charlton

Thank you very much!  I'll try that,
Jim  AD0AB

VE3DZP

Hey James good morning. I am running just the 6400M with AcLog but on the rig interface on the the bottom left is were you set up for two rigs. Not sure how that works with different slices on the same radio but did have it set up for my Flex and Kenwood. Give it a try.

Gary VE3DZP

James Charlton

Gary,
Thanks, I'll try that.

Steven WA8Y

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

VE3DZP

James this might work as well. You will have to run "2" instances of AcLog. Give slices "A"and "B" there own com port.
Fire up your Flex then the AcLogs.I think you know where I am going. The only thing is at the end of the day you will have to merge the two logs into one.
**** ya got nothing to lose.

Gary 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

Don Achelpohl

Jim, ABD0AB,

I did try the lower left hand corner of the rig interface in the NEFJP logger and mine showed the same same 3 choices I believe yours did. #1 Flex API, #2 Flex Radio, #3 None. Bands and frequencies jumped and switched with #1 and #2 when the ACLogger active. #3 stopped the jumping and switching but of course is unworkable for being able to log contacts.

Don, AC0UH

Don Achelpohl

Jim, AD0AB,

Did you ever come up with a solution to the difficulty? I appear to be experiencing somewhat the same problem today. I am stable and fine with my 4-slice Flex 6600m with SliceMaster running along with SmartSDR and WSJT-x. Once N3JTP's ACLog is started, the band of one slice jumps to one of the other slice's band and frequency. I have been through WSJT-x and SmartSDR trying to find anything that would be impacting and causing this behavior. I used to be able to run SliceMaster and ACLog with 4-slices without this behavior. My problems started after Field Day when I took my Flex 6600M to do FT-8. I sent my Microsoft Surface Pilot Laptop with Windows 11 operating SmartSDR, WSJT-x, and using SliceMaster to one monitor. I used my Microsfot Surface Book II with Windows 10 up as a N3JTP server collecting data from the Surface Pilot Laptop's logging of contacts on ACLog. This allowed 2 monitors so observers and operators could see all the operations taking place and worked fine once we got it set up. The second monitor via the Surface Book computer showed just the server logbook where as the other monitor showed WSJT-x decodes and SmartSDR.

I am operating the the Flex Radio Firmware: v3.9.19.37287 and the same Smart SDR on both computers. When I try either computer (individually with the other off), I get the same frequency switching and jumping when ACLog comes on line - I am stable prior to this.

Anyone with any thoughts? Jim?

Thanks in advance,

Don, AC0UH

James Charlton

Don AC0UH,

My setup is much simpler than yours, but here's what I've found. Over 99% of my operation is CW so I don't use Smart SSDR. If I need to operate more that two slices I use a Maestro for slices C and D. For Field Day operation we use an IC7300 and N3FJP Field Day group logger with stations linked via a microwave mesh.

When I use N3FJP ACLog I use the Flex API. It took me a long time to realize that it doesn't really control the radio, it simply logs the active slice's frequency. That is, the slice without the red pointer. Unfortunately, that is always the last slice tuned, not the slice selected for transmit.

The hazard is that if I'm operating on slice A and accidentally bump the tuning knob for slice B, The logger switches to the slice B frequency because that's now the last slice tuned. Nothing changes on the radio except the active slice, the audio stays as it was set, the transmit freq and mode stay as before bumping the knob. But now the logger is logging my QSOs with slice B's frequency even though I'm transmitting on slice A. I have gotten used to this and carefully watch it.

The reason I use the N3FJP Flex API is it provides spotted callsigns on the transceiver screen. this is a big help for contesting.

If you would like the ACL to provide more control of the radio, try the Kenwood setup instead of Flex API. With it you can embed control codes, accessed via the logger's screen, that switch between two radios (slices) etc. I haven't found a way to get spotted callsigns on the transceiver screen this way. They do show up in the N3FJP bandmap.

Another way to control your transceiver is via a free third party app called FlexButtons that runs on your PC. It's easier to use for setting various parameters than the Flex menus etc.

But the best PC logger I've found that completely controls the radio is N1MM+. It's free and interacts very well with Flex. It takes some getting used to, but you rarely need to touch your radio. The logger tunes the radio, selects the slice, switches to any spotted callsign, indicates which ones have been worked and which are worth the most contest points etc.

For me, N1MM+ is the way to go because I can jump around between frequencies and slices very quickly without touching the radio. Since I also run the Flex PGXL, TGXL and AT, this is a big deal.

I hope my experiences are somewhat useful. Incidentally, I've found that Wifi is not a good way to interconnect devices. Hardwiring to a fast router or Internet switch solves a lot of mysterious problems and you don't have to mess with those tricky USB cables.

Good luck,

Jim AD0AB

David Decoons, wo2x

The problem with N1MM+ for a DX or general log is the azimuth lookup returns the center of a country. Not a very big problem for working DX but certainly an issue working stateside stations as every lookup returns center of US.

I do it using the Flex API and Node Red with AC Log using the Flex API and its own API.

My Node Red dashboard has a call entry window. I enter a call and hit tab. Node Red sends an API command to ACLog to look up the call. ACLog returns the call info. I parse the azimuth and send it to the rotor. Once station is worked I click the log call button on my Node Red dashboard and it logs the call, transmit frequency and other info to ACLog.

73 Dave wo2x

James Charlton

Dave wo2x

I wish I had your azimuth problem! All my antennas are fixed by the location of trees in my yard.

It sounds like you've got a pretty nice logging arrangement. Actually, I only use N1MM for contests, I use N3FJP for everything else. I don't normally use any third party apps except maybe Flexbuttons, now and then.

Jim AD0AB

David Decoons, wo2x

thinking of the issue people are having…

I believe each instance of WSJT-X could be configured to send their info to a port in Node Red. Node Red could then parse the frequency and replace with the radio’s TX frequency at time it is logged. My Node Red flow for Flex stores the radio TX frequency as a global variable so should be fairly easy to make work.

I already have the Node Red to ACLog part written.

73 Dave wo2x