What this category's data looks like
Process specifications and technical standard data for electric motor and generator manufacturing comes from documents including winding process cards, insulation treatment records, dynamic balance reports, voltage withstand insulation test records, and type and factory inspection reports. Data sources cover electromagnetic design data, copper wire and insulating material batch information, winding equipment parameters, balancing machine operation records, electrical test bench results, and ERP/MES system data. Data is updated upon completion of each product or batch production, and synchronized whenever product type changes occur. Document fields include winding turns, wiring methods, impregnation and drying parameters, vibration test values, temperature rise data, voltage withstand test results, and attached material numbers and equipment operation records for the corresponding batch.
What constraints these characteristics impose on tool calling and plugin workflows
Data for this category is updated by batch and product type change. Tool calling must accurately match documents for the current production batch, to avoid using outdated process parameters. Documents include both structured test data and unstructured process instructions. Tools must support both structured field extraction and web content reading. Because errors directly affect product quality and safety, tool calling results must be linked to original data sources to enable traceability. Additionally, cross-departmental document association requires tools to call plugins from multiple data sources, enabling data linkage across winding, insulation, and test processes.
How to set up configurations
The following configurations are compatible with FastGPT v4.17.0:
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Single search limit | Top 6–10 entries | This category has a large number of process and test documents. Limiting returned results prevents context overflow |
| Reranking | Enabled | Process parameters and test data matching the current production batch must be ranked at the top of search results |
| Workflow/API tool selection | auto | Automatically adapts to calling requirements for structured field extraction and unstructured web content reading |
| Workflow/API function-call configuration | Enabled | Forces the model to call tools to extract structured document fields such as winding turns and voltage withstand values |
| Maximum context | 8000–12000 token | Carries complete context for multiple sets of test data, process instructions, and batch information |
| Timeout setting | 300–600 seconds | Adapts to loading times for test reports and large process documents, preventing call interruptions |
Three common errors
- Symptom: After calling a search plugin, only web page titles and summaries are returned, and full web content cannot be read. Cause: Web content extraction plugin configuration is not enabled, and only a basic search tool is called.
- Symptom: Calling a third-party API via an HTTP plugin returns a 502 status code, but the same API works normally in APIFOX. Cause: Incorrect request header parameters or timeout settings are configured, causing gateway forwarding failure.
- Symptom: Only a small number of optional models are visible in tool configuration, and all available models cannot be selected. Cause: Corresponding model keys and access addresses are not configured in system settings, so the model list fails to load completely.
How to confirm configurations are correct
- Submit a test query for winding turns. Confirm that the returned results include the process card content and original data link for the corresponding batch.
- Configure an HTTP plugin to call an internal test data API. Submit a test request and verify that the 502 status code no longer appears, confirming that the request parameters are correct.
- Go to the model configuration page. Confirm that all connected models are displayed in the optional list for tool calling.
- Confirm that the
functionCallconfiguration is enabled. Submit a query containing structured fields, and confirm that the model's returned results include the extracted field values.
The values provided are common starting points, and should be evaluated against the reader's own samples.