Indy Dedicated Communication Protocol (IndyDCP)
IndyDCP is a dedicated communication protocol for controlling Neuromeka's Indy robots, and supports functions that can perform basic setting, control, and data acquisition of the robot. Both IndyDCP and ModbusTCP can be primaryly used to receive robot data and to send commands using external devices such as PC, PLC, and the other devices.
Robot setting, task teaching, and robot programming are commonly performed by Conty, which is Neuromeka's official teach pendant application. The commands such as executing and stopping the registered robot program can be performed by external devices that use IndyDCP or ModbusTCP as well as Conty.
Both IndyDCP and ModbusTCP use dedicated TCP communication and communicate through TCP/IP network protocol. To use TCP/IP protocol, control box (STEP) must be connected with external devices that will use the TCP/IP communication protocol through Ethernet. Here, IndyCB (control box) or STEP that executes Indy Framework will be a server. The Table below shows connection information of IndyDCP server.
|IP Adress||IP adress of STEP Ethernet|
|Maximum connetction number||1|
|Maximum communication rate||100Hz (10ms)|
- IndyDCP server: is implemented in IndyFramework and executed in STEP with robot control program.
- IndyDCP client: is implemented in external devices using the protocol described in this document, and can communicate with the server.
Neuromeka also provides example codes of IndyDCP client. These libraries allow users to call functions without having to know the protocol of a dedicated communication. Currently, IndyDCP example codes and examples written by Python, C++ (Linux/Windows), MATLAB, and Labview are provided. Please refer to following links for detailed description.