Problems Starting Communicator

[W6SDM]

My end goal is to get Log4OM to work with PstRotatorAZ. Log4OM works well in all respects except for Communicator.

Here’s my setup: Windows 10, current version. Log4OM, latest version. I am running OmniRig. When I start Communicator using the Comm Services pull-down at the bottom of the main window, I get a message that Communicator is active in the background and the Communicator icon shows up in the task bar.

When I click on the icon and bring up the Log4OM Communicator dialog box, It’s running and the STOP icon is red. At the bottom is says Connected to 127.0.0.1:8081. This is a screen shot of my activity log:

[KI5IO]

When you start Log4OM it usually automatically starts Communicator. Why are you trying to start it again? The message that it is active in the background is telling you it is already running.

[G4POP]

You need to stop the communicator to set it up for PSTRotator and then restart it once you are finished.

This is covered in the user guide and I think I did a YouTube tutorial video also

[W6SDM]

Nolan,

The reason that I don't have communicator checked to auto start is that when I do, it crashes Log4OM on startup. It acts the same way on startup that it does when I do a "Start WCF" after the fact.

Apparently, there is some sort of conflict with ports.

[W6SDM]

Terry,

I will check your video and re-read the instructions. I think I need to get the Communicator issue fixed before I attempt to link with PstRotator.

[W6SDM]

I think some of my problem may be that I don't have the correct port number for PstRotor set. The ones that default in the program are the ones I'm using. I haven't changed anything. How can I tell which is the correct port number in Communicator under Settings/Outbound/PstRotator Settings? It presently reads 12040.

[G4POP]

How can I tell which is the correct port number in Communicator under Settings/Outbound/PstRotator Settings? It presently reads 12040.

12040 is the normal default PSTRotator setting, chek that PSTRotator is using the same port number.

Check that you are using the correct version of PSTRotator which is the azimuth version not the AZ/EL I don't think the author of PSTrotator ever made the AZ/EL version to integrate with Log4OM