What the data for this category looks like
Data sources for the photovoltaic module encapsulation process include cell grading records, glass film and backplane batch ledgers, factory MES systems, string welding and lamination equipment logs, and output reports from EL testers and IV power testers. Data is generated synchronously for each module and each batch of materials. Daily archived documents include layout diagrams, material batch records, lamination process parameter records, EL defect images, IV test reports, insulation voltage resistance records, and packing lists. This category focuses on cell electrical connection and outdoor weather-resistant encapsulation. Data fields include cell current gear, lamination temperature and holding duration, EL crack coordinates, IV power value, and others. Corresponding units include amperes, degrees Celsius, seconds, watts, and others. This data differs from the semiconductor surface process data characteristics of cell manufacturing.
What constraints these characteristics impose on the "workflow orchestration" link
Multi-source heterogeneous real-time updated data requires workflows to support multi-node parallel association with different data sources, to avoid cross-batch data confusion. Full-link analysis of a single module includes time-consuming steps such as cell gear matching, EL crack interpretation, and power retesting. This requires workflows to split nodes and configure flexible timeout rules. Unstructured documents such as EL images and IV reports need to be bound to the corresponding batch process. This requires workflows to support file upload and path association configuration. Requirements for batch-based grouped processing require workflows to support grouped execution logic for batch data, to adapt to the update rhythm of each batch of materials.
How to Set the Configuration
This configuration applies to FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Variable Settings | Bind variables to component batch ID and EL image storage path | Associate full-link data for a single module to avoid cross-batch confusion |
| Node Timeout Settings | 600–1200 seconds | Cover the execution duration of time-consuming steps such as cell gear matching and EL crack interpretation |
| Batch Data Processing | Execute in batch groups | Match the update rhythm of each batch of materials, avoid processing excessive data on a single node |
| Form Input Validation | Enable required field validation, restrict non-empty submissions | Ensure the process starts only after all form fields are complete |
| File Upload Node Configuration | Support upload of EL image and IV report formats, limit single file size to 1000 MB | Match the format and volume requirements of daily archived documents |
| API Call Timeout | 1800 seconds | Cover the ultra-long execution requirements of complex analysis scenarios |
Three Common Misconfigurations
- After integrating an external search node into the workflow, the returned results do not match the target component. The cause is failure to bind search keywords and component batch information via
variables, and failure to distinguish node execution logic, leading to search results deviating from the analysis target. - Workflow execution is forcibly terminated after exceeding 1200 seconds, generating incomplete analysis reports. The cause is failure to adjust node timeout settings for the complex analysis links of photovoltaic module encapsulation, using the default short timeout configuration.
- Calling the workflow API with file upload returns parameter verification failure. The cause is failure to correctly bind file paths to the workflow's file upload node configuration in the API request, resulting in files failing to associate properly with the process.
How to Confirm the Configuration is Correct
- Submit test batch component data, check whether the workflow automatically associates archived documents such as corresponding batch EL images and IV test reports.
- Trigger a single complex analysis process, confirm that the execution duration does not exceed the preset timeout threshold, and there is no mid-run interruption.
- Submit a form that is not fully completed, check whether the workflow rejects startup and returns a validation prompt.
- Call the API interface with file upload, upload an EL image file, confirm that the process can normally receive and process the file content.
The values given are common starting points and should be measured against the reader's own samples.