Omron NJ Ethernet

review the following information for setting up and configuring the omron nj ethernet driver litmus edge compatible series compatibility parameter compatible items driver type ethernet validated devices/series nj series replaces gen 1 driver(s) omron nj ethernet (gen1) to set up and configure this device in litmus 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 litmus 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 the default port for omron nj series plcs is 44818 step 2 set up the plc device in litmus edge devicehub configure the following parameters when you connect a device with this driver update default values to the specific setup of your device parameter value type omron driver omron nj ethernet network address the device ip address you recorded in step 1 network port 44818 advanced show advanced options (disabled by default) response timeout 2000 (ms) maximum packet size 1994 (bytes) optional step 3 configure the list of registers when you add tags to the connected device, refer to the following register table and tag parameters refer to the following additional resources organize device and tag data by using metadata docid\ mu 6j6zhi0cvchdad0w8n tag formula variables docid\ io7xgyrdvv vmpnfxoaci register table note this driver uses symbolic (tag based) addressing enter the tag name exactly as it appears in your plc program the driver supports reading basic data types from arrays and user defined types (udts) by specifying the full tag path (for example, myarray\[0] or myudt member) name value types access type description r bool, sint, int, dint, lint, usint, uint, udint, ulint, byte, word, dword, lword, real, lreal, string, enum, date, time, date and time, time of day r/w read/write plc tags supported data types the driver supports the following omron nj data types bool boolean (bit) sint short integer (8 bit signed) usint unsigned short integer (8 bit unsigned) int integer (16 bit signed) uint unsigned integer (16 bit unsigned) dint double integer (32 bit signed) udint unsigned double integer (32 bit unsigned) lint long integer (64 bit signed) ulint unsigned long integer (64 bit unsigned) real floating point (32 bit) lreal long real (64 bit floating point) time integer time in nanoseconds date format yyyy mm dd time of day format hh\ mm 000000000 date and time format yyyy mm dd hh\ mm 000000000 string utf 8 string (default length 256, custom lengths supported) for complete data type specifications, refer to nx and nj basic data types and ranges tag parameters name enter the plc tag name exactly as it appears in your controller program for array elements, use bracket notation (for example, tagname\[0]) for structure members, use dot notation (for example, structname member) value type select a data type from the drop down list the available options correspond to the omron nj data types listed in the register table polling interval enter a value in milliseconds this determines how often the tag should poll the register for data tag name enter a name for the tag in litmus edge 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 customize nats messages to be published only when the value parameter changes to a new one 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 it can then be used to find, use, and reuse particular instances of data 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)