What Data for This Category Looks Like
Data sources for this category include Gerber files, drill files, and BOMs provided by customers, as well as factory CAM parsing records, drilling and lamination equipment parameters, bath chemistry test reports, AOI and electrical test results, and laboratory slice reports. Data is updated continuously per production batch and shift. Daily documents include engineering production instructions, drilling and lamination parameter records, chemical analysis ledgers, and various defect detection reports. Fields include layer identifiers, aperture values, defect coordinates, continuity test values, and more. Units include millimeters, inches, ohms, and other standard units.
What Constraints These Characteristics Impose During Deployment and Upgrade
The multi-source heterogeneous business data, high-frequency update rhythm, and specific field units of this category impose multiple constraints on deployment and upgrade. Multi-source data includes files in different formats such as Gerber, equipment parameters, and detection reports. During deployment, multi-format parsing and access must be adapted. During upgrade, data formats from newly added detection equipment must be supported. For the update rhythm of per-batch and continuous collection, sufficient database connection resources must be configured during deployment to support concurrent writes. During upgrade, data synchronization interruptions must be avoided. For specific field units and business association logic, field mapping rules must be preset during deployment. During upgrade, old version fields must be retained to be compatible with existing production data.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 100–150 connections | PCB manufacturing data has large batch sizes and frequent concurrent writes. This parameter controls the maximum number of database connections to adapt to the storage needs of high-frequency production data |
MONGODB_URI | mongodb://username:password@host:port/dbname?authSource=admin | Stores unstructured detection reports such as AOI and electrical test results, and batch production batch data. Authentication source and target database must be specified |
REDIS_URL | redis://:password@host:port/0 | Caches frequently accessed Gerber parsing records and production batch metadata to reduce database query pressure |
FILE_TOKEN_KEY | 32-character random string | Generates file download tokens to protect access permissions for sensitive production documents such as engineering drawings and detection reports |
STORAGE_S3_ENDPOINT | Fill in according to the enterprise's internal object storage address | Stores large-volume files such as batch-produced slice reports and original equipment logs to meet the persistence needs of multi-source data |
Three Common Errors to Avoid
- Errors related to
config.jsonoccur after upgrade, and the interface fails to load configuration items. The cause is that old configuration files were not fully cleaned up, or the upgrade script did not overwrite the new version configuration logic. - The version still shows the old version number after Docker deployment and upgrade. The cause is that the correct version tag was not specified when pulling the image, or the old version image was cached locally and not re-pulled.
- Associated fields are missing from historical production batch data after upgrade. The cause is that the database migration script was not executed during upgrade, and the field structure of old version data was not compatible.
How to Verify Proper Configuration
- Run the version query command to confirm that the currently running FastGPT version is v4.17.0.
- Upload a test Gerber file and AOI report to check whether the system can parse them normally and associate them with the corresponding production batch.
- Access the configured
FE_DOMAINaddress to verify that the interface loads normally and there are no configuration-related errors. - Run a database connection test to confirm that the addresses configured for
MONGODB_URIandREDIS_URLcan be connected normally.
The values provided are common starting points and should be measured against the reader's own samples.