LMES FAQ

This chapter organizes common problems and solutions during the use of the LMES system to help you quickly locate and solve problems.

Part 1: Installation, Startup, and Environment Issues

Q1: The software cannot start, the log shows that it cannot connect to SIOT, and the SIOT process starts and stops repeatedly in the task manager.

A: This is because the SIOT environment requires GBK encoding, and your operating system may have enabled UTF-8 as the default encoding.

Solution: In Windows "Region Settings", find "Administrative language settings", uncheck the option "Beta: Use Unicode UTF-8 for worldwide language support", and then restart the computer.

Q2: The SIOT service cannot start or communication is abnormal, especially after changing or adding/removing network cards (such as VPN, virtual network cards).

A: When the SIOT service starts for the first time, it generates a device authorization file (License) based on the current network card information. If the computer's network card information changes later, it will cause authorization verification failure.

Solution: Stop the CMS service, delete the License folder under the software directory ...bin\siot\, and then restart CMS. The system will automatically generate a new authorization.

Q3: Why do CMS or related services (such as alarms, traceability) start very slowly or even fail due to timeout?

A: Slow service startup is usually due to the large amount of data that needs to be loaded or initialized during startup. Common reasons are: 1. The alarm module is configured with tens of thousands of alarm points; 2. The historical data cache cycle of the traceability or log service is set too long (such as more than 180 days).

Solution:

1. For alarm service: Check and optimize alarm configuration, remove unnecessary alarm points. The new version has optimized the alarm service startup performance, it is recommended to upgrade.

2. For traceability service/startup timeout: In the appsettings.json configuration file under the CMS installation root directory, appropriately shorten the historical data cache days or extend the service startup timeout (Timeout parameter, in seconds).

Q4: Startup on boot is set, why does the program not run automatically after restarting the computer?

A: This is usually an operating system permission issue or related services are disabled.

Solution:

1. Confirm that the Windows account used to run the startup task has sufficient permissions.

2. Open Task Manager, switch to the "Startup" tab, find "Windows Command Processor" or similar entries, and ensure their status is "Enabled".

Q5: After starting CMS, the interface reports Error: ERR_INVALID_HTTP_RESPONSE(-370) or cannot load.

A: This problem is usually caused by security software (such as antivirus software, firewall) on the computer limiting the network access of the new version of the Chrome kernel. The CMS interface is based on B/S architecture and relies on the embedded browser kernel, so it will be affected.

Solution: Temporarily use Edge or Chrome browser to access the development version interface directly via http://127.0.0.1:18000.

Q6: When running the program in the development version (CMS Editor), why does the service stop or crash for no reason?

A: This is normal behavior designed for the development version. In the development version, the life cycle of background services (such as variable services, flow services, etc.) is bound to the front-end interface. When you close or refresh the browser window of the development version, the background service will stop accordingly.

Solution: Daily development and debugging can use the development version, but the official production environment must use the runtime version (CMS Vision) for deployment to ensure continuous and stable operation of services.

Q7: The software or client crashes and exits or reports an error suddenly during operation.

A: If the problem is sporadic, it is likely caused by external environmental factors.

Solution: Please check the Windows System Event Viewer to troubleshoot whether there are records of insufficient memory (such as memory leaks in other programs), disk errors, or specific driver (such as graphics card driver) crashes at the time the problem occurred. External programs or system resource exhaustion are common causes of CMS instability.

Q8: When installing CMS, the error "Error sending data: (12007) The server name or address could not be resolved" is reported.

A: This is because the installation process requires a network connection to obtain certain components, but it failed.

Solution: Please install the "Offline Driver Package" first, and then run the CMS main installer.

Part 2: Project, Configuration, and Data Management

Q9: When opening a project, the error "Invalid project file", "no such table", or "file is not a database" is reported.

A: These types of problems indicate that you are not opening a valid project file. Common reasons are: opening a 0KB empty file, or opening a shortcut to the project file instead of the file itself.

Solution: Please ensure that you select and open the correct and complete project file.

Q10: When opening a project, the error "An error occurred while saving..." or "Server program was terminated" is reported.

A: These two problems usually point to the same reason: the project file is set to "Read-only" attribute. This situation is very common when transferring files directly using tools like WeChat.

Solution: Right-click your project file, select "Properties", in the General tab, uncheck the "Read-only" attribute, and then click OK.

Q11: When opening a project, SQLite Error 11: 'database disk image is malformed' is reported.

A: This error indicates that the project file (which is essentially a SQLite database) is damaged. The most common cause is that the computer was shut down abnormally (such as power failure, forced restart) while CMS was running.

Solution: You can only restore an undamaged project file from backup, or re-import the project.

Q12: Why can't I find historical data in the traceability report after updating or modifying the configuration?

A: This is because the system's reports and traceability functions associate data through unique internal IDs. If you delete a configuration item (such as a process, station, collection parameter) and re-create it, even if the name is the same, the system will generate a new ID. This causes the new configuration item to be unable to associate with the historical data generated by the old ID.

Solution: Try to modify the existing configuration and avoid "delete and rebuild" operations. If accidentally deleted, seek technical support to recover from the database level (soft deleted data), or repair through data mapping relationships.

Q13: The data aggregation function sometimes stops working, and checking the database reveals that the Trigger has disappeared.

A: Data aggregation relies on database triggers. Trigger loss may be due to problems with the configuration of other tables (for example, a field configuration error), causing an exception when updating the database structure, affecting trigger generation.

Solution: Check if the configuration of all data tables in the project is correct, especially the source tables relied upon by the aggregation table. Re-editing and saving the aggregation table configuration once can attempt to regenerate the trigger.

Q14: Project data backup or restore failed without prompt.

A: This type of problem has been optimized in the new version. In older versions, common reasons for failure are: 1. The backup file contains plugin data not supported by the current version for restore (such as some LMES plugins); 2. The file to be restored was damaged during transmission.

Solution: It is recommended to upgrade to the new version for a better backup and restore experience and prompts. If it fails, please check file integrity and confirm plugin compatibility.

Part 3: Database Issues (MySQL/InfluxDB)

Q15: Why does the MySQL database service stop suddenly and cannot be started manually?

A: If you see "Operating system error" or InnoDB related IO errors in the MySQL error log, this strongly implies a hardware level problem, usually disk (HDD/SSD) bad sectors or read/write errors.

Solution: Please verify the Windows system log on the server immediately to find disk-related error information, and use tools to detect disk health status. If confirmed to be caused by abnormal shutdown, you can try reinstalling the database or recovering from backup. To prevent this problem, it is recommended to configure innodb_flush_log_at_trx_commit = 1 and sync_binlog = 1 in my.ini to enhance data security.

Q16: The historical archiving service startup reports "unauthorized access".

A: This indicates that the password of the existing InfluxDB database in your environment does not match the default password expected by CMS.

Solution:

• If you remember the old password: Modify the CMS configuration file host/appsettings.json, find the InfluxDB connection string, and change the password to your original password.

• If you don't remember the password or don't need old data: Delete the historical data directly and let CMS rebuild it. Go to the C drive user directory (C:\Users\YourUserName\), delete the hidden .influxdbv2 folder, and then restart CMS.

Q17: Why does software startup fail, and the log prompts duplicate or invalid column names (e.g., CPK and Cpk)?

A: Databases (such as MySQL) are case-insensitive to table names and column names under certain configurations. If you use column names that differ only in case in different places (such as two dynamic data tables), the database will consider them as duplicate column names when creating or modifying the table structure, causing the operation to fail and the service unable to start.

Solution: Check your configuration to ensure that naming within the same scope is unique when case is ignored.

Part 4: Data Communication and PLC/Hardware Protocols

Q18: During communication, variable values show "??" or quality stamp is 3, how to troubleshoot?

A: Quality stamp 3 usually indicates that communication is not initialized or configured incorrectly, which is a comprehensive problem.

Troubleshooting Steps:

1. Authorization Check: Confirm that the protocol used (especially Modbus, OPC UA transparent transmission, etc.) has obtained formal authorization and has not exceeded the authorized number of points. Unauthorized protocols have a 2-hour trial period, and the service will stop after expiration.

2. PLC Side Configuration: For Siemens PLCs, please ensure that "Optimized block access" is disabled for the target DB block. For Mitsubishi PLCs, ensure that MC protocol communication is enabled for the Ethernet port in PLC parameters.

3. Network Check: Confirm that the network is smooth, there is no IP address conflict, and the device connecting to the PLC does not exceed its maximum connection limit (for example, the FINS/TCP maximum connection number for some Omron PLCs is 3).

4. Address Configuration: Check if the variable address is correct. Especially for Modbus protocol, distinguish function code areas (such as 0x, 1x, 4x, etc.).

5. Driver Version: Some communication problems are bugs in old drivers, upgrading to the latest protocol driver plugin can solve them.

Q19: When reading strings with S7 protocol, the first two characters are missing.

A: This is because the data type definition for the string variable in the PLC side data block (DB) is incorrect.

Solution: Please check and correct the data type of the variable in PLC programming software such as TIA Portal to ensure it is consistent with the type configured in CMS.

Q20: When using TCP/IP or Modbus TCP protocol, the "Byte Order" option in the configuration seems not to work.

A: The function of byte order (endianness conversion) depends on the version of the communication driver plugin. Old versions of drivers may not support byte order adjustment for all data types.

Solution: Please upgrade your protocol driver plugin to the latest version to get more comprehensive feature support.

Q21: Using a serial (RS232) scanner, when the barcode length is long, the received data is incomplete.

A: This is because serial data may be sent in multiple packets (messages). Old drivers may not handle this segmented message correctly, resulting in incomplete data splicing.

Solution: This problem has been fixed in the new version, please update your CMS version or related serial driver plugin.

Q22: When using the remote operation and maintenance function to download PLC programs (such as S7-1500), why does it fail or cause PLC errors?

A: The remote operation and maintenance function has high requirements for network quality. Program download failure or interruption is usually due to network instability, such as packet loss, high latency, or MTU (Maximum Transmission Unit) limits.

Solution: You can troubleshoot yourself: ping the virtual IP address of the field device on your computer to see if there is packet loss. If there are network problems, you need to optimize the local or field network environment first.

Q23: When using Panasonic PLC and MC protocol, the content is incorrect when reading strings.

A: Different PLC manufacturers may have slight differences in the implementation of standard protocols. It has been found that when connecting to a Panasonic PLC using the MC protocol, selecting "Mitsubishi" as the device model in the driver configuration can solve the problem of incorrect string parsing.

Solution: This is an effective workaround, please try switching the device model during configuration.

Part 5: LMES, Function Configuration, and Application Logic

Q24: Why does the completion signal not reset, or the system prompts "Missed Process" and cannot enter the station normally?

A: These types of problems are usually production flow logic configuration issues.

• Missed Process: Most likely due to incorrect PLC interaction address configuration. Please check whether the addresses of key interaction variables such as "Inbound Signal" and "Outbound Completion Signal" of the previous and next processes in the process route are configured correctly.

• Not Reset: It may be because there are computers with "duplicate hostnames" in the network, interfering with database communication; it may also be because the flow is stuck in a custom business and has not executed to the final reset step; or data push from SIOT to CMS is delayed due to performance issues.

Q25: Recipe parameter dispatch failed, or there is no record in the recipe log?

A:

• Dispatch Failed: Mostly configuration issues. Please check whether the parameter referenced in the recipe has been accidentally deleted, or whether the dispatch address is correct, especially pay attention to whether there is address conflict or out of bounds (for example, dispatching an INT type variable affects adjacent addresses).

• No Log: This is by design. To generate logs, you need to configure a "Monitoring Variable" in the recipe parameters. Only when the actual value of the monitoring variable is inconsistent with the set recipe value, the system will record a recipe log.

Q26: After a product is judged for rework, when it enters the processed station again, the system reports "Duplicate Code (Result Code 3)" instead of "Pass Through (Result Code 7)".

A: This is the system's design logic. To prevent data confusion, the system does not allow processed products to enter again by default. The correct rework process needs to be specifically configured to ensure that the system can identify that the current product is in "Rework Status", thereby executing specific rework logic instead of standard production logic.

Q27: I configured reading multiple variables in material verification or other functions, but the system reports An item with the same key has already been added.

A: This error indicates that you asked the system to read multiple variables with exactly the same name in one request. The system cannot put these same-named variables into a unique collection when processing internally.

Solution: Please check your function configuration (such as material verification rules) to ensure that variable names referenced in the same operation are unique.

Q28: How to confirm that the interconnected MQTT function works normally after enabling?

A: The MQTT function does not print detailed logs by default.

Solution: Modify the configuration file host/appsettings.json, change the value of UpCloudLogLevel from 0 to 7. Afterwards, you can find detailed cloud_sdk logs in the host\sdklog\[date]\ directory.

Part 6: UI, Components, and Report Issues

Q29: Why does a module (such as Work Order Management) or page on the software interface show blank/abnormal?

A: These types of problems are usually caused by front-end component loading failure or caching.

Solution:

1. Check if it is caused by network fluctuations (error code ERR_NETWORK_CHANGED), ensure the network environment is stable.

2. Clear the cache of the software or browser, a wrong cache file may cause page decoding failure.

3. If a specific function module is blank, try to overwrite or update the component package of that function.

Q30: Exporting reports from the Web side reports an error or fails, but client export is normal.

A: This is usually because you used special characters illegal in URLs or file names when naming "Process" or "Station", such as \, /, :, *, ?, etc. These characters interfere with the background generation of file paths, causing export failure.

Solution: Please check and modify your process/station names to remove these special characters.

Q31: Report or XY curve query is slow, or even causes service crash.

A: This is because the amount of data queried is too large, exceeding the processing capacity of the system or hardware, especially when hundreds of fields or dimension indicators are configured.

Solution: Optimize your query configuration, reduce the number of fields and time range for a single query. For complex reports, it is recommended to cancel automatic refresh and change to manual query. If business really requires large data volume analysis, please contact us to discuss performance optimization solutions.

Q32: The variable value on the interface shows empty, but real-time data can be seen in variable management.

A: This problem usually occurs when you bind a variable to an interface component (such as IO mapping) and then go back to modify the "Data Type" of this variable. This operation may cause a data type mismatch between the front-end component and the back-end variable, resulting in incorrect display.

Solution: Before binding variables, please determine their data type to avoid subsequent modification. If it has occurred, please try to delete the binding and reconfigure.