8600 and 6600 on the same network

Tom C

I hope this is the right category.

I have a 6600 and 8600 both on my network along with my TGXL and PGXL and  2 pc ‘s,  my main tower and a mini PC. All software is up to date.  All these devices are on ethernet, not Wifi.

The problem is, with each PC running SmartSDR for its associated radio, when using WSJTX, both radios will key up the active slice instead of just the 8600.  Also, AClog insists on using the band data from the 6600, even though the program is running on the other PC.

I can fix AClog  by opening SSDR for the 8600 first, then AClog, then I can start SSDR on the other PC for the 6600 and AClog stays on the 8600. 

As for WSJTX, I made sure that neither instance of SSDR uses the same named comports, but it still wants to key both radios.

I hope I explained this enough, easier to see than explain. I can work around this but I wonder if I am missing something, I am not a network brain.

Thanks

Tom

N9RU

Mike-VA3MW

The single bottleneck is that you can only run 1 copy of DAX or CAT at a time and they can only be associated with 1 copy of SSDR at a time.

You may have to add a 2nd computer to make this work the way you wish.

Tom C

I actually am using 2 computers, main PC with logging and all programs and mini pc with just satpc32 and flex software.
The main PC is my 8600 doing everyday stuff, the mini pc has the 6600 using transverters for SAT.

As long as I start AClog with the 8600, then the 6600, it is OK, but if I shutdown the 8600 or don’t start it first, AClog uses the 6600 data.

With WSJTX keying both radios, I just have to disable TX on one radio. Comport numbers are all different too.

T

Tom C

it may not be SmartSDR, the mini pc has the 6600 following theSatpc32 cat commands and doppler shift and it is not bothering the 8600, maybe the other programs are somehow doing this?

Tom C

I have solved the problem for now by using a com port for AClog instead of the API, not ideal but it works.

KD0RC

Hi Tom, that is a good solution. ACLog is really versatile!

David Decoons, wo2x

unfortunately AC Log was written to use whatever discovery packet it finds first. Our club has two Flex radios and ACLog. Using com ports was the solution.

73

Dave wo2x

Ken Wells

Yes, David. So far, that is my only "beef" with ACLog. I wish it had a "Radio Chooser" screen available.

Even as it is, it is my main logging program for everyday use.

I use N1MM+ for contests and then export the log file to ACLog after the contest.

David Decoons, wo2x

If you only have one of the Flexes powered up at a time, AC Log Flex API works.

I think a case could be made to Scott, N3FJP to support multiple radios via API. Problem is he does not have access to two radios locally to see discovery packets from both radios.

73 Dave wo2x