What the data for this category looks like
Business data for SMT mounting and electronic assembly comes from BOM files, Gerber files, and coordinate files provided by clients, plus real-time data from MES systems, SMT placement machines, SPI/AOI testing equipment, and reflow oven temperature collection equipment. Daily used documents include BOM and coordinate files, line change sheets, stencil and furnace temperature records, first article confirmation reports, SPI/AOI defect reports, maintenance records, and traceability labels. Data updates in real time per work order and each line change. Fields include part number, reference designator, substitute material, component batch number, furnace temperature parameters, and more. Corresponding units include millimeters, degrees Celsius, and others.
Constraints Imposed on Multi-turn Dialogue and Prompt Engineering
This category has highly real-time, frequently updated data, and involves multiple types of specialized documents and fields. These factors create clear constraints for multi-turn dialogue and prompt engineering configurations. First, real-time updated work order data requires dialogue to dynamically pull the latest MES and equipment parameters. This avoids using expired furnace temperature or component batch information. Second, multiple types of documents and specialized fields require prompts to clearly specify call rules for different documents. This prevents confusion between BOM data and defect report content. Third, core field verification requirements require multi-turn dialogue to confirm information such as part numbers and reference designators round by round. This reduces risks such as incorrect mounting and dry soldering. Fourth, independent bid projects require dialogue to bind unique identifiers. This prevents context interference between different projects.
Configuration Settings
This configuration is based on FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Maximum context length | 8000–12000 characters | Matches the total data volume of multiple document types required for a single bid document, avoids truncating core BOM and coordinate file content |
| Single dialogue knowledge base recall count | Top 6 entries | Covers a reasonable number of associated documents such as BOM, line change sheets, furnace temperature records required for a single bid document |
variables | Pass via work order ID | Binds specific work order data corresponding to the current bid, ensures real-time updated MES and SMT placement machine parameters are called |
chatId | Bind unique bid project identifier | Distinguishes dialogue history for different bid projects, prevents context confusion |
| Dialogue history truncation threshold | Last 20 dialogue turns | Focuses on the latest requirements of the current bid, filters redundant early communication content |
| Output format verification switch | Enabled | Filters non-business-necessary formatting symbols |
Three Common Mistakes
- Observation: Dialogue return content contains large numbers of meaningless punctuation marks such as # and *. Cause: Output format verification switch is not enabled, and prompts do not clearly require filtering non-business-necessary symbols.
- Observation: Dialogue interface calls do not return referenced knowledge base IDs. Cause: Dialogue traceability configuration is not enabled, or prompts do not require the model to mark referenced document identifiers.
- Observation: Image URLs in the knowledge base cannot be displayed normally in dialogue results. Cause: Prompts do not clearly require converting image URLs into recognizable output formats, and automatic parsing rules for image links are not configured.
How to Confirm Proper Configuration
- Initiate a test dialogue that includes a BOM part number query, check that returned content has no extra formatting symbols.
- Review fields returned by the dialogue interface, confirm that referenced knowledge base associated identifiers are included.
- Upload a test document containing image URLs, initiate a query, check that image links are correctly displayed in dialogue results.
- Switch the
chatIdof different bid work orders, confirm that dialogue context does not mix data from different projects.
The values provided are common starting points, and should be evaluated against the reader's own samples.