FANUC i-Series MTConnect Machine Adapter
Dynamic MTConnect Adapter for qualified FANUC i-Series controls using the FANUC FOCAS API over Ethernet.
The FANUC FOCAS MTConnect Adapter is available after TAMS confirms the FANUC control generation, Ethernet FOCAS access, Windows deployment host, network routing, firewall rules, and required MTConnect observations. The adapter is not presented as plug-and-play.
Quick Human Summary
This adapter helps qualified FANUC FANUC i-Series equipment publish useful MTConnect data for monitoring, reporting, validation, and downstream manufacturing systems.
Likely fit: Evaluate a qualification-required Windows MTConnect adapter for a FANUC i-Series controller using Ethernet FOCAS.
TAMS will verify the exact equipment, source access, network boundary, requested observations, and validation scope before confirming the quote.
Connection Method: FANUC FOCAS API over Ethernet
You do not need every answer before contacting TAMS. Engineers can help qualify fit, estimate effort, and prepare a realistic quote.
Connect FANUC controller data to an MTConnect pipeline through the FOCAS library.
FOCAS provides access to supported controller data; MTConnect provides a standardized model for communicating that data to downstream systems. They address different parts of the integration.
The adapter generates the MTConnect Device model dynamically by interrogating the qualified FANUC FOCAS source at startup. It discovers machine structure such as axes, spindles, paths, and channels exposed by the control.
A nominal 5-axis machine may expose more than five axes because machine-tool builders can define auxiliary systems such as feeders, tool changers, pallet systems, chip conveyors, or part conveyors as axes and/or paths. Runtime model changes are not claimed unless they are explicitly qualified later.
TAMS maps the available Ethernet FOCAS data into an MTConnect® information model. Supported observations depend on controller generation, enabled FOCAS access, machine-builder configuration, and the project scope. HSSB support is not claimed by this catalog record.
The adapter currently runs on Windows OS only and commonly runs on a customer-owned network server or controller-adjacent PC. TAMS confirms FOCAS enablement, CNC IP address and port, network drops, firewall rules, required DataItems, and downstream interfaces during scoping.
Supported Equipment
Compatibility is qualified from the exact controller, software or firmware, enabled interface, machine-builder configuration, and requested observations. A manufacturer name alone is not a support guarantee.
What TAMS will verify: The generated Device model varies by FANUC control generation, enabled FOCAS access, machine-tool-builder configuration, and the axes, spindles, paths, and channels exposed by the machine.
What You Get / Common Outputs
Published outputs are qualified during adapter assessment. TAMS will confirm the MTConnect observations needed for your downstream systems before quoting or commissioning.
Integration Journey
Review custom MTConnect adapter development and integration services or use the MTConnect Adapter Guide to prepare controller and network details.
Product data
Review delivery paths, qualification facts, and validation evidence used to scope the next step.
The FANUC FOCAS MTConnect Adapter is available after TAMS confirms the FANUC control generation, Ethernet FOCAS access, Windows deployment host, network routing, firewall rules, and required MTConnect observations. The adapter is not presented as plug-and-play.
This report is compliant with no validation errors. The Validator warnings are associated with Description elements used to document component and data item meaning in the generated XML; these descriptions help preserve source context and future-proof understanding of the Device model.
Plan controller access, delivery, installation, and validation.
Review how validation evidence is produced and interpreted.
Review Static, Dynamic, Configured, and Custom modeling patterns.
Review Type, SubType, Units, and Component context.
Integration Details
These details remain available for technical review, but they are grouped here so the page stays easier to scan.
Interface: FANUC FOCAS API over Ethernet
FANUC 16i; FANUC 18i; FANUC 21i; FANUC 30i; FANUC 31i; FANUC 0i; PowerMate-i; Other qualified FANUC i-Series controls
A Dynamic Information Modeling Strategy generates the MTConnect Device model by interrogating the equipment, controller, or source interface at adapter startup or runtime.
Adapter note: The MTConnect Device model is generated dynamically by interrogating the FANUC FOCAS source at adapter startup.
What TAMS will verify before confirming this adapter is the right fit.
You do not need every answer before contacting TAMS. These are the details our engineers use to confirm fit, estimate effort, and prepare a realistic quote.
The reviewed catalog scope is: FANUC 16i; FANUC 18i; FANUC 21i; FANUC 30i; FANUC 31i; FANUC 0i; PowerMate-i; Other qualified FANUC i-Series controls. The generated Device model varies by FANUC control generation, enabled FOCAS access, machine-tool-builder configuration, and the axes, spindles, paths, and channels exposed by the machine.
The reviewed source interface is FANUC FOCAS API over Ethernet.
Published coverage is limited to: The MTConnect Device model is generated dynamically by interrogating the FANUC FOCAS source at adapter startup.. Boundaries: Ethernet FOCAS is confirmed supported; HSSB support is uncertain and is not claimed by this catalog record.; FANUC FOCAS is often disabled by default and usually must be enabled on the control.; No other known FANUC licensing or options requirements are currently known.; Exact observations vary by controller generation, enabled FOCAS access, and machine-tool-builder configuration.; Commonly available observations include availability and emergency stop.; Controller and execution state may be available where exposed by FOCAS.; Program, feed, spindle, axis, alarm, override, path, part count, tool, and cycle-related observations are commonly expected where exposed by the qualified control, but are not guaranteed universally.; A nominal 5-axis machine may expose more than five axes because builders may define auxiliary systems such as feeders, tool changers, pallet systems, chip conveyors, or part conveyors as axes and/or paths.; Runtime Device model changes are not claimed unless explicitly confirmed in a future adapter qualification..
This record currently lists software delivery only. Edge-Connect availability is not implied.
A public implementation example is linked for this record. The report applies only to the reviewed sample and scope.
HTTPS, antiforgery validation, input limits, and reCAPTCHA protect public form submissions. Review the safeguards.
Inspect the MTConnect adapter catalog, online validator, and implementation guides directly.
Call +1 (317) 907-8897 or email sales@tams.ai for sales, support, privacy, or security questions.