18
COM-port parameters are fixed on the controller-side:
Speed:
115200 baud
Frame size:
8 bits
Stop-bits:
1 bits
Parity:
none
Flow control:
none
Byte receive timeout:
400 ms
*
USB port simulates COM port on a PC.
All the commands are the same for all communication protocols (see “6.4 Controller
Commands”).
For more information please see “RS232 communication example” software and C# code
(Visual Studio project).
6.2 Ethernet protocol description
When using “Ethernet” port all communication between controller and PC (or other device) is
established by using TCP/IP communication protocol. When controller is connected to “Ethernet”
port it constantly tries to connect to device (server) which IP address is specified in controller’s
memory. To connect and communicate with controller you should create dedicated TCP server
which will send and receive data to and from controller.
To achieve connection between server and the controller you must configure specific
addresses and ports in the controller and the server (they must match in both devices). You can
change controllers IP address and port using “TCP sample” software.
When creating server on your device don’t use dynamic IP (DHCP), because your server IP
address should be static for controller to maintain the connection.
All the commands are the same for all communication protocols (see “6.4 Controller Commands”).
For more information please see “TCP sample” software and C# code (Visual Studio project).
6.3 Command execution
All data transfers are initiated by the PC, meaning that the controller waits for incoming
commands and replies accordingly. Each command is followed by the controller response, with
rare exceptions of some service commands. One should not send another command without
waiting for the previous command answer.
Command processing does not affect real-time engine control (PWM and etc).
