Set Up Communication between External Device and Mech-MSR via TCP ASCII

You are viewing an old version of the documentation. You can switch to the documentation of the latest version by clicking the top-right corner of the page.

TCP ASCII Communication Workflow

The workflow of TCP ASCII communication is shown in the figure below.

tcp workflow

  • In the above figure, the command name is separated from the parameter by the English comma (default value). If you need to use another delimiter in the actual project, set the string delimiter parameter in the Communication Configuration window.

  • In addition to the return command, the 3D measurement system also allows you to obtain measurement results with other commands. For details, refer to TCP ASCII Commands.

The workflow of TCP ASCII communication is explained in detail as follows:

  1. A TCP client (an external device such as a PLC) establishes a TCP connection with the 3D measurement system (Mech-MSR).

  2. The TCP client sends a trigger command to trigger the project to run.

  3. Mech-MSR returns the status code for the command. For example, if the project is triggered successfully, Mech-MSR returns 0.

  4. The TCP client sends a return command to obtain the measurement results. After Mech-MSR receives the command, it starts the countdown for 10 seconds.

  5. Mech-MSR returns results. For example, if the project is run successfully, Mech-MSR returns the measurement results. If the project has not finished running within 10 seconds, Mech-MSR returns the error code -3.

The next section on TCP ASCII commands will show the commands supported and analyze the returned results.

We Value Your Privacy

We use cookies to provide you with the best possible experience on our website. By continuing to use the site, you acknowledge that you agree to the use of cookies. If you decline, a single cookie will be used to ensure you're not tracked or remembered when you visit this website.

  • Preference
  • I accept
  • I don't accept