What this category of data looks like
This category of data covers the entire photovoltaic module encapsulation process, serving departments including string welding, lamination, frame assembly, and testing. Data sources include wafer grading systems, glass adhesive film and backplane batch ledgers, factory MES systems, string welding and lamination equipment, and EL/IV testers. Daily documents include layout diagrams, material batch records, lamination process records, EL defect images, IV test reports, insulation withstand voltage records, and packing lists. Data updates follow the pattern that each module generates an independent record, and each batch of raw materials synchronously updates the batch ledger. Fields include equipment operating parameters, test values, material batch numbers, production time, and similar items. No additional fictional statistical values are included.
What constraints these characteristics impose during deployment and upgrade
Data for this category comes from multiple dispersed sources and has a high update frequency. Each module and batch of materials generates an independent record. This requires the deployment phase to support stable connection configurations for multiple data sources. Multiple document types (such as EL images and IV test reports) require corresponding parsing rules. Upgrades must maintain compatibility with newly added device log fields. High-frequency updated data creates storage and retrieval pressure, so sufficient database connection and cache resources must be reserved. Core business links rely on specific field matching. Deployment must ensure the correctness of knowledge base associated fields to avoid retrieval results deviating from the equipment inspection and maintenance business scenario.
Configuration Settings
The following configurations apply to FastGPT v4.17.0.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
MONGODB_URI | mongodb://username:password@host:27017/fastgpt?authSource=admin | Adapts to multi-type document storage, associates business data such as device logs and test reports |
DB_MAX_LINK | 200–300 | Addresses high-frequency record generation per module, covers connection requirements for concurrent access and data updates |
REDIS_URL | redis://:password@host:6379/0 | Caches inspection rules and retrieval results, reduces real-time query pressure on the database |
STORAGE_S3_ENDPOINT | Fill in according to the enterprise's internal object storage address | Stores large-volume documents such as EL images and IV test reports, adapts to the enterprise's existing storage architecture |
ROOT_KEY | Generate a strong key based on actual measurements | Ensures the security of system background operation permissions, prevents unauthorized configuration modifications |
Three Common Configuration Errors
- Symptom: Container restarts continuously, frontend is inaccessible, logs prompt MongoDB connection errors or authentication failures. Cause: Authentication parameters for
MONGODB_URIare not configured correctly, or database connection count exceeds the limit set byDB_MAX_LINK. - Symptom: Retrieval results for equipment inspection cannot be associated with EL images and IV test reports. Cause: The storage path of the corresponding document is not bound in the knowledge base configuration, or the data source configuration does not associate the device ID field from the MES system.
- Symptom: Container fails to start when deployed via Synology Docker, logs prompt database configuration errors. Cause: The connection address for
PG_URLorMONGODB_URIis not filled correctly, or the corresponding port permissions for the container are not opened.
How to Verify Successful Configuration
- After starting the deployment container, check database connection-related logs to confirm that the configurations for
MONGODB_URIandREDIS_URLcan establish normal connections. - Upload a single photovoltaic module's EL image and IV test report, perform a retrieval test related to equipment inspection, confirm that retrieval results can associate the storage address of the corresponding document.
- Access the system background management page, verify the permission check logic, confirm that unauthorized keys cannot modify core configuration items.
- Simulate multiple devices initiating retrieval requests simultaneously, observe system operating status, confirm that the value of
DB_MAX_LINKadapts to the concurrent requirements of the current scenario.
The values provided are common starting points and should be measured against the reader's own samples.