Help with PstRotator Configuration

[KD0Q]

I have a problem with Log4OM and PstRotator configuration. PstRotator works manually but commands from Log4OM have no effect.

Both Log4OM and PstRotator are set to use port 12040, PstRotator Tracker is set to Log4OM.

I see messages in the Log4OM log like:

2015-11-06 11:13:32.3177 INFO: #=qtY1R_zBrtBF15c8uGNmzFz6Ra_1MFjbl1oWmasiAjQI=: Sending rotator azimuth message to communicator

2015-11-06 11:13:32.3267 DEBUG: TCPServer: TCP MESSAGE OUT: RotatorMessage ROTATE BEARING B:False D:43 S: --- CALL B:False D:0 S:9A2YM --- FREQ B:False D:18142.000 S: ---

and in the Communicator log like:

2015-11-06 11:13:32.3337 DEBUG: TCPEventManager: INCOMING TCP MESSAGE: RotatorMessage ROTATE BEARING B:False D:43 S: --- CALL B:False D:0 S:9A2YM --- FREQ B:False D:18142.000 S: ---

It doesn't look like anything is being sent to PstRotator.

I noticed that all items on the Communicator PST Rotator Setting dialog are disabled.

What configuration am I missing?

Any help is appreciated. Glenn - KD0Q

[IW3HMH]

Hi Glenn
settings are disabled when communicator is running, so this is correct and means Communicator is currently active.

Packets are sent from Log4OM -> Communicator -> PST Rotator
Log in Log4Om indicates that Log4Om is requesting Communicator to send a packet to the rotor system
Log in Communicator reports that the message is received from Log4OM (communicator can work remotely on another system)

It should report something in output too (i don't have code here, so i can't check exactly what to search for).
Common cause of interop integration troubles is administrator rights. Are you running log4om under administrator rights?

[KD0Q]

Everything is running under administrator rights. Just to be sure I re-installed "As Administrator" and have the shortcut advanced settings set to "Run as Administrator" for both Log4OM and PstRotator.

No other events after the ROTATE command.

But I do see see the following in the log at program startup:
2015-11-06 10:35:46.5986 ERROR: *** NotificationManagement: GROWL Error - 201 : The destination server was not reachable
2015-11-06 10:35:46.5986 ERROR: *** NotificationManagement: GROWL Error - 201 : The request failed to be sent successfully due to a network problem.
2015-11-06 10:35:46.5986 ERROR: *** NotificationManagement: GROWL Error - 201 : The response failed to be read successfully due to a network problem.

Is that part of the PstRotator comms?

[yo3dmu]

Hi Glen,

If you install the TeamViewer program and send me an email with the User ID and the password, I will can take a look via remote to your settings and try to fix any problem.

73,
Codrut - YO3DMU

http://www.qsl.net/yo3dmu/index_Page346.htm

[KD0Q]

The interface to Pstrotator is now working.

The solution was as simple as stopping Communicator, enabling the PstRotator interface, and starting Communicator.

Thanks to Codrut, Y03DMU, for helping out.

73, Glenn - KD0Q

[IW3HMH]

Thanks Codrut