Serial communication in MCSDK 6.3.0

[hu88]

We have to been trying to establish serial communication between our motor and controller. For that we are referring the document attached in the mail. We are using the mc workbench version 6.3.0 . 

When we connect and control motor from motor pilot it works fine , but when we try some other serial communication software ( like real term , Hercules) then we are unable to run the motor even though we are sending the same hex code. 

This is the command motor pilot sends for starting the motor, and in this case motor starts correctly.

We are sending the same command through other serial communication software (like real term)  but motor is not starting.

Please look into the problem . Looking forward to your response .

[Gael A · Accepted solution]

Hello hu88,

The MotorPilot follows a communication protocol called MCPv2, which is described in the MCSDK User Manual :

Via WorkBench, you can find it by clicking on About -> Documentations -> Documentation -> in the newly open browser window, click on User Manual

Before sending any command to the FW, the Pilot has to make sure that connection is established correctly. This is why simply sending a command to the FW does not work.

[hu88]

So every time do we have to establish a connection before sending any command,or after establishing connection once ,we can send multiple  commands like motor start, motor stop,etc

Also we have gone through the document and it is unclear, if you have any other reference or solution please share, it will be helpful.

[Gael A]

Hello hu88,

Unfortunately, we do not provide any other documentation on the MCPv2. You can have a look at how it is implemented in our FW.

To answer your question : once communication has been established (connected state), you can send as many command as you want, but since it is a synchronous communication (except for datalogging), you have to wait for the confirmation on the performer side before sending a new command.