I opened two sessions for the test. For the first one, I did "./sacpp_Rotator_start_controller". For the second one, I did "./sacpp_Rotator_start_commander" first and got the error message for the input. Then, I did "./sacpp_Rotator_start_commander test" and wrote a message. However, the first session (controller) received two messages (one is ack and the other is done) as the following:
Checked with Dave this is correct or not.
After this, I tested the commands: start, enable, test, move, and positionSet. All messages are received and shows the ack and done for all of them. Therefore, I thought this might be a new behavior of SAL 4.0 RC2.
Tested the move command with the middleware by Moog and did not see the problem.
The above tests were on my Linux desktop.
Did the same test on the management PC of Moog and it works well.