What the Data for This Use Case Looks Like
PCB manufacturing process and exception data sources include Gerber files, drill files, and BOM provided by clients, as well as CAM system data, production equipment parameters, bath solution test results, AOI inspection reports, electrical test reports, and laboratory slice reports. Data update frequency follows per production batch, per shift, or continuous collection. Documents include engineering production instructions, drilling and lamination parameters, chemical solution concentration records, and more. Most fields are professional process parameters: drill hole diameter (unit mm), lamination temperature (unit ℃), active ingredient concentration of chemical solutions (unit g/L). The data structure is split into two categories: structured process parameters and unstructured inspection reports.
Constraints Imposed by These Characteristics During Deployment and Upgrade
PCB manufacturing process and exception data has diverse formats, including binary Gerber files, structured database parameters, and unstructured inspection reports. Update frequency is high, so the system must support high-frequency write and read operations. Factory production environments are often isolated on internal networks, with no direct public network exposure. Deployment must adapt to internal network storage and database connections, avoiding public network dependencies. Accurate matching of professional process fields requires the system to connect to specific business databases. Deployment must complete data link setup in advance to ensure stable parameter reading and document storage.
How to Set Configurations
These configurations apply to FastGPT v4.17.0, as detailed below:
| Configuration Item | Recommended Configuration | Rationale |
|---|---|---|
STORAGE_S3_ENDPOINT | Factory intranet MinIO service address, such as http://192.168.1.100:9000 | Meets the storage needs of multi-format large files for PCB manufacturing, supports intranet deployment without public network exposure |
REDIS_URL | Factory intranet Redis instance address, set timeout to 300 seconds | Adapts to caching of high-frequency collected process data, avoids frequent reads from the original database |
MONGODB_URI | Bind to the process database address exported from the CAM system | Stores unstructured process documents such as Gerber parsing records and AOI reports |
PG_URL | Associate with the structured parameter database for production batches | Stores standardized process parameters such as drilling and lamination parameters |
FILE_TOKEN_KEY | Custom 32-bit random string | Protects access permissions for uploaded process files, prevents unauthorized access |
ROOT_KEY | Only used for internal administrator configuration, not exposed externally | Controls deployment permissions for system plugins, adapts to the security requirements of factory intranets |
Three Common Configuration Mistakes
- Using a publicly accessible address when configuring
STORAGE_S3_ENDPOINT, which prevents FastGPT deployed on the intranet from connecting to the factory's local MinIO service. This occurs because the actual environment of factory data storage on the intranet for PCB manufacturing scenarios is not accounted for. - Not setting the timeout parameter for
REDIS_URL, with a value that does not match the high-frequency collection rhythm, leading to cache overflow or read timeouts. This occurs because the continuous collection and frequent update characteristics of PCB manufacturing data are ignored. - Not associating
PG_URLwith the structured process parameter database, which prevents automatic matching of professional fields such as drill hole diameter and lamination temperature when drafting exception reports. This occurs because database association configuration is not completed in line with the process field requirements of PCB manufacturing.
How to Verify Successful Configuration
- Upload a standard Gerber format process file, check that it can be parsed normally and stored to the specified storage service.
- Simulate a single production batch parameter write operation, check that the Redis cache can correctly read the latest process data.
- Call a system plugin to generate an exception report template, check that structured process parameters from the
PG_URLdatabase are automatically associated. - Use
FILE_TOKEN_KEYto generate a temporary access link, confirm that only authorized users can access stored process documents.
The values provided here are common starting points, and should be measured against the reader's own samples.