CZ800: Practical scenarios and troubleshooting

Create an equipment record for the pump and points for the actual measurement locations, with direction matching installation. Open acquisition, connect the card and select the point. Check sensor type, sensitivity, sample rate and count, then begin with a single capture.

After saving, inspect the waveform, spectrum and time-domain statistics. Repeat at the same point under comparable operating conditions and use trends and waterfall plots to compare history. Select explicit records when generating a report.

Check names before saving, record IDs before analysis, operating conditions before comparisons and report scope before delivery. This prevents differences in points or measurement conditions from being mistaken for machine changes.

First check whether sensor mounting, sensitivity, units, operating conditions or speed changed. Repeat the measurement at the same point and inspect waveform impacts and dominant spectral peaks.

If bearing-related components need investigation, use the exact bearing model and valid speed to run diagnosis. Inspect the matching table and decision criteria, save the human conclusion and recommendations, then generate a report.

A rising trend calls for further investigation; it does not identify a particular bearing defect by itself. An envelope match also does not replace checking operating conditions.

Create the equipment and real points, create the route, assign each point's template, set the order and save. Start or continue an execution, then enter acquisition from each execution point.

For every measured point, verify that the actual saved record is linked back, set Normal/Abnormal status and add notes. Explicitly skip points that cannot be measured and give a reason. When all points are processed, complete the execution and select that exact execution in the Report Center.

Ordinary point acquisition does not automatically replace an inspection association. A display of 100% processed does not mean all points were measured or passed.

Confirm licensing and field measurement conditions, select the equipment and point, and choose single-plane or two-plane balancing. Obtain a new record under the actual condition for each stage, check speed and 1X amplitude, and enter phase using one consistent reference.

Complete initial, trial-weight and post-correction residual measurements, review the result and finish the project. Use the project ID for reporting.

Phase is not obtained automatically. Missing measured speed, reuse of a record across stages or a different point prevents the required conditions from being met. The reference verification is not a formal ISO pass.

Generate Word/PDF reports when the recipient needs to read the findings. Export raw waveforms or spectra with metadata for numerical reanalysis. Export equipment configuration when the recipient needs equivalent equipment records. Use system backup to preserve the complete local business data.

Check the equipment, point, capture time and channel in the output. A chart screenshot without measurement context is insufficient for a dependable handoff.

Symptom	First check	Next action
Acquisition, diagnosis or balancing cannot be opened	Service status and the relevant feature license	Check Settings, resolve the error and retry
No device in the serial-port list	Power, cable, driver and operating-system port recognition	Refresh ports and identify the actual card
A port is listed but cannot connect	Wrong port or another application using it	Read the connection error and resolve contention
Start is unavailable	Connection, point, parameter dialog and task state	Satisfy the prerequisites and wait for cleanup
Synchronous acquisition keeps waiting	Speed signal and hardware synchronization conditions	Read timeout information and check the hardware conditions
Stop remains in Stopping state	Device acknowledgment and remaining-data cleanup	Wait for the final state; reconnect if required
No new record after stopping	Whether the first segment had fully arrived	Acquire again under the complete-segment rules
A waveform exists but speed is 0 RPM	Whether valid speed input exists	Assess ordinary and speed-dependent analyses separately
Trend or waterfall is empty	Valid history for the current point	Check filters and record completeness
Chart data differs from the latest capture	Whether an old or sample record is selected	Check record ID, time and point
Balancing rejects a record	Speed, point, sensor, velocity spectrum and channels	Resolve the stated condition; do not reuse stage records
Bearing diagnosis cannot run	Record, model, speed and license	Complete the inputs, run and review decision criteria
Inspection progress does not change after capture	Saved record and failed progress submission	Verify execution context and retry submission
Report generation is unavailable	Record count, project/execution selection and review state	Set the scope and save valid results first
Configuration import has conflicts	Codes, names and matching existing objects	Inspect preflight details, choose a policy, then submit
Restoration seems to have made no change	Whether restoration is only staged and restart occurred	Restart as prompted and inspect failure information
Knowledge base says the local model is not ready	Required model files in the backend's configured model location	Have the model files prepared and checked, then refresh the knowledge base
Documents are counted but knowledge questions fail	Semantic-index readiness	Wait for indexing; inspect the specific error if it fails
The AI stopped answering but acquisition continues	Chat output and tasks run independently	Use acquisition Stop or the applicable task cancellation

Record the page name, operation time, equipment/point/record IDs, current mode, sampling parameters, exact error text and expected result.

For connection issues, include the actual port. For inspection issues, include route and execution IDs. For balancing issues, include project and stage. Do not expose cloud keys or license codes in chats or screenshots.

This guide does not treat reinstalling the software, deleting the database or overwriting configuration as general troubleshooting steps. Address the specific failing object and preserve existing records first.

Use connection and parameters, acquisition and history, analysis views, bearing diagnosis, field balancing, inspection routes, reports and export, settings and recovery, and AI and the knowledge base for the complete steps and limitations.