SMT Placement and Electronic Assembly Process Specification and Technical Standard Q&A: HTTP Interfaces and External Systems

The data sources for processes and standards in SMT placement and electronic assembly cover BOMs, Gerber files, coordinate files provided by

What the data for this category looks like

The data sources for processes and standards in SMT placement and electronic assembly cover BOMs, Gerber files, coordinate files provided by customers, as well as MES systems, solder paste and component batch ledgers, placement machines, SPI/AOI testing equipment, reflow oven temperature records, etc. Data update frequency is adjusted in real time with work orders and line change operations, and includes documents such as BOM lists, line change tables, stencil parameters, furnace temperature curves, first article confirmation reports, defect repair records, and traceability labels. Fields include part numbers, reference designators, component models, soldering temperatures, placement coordinates, etc., with units including millimeters, degrees Celsius, batch numbers, etc. Unlike the PCB manufacturing category, data for this category is generated around the component placement process and does not include content related to substrate circuit manufacturing.

Since data sources are scattered and updated in real time, interfaces must support synchronizing documents in different formats from multiple systems, while adapting to high-frequency work order-level data updates. Document types include structured CSV files, report files, and real-time logs, so interfaces must be compatible with multiple data parsing formats. Fields are highly specialized, so interface parameters must match SMT-specific business fields to avoid deviation in retrieval scope. Errors may trigger mass production issues, so interfaces must have retry and verification mechanisms to ensure the accuracy of data transmission.

How to set the configuration

Configuration ItemRecommended SettingRationale
Authentication MethodBearer {custom API key}Complies with FastGPT v4.17.0 interface authentication standards
Input VariablesIncludes work order ID, component batch number, furnace temperature rangeMatches real-time process data for SMT work orders
Single Search LimitTop 3 entriesAvoid returning too much data that causes system overload
Return Data FormatJSON structure, including specification number, applicable equipment modelAdapts to data parsing for EMS factory MES systems
Request Timeout600 secondsAdapts to delays in real-time pulling of furnace temperature and SPI reports
Maximum Context Length1000–1500 charactersAdapts to field length of BOM files

Three common misconfigurations

  • Phenomenon: When calling the create file collection interface, local CSV format BOM files cannot be uploaded. Cause: The form format for file upload is not correctly configured in the request parameters, or the field requirements for SMT placement documents are not matched.
  • Phenomenon: When calling the interface with a custom authentication token, a permission denied or billing prompt is returned. Cause: The token is not bound to the access permission of the corresponding SMT process knowledge base, or the token configuration format does not meet FastGPT requirements.
  • Phenomenon: The process specification entries returned by the interface do not match the current work order. Cause: The correct work order ID or component batch number is not passed in variables, resulting in the retrieval scope covering expired line change data.

How to confirm the configuration is correct

  • Use a test work order ID to initiate an interface request, check whether the returned responseData includes the line change table content corresponding to that work order.
  • Upload a test BOM CSV file, confirm that the interface can correctly parse the part number and reference designator fields in the file.
  • Call the authentication interface, use the configured authentication method, confirm that the returned status code is 200 and there are no permission error prompts.
  • Simulate real-time updated component batch data, initiate a retrieval request, confirm that the returned results update as the batch number changes.

The values provided are common starting points and should be evaluated against the reader's own samples.