What the data for this category looks like
Photovoltaic module encapsulation production data comes from cell sorting equipment, glass adhesive film backplane batch ledgers, factory MES systems, string welding and lamination production equipment, EL defect detectors, and IV power testers. Daily generated documents include component layout diagrams, material batch records, lamination process parameter records, EL defect images, IV test reports, insulation withstand voltage test records, and finished product packing lists. Data update granularity is per single module or single batch of materials. Fields include component serial number, cell current gear, lamination temperature and duration, EL crack level, IV power value, insulation withstand voltage value, and other related items. Corresponding units include ℃, seconds, W, MPa, and others.
What constraints these characteristics impose on workflow orchestration
High-frequency data updates for single components or single batches require workflows to support real-time triggering and fine-grained parallel processing, to avoid delays caused by batch processing. Multi-source heterogeneous data sources require workflows to be configured with unified format conversion nodes to standardize outputs from different devices and systems into the fields required for ledgers. The most time-consuming cell current gear matching link requires embedding rule judgment nodes in the workflow to achieve automated processing. Error scenarios such as non-compliant power and lamination delamination need to be configured with exception branches to ensure that abnormal data triggers corresponding retest or reporting processes.
Configuration Settings
All following configuration items are compatible with FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Trigger Mode | Triggered by component completion events reported by devices | Adapts to the real-time data update rhythm of single components |
Input variables variables | Pass in component serial number, material batch number (max 20 characters) | Matches data association between MES systems and test equipment |
| Rule judgment node timeout threshold | 60 seconds | Covers the typical time required for cell current gear matching |
Exception branch nodeId | Bound to two downstream nodes: non-compliant power retest, crack retest | Corresponds to common error scenarios in module encapsulation |
| Knowledge base search limit | Top 3 matching documents | Adapts to the precise query requirement for single-component process parameters |
| Code running module parameters | Enable streaming output switch | Enables real-time synchronous display of test data |
Three Common Misconfigurations
- Symptom: The
variablesparameter is empty during workflow execution, making it impossible to match test data for the corresponding component. Cause: No correct variable mapping was configured in the trigger node, and the component ID reported by the device was not bound to the workflow input variables. - Symptom: Streaming output has no response when calling the code running module, and the workflow node status remains in running. Cause: The streaming return format was not correctly configured in the code script, and the output stream was not synchronized to the return parameters of the workflow node.
- Symptom: The rule judgment node execution times out, causing delays in subsequent ledger generation. Cause: No reasonable timeout threshold was set, and no exception branch was configured to handle timeout scenarios, making it impossible to trigger the corresponding retest process.
How to Verify Successful Configuration
- Manually trigger a test workflow for a single component, check whether the
variablesparameter input to the workflow correctly passes the component serial number and material batch number. - Simulate test data with non-compliant power, verify whether the exception branch
nodeIdtriggers the corresponding retest process node. - View the workflow running logs, confirm that the execution time of the rule judgment node does not exceed the preset 60-second threshold.
- Call the code running module, verify whether the streaming output content is synchronized to the final output result of the workflow.
The values listed above are common starting points and should be evaluated against the user's own samples.