Specifications

Axis Communications
23-3
• Q1755 without PT head installed will still show up as a PTZ camera in NVR. However, none of
the PTZ functions will work. This limitation could apply to all cameras that has built-in PT/PTZ
head support.
• Older versions of the AXIS handler may have set the “exposure”, “input gain”, “wdr” and other
parameters on some AXIS cameras to invalid values.
• The camera’s web interface can be used to determine whether the camera parameters have
been set to invalid values. Click “Setup->System Options->Advanced->Plain Config” and then
select the appropriate parameter group (image source, PTZ, etc). The invalid values will be
displayed but will be appended with “(not supported?)”. The AXIS handler will also see the “(not
supported?)” in the parameter value strings it reads from the camera. If any invalid values are
found then use the camera’s web interface to change invalid settings to valid settings.
• An attempt to add a preset to AXIS encoders (with AD Ultra 8 analog PTZ camera) will result in a
“Error: query not implemented” HTTP error being returned in response to a
“http://<ipaddress>/AXIS-cgi/com/ptz.cgi?query=position&camera=1” HTTP request. The
reason for this is that the Sensormatic driver for the AD Ultra 8 camera does not allow the
position to be queried. The parameter list retrieved from the encoder will report that absolute
pan, tilt, zoom is not supported
• An attempt to add a PTZ preset for AXIS Q1755 fails because the getPositionSync method
returns “Not supported” error as a result of the AXIS Q1755 not returning pan and tilt position
info when PTZ position is queried. The zoom position is returned but not the pan and tilt position.
Since the Q1755 cannot pan and tilt without the motor accessory then perhaps the need to set
presets for zoom only is not critical.
• When an AXIS 240Q or 241Q four-port encoder is added to the NVR, camera slots will be
created for all four ports regardless of whether the encoder inputs are receiving analog signals. If
an analog signal is not preset, black video will be received by the NVR and recorded / streamed
to viewing clients. To conserve NVR disk space and reduce network traffic, the camera slots
associated with the unused inputs can be deleted from the NVR but they cannot be added again
unless the entire encoder is deleted and re-added.
• The latest firmware (4.47) in the AXIS 210A camera and some other VAPIX 2 camera and
encoder models have a flaw that limits the FPS of MJPEG streams to the FPS of an existing
MPEG-4 stream until the MPEG-4 stream is destroyed. For example, if the configured FPS of
two MJPEG streams are 20 FPS and 5 FPS and the FPS of the MPEG-4 stream is 15 FPS then
the actual FPS of the MJPEG streams will be 15 FPS and 5 FPS until the MPEG-4 stream is
destroyed. Similarly, if the MPEG-4 stream is 1 FPS then the actual FPS of the two MJPEG
streams will be 1 FPS. A workaround is to ensure that the FPS of an existing MPEG-4 stream is
greater that the configured FPS of the MJPEG streams. Another workaround is to revert the
AXIS firmware to an older version (4.40 for example ) which does not exhibit this symptom.
• After an AXIS camera has been disconnected from the network, it can take up to 22 seconds to
raise an alarm and attempt a reconnect after the dry contact connection to the device is lost.
However, the loss of the video stream from that camera will be detected within a few seconds
and an alarm will be raised.
• If the camera’s own web GUI is used to rotate an image (instead of using the NVR web client
“Image Settings” screen) then the change does not take effect on existing streams until an FPS
or resolution change causes the stream to be destroyed and recreated. It is better to use the
NVR web client “Image Settings” screen to rotate the image because that will cause the stream
to be destroyed and recreated.
• When using /AXIS-cgi/com/ptz.cgi?camera=1&areazoom=<int>,<int>,<int less than 100> AXIS
API to zoom out on AXIS 214 PTZ camera, the zoom position will reverse to maximum zoom in
when the request causes a zoom out to go beyond the widest zoom out position. This, according
to AXIS technical support, is a bug within the AXIS 214 PTZ camera (v4.40). The above
mentioned API is used by NVR Web client and VE API to perform PTZ Nudge operation.
• An AXIS VAPIX 2 camera will momentarily disrupt an MPEG-4 video stream as a result of
changing the audio codec which causes the NVR to stop/recreate the video stream. During