Table of Contents

Amit

This page is the central starting point for connecting AMiT controllers to Mervis SCADA. AMiT PLCs can communicate with Mervis in two ways, depending on the age of your controller and firmware:

If you are unsure which method applies to your controller, contact AMiT technical support or Mervis technical support.

Newer AMiT controllers offer native support for Mervis CloudAccess, using AMiT's own WebSocket protocol directly in the controller. This removes the need for a separate proxy tunnel — the PLC connects directly to the CloudAccess cloud service, and the Mervis SCADA project is generated from a WebSocket mapping file.

  1. Configure CloudAccess on the PLC.
    Set up the connection to the CloudAccess server in DetStudio. See Mervis CloudAccess - AMiT for certificate setup and configuration steps. Requires DetStudio version 3.2.12 or newer.
  2. Generate the mapping file.
    Use the helper application AmitWebSocketUtil.exe to generate an XLSX mapping file directly from the project uploaded to the PLC.
  3. Generate the Mervis SCADA project.
    Upload the mapping file to the Project Generator and set the correct parameters.

For the full step-by-step procedure, download links, and example generator parameters, see: Amit WebSocket - Integration.

Method 2: DB-Net/IP via AmitProxy (Legacy)

For older AMiT controllers, communication is handled through the Mervis Proxy Service using the DB-Net/IP protocol. This method requires configuring a ProxyID, password, and proxy server address on the controller, and using the AtouchProxy helper application for third-party tools (DetStudio, ViewDet) that don't support Mervis Proxy natively.

For full configuration details — including server addresses, ports, ProxyID/password setup, application code examples, and AtouchProxy — see: Amit DB-Net/IP - AmitProxy.

Choosing a Method

Method Best for Requires
AMiT WebSocket + CloudAccess Newer controllers, new installations DetStudio 3.2.12+, CloudAccess configuration
DB-Net/IP + AmitProxy Older controllers, existing DB-Net installations ProxyID/password, AtouchProxy (for legacy tools)

For a broader overview of Mervis Proxy vs. CloudAccess (not AMiT-specific), see: Proxy & CloudAccess.

Technical Support