CZ800: AI assistant and knowledge base

Product Knowledge mode answers questions about product specifications, applications and the operating procedures in this guide. Software mode queries current equipment, points, acquisition status, records and inspection executions, and proposes plans for supported actions.

"How does CZ800 continuous acquisition work?" is a guide question. "Is acquisition running now?" needs the software's current state. Documentation text is not live device status, and a software query is only a snapshot that can change.

The local embedding model converts questions and document passages into vectors for semantic retrieval. The recorded application uses multilingual-e5-small in the local backend. The DeepSeek chat model runs in the cloud and composes answers from selected document passages. These serve different purposes; entering a DeepSeek key does not provide the local embedding files.

Knowledge questions require the AI switch to be enabled, a configured cloud key, complete local embedding files and a ready semantic index. A "key entered" indication only checks configuration. It does not validate connectivity, key validity, account balance or a successful cloud-model call.

The document count reports files scanned and registered, not completion of the vector index. Documents may remain browsable when the model is missing, while semantic questions remain unavailable.

After preparing the model files, click Refresh Knowledge Base and wait for background segmentation and indexing to finish. Refresh in progress, build failure and model files present but failing to load are different states.

If a previous valid index exists, a failed refresh retains that complete earlier version. Without a usable earlier version, resolve the error and rebuild before using semantic questions.

Open the knowledge browser, search by name or model, read the document and ask a question about a particular item when needed. Verify critical specifications and complex diagrams against the approved documentation for the exact product and source.

These software-guide chapters are historical operating records without a confirmed software-release association. They have no brochure page numbering or original PDF pages. Refer to a chapter title and its content; do not invent a manual page number for a software-guide statement.

After documentation changes, older chat references may no longer open because the version changed. Query again to obtain references to available material.

To make updated guide content searchable, an administrator must place it in the registered knowledge collection and register it in the collection index. A document saved elsewhere is not automatically included. Refresh Knowledge Base, allow the new version to be built in the background and wait for Ready before asking about the new material.

The model and document browser do not require an entire manual to be uploaded to the cloud. During questions and answers, the application sends the question, necessary conversation history and retrieved text passages to DeepSeek. The recorded workflow does not send original-page images externally.

Software mode sends the information required by its implemented tools, such as equipment and point names, statuses and parameters.

The recorded AI integration can query:

• The selected equipment and point context on the page.
• Equipment search and points belonging to equipment.
• Acquisition connection and task status.
• Available serial ports.
• Historical-record summaries for an explicit point.
• Route lists, inspection execution history and execution details.

Some queries use pagination, so a result may be only part of the available data.

Requests to open an existing page produce a navigation button that the user clicks. Text saying that a page will be opened does not mean navigation already occurred.

For duplicate names, supply the parent equipment, code or explicit ID. The first result in a list is not automatically the unique intended target.

The recorded plan-confirmation integration includes creating equipment or groups, creating measurement points, editing equipment details, deleting explicitly identified equipment or points, and ordinary-acquisition connection, configuration, start, stop, idle disconnection and some multistep flows.

The sequence is:

1. State the target and requirements clearly.
2. Review the AI's query results and plan card.
3. Read the object, parameters, before-and-after values or deletion effects.
4. Click the confirmation control supplied by the application.
5. Inspect task status and the actual result.

Plans expire. A changed object or device state may invalidate an earlier plan and require a new one.

Confirmed tasks are independent of the chat response. Stop Answering does not stop acquisition or undo a confirmed write. Use an explicit acquisition stop action; AI-started tasks may have a separate cancellation entry provided by the application. Starting a new conversation does not delete equipment records or captured data.

The recorded AI integration does not cover route changes and point-by-point inspection advancement, the dedicated balancing workflow, most chart interactions, diagnosis and report generation, backup and restoration, or other manual operations that have not been adapted.

A feature being available on a software page does not mean an AI tool exists for it. The assistant can explain a procedure without actually performing it.

An ordinary-acquisition AI flow must not use inspection-page context as though it were an ordinary acquisition target. Use the inspection execution panel for an inspection workflow.

For operating guidance, ask:

• "What are the full steps for a first CZ800 connection and single acquisition?"
• "What are waveform, spectrum and envelope spectrum used for?"
• "Why does CZ800 field balancing require manual phase entry?"

For current software information, ask:

• "Show the measurement points for equipment named Cooling Water Pump 1."
• "Query the current acquisition status."
• "List the inspection routes."
• "Show execution details for routeId: 12 and executionId: 34."

The IDs in the last example only demonstrate syntax. Use real IDs returned by the software.

Before submitting an operation, identify the equipment, point and parameters, and verify the target on the confirmation card. Short requests such as "start" or "delete that" leave the target ambiguous.