Data Sources and Structure for This Category
Core data for this category comes from cell grading systems, workshop MES systems, welding and torque collection equipment, BMS software version repositories, and EOL test benches. Data is updated once per battery pack or energy storage cabinet produced, and synced each time the BMS software version changes. Documents used for daily operation, maintenance and troubleshooting include cell grouping rules, material BOM lists, welding and torque calibration records, BMS flashing logs, insulation and pressure resistance test reports, EOL test reports, and system configuration parameter lists. Data fields include cell model, grouping parameters, welding torque value, BMS version number, insulation resistance value, charge-discharge test results, and other related metrics.
Constraints for Deployment and Upgrade
Data sources for this category are scattered and tied to production line equipment. Reserve docking configuration items for MES and BMS systems during deployment to ensure compatibility for data synchronization. Data updates for individual equipment occur frequently. Configure storage parameters that support real-time or near-real-time synchronization to prevent data lag from reducing the accuracy of inspection and maintenance Q&A. Document types are diverse and have clear fields. Pre-set parsing templates for each document type during deployment to adapt to content in different formats such as grouping rules and test reports. Fault outcomes directly relate to system safety. During upgrades, ensure the Q&A model’s knowledge base strictly matches the current production line’s BMS version and grouping parameters to avoid protection failure risks caused by configuration deviations.
Configuration Settings
This section applies to FastGPT v4.17.0 deployment configurations.
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
DB_MAX_LINK | 200–300 connections | This category has multiple data sources and frequent updates. Sufficient database connections are required to maintain stability for multi-source data synchronization |
MONGODB_URI | mongodb://admin:securepass@internal-mongo:27017/fastgpt?authSource=admin | Unstructured test reports, logs and other document data must be stored. MongoDB is suited for this semi-structured storage requirement |
REDIS_URL | redis://:securepass@internal-redis:6379/0 | Real-time device status, user sessions and shared link information must be cached to ensure fast Q&A response times |
STORAGE_S3_ENDPOINT | Fill in according to the enterprise’s internal object storage address | Files such as test reports and BMS flashing records for this category have large file sizes. Use object storage for unified management |
ROOT_KEY | Randomly generated string of 32 or more characters | Access security for system background management interfaces must be ensured to prevent data leaks from unauthorized operations |
Three Common Configuration Errors
- Phenomenon: After modifying docker-compose.yml to configure multiple API keys, model calls return a 401 unauthorized error. Cause: Multi-key environment variable bindings were not correctly declared in the configuration file, so the system cannot recognize the specified model combination keys.
- Phenomenon: For FastGPT deployed via Docker on Windows systems, password-free shared links in the workspace disappear after restarting the computer. Cause: Shared link cache data was not mounted to a persistent storage volume, so cache data inside the container is lost after restart.
- Phenomenon: After connecting to a model gateway, equipment inspection Q&A cannot return valid results, and logs show core fields are empty. Cause: Field mapping rules between the gateway and this category’s data were not configured, so key data such as grouping parameters and BMS versions cannot be matched.
How to Validate Configuration
- Run a database connection pool test, monitor connection usage, and confirm that the
DB_MAX_LINKconfigured connection count can support daily data synchronization requirements. - Upload an EOL test report for a battery PACK, verify that the system can correctly parse fields such as insulation resistance and charge-discharge parameters from the document, and match the document structure for this category.
- Restart the deployment environment, access the previously generated password-free shared link, confirm the link is still accessible, and verify that the persistent storage configuration is active.
- Call the test interface configured with multiple API keys, confirm that different keys correspond to different model combinations, and verify that the key configuration is correct.
The values provided are common starting points and should be evaluated using local deployment samples.