What Data for This Category Includes
Data sources for this category include cell grading systems, glass adhesive film backplane batch ledgers, production MES systems, string welding and lamination equipment logs, EL defect detectors, and IV power testers. Data updates follow a schedule where a dedicated record is generated for each module, and batch ledgers are synchronized for each batch of raw materials. Daily documents include layout diagrams, material batch records, lamination process records, EL defect images, IV test reports, insulation withstand voltage records, and packing lists. Fields cover cell current gear, lamination process parameters, crack coordinates, power values, withstand voltage values, and more, with corresponding units including amperes, degrees Celsius, seconds, watts, megohms, and others.
What Constraints These Characteristics Impose on Tool Calling and Plugins
The dedicated data for individual modules and the heterogeneous nature of multiple document types require that tool calls be precisely bound to the unique identifier of the module to avoid cross-batch data confusion. Large differences in data formats across sources mean text records, image-based EL defect images, and numerical test reports each require separate adaptation to calling rules, increasing the complexity of plugin configuration. Frequently updated production data requires that the context window for tool calls be limited to the scope of a single module or single batch to prevent context overload. The need for automation of core time-consuming processes requires that plugins integrate dedicated functions such as EL crack interpretation, cell gear matching, and power retest verification.
How to Configure
This configuration is based on FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | auto | Automatically adapts to dedicated plugins for photovoltaic module inspection scenarios, no manual specification of call targets required |
| Workflow/API function-call configuration | enabled | Enables function call functionality to interface with plugins for device data pulling and document parsing |
| Maximum single tool call count | First 3 entries | Individual module inspection data has limited entries, limiting call counts reduces context load |
| Plugin timeout period | 120 seconds | EL image parsing and power calculation require reasonable processing time, balancing session efficiency and call success rate |
| Context window scope | Single batch of module data | Material and process parameters for modules in the same batch are unified, limiting scope avoids interference from unrelated data |
| Result rearrangement rule | Sort by field relevance | Prioritizes results related to cell gear matching and EL crack interpretation to improve audit efficiency |
Three Common Misconfigurations
- When calling the
/api/v1/chat/completionsinterface, the preset inspection and audit prompt does not take effect, and the returned results do not associate with cell batch information. The cause is failure to correctly include the prompt parameter in the request body, or failure to enable thefunctionCallparameter to bind dedicated plugins. - EL crack coordinates returned by tool calls are empty, or IV test power values have large deviations. The cause is failure to limit the context window scope, introducing redundant cross-batch data which prevents the plugin from precisely matching the dedicated record for the current module.
- The interface returns
401 Unauthorizedwhen called, and inspection data cannot be pulled normally. The cause is failure to correctly configure the verification token delivery method, or the token validity period not matching the production data update rhythm.
How to Confirm Successful Configuration
- Initiate a test session for single module inspection, view the tool call log, and confirm that
toolChoiceautomatically triggers the dedicated plugins for cell gear matching and EL crack interpretation. - Check the plugin call results returned by the interface, and confirm that required fields including cell current gear, EL crack coordinates, and IV power value are included.
- Simulate input of multi-batch data, and confirm that the context window only loads relevant records for the current batch, with no unrelated data introduced.
- Test verification tokens with different validity periods, and confirm that interface calls pass identity verification normally, with no
401errors occurring.
The values provided are common starting points and should be measured against samples specific to the deployment context.