Improved Fault Diagnosis Method for PLC-Based Manufacturing Processes with Validation through a Cyber-Physical System
Bibliographic record
Abstract
Most manufacturing systems in the industry nowadays are controlled by Programmable Logic Controllers (PLCs), which are characterized by their high robustness and low cost. The systems controlled by PLCs are typically described as Discrete Event Systems (DESs), and it is often difficult to detect faults and behavioral abnormalities related to the PLC process. Researchers proposed an automated tool called fault and behavior monitoring tool for PLC (FBMTP) whose main advantage is its ability to effectively handle inaccuracies with large-scale PLC-controlled manufacturing systems. Although FBMTP effectively addresses the issues in PLC-controlled systems, only the Boolean I/O signals (1/0) intercepted from the memory area of the PLC are examined. However, PLC I/O often involves analog signals, which are real values. Therefore, we introduced a new parameter to increase the diversity of this mechanism, an improved fault and behavior monitoring tool for PLC (IFBMTP). Cyber-Physical System (CPS) technology is applied across various fields. In the manufacturing sector, it is used for real-time monitoring, production control, and information sharing, enhancing the flexibility of manufacturing systems. Moreover, CPS is practical for simulating and testing different fault detection models, such as IFBMTP, given the limited availability of large-scale equipment for testing in industries. Presently, many software platforms focus primarily on animation or integer computations but cannot accurately reflect physical analog data, making integration among multiple technologies challenging. Automation Studio, developed by Famic Technologies Inc., stands out for its rapid modeling, multi-technology integration, and application in virtual commissioning. We leveraged Automation Studio as the development platform to create an integrated CPS and validated the robustness of IFBMTP under various scenarios for debugging and testing. Such integration of multiple technological virtual systems is essential for industrial applications and validations.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".