System Maintenance

Factory Reset

Terminal Factory Reset

On the terminal, go to "System Settings" → "System Information", press and hold the "Factory Reset" button for more than 5 seconds. The terminal will restore factory settings and restart automatically. The following items will be restored:

• Terminal ID;
• Network configuration (restored to DHCP auto-obtain);
• Server IP address (restored to default address);
• Display brightness and volume settings (restored to default values);
• Language settings (restored to default language);
• Locally saved annotation files and temporary files (all cleared);
• User-defined quick phrases, signature templates, etc.;
• Connected WiFi passwords (cleared);
• Private materials uploaded in the Personal Center (cleared);

warning

Before performing a factory reset, please confirm that important annotation files have been uploaded to the server or exported and saved. Local files will be unrecoverable after the factory reset. The factory reset operation is irreversible; please proceed with caution.

Electronic Nameplate Factory Reset

• Press and hold the reset button on the nameplate base for more than 5 seconds;
• The nameplate will automatically restore factory settings and restart;
• Restored items include: display content, network configuration, background templates, name information, etc.;
• After the factory reset, the nameplate displays the default welcome screen and needs to re-synchronize name information;

Batch Factory Reset

• The administrator logs into the backend and enters "Device Management" → "Terminal Management";
• Check the terminals that need to be reset (you can select all);
• Click "Batch Factory Reset" and confirm the operation;
• The selected terminals will automatically execute the factory reset and restart;
• The operation results are displayed in the backend (success/failure and reasons);

info

Batch factory reset is suitable for uniformly cleaning terminals after a meeting or for batch troubleshooting. After the factory reset, terminals need to reconfigure the server IP to connect.

Terminal Software Upgrade (OTA Method)

Preparation

• Several terminals to be upgraded (with power supply);
• Network switch and meeting server running normally;
• One Windows 10/11 computer (for operating the backend);
• One terminal upgrade firmware package (File Server\Paperless Terminal\OTA Upgrade Firmware);
• Confirm that the firmware version matches the terminal model; do not mix firmware for different models;

Operation Steps

• Connect the computer to the network where the meeting server is located, ensuring it is in the same network segment as the terminals to be upgraded;
• Log in to the meeting management platform backend;
• Enter "System O&M" → "Terminal Upgrade";
• Click "Upload Firmware", select the terminal upgrade firmware package (.bin or .zip format);
• After the firmware is uploaded, the system automatically verifies file integrity;
• Check the terminals that need to be upgraded (or click "Select All"), then click "Start Upgrade";
• After receiving the upgrade command, the terminal automatically downloads the firmware and executes the upgrade;
• The upgrade progress is displayed in real-time in the backend (percentage);
• After the upgrade is complete, the terminal restarts automatically and displays the new version number;
• In the backend "Terminal Management", verify the terminal version number to confirm the upgrade was successful;

warning

Note 1: Do not turn off the terminal power or disconnect the network connection during the upgrade process, otherwise it may cause the upgrade to fail or the terminal to be unable to start. If the upgrade fails, the terminal will automatically roll back to the previous version, and you can re-initiate the upgrade.

warning

Note 2: It is recommended to upgrade in batches. First upgrade one terminal to confirm it is correct, then batch upgrade the remaining terminals. When batch upgrading, it is recommended to avoid meeting times and choose non-working hours.

info

Note 3: Firmware for different terminal models cannot be mixed. Before upgrading, please carefully check the terminal model and firmware package name. Firmware package naming rules are usually: Model_Version_Date.bin.

Upgrade Failure Handling

• If the terminal upgrade fails and cannot start:
  • Try powering it on again to see if it can start normally;
  • If it still cannot start, contact after-sales personnel to obtain a recovery firmware and restore via USB flashing;
  • USB flashing requires special flashing tools and cables; it is recommended to be operated by after-sales personnel;

Electronic Nameplate Firmware Upgrade

TF Card Upgrade Method

Preparation:

• Several electronic nameplates to be upgraded;
• One TF card, 8-128GB, formatted to FAT32;
• One card reader;
• The latest version of the nameplate firmware (File Server\Electronic Nameplate\Firmware);

Operation Steps:

• Copy the nameplate firmware file to the root directory of the TF card (file name is usually update.bin or firmware package folder);
• Insert the TF card into the electronic nameplate's TF card slot (if available) or connect via the TYPE-C interface (requires OTG adapter);
• After the nameplate is powered on, it automatically detects the firmware and executes the upgrade;
• During the upgrade process, the nameplate screen displays the upgrade progress;
• After the upgrade is complete, the nameplate restarts automatically; remove the TF card;
• Check the nameplate version information to confirm the upgrade was successful;

OTA Online Upgrade Method

• Some electronic nameplates support OTA online upgrade via the backend;
• The operation method is similar to terminal OTA upgrade:
  • Log in to the backend "System O&M" → "Nameplate Upgrade";
  • Upload the nameplate firmware package;
  • Check the nameplates that need to be upgraded, then click "Start Upgrade";
  • The nameplate automatically downloads and executes the upgrade, then restarts after completion;

info

The upgrade method for e-ink electronic nameplates may differ; please refer to the upgrade instructions for the specific model. Some e-ink nameplates support Bluetooth upgrade, which requires operation via a mobile app.

Meeting Management Platform Upgrade

Preparation

• One server host to be upgraded;
• One management platform upgrade package (File Server\Meeting Management Platform\Upgrade Package);
• Back up the current database and configuration files (Important!);
• Confirm that the upgrade package version is compatible with the current version (check the upgrade instructions document);
• Choose a non-meeting time period for the upgrade to avoid affecting normal use;

Operation Steps (Windows)

• Stop the meeting management platform service (find CMP-Server in the service manager and click Stop);
• Back up the original installation directory (copy the entire folder to a backup location);
• Back up the database files (export using database management tools);
• Back up the configuration files (all configuration files in the config directory);
• Extract the upgrade package and overwrite the files in the original installation directory (be careful to retain data directories such as uploads);
• Execute the upgrade script (if any, usually upgrade.bat or SQL script);
• Start the meeting management platform service;
• Log in to the backend to check the version information and whether functions are normal;
• Test core functions (sign-in, voting, screen sharing, etc.) to confirm the upgrade was successful;

Operation Steps (Linux)

• Stop the service: sudo systemctl stop cmp-server;
• Back up data: sudo cp -r /opt/cmp-server /opt/cmp-server-backup;
• Back up database: mysqldump -u root -p cmp_db > cmp_db_backup.sql;
• Extract upgrade package: tar -xzf cmp-server-upgrade-vxxx.tar.gz;
• Overwrite files: sudo cp -r cmp-server-upgrade/* /opt/cmp-server/;
• Execute upgrade script: sudo bash /opt/cmp-server/upgrade.sh;
• Start service: sudo systemctl start cmp-server;
• Check status: sudo systemctl status cmp-server;
• Log in to the backend to verify;

warning

Be sure to back up the database and configuration files before upgrading to prevent data loss in case of upgrade failure. It is recommended to verify in a test environment before upgrading, and only execute in the production environment after confirmation. Do not interrupt the service or restart the server during the upgrade process.

Data Backup and Recovery

Automatic Backup

• The meeting management platform supports setting automatic backup policies;
• Configuration path: "System Settings" → "Backup Management" → "Automatic Backup";
• Backup parameters that can be set:
  • Backup cycle: Daily / Weekly / Monthly;
  • Backup time: Select the specific backup execution time (e.g., 2:00 AM);
  • Backup content: Database / Files / Logs / All;
  • Retention copies: Automatically retain the last N copies of backups; old backups are automatically deleted when exceeded;
  • Backup storage location: Local directory / Network storage / Cloud storage (requires configuration);
• Automatic backup content includes:
  • Meeting data: Meeting information, agendas, attendees, sign-in records;
  • Personnel data: Personnel database, organizational structure, account information;
  • File data: Uploaded meeting files, annotation files, meeting minutes;
  • Voting data: Voting topics, options, results, details;
  • System configuration: Permission configuration, template configuration, system parameters;
  • Log data: Operation logs, connection logs, alarm logs;
• After the backup task is executed, the system sends a notification (email/SMS) to inform the backup result;

Manual Backup

• Log in to the management backend and enter "System Settings" → "Backup Management";
• Click "Backup Now", select the backup content (All / Custom);
• Custom backup can select: Database, Files, Configuration, Logs, etc.;
• Click "Start Backup", the system generates a complete data backup package;
• After the backup is complete, download the backup package to local storage;
• Supports setting a backup package password to enhance security;

Data Recovery

• Enter "System Settings" → "Backup Management" → "Data Recovery";
• Select recovery method:
  • Recover from local backup: Upload a local backup package;
  • Recover from server backup: Select an existing backup file on the server;
• Select recovery content: Full recovery / Database only / Files only;
• Click "Start Recovery", the system executes the recovery operation;
• After recovery is complete, the system data will be rolled back to the backup time point;
• Recovery result notification is sent to the administrator;

danger

Data recovery operations will overwrite current data. Please proceed with caution; it is recommended to execute during non-meeting periods. It is recommended to back up current data before recovery to prevent the need to roll back after recovery. The recovery operation is irreversible; please confirm that the backup file is complete and correct before executing.

Log Management

Log Types

• Operation Log: Records all user operations in the backend (login, creating meetings, modifying configurations, deleting data, etc.);
• Terminal Connection Log: Records terminal online/offline, connection/disconnection, IP changes, etc.;
• Meeting Log: Records meeting creation, start, end, agenda switching, voting initiation, etc.;
• File Log: Records file upload, download, view, annotation, deletion, etc.;
• Exception Alarm Log: Records system exceptions, errors, and alarm information;
• Security Log: Records login failures, permission violations, illegal access, and other security events;

Log Query

• Enter "System Settings" → "Log Management";
• Select the log type and set query conditions:
  • Time range: Start time ~ End time;
  • User account: Specify the operator;
  • Operation type: Filter specific operations;
  • Keywords: Search log content;
• Click "Query" to display the log list that meets the conditions;
• Supports exporting logs (Excel/CSV format);
• Supports setting log retention period (e.g., retain for 90 days; automatically cleaned after expiration);

Log Analysis

• The system provides log statistics charts:
  • Operation frequency trend chart (by day/week/month);
  • User activity ranking;
  • Exception event statistics;
  • Login failure analysis (identifying brute-force attempts);

info

Logs are an important basis for system operation and troubleshooting. It is recommended to regularly check logs and pay attention to abnormal alarms and security events. Log files occupy disk space; it is recommended to set a reasonable retention period and automatic cleanup policy.

Status Codes and Troubleshooting

Terminal Status Code Description

This system uses status codes to indicate the current operating status of the terminal. The specific codes are as follows:

Code	Description	Corresponding Handling Method
0x000	System Normal	No action required
0x001	Network Not Connected	Check if the network cable is plugged in, whether the switch is working normally, and whether the network configuration is correct;
0x002	Server Not Found	Confirm that the server IP address is configured correctly, whether the server service is running normally, and whether the firewall allows access;
0x003	Server Refused Connection	Confirm that the terminal is authorized, the license has not expired, and the number of terminals has not exceeded the limit;
0x004	Meeting Not Started	Confirm whether the meeting has been created and published, or contact the administrator to start the meeting;
0x005	Meeting Ended	The meeting has ended; the terminal enters standby mode, waiting for the next meeting;
0x008	Terminal Not Authorized	The terminal is not registered on the management platform; please contact the administrator to add the terminal;
0x010	File Download Failed	Check the network connection, confirm that the file server is accessible normally, and whether the file exists;
0x020	Insufficient Storage Space	Clean up terminal local temporary files, or contact the administrator to expand storage;
0x040	System Temperature Too High	Check if the terminal heat dissipation holes are blocked, whether the ambient temperature is too high; it is recommended not to exceed 50℃;
0x080	Touch Calibration Abnormal	Enter system settings to recalibrate the touch screen;
0x100	Firmware Version Mismatch	Upgrade the terminal firmware to the latest version;
0x200	License Expired	Contact after-sales personnel to update the license;
0x400	License Terminal Count Exceeded	The number of currently online terminals exceeds the number authorized by the license; please contact after-sales for expansion;
0x800	Insufficient Network Bandwidth	Check the network status, reduce the number of screen sharing terminals or lower the screen sharing quality;
0x1000	Server Storage Space Insufficient	Contact the administrator to clean up server storage or expand capacity;
0x2000	Database Connection Abnormal	Check whether the database service is running normally and contact the administrator for handling;
0x4000	System Under Maintenance	The server is under maintenance; please try again later;
0x8000	Unknown Error	Record the status code and the scenario in which it occurred, and contact after-sales personnel for handling;

Viewing Status Codes

• The terminal enters the "System Settings" → "System Information" page;
• The status code is displayed at the bottom of the page; click to view detailed description and suggested handling plan;
• The status codes of all terminals can also be viewed in the backend "Terminal Management";

FAQ (Continuously Updated)

Q: The terminal cannot connect to the server after powering on

A:

• Check if the network cable is plugged in and whether the network indicator lights are on normally (green solid or blinking);
• Confirm whether the server IP address in the terminal network configuration is correct (enter System Settings → Network Settings to view);
• Use a computer to ping the server IP address to confirm whether the server is reachable;
• Check whether the meeting management platform service on the server is running normally (log in to the server to view the service status);
• Check whether the server firewall has allowed port 8080;
• Try restoring the terminal to factory settings and then reconfiguring the server IP;
• If all of the above are normal, record the terminal status code and contact after-sales personnel;

---

Q: The electronic nameplate does not display names or displays incorrect names

A:

• Confirm that the meeting management platform has published the seating arrangement information (enter Seat Management to view the publication status);
• Check whether the nameplate network connection is normal (network indicator light status);
• Try republishing the seat information, or refresh the nameplate individually (Backend Nameplate Management → Refresh);
• If using the USB import method, please confirm that the Excel file format is correct (Name, Position, and Organization column names match the template);
• Check whether the nameplate is bound to the correct meeting room and seat;
• Try restoring the nameplate to factory settings and then re-synchronizing;

---

Q: Screen sharing is stuttering or has severe delay

A:

• Check whether the network bandwidth is sufficient; it is recommended to use a gigabit network environment; screen sharing bandwidth usage is about 10-20Mbps per stream;
• Reduce the number of screen sharing terminals, or use grouped screen sharing (only broadcast to the required terminals);
• Lower the screen sharing resolution or frame rate (Backend Settings → Screen Sharing Parameter Settings);
• Check whether other high-traffic applications are occupying network bandwidth (such as video downloads, large file transfers);
• Confirm whether the terminal and server hardware performance meet the requirements (CPU, memory usage);
• Try restarting the terminal or re-initiating screen sharing;
• Wired network environment provides better screen sharing effect than wireless; it is recommended to use wired for important scenarios;

---

Q: File annotations cannot be saved

A:

• Check whether the terminal storage space is sufficient (enter System Settings → System Information to view storage space);
• Confirm whether the current file has annotation permission (some files may be set to view only);
• Try saving the annotation locally instead of to the server (select "Local" when choosing the save location);
• Check whether the network connection is normal; saving to the server requires a smooth network connection;
• Restart the terminal and try again;
• If the problem persists, try restoring to factory settings and reconfiguring;

---

Q: Voting results are not displayed or displayed abnormally

A:

• Confirm that the vote has ended normally (the chairperson clicks "End Vote" or it ends automatically after timeout);
• Check whether all terminals participating in the vote have submitted (those not submitted are considered abstentions);
• Refresh the backend page or re-enter the Vote Management to view;
• Confirm that the voting mode is set correctly (real-name/anonymous); anonymous votes do not display individual voting details;
• Check whether the server time and terminal time are synchronized; time desynchronization may cause voting data anomalies;
• If voting data is lost, check whether the server database is normal and view the logs to investigate the cause;

---

Q: Terminal lifting abnormality (cannot lift or does not lift to the correct position)

A:

• Check whether the power connection is normal and confirm that the power indicator light is on;
• Confirm that the lifting mechanism has no foreign objects blocking it and whether the desktop opening size matches;
• Try manually pushing gently to assist the lift to eliminate mechanical jamming (pay attention to the force; do not forcibly push);
• Enter system settings and check the lifting parameter settings (speed, limit position, etc.);
• Try restoring to factory settings and reconfiguring;
• If it still cannot be resolved, please stop using it immediately and contact after-sales personnel for repair;

warning

Non-professionals should not disassemble the lifting mechanism to avoid damaging the equipment or causing personal injury. The lifting mechanism contains precision motors and transmission devices; self-disassembly may void the warranty.

---

Q: Terminal files are not automatically cleared after the meeting ends

A:

• Confirm whether the meeting has been correctly clicked "End Meeting" (only closing the meeting interface does not equal ending the meeting);
• Check whether the terminal has normally connected to the server to receive commands (whether the network status is normal);
• Manually enter the terminal "System Settings" → "Clear Cache" to execute file clearing;
• If it involves a confidential meeting, it is recommended to manually restore to factory settings to ensure data is completely cleared;
• Check whether the automatic cleanup policy in the backend "System Settings" → "Security Policy" is enabled;

---

Q: The meeting management platform webpage cannot be opened

A:

• Confirm that the server host is powered on and the network connection is normal (server indicator light status);
• Check whether the meeting management platform service has started (Windows Service Manager / Linux systemctl);
• Confirm that the access address and port number are correct (default http://ServerIP:8080/admin);
• Check whether the server firewall has allowed port 8080 (Windows Firewall / iptables / firewalld);
• Use commands to check port occupancy:
  • Windows: netstat -ano | findstr 8080
  • Linux: netstat -tlnp | grep 8080 or ss -tlnp | grep 8080
• Check whether the port is occupied by other programs; if occupied, modify the configuration or release the port;
• View the server log files (under the logs directory) to investigate startup errors;
• Try restarting the meeting management platform service;

---

Q: External signal cannot be screen-shared to the terminal

A:

• Confirm that the external signal source is correctly connected to the matrix or signal acquisition device (cable connection, interface correspondence);
• Check whether the signal source device is powered on and outputting signals normally (the signal source itself displays normally);
• In the backend "Signal Management", confirm whether the signal source is recognized (displaying online status);
• Check whether the matrix switching channel is correct (matrix input/output channel correspondence);
• Confirm that the terminal and large screen resolution settings match the signal source (to avoid black screen caused by resolution incompatibility);
• Try re-plugging the signal cable or replacing the cable for testing;
• Check whether the signal acquisition device driver is normal and try restarting the acquisition device;

---

Q: Terminal touch is not sensitive or offset

A:

• Enter "System Settings" → "Touch Calibration", and recalibrate the touch screen according to the on-screen prompts (click the calibration points on the screen in sequence);
• Clean the screen surface to eliminate stains, water stains, and fingerprint interference (wipe with a clean, soft cloth);
• Check whether the screen protector is bubbling, shifting, or worn; replace the protector if necessary;
• Confirm that the terminal is not connected to an external mouse/keyboard (some terminals disable touch when external devices are connected);
• If it is still abnormal after calibration, record the terminal model and firmware version and contact after-sales personnel for handling;

---

Q: How to export meeting sign-in records and voting results

A:

• Log in to the meeting management platform backend;
• Enter the corresponding meeting's "Sign-in Management" or "Vote Management" page;
• Click the "Export" button and select the export format (Excel/PDF);
• Select the export content (all data / summary data / detailed data);
• Click "Confirm" to download the exported file to local storage;
• Sign-in record export content includes: Name, Seat Number, Sign-in Time, Signature Image, Sign-in Method;
• Voting result export content includes: Topic, Options, Votes, Percentage, Real-name Voting Details (if real-name is enabled);

---

Q: What file formats does the terminal support

A:

• Documents: Word(doc/docx), Excel(xls/xlsx), PowerPoint(ppt/pptx), PDF, TXT, RTF;
• Images: JPG, JPEG, PNG, BMP, GIF, TIFF, WebP;
• Videos: MP4, AVI, MKV, MOV, WMV, FLV (some formats require decoder installation);
• Audio: MP3, WAV, AAC, FLAC, OGG;
• Archives: ZIP, RAR (supports decompression to view internal files);

info

Some special format files may need to be converted before uploading; it is recommended to use common office formats to ensure compatibility. Video files are recommended to be converted to MP4 format (H.264 encoding) for the best compatibility. For oversized files (exceeding 500MB), it is recommended to compress or split them before uploading.

---

Q: How to set up a confidential meeting

A:

• When creating the meeting, select "Confidential Meeting" for the "Meeting Type";
• Enable the following settings in the "Security Policy":
  • Materials not viewable before meeting: The terminal does not display any files before the meeting starts;
  • Immediate cleanup after meeting: Immediately clear all local files after the meeting ends;
  • Disable download: Prohibit downloading files to local storage;
  • Disable sharing: Prohibit file sharing and forwarding;
  • Enable strongest watermark: Full-screen tiled display of username and time watermark;
  • Enable anti-screenshot: Disable system screenshot function;
  • Disable USB: Prohibit reading USB drives and external storage;
• Set file permissions to "View Only" and turn off annotation permissions (or force upload after annotation, not allowing local saving);
• Disable the meeting communication function to prevent information leakage;
• Disable the web browsing function to prevent sending materials via the network;
• After the meeting ends, execute "Thorough Cleanup" in the backend to ensure that temporary files on the server are also deleted;

warning

Security settings for confidential meetings should be configured in full at the time of meeting creation; modifications during the meeting may cause some terminals to not synchronize in time. For meetings involving state secrets, it is recommended to use physically isolated networks and dedicated confidential terminals.

---

Q: How to handle an expired meeting management platform license

A:

• Log in to the backend and enter "System Settings" → "License Management";
• View the license validity period and authorization information;
• Contact after-sales personnel and provide the current license number and machine code;
• After-sales personnel will generate a new license file based on requirements;
• Upload the new license file in the backend and click "Activate";
• After successful activation, the system returns to normal use;
• The system will send a reminder notification 30 days before the license expires; please renew in time;

---

Q: The terminal displays "License Terminal Count Exceeded"

A:

• The number of currently online terminals exceeds the maximum number of terminals authorized by the license;
• Solutions:
  • Contact after-sales personnel to purchase an expansion license to increase the number of authorized terminals;
  • Temporarily shut down some non-essential terminals to free up authorized slots;
  • Check whether there are offline terminals still occupying authorization (clean up zombie terminals in the backend terminal management);
• The license authorized quantity includes all connected terminals (meeting terminals + electronic nameplates + screen sharing terminals, etc.); please count all device quantities;