CZ800: Settings, licensing and backup recovery

Settings contains acquisition defaults, backup and storage, licensing, and language. It saves the baseline for later operations and manages software data and feature permissions.

Changing defaults does not change existing acquisition records and does not mean parameters have been sent to the acquisition card.

Open Settings, then Acquisition Settings. Select the sample rate and sample count, enter sensitivity and save.

The recorded rate options are 5120, 10240, 20480 and 40960 Hz. Sample counts are 1024, 4096, 8192, 16384 and 32768. The Settings default sensor is fixed to acceleration, and the sensitivity control accepts 0.1 to 10000.

On the acquisition page, still check the current form against the actual sensor, particularly when a route template supplies parameters or the form was already edited. Saving defaults does not immediately alter an active task.

The licensing area shows the machine fingerprint, expiry date, and Portable Acquisition, Bearing Diagnosis and Field Balancing feature switches.

To import authorization, copy the machine fingerprint, obtain a valid license code through the established issuing process, paste it into the field, click Import and Validate, and check the updated status.

Validity depends on actual validation and device binding. Development/debug availability differs from production licensing; features visible in development mode do not establish a production entitlement. If a module cannot be opened, check its own license rather than only confirming that Home opens.

Open Backup and Storage, click Back Up Now, wait for success and check the backup list's time and size. A backup preserves software data; it is separate from equipment-configuration export and report downloads. Clicking the button alone does not establish completion.

Keep an appropriate backup before a broad import, configuration overwrite or restoration. Listed backup items come from the software's backup process. Renaming an arbitrary file does not make it a valid backup.

Enable automatic backup if needed and set an interval from 1 to 168 hours. Backup on exit is also available. Save after changing these settings.

The storage area shows database size, free space and low-space status. The warning threshold can be adjusted within the page's allowed range.

Verify automatic backups by their actual results. If disk space is low, handle storage according to the site's retention requirements. Lowering the warning threshold does not resolve a genuine shortage of space.

1. Check the required restore point's time and file, and preserve current data that must be retained.
2. Click Restore for that backup, read the overwrite implications and confirm.
3. The software stages a restore request and displays a pending-restoration state. The currently running data has not yet been replaced.
4. If the wrong backup was selected, use Cancel Restore.
5. Restart the software as prompted to apply restoration.
6. After restart, inspect restore status and failure messages, then verify equipment, points and important records.

Restoration changes the current data state; understand its effect before proceeding. If it fails, use the actual failure explanation. Do not repeatedly submit restore requests or manually overwrite a database while it is running.

The recorded languages are Simplified Chinese and English. Select the language in Settings or with the Home language button; the existing workflow saves the choice.

Home provides light/dark theme switching. The workspace layout menu changes how the interface is arranged without changing measurement data.

The desktop window menu offers fixed actions such as Minimize and Exit. On exit, follow the application's active-acquisition and backup prompts. Closing a report or other business dialog only closes that view; it does not stop an independently running acquisition task.

Home displays service checks, connection state and errors. Use Reconnect or Retry and inspect the error details. An unavailable backend can also prevent data and license status from loading correctly.

Restore the service before deciding that business data is missing. A temporary read failure does not establish that records were deleted.