What data for this use case looks like
Photovoltaic module encapsulation scenario data originates from wafer grading records, glass and backsheet batch ledgers, workshop MES systems, string welding and lamination production equipment, EL defect detectors, and IV power testers. Data is updated once per generated module, with batch ledgers synchronized for each batch of raw materials. Daily produced documents include layout diagrams, material batch traceability tables, lamination process parameter records, EL crack imaging maps, IV test power reports, insulation voltage withstand test records, and finished product packing lists. Data fields include wafer current grade values, lamination temperature and time, EL crack coordinates, IV test power values, insulation voltage withstand megohm values, and other fields, all with clear engineering units.
What constraints these characteristics impose on multi-turn dialogue and prompt engineering
Since data is updated per individual module and per single batch, multi-turn dialogue must bind a unique session identifier to avoid confusing context across different modules. Multiple data sources require prompts to explicitly specify calling fields from corresponding equipment or systems; generic document retrieval alone is insufficient. Diverse document formats require multi-turn dialogue to gradually guide users to upload or specify corresponding types of files, rather than requesting all materials at once. For time-consuming matching and judgment tasks, prompts must prioritize core tasks such as wafer grade matching and EL crack determination, to ensure generated process documents and exception reports comply with production specifications.
Configuration Specifications
This document is formulated based on FastGPT v4.17.0 configuration standards.
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
| Maximum context length | First 20000 characters | Covers all associated documents for a single batch of material ledgers and a single module, to avoid context overflow |
chatId binding rule | Bind to module serial number | Distinguishes dialogue flows for different modules, ensuring context is not confused |
messages format | Group by single-module sessions | Associates each round of dialogue context to the corresponding module, ensuring logs and responses match |
variables configuration | Bind to wafer batch and lamination parameter fields | Extracts corresponding variables from MES and equipment data to populate prompt templates |
| Streaming output interval | 1–2 seconds | Adapts to front-end display rhythm, preventing viewing disruptions from overly fast or slow response speeds |
| Guest login window icon | Replace per workshop visual specifications | Matches the style of existing workshop interfaces, improving operational recognition |
Three Common Configuration Mistakes
- Links in streaming output only function within the current page and cannot be opened in a new window. Phenomenon: Clicking document links returned via streaming output does not open a new window, and only replaces the current page content. Cause: Link jump parameters for streaming output are not configured, and the default current context jump rule is used.
- Conversation logs do not match actual response content. Phenomenon: Content displayed in conversation details does not match responses returned on the front end, and details remain consistent across multiple conversations. Cause:
chatIdis not correctly bound to individual module serial numbers, and context is not updated in groups per module. - Generated process documents lack core fields. Phenomenon: Generated process documents do not include wafer current grade values or EL crack determination results. Cause: Corresponding data source field mappings are not configured in
variables, and calls to raw data from string welding or EL testers are not guided.
How to Verify Successful Configuration
- Initiate a multi-turn dialogue for a single module, and confirm that returned responses include corresponding batch material parameters, EL test results, and lamination process data.
- Enable the streaming output function, click a document link in the returned content, and confirm the link opens in a new browser window.
- View conversation logs, confirm that the
chatIdfor each conversation matches the module serial number, and that log content fully matches responses displayed on the front end. - Modify the guest login window icon file, refresh the page, and confirm the icon has updated to the custom style.
The values provided here are common starting points, and should be validated against the user’s own samples.