Filter
Top Products
AXIS 230 Troubleshooting
41
Note: If you still have a problem after reading this information, please contact your reseller or visit the
Axis Support Web at www.axis.com/techsup/
Slow video Outdated drivers for graphics
card.
Obtain and install the latest device driver for your graphics card from
the manufacturer’s web site. Also check that DirectDraw acceleration
is enabled. This can be done by running the program DxDiag.exe (click
Start - Run and then type dxdiag.exe) Check on the Display tab that
DirectDraw acceleration is enabled.
Another application is using
DirectDraw acceleration,
making this unavailable to the
AXIS 230.
Close the other application, and then re-open the AXIS 230’s Live View
page. Examples of other applications that use DirectDraw acceleration
are: video conferencing software, Web TV, video playback software and
video editing software.
Insufficient free memory on
graphics card for using the
hardware acceleration
capabilities.
Lower the resolution/color depth for the monitor. Right-click on the
desktop and select Properties - Settings.
Poor quality video (image
hopping, etc.), wrong
image format (b/w,
inverted, etc.)
Outdated drivers for graphics
card.
See “Slow video” above.
No audio / poor audio. Faulty connection to external
mic or audio input device.
Error in power supply to
external microphone.
Check connections. If the audio LED flashes or is steady green, then
audio is reaching the MPEG decoder in the AXIS 230 and is included in
the stream.
Incorrect settings. Check that the correct input is selected. Check the input sensitivity. If
the audio LED flashes or is steady green, then audio is reaching the
MPEG decoder in the AXIS 230 and is included in the stream.
Error in client. Check the settings for the client PC’s sound card. If audio is weak or
distorted, check the master gain setting in the AXIS 230.
Outdated drivers for sound
card.
Check that you are using the latest device driver for your sound card.
Check the manufacturer’s web site for new drivers.
Triggering difficulties
with programming scripts.
Unable to trigger on both
positive and negative
transitions of the Control
Button and/or I/O ports
(double-edged triggering).
Repetitive trigger conditions that occur in quick succession can be
missed. This is because the command initiated by the first trigger event
may not have been fully executed before the second event starts. This
scenario is demonstrated in the illustration below:
This feature has particular significance when using commands that
take a relatively long time to process, e.g. mail or FTP, especially if they
are transmitting a pre/post alarm buffer.
Symptoms Possible causes Remedial actions
Trigger
Command
Command
T1
T2 T3
Command
Time
?