Print

[W9ACF]

Well I made the mistake of upgrading the WSJT software from 2.5.4 to 2.6. Now I have lost the ability to log to Amateur Contact Log. I have reached out to Scott/N3FPJ and followed his instructions to get the interface to work, but it still doesn't log the contacts. The cursor is flashing in the call box of the logging program, but the contact in WSJT is not auto logging to N3FJP Contact Log. I swear I will never do another upgrade!!! hi hi.....Any help at all will be much appreciated. Thanks--Jeff

[K0UA]

Well I made the mistake of upgrading the WSJT software from 2.5.4 to 2.6. Now I have lost the ability to log to Amateur Contact Log. I have reached out to Scott/N3FPJ and followed his instructions to get the interface to work, but it still doesn't log the contacts. The cursor is flashing in the call box of the logging program, but the contact in WSJT is not auto logging to N3FJP Contact Log. I swear I will never do another upgrade!!! hi hi.....Any help at all will be much appreciated. Thanks--Jeff

you could always do a rollback and downgrade to the previous wsjt-x.  Try that and see if it restores usability.  If I was to guess, there might be a problem on the advanced page of the setup on wsjt either in the default IP address or port settings. Downgrade and see what happens. OR if you have another PC install the previous version and then do a "stare and compare" with the settings on the new version.

Is JT alert involved in your setup?   Call me if you want me to work on it for you remotely.

[KK2DOG]

I updated to 2.6 and my ACLog still works fine.

[K0UA]

I updated to 2.6 and my ACLog still works fine.

do you use jtalert?  He does not, and 2.5.4 works fine with AC log but 2.6.1 does not work. They fail to communicate even when for sure the 127.0.0.1 address matches and the ports match.

[W9ACF]

First of all, thank you to James, K0UA for his kind assistance.

We were not able to get the new version of WSJT-X 2.6, to communicate with N3JFP Amateur Contact Log. So we went back to the 2.5.6 version and everything communicated just fine. I have reached out to Scott/N3JFP to let him know what we experienced. For now, I will continue to use the 2.5.6 version. Thanks again James!!!

[N5PG]

What version of ACLog are you using ?

[KK2DOG]

I updated to 2.6 and my ACLog still works fine.

do you use jtalert?  He does not, and 2.5.4 works fine with AC log but 2.6.1 does not work. They fail to communicate even when for sure the 127.0.0.1 address matches and the ports match.

I don't see any mention of JTAlert in the original question and no, I'm not using JTAlert either. For the record I'm using WSJT-X v2.6.1 and ACLog v7.0.7 and mine works fine.

[K0UA]

I updated to 2.6 and my ACLog still works fine.

do you use jtalert?  He does not, and 2.5.4 works fine with AC log but 2.6.1 does not work. They fail to communicate even when for sure the 127.0.0.1 address matches and the ports match.

I don't see any mention of JTAlert in the original question and no, I'm not using JTAlert either. For the record I'm using WSJT-X v2.6.1 and ACLog v7.0.7 and mine works fine.

Perhaps you two could get together and compare settings?

[W9ACF]

I'm using ACLog 7.0.7.

If you care to share your settings, I would be willing to give it another go.....