Return to Help Index
Pro Tips
Axis P5534 and Dotworkz D2 outdoor dome housing 10 minute installation guide
Axis P5534 HD network/IP PTZ camera into the Dotworkz D2 outdoor protective dome housing - 10 minute installation guide

We have put together this quick installation guide on how to properly install the Axis P5534 HD camera inside the new Dotworkz D2 rugged IP66 camera enclosure, with step-by-step photos and procedures. Be sure to check our pro tips to avoid pit falls and installation mistakes.

The Dotworkz housing is great choice for the Axis HD camera for many reasons: it looks great when installed, versatile so you can add wireless or other products safely inside with the camera and best of all it is engineered to protect the camera better then any other product available.

The process should take 10 minutes:

All the parts and tools
Please read both Axis and Dotworkz manuals before beginning. Photo of hardware and components you will need to have the Axis P5534 installed into the D2 outdoor enclosure system.

Prepare the camera
Using the included Axis Torx screw driver unscrew all 8 bottom Torx screws (4 "outside" ones for the main cover plus 4 for smaller cables latch cover).

Remove shroud
After unscrewing, remove P5534 camera cover and open smaller cable latch. Set aside the main lower camera shroud as it is not going to be needed.

Connect cables
Attach the Dotworkz 5502-491 patch cable that will provide camera power; attach the RG45 connector of a CAT5 Ethernet cable to the camera; Feed both cables out their respective slots.

Reassemble latch cover
Securely close the cable latch using the Torx screw driver again.

Install Axis collar
Attach the Axis P5534 camera collar to the Dotworkz universal camera mounting plate, making sure to line up correctly and tightening lock washers securely.

Mount the standoffs
You will need to use the 1.5 and the 0.75 inches standoffs on the 4 brass inserts on top of the D2 enclosure - DO NOT over tighten or cross thread the standoffs.

Secure camera
Twist-lock camera into collar while applying down pressure; line up the diamond mark as in this picture; Secure the camera plate to the standoffs using included 832 pan head screws.

Check camera fit
Check camera install by carefully closing the D2 camera hatch and verifying clearance between camera and D2 lens: should be enough space between the clear dome and the camera to move freely.

Using Dotworkz cable
Remove the terminal block from Dotworkz 5502-491 cable: you will only use BROWN and RED wires.

Correct poles
Connect BROWN wire to (-) negative and RED to (+) positive on the MVP terminal. The BLACK wire is not used so we recommend isolating it with electrical tape.

IP68 Cable glands
Run CAT5 cable through existing D2 cable gland; Remove the plug and install an included second cable gland, making sure to seal it tight. Note: if using conduit be sure sealing to avoid water moisture.

External power source
Have a qualified electrician connect an external power source to D2 terminal power block. See manual for more details.

Tighten cable glands
Make sure to have only one cable per gland and tighten them really shut to completely seal D2 enclosure from the outside.

Close the D2
Close the enclosure and tighten all screws using a philips screw driver. The D2 can be mounted directly to a wall or to a pole mount adapter.

Leave a drip loop
Make sure to create a U shape drip loop with the cables to prevent water from pooling and possibily seeping inside.
PRO Tips:
  • The camera uses and comes standard with a proprietary POE (802.3AT) that is not compatible with standard POE 802.3AF. With the AXIS POE you are limited to under 90 feet in total end to end CAT5 cable run
  • Install the camera high enough to prevent camera theft and improve viewing angle.
  • Be sure to install the camera while safely on the ground to avoid acidents.
  • Check everything that is NOT going to be used on this install.
  • For cleaning the outdoor lower lens on the housing be sure to use the DomeWizard™ dome cleaner at
Things to consider when mounting cameras outdoors...

If a Network based IP or Analog camera is to be exposed to outdoor elements or is placed in a industrial setting, an external housing is need to protect it. There are standards that specify the degree of protection to be provided by enclosures. Two digits prefixed by the  letters IP define the rating of protection look for IP 66 or higher. Vandalism and theft of hardware is not consider in this rating scheme.

Environmental Factors

Camera housings are normally made of aluminum or more recently now from extremely durable specialty thermoplastics. Weather conditions, outdoor temperature and equipment temperature rating should dictate if the camera housings will require a heater, de icing system, multiple hi flow fans or possibly an active cooling system. Remember sensitive electronics are just that sensitive -long life, reliability and down time should be all be considered.  In climates where the weather can vary from bright sunlight to cold and damp there will need to be some form of heater mounted below the front glass plate or lower dome. The heater and fans act as a defogger for the lens and prevents the build up of condensation along it is suggested that a silica desiccant pack be  placed in the housing.

Dome housings, speed dome or dome enclosures are used for Pan Tilt and Zoom cameras because the internal mechanisms can be of a lighter construction and therefore permit very fast speeds of pan and tilt. If the dome is tinted or “smoked” it makes it difficult for a person to detect in which direction the camera is pointing. All material in front of the camera lens will attenuate the light and an allowance of at least one full f-stop should be used in calculating lighting and camera sensitivity. An auto iris lens should always be used with an outdoor camera. This will give the camera a better dynamic range and protect the image sensor from being damaged by direct sunlight.

If you mount a camera behind glass, for example in an outdoor housing, make sure that the lens is close to the external lens. If it is too far away, reflections from the camera and the background may appear in the image.

If cameras are to be used at night additional external light sources may be required such as incandescent, HID or IR illumination. Lamps should be mounted in such a way as to avoid reflections and shadows. Special color corrected lamps are available which produce a balanced white light suitable for most cameras. Infrared illuminators can also be used for covert or semi-covert operation. Not all color cameras are rated for IR infrared illumination due to a lack of IR cut filter.
Avoid Direct Sunlight

Always try to avoid direct sunlight in an image. Direct sunlight may “blind” the camera and filters and burn the CCD causing stripes in the image. When using a camera outdoors, avoid including too much sky in the image. Due to the large contrast, the camera will adjust in order to achieve a good level for the sky and the interesting landscape or objects may appear too dark. One way to avoid these problems is to mount the camera high above the ground. Used a proper pole with sturdy pole mount adapter or wall mounted bracket and always use proper mountings to avoid vibrations caused by wind.
Troubleshooting Your Network Camera and Components
  Troubleshooting IP or network based live cameras is much simpler than it may appear. Most issues are related to power loss or a change in the network that supports the camera. All brands of cameras—Axis, Sony, Panasonic and others—are equally susceptible to outages and most likely will require some troubleshooting during the life of the camera.

The following outline was written by Steve Surfaro of Axis Communications

When troubleshooting physical infrastructure, integrators must examine:
  • Cabling and wireless networks,
  • Equipment that controls the network devices and system power, and
  • Wiring plant that supports the multiple network-based security systems.

The wiring plant includes the telecommunications closet, the intermediate cross-connect, the main cross-connect and the data center, as well as the command monitoring center and the main cable head where the physical infrastructure connects to TELCO services, external WANs or the Internet.

To determine the source problem, ask these questions:

Is there power?
This is the most obvious place to start troubleshooting. Ferret out whether a break in the network cable is present or if the problem lies with the power sourcing equipment (PSE) or the powered device (PD) itself. It’s advantageous to have a network management system that can consistently monitor the endpoints of the network and pinpoint where performance has slowed down or stopped altogether, especially for larger networks.

Is the PSE’s capacity exceeded?
If an Ethernet cable connects devices to a Power-over-Ethernet (PoE) switch, confirm that the device being powered can accept and use power from that Ethernet cable for its operation. As a safety precaution, a PoE switch or other PoE-compliant PSE won’t supply power over an Ethernet cable if it’s not connected to a PoE-compliant device.

Second, check the wattage rating of the network switch and the power requirements of all the PoE devices being powered by that switch. The PoE standard — also known as the IEEE 802.3af standard — designates a maximum power output of 15.4 watts per port, or 12.95 watts to the powered device after factoring in the normal power loss that occurs on a twisted pair cable. Attaching too many devices with large power requirements to a switch can exceed its power capacity. To determine the classification of a particular powered device, check the manufacturer’s specification sheet.

If the network switch supports the newly ratified Hi PoE standard — also known as IEEE 802.3at or PoE+ — it can deliver 25 watts of power per port, or 22.55 watts to the powered device once power dissipation in the cable is considered. If the Hi PoE network switch uses all four of the twisted pairs in the Cat 5 cable, it can deliver up to 51 watts of power per channel. This is more than sufficient to power and control pan/tilt/zoom network cameras, as well as (small) heaters and fans in outdoor network cameras, over a single Ethernet cable.

Is the wireless network experiencing interference?
Much like hardwired network systems, integrators should set up a network management system to monitor wireless transceivers or radios for power loss, fluctuating network throughput and poor signal strength. Radios can also be monitored for interference from external sources.

Rooting Out Logical Infrastructure Problems

When troubleshooting logical infrastructure, integrators must examine:
  • Network switches,
  • Firewalls, and
  • Network management systems.

This is the virtual portion of your network that controls how you segment access to network security devices and systems. It also involves the way you guarantee quality of service (QoS) for critical systems during spikes in bandwidth demand from various security systems on the network.

To determine where the problem might be originating in the logical infrastructure, here are a few pertinent questions to investigate:

Does the user have permission to access the system?
If a user complains that they’re not receiving information from a particular network-based device, check the Virtual Local Area Network (VLAN) to see if they have been granted permission to access that device. The VLAN is designed to separate groups of users to prevent unauthorized access to network components such as devices or databases.

For instance, human resources might have permission to look at an access control database but is barred from the access control panels themselves. A school superintendent may be able to see all of the video cameras in the district, but principals can see only the cameras covering their own campuses. Or in an emergency, first responders may be given temporary access to a building’s security cameras.

Is a new logical security application causing communication failures?
If network-based devices suddenly stop communication, check to see if the network administrator has introduced a new logical security application that may have triggered the failure. This could be a new proxy server that doesn’t recognize the device, a new firewall that creates a barrier between the device and the network in accordance with the company’s information security management (ISM) policy, or a piece of security software that is blocking the network port used by the device.

The best way to test for these problems is to shut down the new application and see if the device begins communicating again. Start with the simplest communications path possible and then add layers of logical infrastructure and tracking when things start to fail.

Troubleshooting Specific, Network-Based Security Systems

After investigating the infrastructures, integrators should move on to the specific network systems for further inspection. The diagnostic strategies for two of the more popular network-based security systems — video surveillance and access control — are very similar.

Is the powered device working?
Whether it’s a network camera or a card reader, the first thing to check is the device itself. Is it receiving power? Are all its parts functioning? If the problem doesn’t seem to be power or part failure, try resetting the device. Start with a soft reset: simply powering down the device and then powering it back up again. If that doesn’t work, a hard reset will restore the device’s settings to its factory default. Then you can change the settings one at a time to see if a particular new setting is causing the problem.

Is the problem in the firmware?
One of the most common oversights in upgrading network-based systems is firmware compatibility between the network camera and the video management system or between the card reader, the door control panel and the access control management system. A manufacturer might have shipped you a firmware revision for the network device that isn’t supported by the management system. Or the network administrator might have upgraded the management system without considering its compatibility with the network device. Any of these scenarios could lead to a communications issue.

Are the databases synched?
If multiple network-based security systems are designed to work in tandem, it’s important to synchronize their databases to ensure that they operate properly. For example, a visitor management system might allow visitors to enroll online to ensure a badge is waiting for them when they arrive at the facility. However, if that information doesn’t automatically populate the access control system database, then the visitor’s badge won’t be recognized by the card reader.

Is remote access being hampered?
For network video surveillance systems in particular, problems can emerge with WAN connectivity when monitoring video streams remotely. To correct, first ensure that the individual monitoring the cameras is accessing the correct static IP addresses. If the network doesn’t use static IP addresses for the network cameras, check that correct port forwarding or network address translation protocols are in place. This might require specialized programming to determine if the camera’s video stream is transmitting properly through the router.

Hosted video solutions (i.e avoid much of this complex protocol connectivity by connecting the cameras to an outside dispatch service. The service automatically reconfigures the cameras to stream video to a hosted video portal, where it can be accessed by remote users.

Keeping It Simple

Even in a complex network environment, the simplest approach is the most effective one. Start troubleshooting by ruling out more obvious problems such as power loss before exploring other possible issues affecting system performance. Try to recreate a simple communications path between the network device and the user of that device’s information — be it a video stream or an entrance permission. Then gradually introduce other areas of the network to determine where and when the problem occurs. This systematic layering of complexity will make it easier and faster for you to root out the problem and bring the security systems back to full operation.

Troubleshooting Checklist:

Check physical infrastructure
  • Power to all devices?
  • Manual soft or hard reset?
  • PoE capacity exceeded?
  • Wireless interference?

Check logical infrastructure
  • User permission for VLAN?
  • New logical security application?
  • (Proxy server, firewall, security software, etc.)
  • Firmware compatibility?