This configuration example applies to FastGPT v4.17.0.
What data looks like for this category
Typical data for this category comes from production links of machining plants and precision parts factories. It covers documents such as process routes, operation cards, tool lists, CNC programs, first-piece inspection records, patrol inspection forms, and measuring tool calibration records. Data sources include product drawings and 3D models, CAPP/CAM systems, machine tool collection terminals, tool management systems, MES systems, and measuring tool data. Data update frequency is triggered by work orders, individual products, sampling batches, or tool changes. Fields and units vary across different documents. For example, operation cards mark clamping reference parameters, with millimeters as the unit. Tool lists record tool life, with minutes as the unit. CNC programs include feed speed parameters, with revolutions per minute as the unit.
What constraints these characteristics impose on the tool calling and plugin workflow
Data sources for this category are scattered, and update frequency is tied to production nodes. This requires tool calling to support real-time data pulling from multiple sources and adaptation to heterogeneous formats. Fields and units differ across documents, so tools must have structured parsing capabilities. These tools convert scattered data into a unified process or exception report format. Process preparation and exception handling are the most time-consuming links for this category. This requires tool calling to associate real-time data of processes, tools, and machine tools. This assists with benchmark selection, program verification, and exception root cause analysis. The consequences of errors directly relate to workpiece scrap or machine tool downtime. This requires tool calling results to undergo format verification. This prevents subsequent production abnormalities caused by parameter errors.
How to configure the settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Workflow/API tool selection | auto | Adapt to multi-tool calling scenarios, automatically match tools required for process document generation and exception report drafting |
| Workflow/API function-call configuration | enabled | Force structured output to ensure that the format of process parameters and exception data meets the field requirements of operation cards and CNC programs |
| Tool calling data source configuration | Connect to machine tool collection, MES, and tool management system interfaces | Cover real-time tool life, process progress, and machine tool status data required for process document generation |
| Context window size | 8000–12000 token | Accommodate complete process route, CNC program, and exception log data to avoid truncation of key information |
| Timeout threshold | 300 seconds | Adapt to conventional time-consuming scenarios of machine tool data pulling and process program verification, avoid interrupting calls due to wait timeouts |
| Exception trigger rule | Triggered by tool changes or dimensional deviation overruns | Match production scenarios for data updates in this category, reduce invalid tool calls |
Three common configuration errors
- When calling a tool,
{"code":514,"statusText":"unAuthApiKey"}is returned. The cause is that the API key permission for tool calling is not correctly configured, and the legal key corresponding to the machine tool or MES system is not bound. - Global variables are not updated after tool calling is completed. The cause is that the variable synchronization switch after tool calling is not enabled, resulting in the generated process parameters not being written to the context variable pool.
- The calling log prompts data acquisition exception. The cause is that the correct data source interface address is not configured, or the response format of the data source interface does not match the parsing rules preset by the tool.
How to confirm the configuration is complete
- Test calling the process document generation tool to verify whether the tool list and operation card data of the corresponding work order can be pulled.
- Submit an exception report drafting request, check whether the returned result includes standardized exception types, dimensional deviation values, and processing suggestions.
- View the tool calling log to confirm that all API requests return a 200 status code, with no
unAuthApiKeyor data acquisition failure error messages. - Verify that global variables can be automatically updated to the generated process parameter values after tool calling.
The values provided are common starting points and should be measured against the reader's own samples.