--- title: "DNP Client | Module Instance | N3uron KB V.1.20" slug: "dnp-client-module-instance" description: "DNP Client is a N3uron module designed to provide a reliable way of connecting to any Distributed Network Protocol (DNP3) compliant device through…" updated: 2022-03-29T07:58:24Z published: 2022-03-29T07:58:24Z canonical: "docs.n3uron.com/dnp-client-module-instance" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.n3uron.com/llms.txt > Use this file to discover all available pages before exploring further. # Creating Module Instances The first step when using DnpClient after N3uron installation is to instantiate a DnpClient module: - Open **N3uron** and navigate to the “Config” menu. - Click on “Modules”, then create a new module. This instance can be given any name (except names with special characters like ‘.’, ‘/’, etc.), although users are recommended to name instances in a similar way to the name of the module being instantiated for easy identification. In this example, it has been named **DnpClient**. ![01-new-module-creation](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/01-new-module-creation.png)Figure 1: Creating new module instances By setting the module **type** to **DnpClient**, the created instance will automatically become a **DnpClient** instance. Once saved, **Dnp3** should appear in bold in the module list because there are unsaved changes. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/02-Setting-the-instance-type.png) Figure 2: Setting the instance type Each instance can also be configured according to the following options: - **Required:** When set to enabled and when this module is receiving data from other N3uron nodes, all links will be paused whilst the module is offline to avoid data loss. If disabled, this module will have no effect on links when offline. - **Start:** This section controls how the module behaves when the N3uron service is started (which also includes service restarts). - **Enabled**: If true, the module will automatically start when the N3uron service starts. If disabled, the module must be started manually. - **Start delay:** When automatic start is enabled, this setting is used to control how much delay there should be between starting the N3uron service and starting the module. This value is displayed in milliseconds. - **Monitor:** This section is used to monitor the status of each module, as well as to enable automatic restart if the module goes offline. - **Automatic restart:** If true, whenever the module goes offline (except when manually stopped by the user), the module will automatically restart. - **Restart delay:** Determines the delay before restarting the module after going offline.