--- title: "IEC 102 Client | Module Instance | N3uron KB V.1.20" slug: "iec-102-client-module-instance" description: "IEC 102 Client is a N3uron module designed to allow users to quickly and easily connect to any electrical meter supporting IEC60870-5-102 (REE) protocol…" updated: 2021-12-15T11:29:20Z published: 2021-12-15T11:29:20Z canonical: "docs.n3uron.com/iec-102-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 **Iec102Client** after **N3uron** installation is to instantiate an Iec102Client 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 Iec102Client**.** **![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/1-Creating%20new%20module%20instances.png)**Figure 1. Creating new module instances By setting the **Module type** to **Iec102Client**, the created instance will automatically become an **Iec102Client** instance. Once saved, **Iec102Client** should appear in the module list in bold because there are unsaved changes. ![](https://cdn.document360.io/54093ab5-6b22-4542-a265-04377931f11a/Images/Documentation/2-Setting%20the%20instance%20type.png)Figure 2. Setting the instance type Additionally, each instance can be configured with 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** services starts. Otherwise, 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 it 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 it has gone offline. Note:In addition to configuring this instance, each module has a Logger and API section which needs to be configured separately. The default settings will be sufficient for this, but users will need to actively open the Logger and API configuration settings and save the default values to fully apply the settings.