Workbench_6.3.0 Motor Control Protocol Rx 0F 04 04 C0

[honkerhz]

Using the motor control program generated by Workbench_6.3.0, Motor Pilot_6 can communicate normally. However, when sending manually using a serial port assistant, it always replies with 0F 04 04 C0 and cannot communicate normally. This issue does not occur with the motor control program generated by Workbench_6.2.1.

[16:15:36.452]TX→◇85 FF FF BF 
[16:15:36.460]RX←◆05 C3 00 D4
[16:15:41.357]TX→◇05 C3 00 D4 
[16:15:41.369]RX←◆05 C3 00 D4
[16:15:48.537]TX→◇06 00 00 60 
[16:15:48.543]RX←◆F6 00 00 C0
[16:15:59.895]TX→◇49 00 00 70 10 00 28 00 
[16:16:01.375]TX→◇49 00 00 70 10 00 28 00 
[16:16:01.380]RX←◆0F 04 04 C0 0F 04 04 C0

[iskan]

I do not know:)

[GMA · Accepted solution]

Hello @honkerhz,

Going through "Motor Control Protocol Suite" documentation available via "Motor Control Workbench Tool>About>Documentations>Documentation", "User Manual" Tab, "Motor Control Protocol Suite"; the RX response starting with 0F means error and 04 means "Bad Header: Verification of the CRCH field of the last packet received from the Controller failed" but could you please check two points:

1. That "Intra Packet Pause" is implemented as specified on user manual (between 49 TX Command header and its payload)
2. Try by waiting a RX response for each TX command before sending a new TX command