SICK Safety Scanner Error Codes

E1: Sensor head faulty

What it means: The scanner has found an internal fault in the sensor head, so it keeps the OSSDs off. The display alternates E and 1.^[1]

Also on: microScan3 also uses E1, with a different meaning (internal scanner error)

Device response: OSSDs off; power off for at least 2 s and on again; if it stays, send for repair

Likely causes

• Internal fault in the sensor head
• A transient fault that clears after a power cycle

First checks, in this order

1. Switch off the supply voltage for at least 2 seconds, then switch it back on.
2. If E1 comes back, the sensor head, I/O module or system plug has to go to SICK for repair.
3. Use the CDS diagnostics to read the error details before replacing parts.

E1: Safety laser scanner defective

What it means: The S300 has found an internal fault and keeps the OSSDs off. The display alternates E and 1.^[2][3]

Also on: S300 Mini (listed as safety laser scanner in error state or faulty)

Device response: OSSDs off; power off for at least 2 s and on again; if it stays, send for repair

Likely causes

• Internal fault in the scanner
• A transient fault that clears after a power cycle

First checks, in this order

1. Switch off the supply voltage for at least 2 seconds, then switch it back on.
2. If E1 comes back, send the scanner or the system plug to SICK for repair.
3. Use the CDS diagnostics to read the error details.

E2: I/O module faulty

What it means: The S3000 has found a fault in its I/O module (the electronics unit between the sensor head and the system plug) and keeps the OSSDs off.^[1]

Device response: OSSDs off; power off for at least 2 s and on again; if it stays, send for repair

Likely causes

• Internal fault in the I/O module
• A transient fault that clears after a power cycle

First checks, in this order

1. Switch off the supply voltage for at least 2 seconds, then switch it back on.
2. If E2 comes back, send the I/O module to SICK for repair.
3. Read the error details with the CDS before replacing parts.

4: Waiting for valid input signals

What it means: The scanner is waiting for a valid signal pattern on its control inputs to select a monitoring case, so the OSSDs stay off. It is normal for a moment at start-up and clears by itself when a valid signal arrives.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Control input wiring fault
• Control signals do not match the configured evaluation type (1-of-n or complementary)
• EFI status Speed valid not received when speed ranges switch the monitoring cases
• Configuration does not match the machine control

First checks, in this order

1. Check the wiring of the control inputs.
2. Check that the control signals switch correctly and match the evaluation type set in the configuration.
3. If speed ranges switch the monitoring cases, check that the EFI status Speed valid is transferred.
4. Check the configuration with the CDS and transfer the corrected configuration to the scanner.

6: Waiting for configuration or configuration not completed

What it means: The scanner has no valid configuration, so the OSSDs stay off. New scanners leave the factory in this state, and it also shows when the configuration in the system plug does not fit the scanner.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• New or reset scanner that has not been configured yet
• Configuration transfer not completed
• Configuration in the system plug made for a higher variant (for example an Expert configuration on a Professional scanner)

First checks, in this order

1. Transfer the configuration with the CDS; the 6 goes out once the transfer succeeds.
2. If it stays, check the configuration with the CDS and transfer the corrected configuration again.
3. Check that the configuration saved in the system plug is compatible with this scanner variant. Replacement scanners must be the same variant or a higher one.

6 (flashing): Waiting for restart of the device

What it means: The scanner needs a full restart, for example after a configuration change, and keeps the OSSDs off until it gets one.^[1][2][3]

Also on: S300 Mini (same code and text)

Device response: OSSDs off until power cycled (at least 2 s off)

Likely causes

• Device restart required after configuration or after an error

First checks, in this order

1. Switch off the supply voltage for at least 2 seconds, then switch it back on.

8: Error in the external device monitoring (EDM)

What it means: The feedback from the machine contactors (EDM) did not respond as expected. With restart interlock configured, the scanner switches the OSSDs off, the red LED lights and 8 shows steady.^[1][2][3]

Also on: S300 Mini (same code and text)

Device response: OSSDs off (restart interlock configured)

Likely causes

• Contactor welded, sticking or too slow to drop out
• EDM feedback wiring fault
• EDM input wired but the function set differently in the configuration

First checks, in this order

1. Check that the contactors work correctly and are wired correctly, then fix any fault.
2. Check the EDM feedback contacts and wiring.
3. Check the EDM setting in the CDS. If EDM is not used, the EDM inputs stay unconnected.

8 (flashing): Error in the external device monitoring (EDM), lock-out

What it means: A contactor (EDM) error when the scanner runs without internal restart interlock or with a restart delay. The system locks out completely and 8 flashes.^[1][2][3]

Also on: S300 Mini (same code and text, 2 s wait)

Device response: Lock-out; power cycle after fixing the contactor fault

Likely causes

• Contactor welded, sticking or too slow to drop out
• EDM feedback wiring fault

First checks, in this order

1. Check that the contactors work correctly and are wired correctly, then fix any fault.
2. Then switch the supply off and back on: the S3000 manual says wait at least 3 seconds, the S300 manual at least 2 seconds.

9: Error in the control switch for restart or reset

What it means: The scanner sees a fault on the restart/reset button input. During start-up the S3000 manual also lists 9 as waiting for reset; if it stays, check the button and its wiring.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Restart/reset pushbutton defective or stuck
• Reset input wiring shorted to 24 V

First checks, in this order

1. Check that the restart/reset control switch works. The pushbutton may be defective or stuck.
2. Check the wiring of the control switch for a short circuit to 24 V.

3: Initialization or waiting for the EFI partner device

What it means: The scanner is starting up, or it is waiting for a second device connected through the EFI interface to finish starting up. It normally goes out by itself; while it shows, the OSSDs stay off.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Partner device on the EFI link not running
• EFI wiring fault
• Configuration expects a partner device that is not connected

First checks, in this order

1. Wait for the display to go out after start-up.
2. If it stays, check that the partner device is running and check the EFI wiring.
3. If no partner device is connected, check the system configuration with the CDS and transfer the corrected configuration.

E3: Configuration memory in the system plug defective

What it means: The memory in the system plug, which holds the scanner configuration, has failed.^[1][2]

Device response: OSSDs off; power off for at least 2 s and on again; if it stays, send for repair

Likely causes

• Defective configuration memory in the system plug

First checks, in this order

1. Switch off the supply voltage for at least 2 seconds, then switch it back on.
2. If E3 comes back, send the system plug to SICK for repair.
3. A replaced system plug needs the configuration transferred with the CDS and acceptance by qualified safety personnel.

E4: Second device on EFI in error state

What it means: A second scanner or device connected through EFI is in its error state, so this scanner reports it too.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Fault on the connected EFI partner device
• EFI connection fault

First checks, in this order

1. Read the code on the connected device and fix that error first.
2. Check the EFI connection between the devices.

1: Object in the simultaneous protective field (dual field mode)

What it means: Status, not an error. On an S3000 in dual field mode, the right-hand vertical segments (shown as 1) mean an object is in the simultaneous protective field or the monitored contour has changed. It helps when testing simultaneous fields or EFI systems.^[1]

Likely causes

• Person or object in the simultaneous protective field
• Surrounding contour changed (when contour as reference is configured)

First checks, in this order

1. Clear the simultaneous protective field.
2. If nothing is in the field, check the field layout and reference contour with the CDS.

I: Object in the protective field (dual field or compatibility mode)

What it means: Status, not an error. The left-hand vertical segments (shown as I) mean an object is in the protective field: on the S3000 in dual field mode, on the S300 in compatibility mode.^[1][2]

Likely causes

• Person or object in the protective field
• Surrounding contour changed (S3000, when contour as reference is configured)

First checks, in this order

1. Clear the protective field.
2. If nothing is in the field, check the field layout with the CDS.

F1: Overcurrent at OSSD connection 1

What it means: Output OSSD 1 is drawing too much current.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Faulty or oversized switching element (contactor, relay) on OSSD 1
• Short circuit to 0 V on the OSSD 1 wiring

First checks, in this order

1. Check the contactor or relay on OSSD 1 and replace it if needed.
2. Check the wiring for a short circuit to 0 V.

F2: Short circuit to 24 V at OSSD connection 1

What it means: Output OSSD 1 is shorted to 24 V, so the scanner cannot switch it off reliably.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• OSSD 1 wire touching 24 V (damaged cable, terminal, wrong wiring)

First checks, in this order

1. Check the OSSD 1 wiring for a short circuit to 24 V.

F3: Short circuit to 0 V at OSSD connection 1

What it means: Output OSSD 1 is shorted to 0 V.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• OSSD 1 wire touching 0 V (damaged cable, terminal, wrong wiring)

First checks, in this order

1. Check the OSSD 1 wiring for a short circuit to 0 V.

F4: Overcurrent at OSSD connection 2

What it means: Output OSSD 2 is drawing too much current.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Faulty or oversized switching element (contactor, relay) on OSSD 2
• Short circuit to 0 V on the OSSD 2 wiring

First checks, in this order

1. Check the contactor or relay on OSSD 2 and replace it if needed.
2. Check the wiring for a short circuit to 0 V.

F5: Short circuit to 24 V at OSSD connection 2

What it means: Output OSSD 2 is shorted to 24 V.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• OSSD 2 wire touching 24 V (damaged cable, terminal, wrong wiring)

First checks, in this order

1. Check the OSSD 2 wiring for a short circuit to 24 V.

F6: Short circuit to 0 V at OSSD connection 2

What it means: Output OSSD 2 is shorted to 0 V.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• OSSD 2 wire touching 0 V (damaged cable, terminal, wrong wiring)

First checks, in this order

1. Check the OSSD 2 wiring for a short circuit to 0 V.

F7: Short circuit between OSSD connection 1 and 2

What it means: The two safety outputs are shorted together, so they are no longer independent.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Cross-connection between the OSSD 1 and OSSD 2 wires
• Wiring error at the safety relay or controller inputs

First checks, in this order

1. Check the OSSD wiring and remove the short between OSSD 1 and OSSD 2.

F9: General OSSD wiring error

What it means: The scanner sees a fault on the OSSD wiring that does not match one of the specific F codes.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• OSSD wiring fault somewhere between the scanner and the machine control

First checks, in this order

1. Check the complete wiring of both OSSDs, including connectors and terminals.

I1: No measured values within at least 90 degrees

What it means: Across a sector of at least 90 degrees the scanner gets no reflections back (within its maximum measuring range: 49 m on the S3000, 29.9 m on the S300), so it cannot see any obstacle there, for example building walls.^[1][2][3]

Also on: S300 Mini (same code and text, 29.9 m)

Likely causes

• Scanner looking into open space with nothing within range across 90 degrees
• Scanner tilted or mounted so the scan plane misses the surroundings

First checks, in this order

1. Make sure the scanner always receives measured values somewhere within a 90 degree range; that range can sit anywhere in the scan range.
2. Check the mounting angle and the scan plane.

I1 (flashing): Manipulation prevention shut-down

What it means: The scanner checks whether every measured value in any 90 degree segment equals the maximum measurable distance (nothing in view, as if covered or turned away). If so, it shuts down: after 2 hours in mobile applications (flashing I alternating with 1) or after 5 seconds in stationary applications (flashing I and flashing 1).^[1][2][3]

Also on: S300 Mini (manipulation prevention section)

Device response: Device shuts down after 2 hours (mobile) or 5 seconds (stationary)

Likely causes

• Scanner view blocked or turned away from its surroundings
• Scanner mounted so a 90 degree segment sees only open space

First checks, in this order

1. Check that nothing has covered, moved or turned the scanner.
2. Check that the scanner receives measured values within a 90 degree range.

I2: Device is dazzled

What it means: Strong outside light is blinding the scanner.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Headlights, infrared light sources, strobe lights or direct sun in the scan plane

First checks, in this order

1. Check for an outside light source shining into the scanner (headlight, infrared source, strobe, sun).
2. If needed, remount the scanner so the light source is out of its view.

I3: Temperature error

What it means: The scanner's operating temperature is outside the permitted range.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Ambient temperature too high or too low
• Heat source or cold air flow near the scanner

First checks, in this order

1. Check that the scanner is used within the permitted ambient conditions in the technical data.

u1: Contamination measurement: window contaminated

What it means: The contamination measurement reports a dirty window. On the S3000 it means channel 1 of the front screen measurement; on the S300 it means the light emission window on the optics cover.^[1][2][3]

Also on: S300 Mini (same code and text as the S300)

Likely causes

• Dust, oil mist, fingerprints or residue on the light emission window

First checks, in this order

1. Clean the front screen (S3000) or the light emission window on the optics cover (S300).
2. Remove dust with a clean, soft brush, then wipe the light emission window with a SICK lens cloth moistened with lens cleaner. Do not use aggressive or abrasive cleaners.
3. If the cover is scratched or damaged, it must be replaced and then calibrated.

u2 to u6: Contamination measurement channels 2 to 6 contaminated

What it means: One of channels 2 to 6 of the S3000 front screen contamination measurement sees a dirty window (u2 is channel 2, and so on up to u6).^[1]

Likely causes

• Dust, oil mist, fingerprints or residue on part of the front screen

First checks, in this order

1. Clean the front screen: soft brush first, then a SICK lens cloth with lens cleaner on the light emission window.
2. Do not use aggressive or abrasive cleaners.
3. If the front screen is scratched or damaged, replace it and run a front screen calibration.

u7: No front screen fitted or contamination measurement dazzled

What it means: The S3000 contamination measurement cannot work: either the front screen is missing or outside light is dazzling the measurement.^[1]

Likely causes

• Front screen removed or not fitted
• Headlight, infrared source, strobe or sun shining on the scanner

First checks, in this order

1. If no front screen is fitted, fit a new front screen and then run a front screen calibration.
2. If a front screen was fitted, check for an outside light source dazzling the scanner.

u8: Traceability data incorrect or front screen calibration failed

What it means: The S3000 front screen calibration data is not valid.^[1]

Likely causes

• Front screen calibration failed or was not done after a front screen change
• Incorrect traceability data

First checks, in this order

1. Run a front screen calibration with the CDS (new, clean front screen, at room temperature 10 to 30 °C).
2. If the code stays, replace the device.

u9: Traceability data incorrect or front screen calibration failed

What it means: Same meaning as u8 on the S3000: the front screen calibration data is not valid.^[1]

Likely causes

• Front screen calibration failed or was not done after a front screen change
• Incorrect traceability data

First checks, in this order

1. Run a front screen calibration with the CDS (new, clean front screen, at room temperature 10 to 30 °C).
2. If the code stays, replace the device.

u8: Dazzling of the contamination measurement

What it means: On the S300, the contamination measurement is being dazzled; the optics cover may also be missing.^[2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Headlight, infrared source, strobe or sun shining on the scanner
• Optics cover not fitted

First checks, in this order

1. Check for an outside light source dazzling the scanner.
2. If the optics cover is missing, fit a new optics cover and run an optics cover calibration.

u9: Dazzling of the contamination measurement

What it means: Same meaning as u8 on the S300: the contamination measurement is dazzled, or the optics cover may be missing.^[2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Headlight, infrared source, strobe or sun shining on the scanner
• Optics cover not fitted

First checks, in this order

1. Check for an outside light source dazzling the scanner.
2. If the optics cover is missing, fit a new optics cover and run an optics cover calibration.

u (flashing): Front screen or optics cover calibration active

What it means: Status, not an error. The scanner is calibrating its contamination measurement to a new front screen (S3000) or optics cover (S300).^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Calibration started from the CDS after a cover change

First checks, in this order

1. Let the calibration finish. Calibrate only with a new, clean cover at room temperature (10 to 30 °C).

L2: Invalid configuration of the EDM

What it means: The external device monitoring (contactor feedback) setting does not match how the machine side is wired.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• EDM feedback not connected the way the configuration expects

First checks, in this order

1. Check that the machine-side EDM feedback is connected correctly.
2. Compare the EDM setting in the CDS with the actual wiring.

L4: Host and guest addressing or EFI connection fault

What it means: Both scanners in an EFI pair may be addressed as guest, or a device on EFI or its connection is defective or disrupted.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Guest jumper (between terminals 7 ERR and 10 A1) fitted on the host device as well
• Defective EFI partner device
• EFI cable fault or interference

First checks, in this order

1. Remove the jumper on the host device; only the guest carries it.
2. Check the connected device and the EFI connection to it.

L8: Undervoltage of the supply voltage

What it means: The S300 supply voltage has dropped too low.^[2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Weak or overloaded 24 V power supply
• Voltage drop on long or undersized supply cables
• Loose supply connection

First checks, in this order

1. Check the power supply unit.
2. Check the connecting cables and terminals for the supply.

L9: Short circuit at the restart/reset input

What it means: The restart/reset input is shorted to another input or output. On the S3000 the code also shows when the reset pulse does not meet the timing requirements.^[1][2][3]

Also on: S300 Mini (same code and text as the S300)

Likely causes

• Cross-circuit between the reset input wire and another input or output
• Reset pulse too long or too short (S3000)

First checks, in this order

1. Check the wiring for cross-circuits.
2. On the S3000, check that the reset pulse meets the requirements in the manual's reset timing figure.

n1: Input signal for a non-defined monitoring case

What it means: The control inputs select a combination that is not assigned to any monitoring case.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Vehicle or machine in a position or state the configuration does not cover
• Control input signals wrong
• Monitoring cases configured incompletely

First checks, in this order

1. Check the path of the vehicle, or the operating process of the machine.
2. If needed, check the monitoring case configuration with the CDS.

n2: Incorrect sequence when switching the monitoring cases

What it means: The monitoring cases switched in an order that the configured sequence does not allow.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Machine or vehicle process changed
• Monitoring case sequence configured too strictly

First checks, in this order

1. Check the path of the vehicle, or the operating process of the machine.
2. If needed, check the monitoring case configuration with the CDS.

n3: Incorrect operation of the control inputs

What it means: The digital control inputs that switch the monitoring cases are being operated incorrectly.^[1][2][3]

Also on: S300 Mini (listed as incorrect operation of the control inputs via EFI)

Likely causes

• Control signals switching at the wrong time or in the wrong pattern

First checks, in this order

1. Check how the digital control inputs are operated by the machine control.

n4: Short circuit on control inputs A1/A2 or incorrect operation via EFI

What it means: Control input pair A is shorted, or it is being operated incorrectly through EFI.^[1][2][3]

Also on: S300 Mini (incorrect operation of A1/2 via EFI only)

Likely causes

• Short circuit on the A1/A2 input wiring
• Wrong A1/A2 signals from a device on EFI

First checks, in this order

1. Check the wiring and the digital control inputs.
2. Check the wiring to the devices connected through EFI.

n5: Short circuit on control inputs B1/B2 or incorrect operation via EFI

What it means: Control input pair B is shorted, or it is being operated incorrectly through EFI.^[1][2][3]

Also on: S300 Mini (incorrect operation of B1/2 via EFI only)

Likely causes

• Short circuit on the B1/B2 input wiring
• Wrong B1/B2 signals from a device on EFI

First checks, in this order

1. Check the wiring and the digital control inputs.
2. Check the wiring to the devices connected through EFI.

n6: Short circuit on control inputs C1/C2 or incorrect operation via EFI

What it means: Control input pair C is shorted, or it is being operated incorrectly through EFI.^[1][2][3]

Also on: S300 Mini (incorrect operation of C1/2 via EFI only)

Likely causes

• Short circuit on the C1/C2 input wiring
• Wrong C1/C2 signals from a device on EFI

First checks, in this order

1. Check the wiring and the digital control inputs.
2. Check the wiring to the devices connected through EFI.

n7: Control inputs D1/D2: short circuit or incorrect operation via EFI

What it means: On the S3000, control input pair D is shorted or operated incorrectly through EFI. On the S300 the code only covers incorrect operation of D1/D2 through EFI.^[1][2][3]

Also on: S300 Mini (incorrect operation of D1/2 via EFI)

Likely causes

• Short circuit on the D1/D2 input wiring (S3000)
• Wrong D1/D2 signals from a device on EFI

First checks, in this order

1. Check the wiring and the digital control inputs.
2. Check the wiring to the devices connected through EFI.

n8: Incorrect operation of E1/E2 via EFI

What it means: Control input pair E, which is only available through EFI, is being operated incorrectly.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Wrong E1/E2 signals from a device on EFI

First checks, in this order

1. Check the device that sends E1/E2 over EFI and the EFI wiring.

d1: Speed tolerance exceeded

What it means: The speeds measured by the two incremental encoders differ by too much.^[1][2]

Likely causes

• Encoder fault, slipping wheel or loose encoder mounting
• Encoder input configuration wrong

First checks, in this order

1. Check the incremental encoders.
2. Check the configuration of the incremental encoder inputs with the CDS.

d2: Direction of movement from the encoders differs

What it means: The two incremental encoders report different directions of travel.^[1][2]

Likely causes

• Encoder input wiring swapped or wrong pin assignment

First checks, in this order

1. Check the wiring of the incremental encoder inputs, for example for wrong pin assignments.

d3: Maximum frequency at INC1 input exceeded

What it means: The pulse frequency on encoder input INC1 is above the allowed maximum.^[1][2]

Likely causes

• Encoder fault or interference
• Encoder input configuration wrong
• Vehicle faster than the maximum allowed speed

First checks, in this order

1. Check that the incremental encoders work.
2. Check the configuration of the encoder inputs with the CDS.
3. Check whether the vehicle exceeds its maximum allowed speed.

d4: Maximum frequency at INC2 exceeded or speed threshold exceeded

What it means: On the S3000, the pulse frequency on encoder input INC2 is too high, or a monitored speed threshold has been exceeded.^[1]

Likely causes

• Encoder fault or interference
• Encoder input configuration wrong
• Vehicle faster than the maximum allowed speed or than the configured speed threshold

First checks, in this order

1. Check that the incremental encoders work.
2. Check the configuration of the encoder inputs with the CDS.
3. Check whether the vehicle exceeds its maximum allowed speed.
4. Check the speed threshold set in the related monitoring cases.

d4: Maximum frequency at INC2 input exceeded

What it means: On the S300, the pulse frequency on encoder input INC2 is above the allowed maximum.^[2]

Likely causes

• Encoder fault or interference
• Encoder input configuration wrong
• Vehicle faster than the maximum allowed speed

First checks, in this order

1. Check that the incremental encoders work.
2. Check the configuration of the encoder inputs with the CDS.
3. Check whether the vehicle exceeds its maximum allowed speed.

y1: Device internal error

What it means: The S3000 has an internal error that needs a replacement device.^[1]

Likely causes

• Internal hardware fault

First checks, in this order

1. Replace the device. Afterwards, check the protective device as the manual requires.

y2: I/O module internal error

What it means: The S3000 I/O module has an internal error.^[1]

Likely causes

• Internal fault in the I/O module

First checks, in this order

1. Replace the I/O module, following the replacement steps in the manual with the machine isolated.

y3: Invalid combination of I/O module and sensor head

What it means: The S3000 I/O module does not fit the sensor head it is mounted on.^[1]

Likely causes

• Wrong I/O module fitted, for example after a swap

First checks, in this order

1. Check that the correct I/O module is used and replace it if needed.

P: A device connected via EFI reports a malfunction

What it means: A partner device on the EFI link reports an error.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Error on the connected EFI device

First checks, in this order

1. Run error diagnosis on the device connected to this scanner and fix that error.

o: Park or standby mode

What it means: Status, not an error. The scanner is in park or standby mode: the OSSDs are off and the laser is switched off. It returns to operation when a different monitoring case is selected or the standby request is removed.^[1][2][3]

Also on: S300 Mini (same code and text as the S300)

Device response: OSSDs off, laser off (by design)

Likely causes

• Monitoring case with park mode selected
• Standby input (STBY) active, or standby bit set via EFI

First checks, in this order

1. Switch to a different monitoring case or remove the standby request.
2. On the S300, if o stays, test the levels at the STBY input and at the control inputs that select the park monitoring case.

H: Device is addressed as host

What it means: Status, not an error. Shown for about 2 seconds at switch-on when the scanner is the host in an EFI system.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Normal start-up of the host scanner in an EFI pair

First checks, in this order

1. No action needed. In an EFI system with an S3000, the S300 must be the guest, not the host.

G: Device is addressed as guest

What it means: Status, not an error. Shown for about 2 seconds at switch-on when the scanner is the guest in an EFI system.^[1][2][3]

Also on: S300 Mini (same code and text)

Likely causes

• Normal start-up of the guest scanner (jumper between terminals 7 ERR and 10 A1)

First checks, in this order

1. No action needed. The jumper belongs only on the guest device.

E1: Error in the safety laser scanner

What it means: The microScan3 has an internal error. The display shows a warning symbol, E1 and an eight-character code for SICK support on a red flashing background.^[4]

Likely causes

• Internal scanner error

First checks, in this order

1. Restart the device from the display menu or Safety Designer, or switch off the supply for at least 2 seconds.
2. If it comes back, replace the scanner and send it to SICK for repair. Note the eight-character code for SICK support.

E2: Error in the safety laser scanner

What it means: The microScan3 has an internal error (SICK gives E2 the same description and fix as E1).^[4]

Likely causes

• Internal scanner error

First checks, in this order

1. Restart the device from the display menu or Safety Designer, or switch off the supply for at least 2 seconds.
2. If it comes back, replace the scanner and send it to SICK for repair.

E3: Error in the system plug

What it means: The microScan3 system plug has an internal error.^[4]

Likely causes

• Internal fault in the system plug

First checks, in this order

1. Restart the device from the display menu or Safety Designer, or switch off the supply for at least 2 seconds.
2. If it comes back, replace the system plug.

E4: Incompatible system plug

What it means: The system plug fitted is not suitable for this microScan3.^[4]

Likely causes

• Wrong system plug type, for example after swapping parts between scanners

First checks, in this order

1. Check the part number or type code of the system plug.
2. Replace the system plug with the correct one.

E5: Dazzle error

What it means: A strong outside light source is dazzling the microScan3.^[4]

Likely causes

• Sun, halogen headlamps, infrared light source or strobe in the scan plane

First checks, in this order

1. Remove or shield the light source.
2. Restart the device from the display menu or Safety Designer, or switch off the supply for at least 2 seconds.

C1: Faulty configuration

What it means: The microScan3 configuration is faulty.^[4]

Likely causes

• Configuration damaged or incomplete

First checks, in this order

1. Reconfigure the device with Safety Designer.

C2: Incompatible configuration

What it means: The configuration stored in the system plug does not match what this microScan3 variant can do.^[4]

Likely causes

• Replacement scanner of a different variant on an existing system plug

First checks, in this order

1. Check the device variant.
2. Replace or reconfigure the device.

C3: Incompatible firmware

What it means: The configuration in the system plug does not match the scanner's firmware version.^[4]

Likely causes

• Configuration made for a newer firmware than the scanner has

First checks, in this order

1. Check the firmware version of the device (Device info in the display menu).
2. Replace or reconfigure the device.

F1: Current too high at an OSSD

What it means: A microScan3 OSSD has exceeded its short-term or continuous current limit.^[4]

Likely causes

• Faulty or oversized switching element on the OSSD

First checks, in this order

1. Check the connected switching element (contactor, relay).

F2: OSSD short circuit to 24 V

What it means: A microScan3 OSSD is shorted to 24 V.^[4]

Likely causes

• OSSD wire touching 24 V

First checks, in this order

1. Check the OSSD wiring.

F3: OSSD short circuit to 0 V

What it means: A microScan3 OSSD is shorted to 0 V.^[4]

Likely causes

• OSSD wire touching 0 V

First checks, in this order

1. Check the OSSD wiring.

F9: General OSSD error

What it means: At least one microScan3 OSSD is behaving unexpectedly.^[4]

Likely causes

• OSSD wiring fault

First checks, in this order

1. Check the wiring of the OSSDs.

L3: Error in the external device monitoring (EDM)

What it means: A faulty signal is present at the microScan3 EDM input for longer than the allowed tolerance time.^[4]

Likely causes

• Contactor not dropping out or picking up as expected
• EDM feedback wiring fault

First checks, in this order

1. Check that the contactors are wired correctly and work correctly.

L8: Error in the reset input

What it means: An invalid signal is on a microScan3 reset input, or the reset signal is applied for too long.^[4]

Likely causes

• Reset pushbutton stuck or held
• Reset input wiring fault

First checks, in this order

1. Check the reset pushbutton, its wiring and any other parts in that circuit.

N1: Invalid input signal

What it means: The signal on the microScan3 control inputs is not assigned to any monitoring case and stays longer than the set input delay plus 1 second.^[4]

Likely causes

• Machine or vehicle in a state the configuration does not cover
• Control input signals wrong

First checks, in this order

1. Check the configuration with Safety Designer.
2. Check the working process of the machine.

T1: Temperature error

What it means: The microScan3 operating temperature is above or below the permitted range.^[4]

Likely causes

• Ambient temperature outside the specification

First checks, in this order

1. Check that the scanner is used within the permitted ambient conditions.

W1: Warnings exceed tolerance time

What it means: Several warnings at once have lasted longer than the 1 second tolerance time, so the microScan3 turns them into an error.^[4]

Likely causes

• More than one warning condition active at the same time

First checks, in this order

1. Use Safety Designer to see which warnings are present and fix each one.