Reference · built on requestConnectorPLC, SCADA & MES

Sysmac NJ/NX

Network-published variables from NJ/NX-series machine controllers through the CPU Unit's OPC UA server, plus EtherNet/IP tag data.

Request accessPricing ↗

About

Sysmac NJ/NX-series controllers are OMRON's machine automation CPUs. NX701, NX502, NX102, and NJ501 units run an OPC UA server on the built-in EtherNet/IP port alongside normal EtherNet/IP traffic, reached at opc.tcp on port 4840 by default. The server follows the Embedded 2017 UA Server Profile and the PLCopen Information Model 1.00, and exposes the global variables, function block instance variables, and companion-specification variables you mark with the Network Publish attribute in Sysmac Studio. The same port serves cyclic tag data links and CIP explicit messages that read and write variables by name.

An operator on Fibric subscribes to published variables, watches states and counters, and proposes a variable write for your approval. Writes respect the roles you assign in Sysmac Studio and leave a receipt.

This is a reference listing. It documents what Fibric would read from Sysmac NJ/NX and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Global variables published to OPC UA with the Network Publish attribute, browsed under DeviceSet in the controller's address space
  • Variables inside user-defined function block instances, published when the instance is in the variable table and its program is assigned to a task
  • Subscriptions with monitored items: up to 100 subscriptions and 2,000 monitored items server-wide (20,000 on NX701 from unit version 1.34)
  • Structures published as one node or expanded per member, and arrays expanded per element, as set in the Node Setting
  • Cyclic input and output tag sets exchanged by EtherNet/IP tag data links between the controller and other nodes
  • Variable values read by name through CIP explicit messages to the built-in port, using the CIP Read Data service

Proposed actions

  • Target capability: propose a value for a published variable the CPU lets an OPC UA client write, subject to the user's role
  • Target capability: propose a write to a variable by name through a CIP explicit message on the built-in EtherNet/IP port

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Hold a lot when inspection values trip

    Subscribe to inspection results and lot number variables, compare each result with its spec, and propose a quality hold on the lot before it ships.

    With Quality Hold

  • Confirm a clean-in-place cycle ran to plan

    Read CIP phase, temperature, and duration variables, check each phase against the recipe, and propose sign-off or a repeat cycle.

    With Clean Cycle

  • Close the loop on line stops

    Watch machine state and stop-reason variables, stamp each stop, and open a downtime record with the reason the controller reported.

    With Line Downtime

  • Feed controller health into maintenance

    Trend axis load, temperature, and cycle counters published from the controller, and propose a work order when a trend crosses its line.

    With Predictive Maintenance

Requirements

  • An NX701 (unit version 1.24 or later), NX502 (1.60 or later), NX102 (1.30 or later), or NJ501 (1.17 or later) CPU Unit
  • Sysmac Studio at the version the manual lists for that unit, to set the OPC UA Server Settings, security settings, and publishing settings
  • Variables marked with the Network Publish attribute and, for OPC UA, a namespace selected to publish
  • The connector's client certificate registered in the CPU's Trusted Certificate List, and the server certificate exported to the client
  • One of the five session slots on the CPU Unit, since the server admits at most 5 sessions
Authentication
OPC UA user name and password with an assigned role (Operator or Observer), or anonymous login where permitted, over a channel secured by X.509 certificates held in the CPU's Trusted Certificate List with SignAndEncrypt, Sign, or None.

Limits

  • At most 5 sessions, 100 subscriptions, and 2,000 monitored items per server (20,000 monitored items on NX701 from unit version 1.34)
  • A published variable is capped at 60 KB, an array at 2,048 elements, and a structure at 100 members and three nesting levels
  • Unions, system-defined variables, and arrays whose index does not start at 0 cannot be published
  • Roles apply to namespaces and function block instances only; every user can read any published global variable

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Sysmac NJ/NX ↗

Questions and answers

Which variables can the connector see?
Only those you publish. In Sysmac Studio you set the Network Publish attribute on global variables, choose namespaces and function block instances to publish, and decide whether structures and arrays expand into member nodes. System-defined variables cannot be published. The address space appears under Root > Objects > DeviceSet.
How is access to the server secured?
Application authentication uses X.509 certificates, with 32 slots each for trusted, CA, and rejected certificates. Messages can be SignAndEncrypt or Sign with Aes256Sha256RsaPss, Aes128Sha256RsaOaep, Basic256Sha256, Basic256, or Basic128Rsa15. Users log in with user name, password, and role, or anonymously if permitted. OMRON advises clearing None, Basic128Rsa15, and Basic256.
What are the server's size limits?
5 sessions, 100 subscriptions, and 2,000 monitored items server-wide; 10,000 published variables; 100 published structure definitions. NX701 units from version 1.34 raise monitored items to 20,000 and published variables to 100,000. A single variable may not exceed 60 KB or 2,048 array elements.
Ask about Sysmac NJ/NX

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Sysmac NJ/NX through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy