How to Integrate an Industrial Electric Screwdriver with PLC and MES
Short answer: A typical integration connects the electric screwdriver or its controller to the PLC for real-time machine control, then sends tightening results to the MES for traceability and analysis. Before commissioning, define the command signals, result fields, communication protocol, product identification method, retry logic and offline data strategy. The integration should prevent the wrong program from running, return a clear OK or NG result, and link every fastening record to the correct product and station.
Industrial tightening integration involves more than opening a network port. The tool, PLC and MES must agree on when a cycle can start, which tightening program applies, how results return, what happens after a fault and how records remain complete during a network interruption. A clear interface specification prevents many commissioning delays.
PLC and MES Have Different Roles
System | Primary role | Typical tightening functions |
Electric screwdriver and controller | Execute and monitor the fastening cycle | Run the selected Pset or Job, measure torque and angle, evaluate limits, store results and curves. |
PLC | Control the station in real time | Verify interlocks, select a program, enable the tool, issue start or reset commands and route OK or NG logic. |
MES | Manage production records and traceability | Provide work-order or product context, receive fastening data, link results to serial numbers and support quality analysis. |
The PLC normally handles deterministic station control. The MES manages the production context and long-term record. Some architectures connect the tool controller directly to the MES, while others route all production data through the PLC or an edge computer. The right architecture depends on line standards, data volume and the required response time.
A Typical Tightening Data Flow
The station identifies the workpiece through a barcode, QR code, RFID tag or production order.
The PLC or production system selects the correct Job or Pset for the product and fastening point.
Interlocks confirm that the workpiece, fixture, socket, tool position and safety conditions are ready.
The PLC enables the screwdriver and sends the start command, or the operator activates an authorized handheld tool.
The screwdriver executes the programmed tightening strategy and evaluates torque, angle, time and other limits.
The controller returns the result, measured values and error information to the PLC.
The PLC allows the sequence to continue after an OK result or starts the defined NG recovery process.
The controller, PLC or edge layer uploads the fastening record to the MES and links it to the product identifier.
Step 1 Define the Control Interface
Start by listing every command and status that the station needs. Avoid beginning software development before the control sequence is approved. A minimum interface often includes tool enable, start, reset, forward or reverse selection, program selection, ready, running, OK, NG and fault status.
For automated stations, the PLC should verify the complete permissive condition before enabling tightening. Typical interlocks include fixture closed, part present, correct socket selected, tool at position, screw available and safety circuit healthy. The PLC should also prevent a second start command while the controller is still processing or reporting the previous result.
Step 2 Choose the Communication Method
Method | Best suited to | Considerations |
Digital I O | Simple start, reset, interlock and OK or NG exchange | Fast and easy to diagnose, but carries limited program and result data. |
RS485 | Compact tools and serial device communication | Useful for commands and results when the system supports the correct serial protocol. |
TCP IP or open protocol | Structured commands, program selection and result transfer | Supports richer data, but requires message definition, connection monitoring and retry logic. |
Modbus TCP | PLC-centered integration using mapped registers | Familiar to many integrators. Register ownership, data types and update timing must be documented. |
Industrial fieldbus | Standardized machine networks such as PROFINET, EtherNet IP or EtherCAT | Check the selected controller, optional interface hardware, cyclic data map and commissioning files. |
Danikor tightening systems can support combinations of digital I/O, RS485, TCP/IP, Modbus TCP and optional industrial bus communication, depending on the selected tool and controller. Confirm the available interface before finalizing the electrical design. Do not assume that every protocol or data field is standard on every configuration.
Step 3 Define Program Selection and Product Binding
The production system must activate the correct tightening program before the tool starts. A Pset normally contains the tightening parameters for one fastening condition. A Job can organize several Psets or tightening points into a controlled sequence. The PLC can select the program through I/O, mapped data, a protocol command or barcode association.
Program selection should include confirmation. After the PLC sends the requested Pset or Job, the controller should return the active program. The station can then compare the requested and active values before enabling the cycle. This handshake prevents the tool from running an earlier program after a changeover or communication interruption.
For mixed-model lines, bind the tightening result to the workpiece, station and program. Danikor controller configurations can support barcode-linked program activation and multi-level association with station, workpiece, Job and Pset information. The exact binding structure should match the customer's MES data model.
Step 4 Specify the Tightening Result Record
Define the data record before building the interface. If the MES schema is incomplete, teams often discover late in commissioning that key identifiers or failure details are missing. A practical record may contain:
Product serial number, work order and variant
Station ID, tool ID and controller ID
Fastening point, Pset and Job
Final torque, final angle and cycle time
OK or NG status and error code
Timestamp, operator ID and shift when required
Tightening curve reference or curve data for critical joints
Use consistent units and field definitions. State whether the reported torque is peak torque, final torque or another value defined by the tightening strategy. Record the controller time source and synchronize clocks across the line so that production events can be reconstructed accurately.
Step 5 Design the OK and NG Sequence
An OK result should allow the station to advance only after the controller has completed the cycle and the PLC has stored the result reference. An NG result needs a defined recovery path. The line should distinguish between a fastening defect, a tool alarm, a communication failure and an operator sequence error.
Decide who can retry an NG fastening and how many retries the process allows. A repair program may use different parameters from the original cycle. Permission control can restrict program changes and repair actions to authorized roles. The MES record should preserve the original NG result as well as the final disposition.
Step 6 Protect Data During Network Interruptions
Production should not lose fastening records when the MES or plant network becomes unavailable. The controller or edge layer should store results locally, assign a unique record identifier and resend pending records after communication returns. The receiving system should reject duplicate uploads without deleting valid history.
Danikor controller options provide local storage for tightening results and curves. Storage capacity varies by platform and configuration. Define the maximum expected outage, estimated records per shift and curve-retention requirement, then verify that local storage covers the risk. The station should generate an alarm before the buffer becomes full.
Step 7 Commission with Normal and Failure Tests
Commissioning should test both the normal fastening sequence and the faults that the architecture must manage. Run a documented test for each command, status, result field and recovery condition.
Correct and incorrect Pset selection
PLC start while the tool is not ready
OK, tightening NG and controller fault results
Barcode mismatch and unknown product
PLC, controller or MES communication loss
Power interruption during and after tightening
Local buffering, reconnection and duplicate-data handling
User permission and repair-cycle control
Compare the controller result, PLC record and MES record for the same fastening cycle. Torque, angle, status, identifiers and timestamps should remain consistent across all three layers.
Common Integration Mistakes
Mistake | Production risk | Recommended control |
Program command without confirmation | The tool may run the previous or wrong Pset | Return the active program and compare it before enabling start. |
Using only OK or NG |
Related Reading
We use cookies to offer our visitors a better experience and personalized content. We also may share information about your use of our site with our social media, advertising and analytics partners. By continuing to browse the site you are agreeing to our Privacy.
Accept
|