Why Can a Cynosure Elite iQ Stop Delivering Output?

An Elite iQ output stop is best described by where it happens in the firing sequence. The machine can stop at power-on, in standby, when a handpiece is connected or during a firing attempt, and the same message at different moments points to different evidence groups. The clinic’s first task is to place the stop on that timeline before anything is interpreted.

This event file is for clinic staff who operate an Elite iQ and need a complete record of an output stop without performing service work. It records the sequence position, the visible state and the documented records, and it leaves the cause to the qualified review.

Record the reported symptom, error message and operating context

Quote the message or code exactly as it appears, with the date, the time and the operator’s name. Note which stage the unit had reached: power-on, standby, handpiece connection or the firing attempt itself, because that position is the first clue the qualified review will use.

Record which handpiece was connected and its serial, and note whether a sensor component was in use and recognised by the console before the stop. The session context belongs in the file: what the treatment was doing, how long the unit had been ready and how many firing attempts preceded the stop.

Record one retry if the clinic makes one, and stop retrying after the first confirmed failure. The result of that single retry is context; further retries change the state of the event and stop being evidence.

Check the unit file for earlier stops on this serial. A stop that has happened before is escalated with the previous file, because the qualified review compares the two events rather than treating the new one as isolated.

Ask whether the handpiece or sensor component was changed before the stop and whether the console recognised it when it was connected. The recognition state is recorded exactly as the console showed it, without interpreting what it means.

Note handpiece, Skintel sensor and connection state without disassembly

Check what is visible without opening the system: the handpiece seated in its connection, the sensor component seated where the system uses one, the labels readable and the cables free of damage at the visible ends. Every observation is dated and photographed.

The console state at the stop is written down before power-down: the message, status indicators and whether the unit stayed in standby or held the error. Switching the unit off first can clear the display and erase part of the event.

Check the handpiece connection area for visible debris or an unseated connector before anything is cleaned. The state at the stop is the evidence, and cleaning it first removes the record the qualified review would need.

If a sensor component is present, record its label state and connection in the same photo set as the handpiece, so the two components share one dated record.

The file also records what was not done: no panels opened, no covers removed, no electrical measurement and no optical adjustment, because those actions belong to a qualified party.

Separate user-error evidence from manufacturer-defined interlock and sensor records

Evidence is sorted by where it came from: the operator’s actions and the console’s own interlock and sensor records. Each section carries its own entries, and a deviation in the first section is recorded as a finding rather than an accusation.

The second group holds the manufacturer-defined interlock and sensor records: documented events that name this unit, its software state and the components involved. These records describe what the console’s own systems registered, and they are requested from the qualified party rather than guessed from the message.

Blending operator notes with console records would hide which evidence answered which question, so the file keeps the two streams separate from the first entry to the final review.

Where the console offers an event or error log on its interface, the clinic notes that the log exists and requests the export rather than copying the screen by hand. The export belongs to the manufacturer-defined record group.

Set safe shutdown and qualified-escalation conditions

Power the console down through the documented off procedure and do not restart it to watch the fault again. After shutdown the operator’s role in the event ends; the file and the escalation carry the event forward.

The unit is taken out of use and marked unavailable when the stop involves visible damage, moisture, an unusual odour or any safety-relevant condition. It stays marked until the review is complete.

The clinic decides in advance what takes the unit out of use: a repeated output stop, an unexplained message or any interlock or safety event. Because the decision is written down, the response does not depend on which shift is on duty.

The event file travels to the qualified party intact. The clinic never clears the error, never re-tests after a reset and never calls the work a repair; repair language belongs to the qualified record.

Define what a qualified diagnostic record must contain

The qualified diagnostic record must name the unit serial and software state, the stage at which the stop occurred, the components tested, the method, the instruments, the date, the performer and the findings. A record without these fields cannot be attached to the event.

The qualified record works through the file’s open rows: evidence group, tests, findings, correction and not-tested items. Each row that stays unanswered keeps the diagnosis incomplete.

Summaries that omit the unit, the stage or the date do not close the file. The clinic requests the full attributable record in writing and files the request with the event.

The record should state the firing stage at which the stop was reproduced during the test. A test that stops at a different stage from the event may be testing a different condition, and the file must be able to show the difference.

Define evidence required before return to service

The machine goes back into use only after the file holds the qualified record, a corrective action tied to this unit, and a follow-up verification that succeeded. None of the three can be replaced by the error disappearing.

The diagnostic record is matched against the event file entries; a finding that does not line up with the recorded stage and message is returned for explanation rather than accepted. The match is the basis for accepting the work.

When a stop returns, the clinic opens the new event against the earlier file and sends both with the reference number. The question for the review is what changed between the two events, not what the message says alone.

Before return to service, confirm that the follow-up verification used the same handpiece and sensor configuration that was in place at the stop. A verification on a different configuration leaves the original stage question open.

The clinic asks the service provider to state in the corrective action whether the stop was reproduced during the test and at which stage, so the repair record can be checked against the event file.

The reference number is recorded on the corrective action as well, so the file, the unit and the repair record all carry the same link.

If the clinic operates more than one Elite iQ, the event file names the serial of the affected unit on every page so logs from different machines are never mixed.

Keep the event file with the unit history and date every entry, because the timing of a stop at one stage versus another is part of what the qualified review weighs. A file that cannot show when each stage happened cannot support a recurrence comparison.

Before any decision on the unit, ask for current condition, configuration and evidence for the exact Cynosure Elite iQ option. The market context is in the Elite running-cost guide, and the PicoSure market guide covers the sibling platform; Cynosure laser systems is the product reference.

Frequently Asked Questions

Why does the register keep sensor records separate?

Because sensor state is a documented component fact that the system may rely on, and mixing it with user-error notes would make the cause harder to determine. The register groups records so the qualified review can weigh each type on its own evidence.

What should the clinic record when the stop happens before the firing sequence starts?

Record the stage exactly as it occurred: power-on or standby, with the message, the console state and the handpiece connection status. A stop before firing is a different evidence group from a stop during firing, and the qualified review needs the stage named rather than assumed.