Leaderboard

I've wanted to make this list for a while, and hopefully it will help answer some simple questions or guide newcomers on their IP video quest. Feel free to add, change, or refine this! Most Popular Camera Manufactures (on this forum): ACTi (http://www.acti.com) - Midrange camera - good price - free software. Avtech (http://www.avtech.com.tw) - Has good 'push' support for events to mobile devices. Avigilon (http://www.avigilon.com) - Similar to Axis cost - must buy through dealer - good software/support. Axis (http://www.axis.com) - Popular choice - higher end cameras get expensive - easy to find online for sale - free + paid software options. Dahua (http://www.dahuasecurity.com‎) - Re-branded as Q-See - low price - difficult to find updates/support. Geovision (http://www.geovision.com.tw‎) - Midrange - have some LPR cameras. Grandstream (http://www.grandstream.com) - Low cost - have some unique features. Hikvision (http://www.hikvision.com‎) - Becoming more popular - re-branded as Lorex/Swann systems from Costco. IQinVision (http://www.iqeye.com) Midrange pricing. Mobotix (http://www.mobotix.com) - Cameras made in Germany - reliable but expensive - no moving parts to fail in their cameras. Vivotek (http://www.vivotek.com) - Midrange pricing. Other Camera Manufactures: Arecont (http://www.arecontvision.com/‎) Brickcom (http://www.brickcom.com/) Bosch (http://www.boschsecurity.us/en-us/ProductInformation/Cameras/NetworkCameras/) Canon (http://www.usa.canon.com/cusa/professional/products/security_video_solutions/network_cameras) GE (Unknown Website Address) Honeywell (http://www.honeywellvideo.com/products/cameras/ip/index.html) JVC (http://pro.jvc.com/prof/attributes/category.jsp?productId=PRO5.2) Panasonic (http://www.panasonic.com/business/psna/products-surveillance-monitoring/index.aspx) Pelco (http://www.pelco.com/sites/global/en/home.page) Samsung (https://www.samsung-security.com/) Sony (http://pro.sony.com/bbsc/ssr/mkt-security/) Toshiba (http://www.toshibasecurity.com/) IR Illuminators: Raytec (http://www.rayteccctv.com/) Axton (http://www.axtontech.com/) Iluminar (http://www.iluminarinc.com/) +Other Generic Brands Accessories: PoE Switch (Unmanaged, or Managed which allows remote powering on/off of specific ports) (TRENDnet, Netgear, D-Link, Cisco, Axis, etc.) Ethernet Cable (Regular/Burial Grade) Lenses (C/CS/S/D Mounts) IR Illuminators (Discussed Above) Enclosures (Pelco, Videolarm, Axis, Generic Brand, etc.) PIR Sensor (Optex, Bosch, etc) UPS Battery Backup System Popular Places To Buy: [Redacted - do a search on the forum for general ideas ] Video Recording Software: ACTi VMS (Free) - Only supports ACTi Cameras. Avigilon (Per channel: Core ~$100, Standard ~$200, Enterprise ~$350) - Purchase through authorized dealers. Axis Camera Companion (Free) - Only supports certain (newer) Axis Cameras. 16 cameras max. Axis Camera Station (~$90/license) Axxon Next (Free for 16 channels) (http://www.axxonsoft.com/products/axxon_next/) BlueIris ($29.95 - $49.95) (http://blueirissoftware.com/) - Supports a large variety of network cameras. exacqVision ($50 - $150/license + $25 yearly for optional updates) Genetec (Expensive) Geovision (Free) Luxriot ($99 - $1000+) Milestone XProtect (Free - $1000+) Mobotix Control Center (Free) - Supports other cameras for viewing. May be able to record with MXServer. OnSSI (Unknown) Vitamin D (Free/$49/$199) (http://www.vitamindinc.com/index.php) - PC + Mac Compatible Zoneminder (Free) - Open source Linux software. ...Etc, Most Manufactures Provide Their Own Software. Network Video Recorders (NVR's)/NAS Stations: Synology (1 License Included - ~$50 /per additional license) Dahua QNAP Luxriot NUUO Hikvision iPhone Viewing Apps: Netcam Viewer (Free/$5.99) (http://bit.ly/18UfXMs) Live Cams Pro ($1.99) (http://bit.ly/19RAleQ) QCamPro ($7.99) (http://bit.ly/14iCWxR) Official Mobotix (Free) (http://bit.ly/15XNtmo) IP Cam Viewer Pro ($3.99) (http://bit.ly/10QAwYn) Dahua iDMSS Lite (Free) (http://bit.ly/110ZjmV) Dahua iDMSS Plus ($4.99) (http://bit.ly/12FyWpw) +Specific Manufacturer's Apps (Q-See, Hikvision, etc) (Search Manually) - Typically better integrated then 3rd party apps. Android Viewing Apps: IP Cam Viewer Pro ($3.99) (http://bit.ly/TG6OyB) Dahua gDMSS Lite (Free) (http://bit.ly/12zjvAs) Dahua gDMSS Plus ($5.00) (http://bit.ly/12FzfAA) +Specific Manufacturer's Apps (Q-See, Hikvision, etc) (Search Manually) - Typically better integrated then 3rd party apps. Review Sites/Sample Videos: Network Camera Critic (http://www.networkcameracritic.com/) Mateusz CCTVnerd (http://www.youtube.com/user/mateuszfen) Megapixel Cameras - Images and Demos (viewtopic.php?f=19&t=11322) Plazor (http://www.plazor.com) Axis YouTube Channel (http://www.youtube.com/user/AxisCommunications) Avigilon YouTube Channel (http://www.youtube.com/user/Avigilon) MXInstaller (http://www.mxinstaller.com/) Companies That Rebrand/Resell: Swann (Rebrands Hikvision Equipment) Lorex (Rebrands Hikvision Equipment) Q-See (Rebrands Dahua Equipment) Toshiba (Appears To Rebrand Vivotek) Cisco (Sometimes Rebrands Pelco) Other Helpful Links: CCTV Lens Calculator (http://www.jvsg.com/online/#) Identification And Recognition Guide (http://www.axis.com/academy/identification/index.htm) - Make sure you have the correct resolution for your application. Security Today - IP Cameras (http://security-today.com/directory/list/ip-video.aspx) CCTV Frame Rates Comparison ( ) - Recordings don't necessarily have to be 30fps for desired results. IP Video 101 Training (http://ipvm.com/report/ip_video_training_course_101) Live Demo Cameras: Mobotix Cameras (http://www.mobotix.ro/live-ro-p-3.html) or (http://comsurv.com/live-video-cameras/) Axis Cameras (http://www.axis.com/camerademo/) or (http://ipcameralive.com/) Mixture (http://camelive.info) Terminology: CBR: "Constant bit rate [encoding] means that the rate at which a codec's output data should be consumed is constant." (i.e. the amount of data flowing from camera to user/nvr is always constant - even during movement or lack thereof. [See also VBR]) DSD: (http://www.dsdcctv.com/) DVR: "a consumer electronics device or application software that records video in a digital format to a disk drive, USB flash drive, SD memory card or other local or networked mass storage device." Edge Recording: "The concept of taking audio/video from a camera, and storing it at the edge of the Ethernet network instead of transporting it across the network to a centralized recording facility such as a Network Video Recorder." (Most cameras have this ability now.) IR/IR Illuminator: LED's (often a separate device) which provide illumination for cameras in near to total darkness. The light produced cannot be seen by the human eye. The camera must be sensitive to IR for this to be useful (some cameras have 'fixed' IR cut filters). 'White light' illuminators are also available. These produce light visible to the human eye and to a camera with or without an IR cut filter. LPR/ANPR/AVI/CPR/LAPI: "A mass surveillance method that uses optical character recognition on images to read vehicle registration plates." NAS: Basically a box filled with hard drives for storage of data. Some cameras have the ability to record directly to these networked boxes without the need for an always on or dedicated computer. NVR: "A software program that records video in a digital format to a disk drive, USB flash drive, SD memory card or other mass storage device." ONVIF: "Open Network Video Interface Forum (ONVIF) is a global and open industry forum with the goal to facilitate the development and use of a global open standard for the interface of physical IP-based security products." PIR: Passive Infrared "is an electronic sensor that measures infrared (IR) light radiating from objects in its field of view. They are most often used in PIR-based motion detectors." PoE: "A system to safely pass electrical power, along with data, on Ethernet cabling." UPS: "uninterruptible power supply...is an electrical apparatus that provides emergency power to a load when the input power source, typically mains power, fails." VBR: "Variable bit rate files vary the amount of output data per time segment." (i.e. Less data during still scenes, more data during high movement periods.) WDR: "'Wide dynamic range' describes an attribute of an imaging system which can capture greater scene details from shadows to highlights than normal." Commonly Asked Questions: Q: "Which brand or manufacturer should I buy?" A: Each brand has its strengths and weakness, whether it be price, size, low light capabilities, resolution, frame rate, support, software, compatibility, etc. There really isn't one magical brand or camera. Each security scenario is different and requires a unique solution. Q: "Where can I buy an IP HD PTZ Outdoor Camera for $200?" A: Probably not going to happen. PTZ cameras are expensive because of all the motors, belts, gears, and such. Perhaps instead consider using several fixed multi-megapixel HD cameras instead for coverage. Q: "How do I embed/add video from a camera to a website?" A: See: http://www.networkcameracritic.com/?p=1290 or http://bit.ly/10rC8WV Q: "How do I view my cameras on my TV/Monitor? A: Consider using an Android powered HDMI dongle. These mini computers are powerful and compact enough to be attached to a TV or monitor for camera viewing using an Android app. Also see: http://www.networkcameracritic.com/?p=1049 Q: "Should I buy a Foscam?" A: These cameras are not typically discussed here because of their poor reliability and feature set. They are often cloned and copied making firmware updates and support hard to come by. So in short, probably not. However if you are just starting with IP cameras, many members have since upgraded from these over time to bigger and better. Q: "How do I view my camera(s) from the internet?" A: You need to setup your router for port forwarding. Here are several guides to assist you. See: http://www.networkcameracritic.com/?p=124 or http://bit.ly/184DTvf Q: "What shutter speed should I use during low light/night?" A: "Typically 1/30 of a second is as low as you would want to have it set. Any longer and moving objects will be blurry making the footage less then useful. Q: "Should I use a wireless camera for my application?" A: Wifi signals, especially at long distances, can drop or become unreliable. They also become targets of hacking "resulting in free access to your personal cameras (EXTREMLY DANGEROUS) or blocked cameras, ones that will not record anything." It is best to use a hardwired connection via cable for installations. PoE installation can supply signal and power over one cable for easy installation. If a cable is not an option consider using a dedicated wifi access point, like the type made by Ubiquiti Networks.

I am starting this thread to capture a bunch of information in one spot to assist those with "bricked" cameras due failed firmware upgrades. I bought my first Dahua IP camera just a couple weeks ago. I was impressed & pretty happy with it, but upon reading about new capabilities in newer firmware, I decided to upgrade it. Then like many others on here, I lost access to the Web GUI and the camera was no longer functioning. I spent the last two weeks getting to know everything about these cameras and this thread will capture all this information. It will take me several weeks to document all the information so please be patient. There are a variety of problems that I will try my best to explain and share the possible solutions. I have gotten pretty comfortable with these cameras and have purposely bricked them to various degrees of severity just to validate the recovery process. Most people "brick" their cameras trying to upgrade the firmware. This is not a serious issue and it can be corrected very easily. The camera runs an upgrade service on port 3800. The configTool always shows a default port of 37777 but this is not an issue as it can do the upgrade on port 3800 anyway. Change your port to 3800 and use a firmware file lsted below and you are back in business. I will keep updating this post as I get more time to write all the details around recovery. I will also post links to over 40+ firmware files that and which cameras they will work with. It will take me a bit of time to capture all this information, so please be patient. BRICKED CAMERA? How can you tell? There are several types of "BRICKED" camera conditions and they have varying levels of severity and also varying levels of complexity for recovery. Most are simple and caused by bad firmware uploads. The worst will require a full rebuild of the partitions which load the kernel, software and all other data. 1. The first step in identifying the severity of your issue is to determine what still working on your camera. In order to do that, lets remove as many variables as possible to the troubleshooting process. If possible, connect the camera ethernet and PC ethernet on it's own switch and make sure that no vlan tagging is enabled on the switch. Next, you need to figure out if the IP address is still reacheable. Ping the last known ip address. The default address for most cameras is 192.168.1.108. If you don't know it you can use the arp/ping method to configure which adds as startic arp entry to a new ip address. (This feature is enabled on the camera by default) 2. Once you have a pingable IP, you need to know what services are still active on the camera. This can be done with a simple port scanner. I have added a link to below in tools. 3. Run the port scanner and record which ports are still open. In many cases port 23 and port 3800 will still be open. If this is your situation, it is a very simple fix. If no ports are open, you will need to do a full image load which is more complex. The typical ports that you would see are: 23 - Telnet access 80 - Web User interface 443 - SSL 554 - Real time streaming port 3800 - Upgrade Deamon 5000 - UPnP 37777 - TCP Video streaming 37778 - UDP Video Streaming 42323 - Real time remote runner Plus a whole bunch more of UDP ports and more TCP ports REPAIR WITH PORT 3800 Download a step by step guide (DAHUA IP Camera Recovery v1.0.pdf) with screen prints @ http://tinyurl.com/lbl3up7 1A. If port 3800 is open you can connect with the Dahua Config tool (link below in tools). I tdefault to port 37777 but change it to 3800 as this port where the upgrade daemon is listening. Port 37777 is a redirect but it won't work if your firmware has failed. Launch the config tool and click on login button. Type the IP address , username and password then port 3800. Open a know working firmware file and upload to the camera. 1B. If port 3800 is not open, go to the next step to enable port 3800. 2. If you have telnet access, you can login with putty. Link to putty below in tools. The default Web UI password is admin / admin. In older firmware the telnet account is root / vizxv In newer firmware the telnet account is admin / 7ujMko0+"web UI password" ---> 7ujmko0admin Once connected you can execute a ps command to see running processes. /usr/sbin/upgraded process is what listens on port 3800 for the firmware binary file. There is also another copy in /var/tmp/ A useful tip for watching the upgrade process is to kill the "upgraded" process that is running and re-launch it in the foreground to watch the upgrade. ~#>ps 625 root 0:00 [mtdblock3] 630 root 0:00 [mtdblock4] 635 root 0:00 [mtdblock5] 772 root 0:00 [ubi_bgt7d] 776 root 0:00 [ubifs_bgt7_0] 790 root 0:00 /sbin/telnetd 798 root 0:00 [OSA_796_1] 860 root 0:00 syshelper elper 60 861 root 0:00 /usr/sbin/upgraded 869 root 0:00 [dsplogd] 870 root 0:00 [encode_guard] 889 root 0:00 [flush-ubifs_6_0] 923 root 3:29 ./VideoDaemon AEWB AF TVOUT ~#> kill -9 861 ~#> /usr/sbin/upgraded [OSA-APP] OSA Build on Apr 19 2014 at 09:55:50. [OSA-APP] SVN NUM: 1609. [libpdi] libpdi.so Build on Apr 19 2014 at 10:06:34. [libpdi] SVN NUM: 13790. [libpdi] Flashtype = 4,patSize = 100000,rwSize = 800,ersSize = 20000 22:52:46|[crypt] crypt_open ok! Name: upgraded, bulid date: Apr 19 2014 09:17:58, svn: 255 [libpdi] >-------getSystemInfo-------> Fail to get env authcode! [libpdi] Get authcode error @@@@ buf = PZC4MU056W00XXX 22:52:52|[pdc] WARN (MISC_ioctl|493): Get SdCard cfg failed ! [libpdi] deviceType: IPC-HFW4300S-V2 [libpdi] processor: A5S88 [libpdi] hardwareVersion: 1.00 [libpdi] appAutoStart: 1 [libpdi] serialNumber: PZC4MU056W00XXX [libpdi] processorCount: 1 [libpdi] deviceClass: IPC [libpdi] noPtz: 1 [libpdi] noSdCard: 1 [libpdi] bandWidth: 48 [libpdi] <-------getSystemInfo-------< UPGRADED_MSG: Can't Open /mnt/mtd/Config/passwd UPGRADED_MSG: Login success! UPGRADED_MSG: Kill 976 successful [libpdi] Read: blkIndex: 1,pageIndex: 0,byteIndex: 0 ,fLag: ff [libpdi] Write: blkIndex: 1,pageIndex: 0,byteIndex: 0 ,fLag: 0 UPGRADED_MSG: reset_watchdog UPGRADED_MSG: Receive A4(alarm) UPGRADED_MSG: reset_watchdog UPGRADED_MSG: Receive A1(alive package) UPGRADED_MSG: reset_watchdog UPGRADED_MSG: Received : 29868252, FileSize : 29868252 UPGRADED_MSG: Download Complete UPGRADED_MSG: DoDownLoad success! UPGRADED_MSG: Flash init success UPGRADED_MSG: hwid file success! Fail to get env native! UPGRADED_ERR: LINE: 1074: invalid file: Install.lua UPGRADED_MSG: zip file total size: 40900220 [libpdi] >-------getSystemInfo-------> Fail to get env authcode! [libpdi] Get authcode error @@@@ buf = PZC4MU056W00XXX 22:53:10|[pdc] WARN (MISC_ioctl|493): Get SdCard cfg failed ! [libpdi] deviceType: IPC-HFW4300S-V2 [libpdi] processor: A5S88 [libpdi] hardwareVersion: 1.00 [libpdi] appAutoStart: 1 [libpdi] serialNumber: PZC4MU056W00XXX [libpdi] processorCount: 1 [libpdi] deviceClass: IPC [libpdi] noPtz: 1 [libpdi] noSdCard: 1 [libpdi] bandWidth: 48 [libpdi] <-------getSystemInfo-------< UPGRADED_MSG: packet.name: SD6XXX, board.name: IPC-HFW4300S-V2 UPGRADED_MSG: packet.hardver: , board.hardver: UPGRADED_MSG: packet.name: IPC-HX3XXX, board.name: IPC-HFW4300S-V2 UPGRADED_MSG: packet.hardver: , board.hardver: UPGRADED_MSG: Verify version success Header CRC Checking ... OK Image Name: kernel.img Image Type: kernel.img (gzip compressed) Data Size: 2546876 B, Bytes = 2.43 MB Load Address: 0XC80000 Data CRC Checking ... OK Programing start at: 0XC80000 [libpdi] write update Flag [libpdi] Read: blkIndex: 0,pageIndex: 0,byteIndex: 0 ,fLag: ff [libpdi] Write: blkIndex: 0,pageIndex: 0,byteIndex: 0 ,fLag: 55 [libpdi] Flash_createPartionTab:6 [libpdi] Erase Partion: 6 [libpdi] FlashErase: addr= 0x0xc80000,blkNum:44, blkSize:0x20000,len:0x580000 <5>UBIFS: un-mount UBI device 2, volume 0 <5>UBIFS: un-mount UBI device 4, volume 0 Upgrade : Complete Total 6%... Header CRC Checking ... OK Image Name: partition-x.cramfs.img Image Type: partition-x.cramfs.img (gzip compressed) Data Size: 4160 B, Bytes = 0.00 MB Load Address: 0X500000 Data CRC Checking ... OK Programing start at: 0X500000 [libpdi] Flash_createPartionTab:3 [libpdi] Erase Partion: 3 [libpdi] FlashErase: addr= 0x0x500000,blkNum:8, blkSize:0x20000,len:0x100000 Upgrade : Complete Total 6%... Header CRC Checking ... OK Image Name: romfs-x.ubifs.img Image Type: romfs-x.ubifs.img (gzip compressed) Data Size: 7340096 B, Bytes = 7.00 MB Load Address: 0X1200000 Data CRC Checking ... OK Programing start at: 0X1200000 [libpdi] Flash_createPartionTab:7 [libpdi] Erase Partion: 7 [libpdi] FlashErase: addr= 0x0x1200000,blkNum:64, blkSize:0x20000,len:0x800000 Upgrade : Complete Total 24%... Header CRC Checking ... OK Image Name: pd-x.ubifs.img Image Type: pd-x.ubifs.img (gzip compressed) Data Size: 1966144 B, Bytes = 1.88 MB Load Address: 0X940000 Data CRC Checking ... OK Programing start at: 0X940000 [libpdi] Flash_createPartionTab:5 [libpdi] Erase Partion: 5 [libpdi] FlashErase: addr= 0x0x940000,blkNum:26, blkSize:0x20000,len:0x340000 Upgrade : Complete Total 28%... Header CRC Checking ... OK Image Name: user-x.ubifs.img Image Type: user-x.ubifs.img (gzip compressed) Data Size: 21233728 B, Bytes = 20.25 MB Load Address: 0X2200000 Data CRC Checking ... OK Programing start at: 0X2200000 [libpdi] Flash_createPartionTab:9 [libpdi] Erase Partion: 9 [libpdi] FlashErase: addr= 0x0x2200000,blkNum:204, blkSize:0x20000,len:0x1980000 Upgrade : Complete Total 80%... Header CRC Checking ... OK Image Name: custom-x.ubifs.img Image Type: custom-x.ubifs.img (gzip compressed) Data Size: 1966144 B, Bytes = 1.88 MB Load Address: 0X600000 Data CRC Checking ... OK Programing start at: 0X600000 [libpdi] Flash_createPartionTab:4 [libpdi] Erase Partion: 4 [libpdi] FlashErase: addr= 0x0x600000,blkNum:26, blkSize:0x20000,len:0x340000 Upgrade : Complete Total 85%... Header CRC Checking ... OK Image Name: web-x.ubifs.img Image Type: web-x.ubifs.img (gzip compressed) Data Size: 5505088 B, Bytes = 5.25 MB Load Address: 0X1A00000 Data CRC Checking ... OK Programing start at: 0X1A00000 [libpdi] Flash_createPartionTab:8 [libpdi] Erase Partion: 8 [libpdi] FlashErase: addr= 0x0x1a00000,blkNum:64, blkSize:0x20000,len:0x800000 Upgrade : Complete Total 99%... [libpdi] Read: blkIndex: 0,pageIndex: 1,byteIndex: 0 ,fLag: ff [libpdi] Write: blkIndex: 0,pageIndex: 1,byteIndex: 0 ,fLag: aa Upgrade : Complete Total 100%... UPGRADED_MSG: will reboot system [libpdi] rebootSystem: i will reboot [libpdi] Read: blkIndex: 1,pageIndex: 0,byteIndex: 0 ,fLag: ff [libpdi] Write: blkIndex: 1,pageIndex: 0,byteIndex: 0 ,fLag: 0 [libpdi] pdi:system will reboot!! Here you can see each partition being loaded wit the individual img files. I will write a quick how to on loading each one individually at a later time. If you chose a valid firmware file, you will be back in working order. If you still have problems, repeat with another firmware file till you have a valid file. The IPC-HFW4300S-V2 is not natively compatible with all other 4300S firmware. I am in the process of writing a how to that explains how to over come this issue. UNBRICK WITH UBOOT via SERIAL NOTE: This section is coming soon... I'm gathering all the images I need for various camera types OTHER USEFUL INFORMATION (to be sorted later) The firmware consists of several images that are loaded into various partitions in flash in a UBI file system. You can load each partition separately if needed. More on this later.... (I'll put a guide together on flashing and recovering partitions) Once you telnet into the camera, there are number of useful binaries in the user shell that can help correct and diagnose some of the problems people are experiencing. One of the helpful steps is to kill the /var/tmp/upgraded process and run it in the foreground so you can see what is going on and easily capture error messaged. The /var/tmp/upgraded process is what opens the port 3800 and allows you to connect to the camera with the config tool if your web services have failed. There is also another copy in usr/sbin/. Also, in there is a command to reset all the parameters back to factory defaults (username, password, ip address back to 192.168.1.108 etc.) This can be accomplished with /sbin/clearparam. Another issue that people run into is the constant reboot issue. This can be caused by a failed process. The main application which provides all the camera capabilities (web interface, streaming, etc.) is /usr/bin/sonia. This process is what makes most firmware different from version to version (sort of). There are also changes to the web partition which contains the web server pages that /usr/bin sonia hosts on port 80. The sonia process is invoked by a shell script in init.d and if the process is killed, the camera reboots after a few minutes. This has cause many people issues when trying to "unbrick" the camera since you only have a few minutes between reboots. To stop the reboots you can update the flash. There is a parameter called appauto that tells the camera to auto start /us/bin/sonia. If you want the camera to start and not invoke the shell script that launches sonia, you need to set appauto to 0. This will stop the camera from rebooting when sonia is not running. This cam be accomplished by running '/sbin/appauto 0'. To turn it back on, just run /sbin/appauto 1. This writes the boot parameter in flash that the kernel reads before starting the process. You can check the current status of the appauto bootparameter with 'cat /proc/dahua/bootpara' It will only show what the parameter was when you booted up, so if you changes it you need to reboot to see the change in /proc/dahua/bootpara. Realtime streaming URL - rtsp://192.168.1.108/cam/realmonitor?channel=1&subtype=0&proto=Onvif You can change the subtype to 1 for the secondary stream also you can add user:password@ in front of the IP address if you have the permissions set requiring it. You can use the HTTP API to configure some parameters that are not yet in the web UI. For instance, another member discovered he could enable NFS through the web UI in addition to the local SD card. This config is not possible through the web interface as you need to pick one or the other. These documents details the API of Dahua video products (links provided to some of the versions below). Programmers or users can access and configure Dahua video products through the API. Every setting of the camera is available through the API whereas only a small number are available through the WEB interface. The document with version 1.10 is available with firmware version 2.0 and above. This document with version 1.20, 1.21, 1.22, 1.23,1.24,1,25,1,26,1,27,1,28 is available with firmware 2.210 and above.This document with version 1. 29 ,1.30, 1.31, 1.32, 1.33, 1.34, 1.35, 1.36 is available with firmware 2.210 and above.This document with version 1.37 is available with firmware 2.212, 2.4 and above. I have also done a bit of testing around the tftp process that is invoked in u-boot that looks for upgrade_info_7db780a713a4.txt and failed.txt. I think with a little more work, I'll figure out if there is a recovery method using tftp without serial access. This would be necessary if you lose telnet access and need to rebuild the kernel partition that hosts telnetd. Tools DAHUA IP Camera Recovery v1.0.pdf....................... http://tinyurl.com/lbl3up7 Port Scanner .................................................. http://tinyurl.com/q53pojg Putty .............................................................. http://tinyurl.com/lvbbmsq Tftp Server ..................................................... http://tinyurl.com/m46wnhe Dahua Docs & Tools DAHUA_HTTP_API 1.0 .pdf ................................................ http://tinyurl.com/lb43lga DAHUA_HTTP_API_1.23.pdf ................................................ http://tinyurl.com/lrwye3k DAHUA_HTTP_API_FOR_IPC 1.28.pdf ........................................ http://tinyurl.com/kskrcay DAHUA_HTTP_API_FOR_IPC&SD-V1.36.pdf .................................... http://tinyurl.com/mooccf9 DAHUA_HTTP_API_FOR_IPC&SD-V1.37.pdf .................................... http://tinyurl.com/kvyddfp DAHUA_HTTP_API_FOR_DVR_V1.29.pdf ....................................... http://tinyurl.com/klc72tr General_ConfigTool_Eng_V1.0.5.R.120428.zip ........................ http://tinyurl.com/mwlzbb3 General_ConfigTool_Eng_V1.06.1.T.120807.zip ........................ http://tinyurl.com/leudphu General_ConfigTool_Eng_V1.07.2.R.130304.zip ....................... http://tinyurl.com/obs5ud7 General_ConfigTool_Eng_V1.07.3.R.130701.zip ....................... http://tinyurl.com/o6p628f <---- Use this one General_ConfigTool_Eng_V2.00.0.R.140410.zip ........................ http://tinyurl.com/nbqtgev Firmware Files Firmware files are grouped by camera type and video signal (NTSC --> Eng_N / PAL --> Eng_P / or BOTH --> Eng_NP) Files are ordered by version number with the latest Firmware in blue. Files with DH_ prefix are DAHUA direct firmware files and those with General_ prefix are general release for OEM cameras but I've had good luck with both. DH_IPC-HX1100_Eng_NP_V2.210.0000.3.R.20140416.bin .................................................. http://tinyurl.com/m2jf3qv General_IPC-HX3(2)XXX_Eng_N_V2.210.0001.0.R.20130517.bin ............................................... http://tinyurl.com/q98zg9x General_IPC-HX3(2)XXX_Eng_P_V2.210.0001.0.R.20130517.bin ................................................ http://tinyurl.com/nekapn3 General_IPC-HX3(2)XXX_Eng_NP_V2.210.0001.0.R.20130517.bin ............................................. http://tinyurl.com/p59ym6z General_IPC-HX3(2)XXX_Eng_P_V2.211.0000.0.R.20130726.bin ................................................ http://tinyurl.com/my54r9z General_IPC-HX3(2)XXX_Eng_N_V2.212.0000.0.R.20131206.bin ............................................... http://tinyurl.com/lrvtm2z General_IPC-HX3(2)XXX_Eng_P_V2.212.0000.0.R.20131206.bin ................................................ http://tinyurl.com/n9rv23n General_IPC-HX3(2)XXX_Eng_N_V2.212.0001.0.R.20131224.bin ............................................... http://tinyurl.com/l5kg2d9 General_IPC-HX3(2)XXX_Eng_P_V2.212.0001.0.R.20131224.bin ................................................ http://tinyurl.com/q6c2gox DH_IPC-HX3(2)XXX_Eng_NP_8M_V2.212.0000.4.R.20140307.bin ............................................... http://tinyurl.com/mnzx33h DH_IPC-HX3(2)XXX_Eng_NP_8M_V2.212.0000.5.R.20140326.bin ............................................... http://tinyurl.com/ke285w5 DH_IPC-HX3(2)XXX_Eng_NP_8M_V2.212.0000.6.R.20140419.bin ............................................... http://tinyurl.com/mllzcox General_IPC-HX3(2)XXX_Eng_P_V2.420.0000.0.R.20140414.bin ................................................ http://tinyurl.com/nftaogy DH_IPC-HX3(2)XXX_Eng_N_V2.420.0000.0.R.20140414.bin .................................................... http://tinyurl.com/ma5q64d General_IPC-HX5(4)XXX_Eng_P_V2.210.0000.2.R.20130821.bin ................................................. http://tinyurl.com/pdcdmdk General_IPC-HX5(4)XXX_Eng_N_V2.210.0000.4.R.20130911.bin ........................................................ http://tinyurl.com/pdoxjzj General_IPC-HX5(4)XXX_Eng_P_V2.210.0000.9.R.20131217.bin ........................................................ http://tinyurl.com/p3g4t54 General_IPC-HX5(4)XXX_Eng_N_V2.210.0000.10.R.20140111.bin ...................................................... http://tinyurl.com/mnjpd79 General_IPC-HX5(4)XXX_Eng_P_V2.210.0000.12.R.20140225.bin ...................................................... http://tinyurl.com/nssnph6 DH_IPC-HX5(4)XXX_Eng_NP_V2.210.0000.12.R.20140225.bin ..................................................... http://tinyurl.com/lcjr8xv DH_IPC-HX5(4)XXX_Eng_NP_V2.210.0000.16.R.20140421.bin ..................................................... http://tinyurl.com/k67gu9u DH_IPC-HX5(4)XXX_Eng_NP_V2.210.0000.18.R.20140429.bin .................................................... http://tinyurl.com/n779scx General_IPC-HX5(4)XXX_Eng_N_V2.210.0000.21.R.20140613.bin ...................................................... http://tinyurl.com/qd2thhe General_IPC-HX5(4)XXX_Eng_P_V2.210.0000.21.R.20140613.bin ...................................................... http://tinyurl.com/p8q75b4 General_IPC-HX5(4)XXX_Eng_N_V2.400.0000.0.R.20131231.bin ........................................................ http://tinyurl.com/kmd7hu9 DH_IPC-HX5(4)XXX_Eng_N_Stream3_V2.420.0000.0.R.20140419.bin .................................................. http://tinyurl.com/mb75g2n DH_IPC-HX5(4)XXX_Eng_P_Stream3_V2.420.0002.0.R.20140621.bin ............................................ http://tinyurl.com/laj29k5 General_IPC-HX5(4)XXX_Eng_N_Stream3_V2.420.0000.0.R.20140419.bin ......................................... http://tinyurl.com/mzw85fz General_IPC-HX5(4)XXX_Eng_P_Stream3_V2.420.0000.0.R.20140419.bin ......................................... http://tinyurl.com/ov6krph General_IPC-HX5(4)XXX_Eng_P_Stream3_P2P_V2.420.0000.0.R.20140419.bin ................................. http://tinyurl.com/oxgblkq General_IPC-HX5(4)XXX_Eng_N_Stream3_V2.420.0002.0.R.20140621.bin ......................................... http://tinyurl.com/kejg3fv General_IPC-HX5(4)XXX_Eng_P_Stream3_V2.420.0002.0.R.20140621.bin ......................................... http://tinyurl.com/pfmevdu General_IPC-HX5(4)XXX_Eng_N_Stream3_V2.420.0003.0.R.20140930.bin ............................................... http://tinyurl.com/kchslos General_IPC-HX5(4)XXX_Eng_N_V2.420.0003.0.R.20140930.bin ........................................................ http://tinyurl.com/ok4f8fx General_IPC-HX5(4)XXX_Eng_N_Stream3_V2.420.0005.0.R.20141205.bin .............................................. http://tinyurl.com/qbrfg3k General_IPC-HX5(4)XXX_Eng_P_Stream3_V2.420.0005.0.R.20141205.bin ......................................... http://tinyurl.com/ot99vgw DH_IPC-HX8XXX_Eng_NP_V2.400.0000.2.R.20140506.bin .......................................................... http://tinyurl.com/lbar98x I will also post the bare metal img files when I get some time which contain the firmware and all the img files including the update.img that can be used for serial recovery. I have just started the process of uploading firmware... There are much more to come as well as many more camera models. Also if you have any you want to share please PM me what you have and where I can link them to this thread. Thanks to Euly for sharing firmware files! ___________________________________ IMPORTANT NOTE FOR IPC-HFW4300S-V2 CAMERAS The new camera appears to have differences (a few that I already found) that makes some of the general firmware incompatible with them. I have found a workaround, but it is complex. I will try to summarize it in a separate thread in the following weeks. I will also repackage the newest firmware files in versions that will work for the V2 cameras. Stay tuned! In the meantime, you can use General_IPC-HX5(4)XXX_Eng_N_V2.210.0000.21.R.20140613.bin or the PAL equivalent to recover your camera. Well, that's all I have time to share for now, but I'll do my best to put together a comprehensive guide to the inner workings of these cameras and a guide to unbrick in any failed software situation. Thanks and take care. Rob

Hi, I recently bought two of these cameras: http://www.amazon.com/Hikvision-DS-2CD2132-I-Fixed-Focal-Camera/dp/B00EJXK0I6 . Here are the specs: Hikvision DS-2CD2132-I 3MP Dome Camera 3MP (2048 x 1536) high resolution Full HD1080p real-time video Up to 30m IR True day/night IP66• Vandal-proof It supports PoE. Here's a video showing it's installation using PoE: My Router does not support PoE, so I used these PoE Injectors to add PoE to the Ethernet cable: http://www.amazon.com/Ubiquiti-Poe-15-Output-Ethernet-Adapter/dp/B002R7JPGE I would think my units were broken/defunct, but getting two that don't work at the same time is very unlikely, I would think. The distance is <100 feet (about 50-70 feet), and I'm using Cat 6A, so I doubt it's distance related. It crosses some electrical lines, but never runs parallel to them closely. I used a network tester to verify that the cables are crimped correctly and that PoE was indeed being added to the line. Everything checks out. However, my problem is that these cameras do not turn on. They do not appear on my network. It's almost like the PoE Injector just destroys the connection, and adds PoE to the Ethernet cable leaving nothing left. I haven't dealt with PoE at all before this, so I may not be understanding how it works. What could my issue be? What should I check? Are my PoE Injectors incompatible with this setup? Any help is appreciated. Thanks, Tremor.

Okay, so I was playing around with the settings as my cameras would not display across the entire screen in 5MP@15/20 fps. It's a 1080p TV and just yesterday, it was displaying fine. Anyway, I started experimenting with a few settings - went into the PTZ menu that you access from the camera's main screen (not the DVR's main menu) - and I changed it from AHD or TVI to CVBS. Now both my cameras (as I changed both their default CVI setting to CVBS to check the aspect ratio) - are stuck in CVBS/ultra low resolution mode or SD. I can no longer access the PTZ menu. When I click on the main interface - nothing happens. I also noticed in the DVR's main menu PTZ settings (under "camera") that the Control Mode option is now greyed out. I can't even access that. This is driving me absolutely nuts - my CCTV camera feed looks like it's more than 20 years old! I'm not even getting colour on one of the cams now. It's just stuck in CVBS mode. How do I restore it to TVI, AHD or CVI? I've literally tried experimenting with every single option in the menu. Please HELP!! I have the Dahua dh-xvr5104hs-x1 with a Dahua camera and Pogo camera, both 5MP@20fps capable and 1080p@30 fps capable.

Yes WD Blue 2TB 3.5" SATA Hard Drive - 7200rpm

Hi WD black or WD blue will also be ok many basic drive make will work if speed is 7200

Hi yes you need a 3.5 jack to rca cable you can make one or buy one argos sells them

Hi .. yes that’s the same just different colour they are known as a patch lead rj45 do you need a longer one ?

Hi. No you don’t need any cables to your pc It will connect over your network

Hi. You will need to run a network cable from your dvr to your router then you need to switch off your recorder after you have connected the cable switch back on ….. right click on your dvr screen to get to menu ….. half way down you will see guide ….. follow the instructions

Hi …. You will need to install a microphone to be able to hear and record sound.

Hi. Button right below menu……marked … source

Hi. On your tv remote controls you should have a source button . Which will switch your tv to TV -HDMI 1 -HDMI 2- SCART- or VGA (can also be called pc) seeifyou get a image then

Hi on your first two pictures ….. you connect VGA on back of recorder to VGA marked on back of tv. to get your unit to talk with your pc ….. first you need to get your system up and running first as the software for your pc is taken from your dvr once all up and running remote viewing is done by an app called explorer which is found on apple store or play store

Hi first came out in 2010 ….. there is no updates for that unit updating firmware will not update the hardware it’s a D1 resolution dvr (which is low by todays standard) unit will not even allow the use of its apps

Hi always welcome and everyone is here to help

Logo's are usually compiled into the full software. I do not know any company that would just give you the uncompiled software.

why does every company call themselves the leaders if any of my installers did like picture below …. It would be there last install it’s a hik turret camera why not just mount it at cable entry and turn camera

Hi Tom! It's all set up!!! It went smoothly and with the new dvr, NO more loud fan noises!! The cameras are great too! Great video pics. Looking forward to seeing night time pics too! Thank you for being there for everyone and especially us old folks! I really appreciate all your time. Thank You!!!

Hi to all forum members, I am newbie here and want to share latest technology, home security products, brands latest news related information here. If you allow me to become part of your useful forum discussions on CCTV cameras, smart home solutions then i will definitely help with my years of researched knowledge and skills in this technical field. Thanks & Regards Securitystoreae

Ok try this one …. This is based on time and date showing in your picture NpSZOo1072 case sensitive

I have an 8CH H.264 Standalone DVR ZMD_DT_SCN8 DVR with 8 ZModo BNC Cameras attached to it. I installed 6-8 years ago. It went belly up yesterday. I would like to buy a replacement DVR and use my existing cameras. It appears that ZModo no longer sells DVRs My question is if I can use any DVR that has BNC inputs. Here is what the ZMode manuals says about its inputs. Analogue video signal: The video input port is BNC connector plug. The demand of input signal is PAL/NTSC BNC (1.0VP-P, 75Ω). Since I am replacing I might go with a 16 CH and adds some additional cameras later but for now I just want to get back up and running. Not much in the way of others requirements LAN, HDMI, Android, etc. I really don't want to install 8 new cameras. These are the cameras. http://surveillance.zmodo.com/700tvl-ultra-hi-reso-outdoor-security-camera.html And here are the camera specs: * 1/4" Color CMOS Image Sensor * 700 TV Lines, Horizontal * 3.6mm Lens * Signal: NTSC * Night Vision Min. Light: 0 Lux (IR On) * IR Irradiation Distance: up to 80' * Operation Temperature: 14F~122F * Weatherproof: Yes * Power: 12V DC * Mount: Wall * Video Connector: BNC * Power Connector: RCA 12V DC I did a search in the forum but didn't find any relevant posts.

Answer from Dahua 1. DH_DVR21xx_SpnEng_NP_V3.200.0001.28.R.20170803 , this program supports two system languages ( Spanish and English), two video standards (P and N) . 2. DH_DVR21xx_Eng_P_V3.200.0001.28.R.20170803, this program supports one system languages ( English), one video standards ( P) .

Hello, For my Dahua DVR5104H-V2 (ver 3.200.0001.24 build 2014-11-14) i was found these firmware. What is the difference between ? DH_DVR21xx_Eng_P_V3.200.0001.28.R.20170803 -13.72MB- Applicable models DHI-DVR2104C-B,DHI-DVR2104C-H,DHI-DVR2104C-V2,DHI-DVR2104C-W,DHI-DVR2104H-H,DHI-DVR2104H-V2,DHI-DVR2104H,DHI-DVR2104HC-H,DHI-DVR2104HC,DHI-DVR2104HE-H,DHI-DVR2104HE-V2,DHI-DVR2108C-B,DHI-DVR2108C-V2,DHI-DVR2108C-W,DHI-DVR2108H-V2,DHI-DVR2108H,DHI-DVR2108HC,DHI-DVR2108HE-V2,DHI-DVR2204A-V2,DHI-DVR2208A-V2,DHI-DVR5104C-V2,DHI-DVR5104H-V2,DHI-DVR5104HE-V2,DVR2104C-B,DVR2104C-H,DVR2104C-V2,DVR2104C-W,DVR2104H-H,DVR2104H-V2,DVR2104HC-H,DVR2104HE-H,DVR2104HE-V2,DVR2104HE,DVR2104HS,DVR2108C-B,DVR2108C-V2,DVR2108C-W,DVR2108H-V2,DVR2108HC,DVR2108HE-V2,DVR2108HE,DVR2108HS,DVR2204A-V2,DVR2208A-V2,DVR5104C-V2,DVR5104H-V2,DVR5104HE-V2 DH_DVR21xx_SpnEng_NP_V3.200.0001.28.R.20170803 - 13.53MB - Applicable models: DHI-DVR2104C-B,DHI-DVR2104C-H,DHI-DVR2104C-V2,DHI-DVR2104C-W,DHI-DVR2104H-H,DHI-DVR2104H-V2,DHI-DVR2104H,DHI-DVR2104HC-H,DHI-DVR2104HC,DHI-DVR2104HE-H,DHI-DVR2104HE-V2,DHI-DVR2108C-B,DHI-DVR2108C-V2,DHI-DVR2108C-W,DHI-DVR2108H-V2,DHI-DVR2108H,DHI-DVR2108HC,DHI-DVR2108HE-V2,DHI-DVR2204A-V2,DHI-DVR2208A-V2,DHI-DVR5104C-V2,DHI-DVR5104H-V2,DHI-DVR5104HE-V2,DVR2104C-B,DVR2104C-H,DVR2104C-V2,DVR2104C-W,DVR2104H-H,DVR2104H-V2,DVR2104HC-H,DVR2104HE-H,DVR2104HE-V2,DVR2104HE,DVR2104HS,DVR2108C-B,DVR2108C-V2,DVR2108C-W,DVR2108H-V2,DVR2108HC,DVR2108HE-V2,DVR2108HE,DVR2108HS,DVR2204A-V2,DVR2208A-V2,DVR5104C-V2,DVR5104H-V2,DVR5104HE-V2

You have purchased the wrong injectors...those are specific to ubiquiti...they are not true poe standard 802.3af compliant..they will not work with your cameras at all..return them asap.. If you want injectors get these injectors (select injector not splitter or kit) http://www.amazon.com/TP-LINK-TL-PoE150S-Gigabit-Injector-compliant/dp/B001PS9E5I/ref=sr_1_1?ie=UTF8&qid=1416977530&sr=8-1&keywords=poe+injector or you could just buy a poe switch, this one will power 4 cameras (the other 4 ports are not poe, just standard ports) http://www.amazon.com/TP-LINK-TL-SF1008P-100Mbps-8-Port-802-3af/dp/B003CFATT2/ref=sr_1_1?s=electronics&ie=UTF8&qid=1416977620&sr=1-1&keywords=poe+switch&pebp=1416977653577