brebenac

You should totally reflash the firmware. Along the created user on the user list there are some right modified to some reserved accounts, including and not limited to "admin". Therefore a new firmware (even if it is the exact same version your system currently has, if greater than 2.616) will destroy whatever is modified in the software and restore the system to it's secure nature. Do not forget to modify the entire userlist password and of course, before the update delete the "system" user. Use port forward not DMZ, and forward only the ports you use. Good luck!

It's HDCVI, for sure. Check the images, you get that quality over coax cable or utp and video baluns. Pretty nice, huh? And not to mention the price, much lower that IP version...

Check gateway section of device, and for God's sake, change the protocol to TCP only for port 37777.

No way a serial keyboard can send commands through standard Pelco protocol to a DVR/NVR. All keyboards that can connect the DVR/NVR are from same manufacturer as the DVR/NVR and use specific protocol to connect to it. Mmmmh guess it will be using HIKVISION protocol then, so a generic controller probably would not cut it. Exactly. Regular controllers can connect to "clients" that consis only of "listening"devices, like cameras. The DVR/NVR is something like a "server" that "sends" the commands. The RS485 port of DVR/NVR is an output-only port. Keyboards (specific models) can be connected to the DVR/NVR on RS232 port (where available) or network port - and only in manufacturer's private protocol.

Never say "never"... hehe.

No way a serial keyboard can send commands through standard Pelco protocol to a DVR/NVR. All keyboards that can connect the DVR/NVR are from same manufacturer as the DVR/NVR and use specific protocol to connect to it.

Many IP cameras still have the RS485 serial control port. Check if your planned device has it and find a controoler that can accomodate the same control protocol as the camera. If in the same location with the camera, then controller can be used, but if over IP... no use.

Check (and change if needed) IPV6 address of nvr and cameras. If identical then there might be a problem of conflict. Also, create and use a different account (reusable) to allow nvr to connect to cameras (user might be locked).

Can you connect the NVR to the PSS? If not, forget connecting the camera... no use... Xvision is a rebrand/copy of dahua for some specific models, and rebrand/copy for other manufacturers for other models. Maybe what you have there is not dahua"-ish".

What?? Really?... HD-SDI on CAT5e? Man, look for technology description first, you will not be able to use 1m of cat5e and get signal lock on HD-SDI... Geez...

Try this simple trick: use passive video baluns for transmit/receive each R G B channles (2 wires for R, 2 for G, 2 for B) and use the last pair to transmit the H and V sync. This might surprise you and give you clear image at 90m.

Maybe the date on the camera is not the date of "today". Try to get the date shown on camera and ask the password for that specific date. Some devices return to 01.01.1970 when cell battery removed.

Usually the DVR's are using multiple ports to send video footage to web browsers. Check if any "data"ports are needed in order to connect. (Check the NETWORK section for this port numbers and forward those, too).

Hi there, unfortunately for you the Dahua is limiting it's device model coverage through any method it can in order to protect it's distributors market share. In your case it's the video standard. To change the video standard look for an official distributor in your area and ask him for the firmware update (or take your unit to their service). This might cost you something... or it might not if it is applied online

Please do not confuse thermal imaging devices to IR Cameras...

Neah... seriously guys! The only thing that is almost 100% sure to not be caught on a camera is to NOT show up at the location the camera is.... I'm saying "almost" because there are video editing software tools out in the wild... that can basically put anyone anywhere.

Dahua NVR does not compute motion detection by itself. It connects with the camera and gets the info from it, so actually the camera has the motion detection functionality. That is why you cannot record non-Dahua cameras connected through ONVIF to record motion events on a Dahua NVR. Other functions like parameter setting of the camera are also unavailable through ONVIF... until ONVIF upgrades the specs of the standard itself...

The man asked for a serious question and what he got was rubbish... not nice. Here's a good one: you can build some kind of "blinding" device to wear on your head but may not want it to be visible by naked eye, so use led's, but use the IR ones instead of normal white leds. And be assured you may not influence cameras without IR sensitivity (normal light), only the ones that have IR ligh on them (or are sensitive to this type of light). Also some good WDR cameras might not be blinded by it.

I think maybe take the dahua speed dome and mount a gun along with the dome itself, then connect the alarm output of the speed to some triggering device... zoom in... and pow! Surprise strikes! They'll never bother you again ) Of course this is not a solution. If you need one, a 700TVL camera helps. Also you can opt for the speed dome version because the lens is different and can have different angles/zoom levels to look from. You can even set a patrol scheme for it as a "home position"...

Set Day/Night to auto. Also check if the Day->Night and Night->day values are editable and adjust a lower threshold for swithcing to color. Also be sure to have different thresholds for the night->day and day->night, or it will oscillate back and forth.

PSS is a simple yet very complex CMS. First, the emailing is done by the DVR. I am familiar with Dahua (Q-See is a rebranded name for Dahua). Check the Detect section to see if Snaphot is activated for more than one channel (the record option refers to the local records on dvr, not snapshots sent). Also chect the text message along the picture to verify the trigger event from wich channel is, and corresponding picture attached. The recordings in PSS should be found in Device record tab, not activation (the activation refers to the record made by PSS locally when you previously defined a alarm record configuration). Also, if you want the dvr to autoupdate ip address in DDNS be sure to have the Preferred DNS and/or Alternate DNS entries completed (default working values are 8.8.8.8 and 8.8.4.4). You can also use No-ip as service, it's free and works like a charm.

At night the IR cameras draw more power from the power supply (you can chech this against the recordings). Just change the power supply. It's capacitors for output are defective (most likely doue to instability of the input line - fast fluctuations can travel form the primary to the secondary part). If you can, replace the capacitors, or replace the entire unit. If possible stop using ONE power supply for all cameras and switch to using one power supply for each camera (usually a 12V 1A supply is sufficient and cost efective).

The connection is correct. You have 2 reds and 2 blacks because the ir board is connected separately: Red = +12V: Video board power Red (+white) = +12V: IR board power Black: GND: Video board GND Black (+white) = GND: IR board GND Yellow: Video signal

If the image recorded on motion areas is allowed to suffer invert colors on the area detected you could activate the motion detection option inside the camera itself (by OSD menu). This way the dvr would detect a larger event and record the motion you need.

Unless you choose to install another camera wich supports RTSP to look at the image given by this model and broadcast it further, you have no chance in getting this to a website (in video i mean). And yes, change the admin pass, it's not safe to leave it defaulted.