---
title: Omron-NJ-Ethernet (Gen1.3)
slug: manufacturing-connect-edge/omron-nj-ethernet-gen13
docTags:
createdAt: 2022-07-04T16:09:33.000Z
---
Review the following information for setting up and configuring the Omron-NJ-Ethernet (Gen1.3) driver.
# Manufacturing Connect Edge Compatible Series
| Compatibility parameter | Compatible items |
| ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Driver type** | Ethernet |
| **Validated devices/series** | [NJ](https://www.ia.omron.com/products/category/automation-systems/programmable-controllers/controller-nj-series/index.html)
[NX1P](https://www.ia.omron.com/products/category/automation-systems/programmable-controllers/controller-nx1p/index.html)
When configuring tags for this driver, you must enter the case-sensitive register name exactly as it is defined in the PLC. See the *Free Tags* section below to learn more. |
To set up and configure this device in Manufacturing Connect Edge, you will need to do the following:
- Step 1: Set up and Configure the PLC Device
- Step 2: Set up the PLC Device in Manufacturing Connect Edge DeviceHub
- Step 3: Configure the List of Registers
# Step 1: Set up and Configure the PLC Device
If the device is configured for Ethernet access, find its network parameters. Otherwise, follow the steps below.
**To configure your device:**
1. Note down the following information and refer to it as needed.
**Device**: Omron NJ Ethernet
**Communication I/F**: Ethernet. Refer to the following figure.
2. Connect the device with a USB cable.
::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/9oG-E_KPeouzfIa_vQkQk_omron-nj-ethernet.png" size="80" width="1248" height="379" caption="Reference image of device" position="center" darkWidth="1248" darkHeight="379" showCaption="true" indent="2"}
3. Launch Sysmac Studio v1.20.1.0 software, select **Controller > Communication Setup**, and then set up the IP address.
4. Use a direct connection in **USB > USB Communication Test**.
# Step 2: Set up the PLC Device in Manufacturing Connect Edge DeviceHub
Configure the following parameters when you [Connect a Device](docId\:RFVIJdxz7DBAd8mwbismA) with this driver. Update default values to the specific set up of your device.
| Parameter | Value |
| ------------------- | -------------------------------------------- |
| **Type** | Omron |
| **Driver** | Omron NJ Ethernet NJ301-1100 |
| **Network Address** | The device address you defined during Step 1 |
| **Port** | 44818 |
# Step 3: Configure the List of Registers
When you [Add Tags](docId\:iOaNZd2AwqnkuppgeE3Eh) to the connected device, refer to the following tag parameters and available value types.
Refer to the following additional resources:
- [Device and Tag Metadata Use Case](docId\:f-B720niVlLBer44RfyHN)
- [Tag Formula Variables](docId\:PWd-7P-kZjXkt_pYAwAOw)
## Free Tags
This driver doesn't have a list of available register names in the DeviceHub *Add Tag* form.
To add tags, you must enter the case-sensitive register name exactly as it is defined in the PLC.
A **Connected **status for the device won't display until a tag with a correct register name is created and a value is generated (not null/blank).
## Available Value Types
The following value types are available for Manufacturing Connect Edge version 3.11.0 and later.
- `bool`
- `sint`
- `usint`
- `byte`
- `int`
- `uint`
- `word`
- `dint`
- `udint`
- `dword`
- `real`
- `lint`
- `ulint`
- `lword`
- `lreal`
- `string`
- `time`
- `date`
- `date_and_time`
- `time_of_day`
The following value types are available for Manufacturing Connect Edge version 3.10.0 and earlier.
- `bool`
- `sint`
- `usint`
- `byte`
- `int`
- `uint`
- `word`
- `dint`
- `udint`
- `dword`
- `real`
## Reading DINT Arrays
If you want to read a DINT array, you need to write the element number of the array that you want to read in square brackets along with the tag name.
:::hint{type="info"}
**Example**: If the array name is ArrayDint and you want to read the third element of the array, the format for the tag name in Manufacturing Connect Edge is `ArrayDint[2]`.
:::
## Tag Parameters
- **Name**: Enter the case-sensitive register name exactly as it is defined in the PLC.
- **Value Type**: Select a data type from the drop-down list.
- **Polling Interval**: Enter a value in seconds. This determines how often the tag should poll the register for data.
- **Tag Name**: Enter a name for the tag.
- **Description** (Optional): Enter a description for the tag.
- **Tag Formula**: Enter a formula for the tag to process the generated data. Two variables are permitted: `value` (current tag value) and `timestamp` (current tag UNIX time in milliseconds). The following math functions are available:
- sin
- cos
- sqrt
- tan
- power: power(`x`) performs the operation `10^x`.
- log: log(`x`) is the natural logarithm (the logarithm is in base `e`).
- exp: exp(`x`) performs the operation `e^x`.
- **Only Publish on Change of Value**: Select the checkbox to only publish NATS messages when the *value *parameter changes to a new value. *Change of Value* only applies to boolean, numeric (such as int or float), and simple string data types. It does not apply to complex types, such as JSON or array. Poll-once topics will not be affected by *Change of Value* settings. These topics will still only see a single message.
- **Meta Data**: Metadata summarizes basic information about data. This feature allows you to define key-value pair data for the device output payload later on. Metadata can then be used to find, use, and reuse particular instances of data.
:::hint{type="info"}
**Note**: If you use special characters in meta data key names, the special characters are replaced with underscore characters in the payload. This can cause two key names to be combined into one. For example, configuring the key names a\*\*b and a&\&b will cause only one key name to be created (a\_\_b).
:::