Configure Communication Trigger Rules

You are currently viewing the documentation for the latest version (2.2.0). To access a different version, click the "Switch version" button located in the upper-right corner of the page.

■ If you are not sure which version of the product you are currently using, please feel free to contact Mech-Mind Technical Support.

This section describes how to configure communication trigger rules.

Custom trigger rules define when a custom communication service triggers project execution. When a custom communication service meets configured trigger conditions, the software automatically triggers the corresponding custom communication project.

For custom communication services of the TCP Server or TCP Client type, see Configure Custom Communication Trigger Rules (TCP Server/TCP Client).

For custom communication services of the TCP Server or TCP Client type, the trigger condition defaults to "Trigger upon receiving data" and cannot be modified. When the service receives any data from the peer side, the software triggers the custom communication project.

For PLC-type custom communication services, see Configure Custom Communication Trigger Rules (PLC-Type Services).

  • PLC-type custom communication services include Siemens S7 Client, Modbus TCP Slave, and Mitsubishi MC Client custom communication services.

  • For PLC-type custom communication services, when the service reads the specified register variable on the peer PLC and its value changes to the trigger value, the software triggers the custom communication project.

Is this page helpful?

You can give a feedback in any of the following ways:

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