On-site equipment access
Provides access methods for CNC, PLC, robots, instruments and other equipment. The brand, model and agreement need to be confirmed according to the project.
Provides protocol adaptation, edge caching, data preprocessing and platform interfaces for CNC, PLC, industrial robots and field equipment. The specific access scope is subject to the equipment list and field testing.
The gateway is used for equipment collection, remote maintenance, edge processing, platform access and on-site monitoring. The specific functions are determined according to equipment conditions and project configuration.
Provides access methods for CNC, PLC, robots, instruments and other equipment. The brand, model and agreement need to be confirmed according to the project.
Supports remote device diagnosis, program download and parameter configuration. Specific permissions are configured according to network and security policies.
Perform status statistics, trend analysis and rule warnings based on collected data; predictive maintenance needs to combine data quality and model verification.
Supports form configuration, MQTT connection management and data preprocessing, and adapts according to the target platform protocol and interface requirements.
Supports local data processing and rule configuration on the gateway side. The specific operation scope is confirmed according to the gateway version and project requirements.
Supports equipment status display, trend query and customized billboards. Display fields are configured according to collection points and business needs.
Supports access through Ethernet, serial port, etc., and provides Web configuration, variable library and custom variable functions. The accessibility of CNC, PLC, robots, instruments, and sensors needs to be confirmed based on the brand, model, protocol, and point table.
Supports configuring applications such as data storage, rule processing, and dashboards on the gateway side. Whether to deploy and run the scope depends on the gateway version, resources, and project requirements.
The verified application configuration can be exported and reused in the same model and environment. Dependencies, permissions, and data points need to be rechecked before deployment.
The data format and push rules can be configured through forms, Lua scripts and MQTT connection management. The specific docking method is determined according to the target platform protocol, authentication method and security requirements.
Verified scripts and configurations can be exported, and the version, variables, and interface environment need to be checked before reuse on other gateways.
The following brands and protocols are common access directions. The actual support range is subject to the device model, controller version and field testing.








Is it for CNC device networking, PLC data collection, remote maintenance, or unified access for multiple devices on-site?
Confirm brand, model, controller version, protocol openness, and whether custom points are needed.
Plan the single unit pilot, single line deployment, or multi-point expansion based on the number of Ethernet ports, serial ports, and wireless links.
Provide device brand, controller model, on-site network, and the fields you want to collect. We can confirm the integration plan first, then decide the gateway type.