What the data for this category looks like
Daily data for SMT mounting and electronic assembly includes multi-source structured and unstructured documents, including BOMs and coordinate files, line change lists, stencils and furnace temperature records, first article inspection reports, SPI/AOI reports, maintenance records, and traceability labels. Data sources include customer-provided BOMs, Gerber files, component coordinates, as well as MES systems, solder paste and component batch ledgers, placement machines, SPI/AOI testing equipment, and reflow furnace temperature collection equipment. Data is updated in real time for each work order and each line change. Fields include part numbers, reference designators, substitute materials, furnace temperature parameters, defect types, coordinate positions, and more. Some fields use dedicated units such as millimeters and degrees Celsius.
What constraints do these characteristics impose on the tool calling and plugins workflow
Multi-source heterogeneous data sources require tool calling to interface with API endpoints from different systems simultaneously, to ensure access to the latest BOM, furnace temperature, and testing data. The high-frequency real-time update feature requires that tool calling response latency be kept within a reasonable range, to avoid disrupting work order processing timelines. The rich set of dedicated fields and units requires that field extraction rules for tool calling be customized for SMT documents, to ensure accurate extraction of key information such as part numbers and reference designators. The significant consequences of errors require that tool calling results undergo secondary verification, to prevent issues such as incorrect component placement and dry joints.
How to configure the setup
This configuration is based on FastGPT v4.17.0.
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | auto | Adapts to the multi-step tool calling needs of SMT work orders, automatically selects appropriate tools to complete data extraction and integration |
| Tool calling timeout | 600 seconds | Matches the average processing duration of SMT work orders, avoids interrupting critical workflows due to single-call timeout |
| Tool calling retry count | 2 times | Balances call success rate and resource usage, avoids excessive device or system load caused by repeated triggers |
| Workflow/API function-call configuration | Enable forced function calling | Ensures extracted field formats meet standardized requirements for process documents and exception reports |
| Result output control | Only retain final report content | Hides intermediate tool calling processes, aligns with user requirements for final document output |
| Maximum data per tool call | 1000 MB | Matches the average size of SMT work order documents, avoids call failures due to exceeded data limits |
Three common configuration errors
- Symptom: Full tool calling logs and intermediate response content remain displayed after tool calling completes. Cause: The result output control setting was not properly configured, and the setting to hide tooling processes was not enabled.
- Symptom: Defect type and coordinate fields cannot be extracted from PDF parsing results of SPI/AOI reports. Cause: Field matching rules were not customized for dedicated SMT document fields such as AOI defect coordinates and solder paste thickness thresholds, leading to matching failures.
- Symptom: Tool calling times out or fails to respond to termination commands. Cause: Reasonable timeout settings and termination trigger conditions were not configured, causing tools to occupy resources for extended periods or fail to recognize termination signals.
How to confirm the configuration is properly applied
- Upload a real SMT work order BOM and SPI report, trigger the tool calling workflow, and check that the generated final document only contains process document or exception report content, with no extra tool calling logs.
- Manually modify field values in PDF parsing results, verify that tool calling can accurately extract and match key information such as part numbers and reference designators.
- Send a termination command after triggering tool calling, check that the tool stops running and releases associated system resources.
- View the tool calling logs in the FastGPT backend, confirm that values for configuration items such as
toolChoiceandfunctionCallhave been correctly applied.
The values provided here are common starting points, and should be evaluated against the reader's own samples.