Table of Contents
Advertisement
M3057-PLR Mk II Dome Camera
Troubleshooting
This camera is designed to deliver up to four different streams. If a fifth unique stream is requested, the camera can't provide it, and
an error message is displayed. The error message depends on the way the stream is requested. The streams are used on a first come,
first served basis. Examples of instances that use a stream are:
• Live viewing in a web browser or other application
• While recording - continuous or motion triggered recording
• An event that uses images on the camera, for example an event that sends an e-mail with an image every hour
• An installed and running application, such as AXIS Video Motion Detection, will always consume a video stream, whether
it is used or not. A stopped application does not consume a video stream.
The camera can deliver more than four simultaneous streams provided the configuration of any additional stream is identical to any
of the first four streams. Identical configuration implies exactly the same resolution, frame rate, compression, video format, rotation
etc. For more information see the white paper "Max number of unique video stream configurations", available at axis.com.
Can't connect over port 8883 with MQTT over SSL
The firewall blocks traffic
using port 8883 as it's
deemed insecure.
Performance considerations
When setting up your system, it is important to consider how various settings and situations affect the performance. Some factors
affect the amount of bandwidth (the bitrate) required, others can affect the frame rate, and some affect both. If the load on the
CPU reaches its maximum, this also affects the frame rate.
The following factors are the most important to consider:
•
High image resolution or lower compression levels result in images containing more data which in turn affects the
bandwidth.
•
Rotating the image in the GUI can increase the product's CPU load.
•
Removing or attaching the cover will restart the camera.
•
Access by large numbers of Motion JPEG or unicast H.264 clients affects the bandwidth.
•
Access by large numbers of Motion JPEG or unicast H.265 clients affects the bandwidth.
•
Simultaneous viewing of different streams (resolution, compression) by different clients affects both frame rate and
bandwidth.
Use identical streams wherever possible to maintain a high frame rate. Stream profiles can be used to ensure that
streams are identical.
•
Accessing Motion JPEG and H.264 video streams simultaneously affects both frame rate and bandwidth.
•
Accessing Motion JPEG and H.265 video streams simultaneously affects both frame rate and bandwidth.
•
Heavy usage of event settings affects the product's CPU load which in turn affects the frame rate.
•
Using HTTPS may reduce frame rate, in particular if streaming Motion JPEG.
•
Heavy network utilization due to poor infrastructure affects the bandwidth.
•
Viewing on poorly performing client computers lowers perceived performance and affects frame rate.
In some cases the server/broker might not provide a specific port for MQTT communication. It may
still be possible to use MQTT over a port normally used for HTTP/HTTPS traffic.
• If the server/broker supports WebSocket/WebSocket Secure (WS/WSS), typically on
port 443, use this protocol instead. Check with the server/broker provider to see if
WS/WSS is supported and which port and basepath to use.
• If the server/broker supports ALPN, the use of MQTT can be negotiated over an open
port, such as 443. Check with your server/broker provider to see if ALPN is supported
and which ALPN protocol and port to use.
65
Advertisement
Table of Contents
