The user found the CR5 TCP link only partially working: reading position and setting acceleration worked, but move commands failed and disconnected with an enable error, with commands routed to the wrong IP. He reported a week later that a robot firmware update fixed it.
- Issue resolved by a firmware update
- Out-of-box firmware broke TCP/IP motion commands from third-party software
- Similar symptoms later reported by a CR12 user
