Error
Possible Causes
Solutions
• Mouse not detected by system.
• Mouse cable is not firmly con-
nected to the system.
Mouse is not connected to the
system.
• Firmly connect the mouse ca-
ble to one of the USB ports.
• System needs to be reset
• Power off the system (discon-
nect power cable). Firmly con-
nect a USB mouse to one of the
USB ports. Reconnect the
power cable to the DC 12V
port on the rear panel.
• There is no picture on selected
channels / camera picture is
not being displayed.
• Camera cables are loose or
have become disconnected.
• Check the camera video cable
and connections.
• Disconnect and reconnect the
cable at the system and at the
camera.
• Try moving the camera to an-
other channel or use another
cable.
Camera is not compatible with the
recorder.
Visit
and
navigate to N842 Series for a list
of all compatible cameras.
Power output of the recorder’s PoE
switch is being exceeded.
If you have multiple PTZ cameras
connected to the recorder’s PoE
ports, the camera power require-
ment may surpass the recorder’s
power output. Lorex PTZ cameras
come with a power adapter, which
you can use to power the camera
instead of the recorder’s PoE ports.
See 20
, page 93for full instructions.
• The system beeps at startup.
• The beep at startup is normal.
• The system beeps during mo-
tion detection.
• Motion detection is enabled
and the alarm buzzer is
activated.
• See 12
, page
37for instructions on configur-
ing motion detection options.
Uncheck the
Buzzer
option in
the motion detection configura-
tion screen.
• I am not receiving email
notifications.
• Email notification is disabled.
• Ensure you have configured
email notification. For details,
see 17.6.3
•
Send Email
setting not enabled
in Event menu.
• Make sure that
Send Email
is
checked for any events you
want to be notified of.
24.1 Top Reasons Your Lorex Camera May Lose Video or Go Black
There are a multitude of reasons why your security camera may lose video or go black. The fol-
lowing list of potential issues will walk you through the process of identifying the root cause and
do a quick fix on the issue.
#LX400113; r. 9.0/57192/57197; en-US
110