Rotator support

[K0HB]

I am using PstRotatorAZ and RotorEZ to turn my tower. The "link" between Log4OM and this seems "fragile".

Mostly it works just fine, but sometimes for no obvious reason, clicking the antenna rotate icon has no effect, and need to restart the program(s) to regain rotator control from Log4OM. (Rotator always works from PstRotatorAz native screen, so the broken link is between Log4OM and PstRotatorAZ, not between PstRotatorAZ and the RotorEZ controller.)

Thoughts where I can fix this?

[G4POP]

I am using PstRotatorAZ and RotorEZ to turn my tower. The "link" between Log4OM and this seems "fragile".

Mostly it works just fine, but sometimes for no obvious reason, clicking the antenna rotate icon has no effect, and need to restart the program(s) to regain rotator control from Log4OM. (Rotator always works from PstRotatorAz native screen, so the broken link is between Log4OM and PstRotatorAZ, not between PstRotatorAZ and the RotorEZ controller.)

Thoughts where I can fix this?

What OS are you using Hans?

[IW3HMH]

please check logs.
Everytime log4om sends a command to Log4OM Communicator it logs the call.
When communicator receives the request, will forward it to PSTRotator, and this is logged into Communicator log.
Errors are reported there as well, please take note when this happens to check the log (mainly the communicator, that it's the last interface through the external world) for errors.

Thanks
Daniele IW3HMH

[K0HB]

Running in Win7 OS.

Of course now that I raised the question, the problem does not occur.

[G4POP]

Running in Win7 OS.

Of course now that I raised the question, the problem does not occur.

Check that Log4om is running with administrator privileges, see page 19 of the user manual.

I recon Daniele frightened the Gremlin away

[K0HB]

The rotor function has gone to sleep again after the program was operating well for some time.

Here is a transcript of the log..... Notice up to 18:53 everything working, but then a failure later when I tried to turn the antenna at 20:15.

After capturing the log below, I shut down Log4OM and restarted it. The rotor function recovered at restart.

------

2013-09-04 16:01:59.4417 INFO: FormMain: Program started
2013-09-04 16:01:59.4637 INFO: FormMain: Log4OMCommunicator folder set: C:\Users\HANS\AppData\Roaming\LogOM\
2013-09-04 16:01:59.4637 INFO: FileManagement: CONFIG begin load
2013-09-04 16:01:59.4667 INFO: FileManagement: CONFIG load completed
2013-09-04 16:01:59.4817 INFO: FormMain: Starting Communicator Services
2013-09-04 16:01:59.4817 INFO: FormMain: Starting WCF Connection...
2013-09-04 16:02:08.0402 INFO: FormMain: WCF Connection started
2013-09-04 16:02:08.0432 INFO: FormMain: Starting TCP Connection with Log4OM...
2013-09-04 16:02:08.0532 INFO: TCPClientManager: Attempting TCP Connection with 127.0.0.1 port 8081
2013-09-04 16:02:08.0672 INFO: TCPClientManager: Connecting socket to 127.0.0.1:8081
2013-09-04 16:02:08.0682 INFO: TCPClientManager: TCP Connection with Log4OM started
2013-09-04 16:02:08.0692 INFO: TCPManagement: Starting PST Rotator Server on port 12040
2013-09-04 16:02:08.0712 WARN: NotificationManagement: Unable to start email polling. Email is not configured
2013-09-04 16:02:08.0742 INFO: NotificationManagement: Starting GROWL Service...
2013-09-04 16:02:08.1162 INFO: NotificationManagement: GROWL Service started
2013-09-04 16:02:08.1182 INFO: FormMain: ****** SERVICE STARTED *****
2013-09-04 16:02:08.1522 INFO: TCPClientManager: Connection established to 127.0.0.1:8081
2013-09-04 16:02:09.1172 ERROR: *** NotificationManagement: GROWL Error - 201 : The destination server was not reachable
2013-09-04 16:02:09.1192 ERROR: *** NotificationManagement: GROWL Error - 201 : The request failed to be sent successfully due to a network problem.
2013-09-04 16:02:09.1202 ERROR: *** NotificationManagement: GROWL Error - 201 : The response failed to be read successfully due to a network problem.
2013-09-04 16:02:27.4103 INFO: TCPManagement: BEGIN send PST Rotator Server message...
2013-09-04 16:02:27.4133 TRACE: TCPManagement: PST Rotator UDP Broadcast azimuth sent: <PST><AZIMUTH>339</AZIMUTH></PST>
2013-09-04 16:02:27.4333 INFO: TCPManagement: END send PST Rotator Server message...
2013-09-04 16:02:57.8040 INFO: TCPManagement: BEGIN send PST Rotator Server message...
2013-09-04 16:02:57.8050 TRACE: TCPManagement: PST Rotator UDP Broadcast azimuth sent: <PST><AZIMUTH>45</AZIMUTH></PST>
2013-09-04 16:02:57.8250 INFO: TCPManagement: END send PST Rotator Server message...
2013-09-04 16:04:46.6152 INFO: TCPManagement: BEGIN send PST Rotator Server message...
2013-09-04 16:04:46.6162 TRACE: TCPManagement: PST Rotator UDP Broadcast azimuth sent: <PST><AZIMUTH>325</AZIMUTH></PST>
2013-09-04 16:04:46.6372 INFO: TCPManagement: END send PST Rotator Server message...
2013-09-04 18:52:11.5898 INFO: TCPManagement: BEGIN send PST Rotator Server message...
2013-09-04 18:52:11.5938 TRACE: TCPManagement: PST Rotator UDP Broadcast azimuth sent: <PST><AZIMUTH>49</AZIMUTH></PST>
2013-09-04 18:52:11.6148 INFO: TCPManagement: END send PST Rotator Server message...
2013-09-04 18:53:40.5359 INFO: TCPManagement: BEGIN send PST Rotator Server message...
2013-09-04 18:53:40.5369 TRACE: TCPManagement: PST Rotator UDP Broadcast azimuth sent: <PST><AZIMUTH>35</AZIMUTH></PST>
2013-09-04 18:53:40.5569 INFO: TCPManagement: END send PST Rotator Server message...
2013-09-04 20:15:47.5127 ERROR: *** TCPClientManager: Error reading from socket: [SerializationException] Binary stream '0' does not contain a valid BinaryHeader. Possible causes are invalid stream or object version change between serialization and deserialization. ******* [Function: ClientSocket_PacketArrived] System.Runtime.Serialization.SerializationException: Binary stream '0' does not contain a valid BinaryHeader. Possible causes are invalid stream or object version change between serialization and deserialization.
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at Messages.Util.Deserialize(Byte[] binaryObject)
at Log4OmCommunicator.TCPClient.TCPClientManager.ClientSocket_PacketArrived(AsyncResultEventArgs`1 e)
2013-09-04 20:15:47.6227 ERROR: *** TCPClientManager: Socket error during Read: [SocketException] A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied

[IW3HMH]

It seems a "known issue" from BinaryDataFormatter in Microsoft Framework.
I will search for a solution

[K0HB]

Now I find the link between Log4OM and PST Rotator is completely broken.

When I open Communicator Settings > Outbound > PSTRotator I find it completely greyed out, showing default port 12040, but no check marks in any box.

In PSTRotator setup also shows port 12040 for communications with Log4OM.

I have email exchange with YO3DMU at PST and my setup of PST matches his recommendations.

[G4POP]

Now I find the link between Log4OM and PST Rotator is completely broken.

When I open Communicator Settings > Outbound > PSTRotator I find it completely greyed out, showing default port 12040, but no check marks in any box.

In PSTRotator setup also shows port 12040 for communications with Log4OM.

I have email exchange with YO3DMU at PST and my setup of PST matches his recommendations.

It will be greyed out unless you stop the communicator and then you can edit the settings!

[VE3VEE]

Hans, I don't have a solution, I just want to mention I run on my Windows 7 64bit laptop the current version 1.15 of Log4om and version 8.8 of PstRotatorAZ (connected to a Green Heron RT-21 rotator controller) without an issue. I hope you'll get it going, too.

73 Marvin VE3VEE