Please enable the logging statements at lines 400, 403 and 408 in rotator/targetx2/commanding.c: the commented-out syslog calls in:
Please also look for and enable similar messages in the hexapod commanding.c
This will help us diagnose when the rotator or hexapod cRIO decides to ignore commands from the CSC.
Note that any command from the "GUI", which is what we call the Engineering User Interface (EUI), will reset gCommandSourceDDS to 0, making the CSC unable to command the cRIO. That is based on different code in rotator/targetx2/cmdClientSocket.c:
This looks like a bug or misfeature to me (unless it also changes the state to Offline/PublishOnly, which I strongly doubt).
I would expect the CSC to always be able to control the rotator except in Offline/PublishOnly mode.
- This task will try to understand the logging mechanism and log the useful information. This will be helpful for the following debug.