brebenac

Check your DVR log. Look for Reboot code similar to 0x05. If found, change s-ata cable and format HDD.

Change S-ATA cables.

export config from good nvr and import in bad one, does this fix it?

Yeah, it might be hacked. To confirm this, try to change other settings, like adding another user, or change current IP or recording mode. Restart and check if new settings are kept. Maybe also try a log clear or even factory reset it.

I can see your port on your picture ..... Have you done this before ? yes the port is there but only can use tftp i can make video to explain what i mind by the way, i'm not expert on linux system could someone tell me which directory have the screen touch drivers? copy log: bin/sh: ?: not found # ls [1;34mbin[0m [1;34metc[0m [1;34mlib[0m [1;34mopt[0m [1;34msbin[0m [1;36mtmp[0m [1;34mutils[0m [1;34mdev[0m [1;34mhome[0m [1;34mmnt[0m [1;34mproc[0m [1;34msys[0m [1;34musr[0m [1;34mvar[0m # ls var [1;34mlib[0m [1;34mtmp[0m [1;34musr[0m # ls var/lib [1;34mmodules[0m # ls var/lib/modules # run up /bin/sh: run: not found # If touch is not in sync with screen position, just simultaneously press UNLOCK + MENU, it will take you to screen calibration (several targets to click). But if the image has a left or right shift, there is no cure for it. Just rollback the update.

Yes, just make sure you choose a video output resolution from camera OSD (not in encode section of DVR)

Have a little patience in there, I know what I am saying here.

Hi there! There is a small 4 pin port inside the VTO that is used as a TTL serial port. Once you brick your device you can connect that port to a pc and use serial commands to revive the unit (as long as uboot is still working). However, I strongly recommend you NOT to alter the partitions on the VTO unless you have knowledge, tools and needed firmware files in order to restore your toy to original state. Having the telnet port open is really a bad idea, since this means the vto is using a really old version of firmware, connecting it to internet would make it vulnerable. I suggest you wait a while, dahua will release a firmware update to change only the audio files, it will work as a patch that can be applied to whatever current firmware version your VTO has, so no need to constantly editing the partitions everytime you update the unit.

You will not be able to use the camera on full specs on this XVR. Your XVR supports maximum 2Mpix while camera is 4Mpix. You need to look for a different XVR to support 4Mpix, or connect the camera on HCVR (or XVR) 4Mpix, enter the OSD menu of the camera and set internal resolution of camera to 1080p and you will be able to use this camera on your XVR (but in 1080p resolution only).

Well what do you expect with stupid questions. You have a plug and play dahua ..... And you are struggling Like I said are your Foscam compatable ???? Or do you not have a clue Hi Tom, we should be more relaxed when offering explanations. He is somehow right about his problem. What he did not "see" was the fact the nvr is using 2 different network adapters and has a problem managing network segments when using same subnet on both. In fact, the NVR uses 2 different adapters but does not offer switching capabilities between them. So, he should use NIC1 as 192.168.1.xxx, set to default interface (in order to have web and other ports assigned to it) and NIC2 as 192.168.2.xxx. Cameras should have the ip as 192.168.2.xxx connected to NIC2. This way all trouble is gone.

Actually, the capabilities for this model are: 16 channels ANY type (CVBS/HDCVI/IP) + 8 channels IP (@max5Mpix each, ONVIF/PSIA/General(rtsp url) compatible), with support for Intelligent video detection of IPcameras. Pretty neat, ha?

Seems to be a parasite signal along your camera power input. If you are absolutely sure all cameras work fine with the power supply, and all power supply work fine with other cameras, and also all cables used have same issue, maybe the problem is a metallic support of the camera touching other metallic parts of the wall/support. Try connecting the camera on a short cable (1-2m) near the dvr. If image is clear, use the long cable, but keep the camera near the dvr also. If still clear image, move the camera under it's current position and at the end try to mount it back. It would also be a good idea to check if the image is distorted ONLY during the night, where the power needed by the camera increases.

Try using Config Tool on port 3800 (not 37777). If it logs on, you still have a chance.

Brian, you could set static DHCP pool table for the MAC address of the cameras. Most of modern routers have this, so you could stay assured the cameras have always the same address set by DHCP. If you use static IP directly on camera, you should first check the DHCP pool size, in order to eliminate any possibility that your router could assign the same ip address you set on camera to a different "new" device joined in your network (e.g. Camera IP is 192.168.1.108 and the router has DHCP addresses starting from 192.168.1.100... the 9-th device added in your network could conflict with static ip of the camera...) Except for that, yes, you can stick to Dahua devices, SmartPSS (CMS) is quite user-friendly and you can also have pretty neat functions to use...

First you have to ask the version V3.201.0000.0.R.20151120 from your supplier, since this is the last available for your model. A portion of the release info for this firmware version is: "This version’s IVS function is disabled in default; you need to enable it manually. The reason that IVS isn’t enabled is IPC in old version connected to NVR will be halted. Thus, in case of this trouble which users don’t use IVS function, this function is disabled. If you need to use IVS, please make sure the non-intelligent IPC is in the latest firmware version. Also IVS function for NVR4XXX only support IPC with IVS function in frontend." Once you have this version on your NVR, considering you have no other non-intelligent IPC, you can enter the general section of the menu and check the IVS box. After reboot you will have the IVS section in EVENT menu. Hope this helps.

E-Sata is probably in this case the worst solution to choose. Direct connections on small distance cables to "secure" recordings is not a good solution. The presumable thief can trace the cable and steal the e-sata device, too, or at least inject higher power through the cable and burn the "safe" hdd. Even on recording on FTP site is not secure, because this thief can access the stolen DVR, verify the connection details of the FTP site (which are stored on DVR), connect on FTP with same user/pass and delete all data, and maybe steal some more info from the site. The best option is to use a DVR combined with a NVR. The DVR will store data locally, and the NVR (on different location) can connect to the DVR channels and record them as IP cameras. This way the thief cannot see the user/pass details to connect to the NVR, and also you can have good control on the recording perio by selecting different schedule fro eac channel (maybe you do not need all channels stored on NVR). Also, you can set the NVR to record channels from different DVR's, this way with one NVR you can protect multiple sites assuming the network bandwith is sufficient...

Please attach pictures of both the upper and the lower side of the PCB. We will be able to detect if the time/date is stored on a RTC chip or just automatically obtained from NTP server. Also, your battery can be of a different model, even one that can be soldered directly on the PCB. If any brackets of the HDD are covering parts of the PCB, please remove before taking the pictures...

I am pretty sure the ENTIRE NVR4xxx series support handling the IVS info from camera (this includes the CHEAPEST models like NVR4104 and NVR4108... The NVR just receives the IVS info from camera, not compute the IVS itself). I am pretty familiar with Dahua, if I remember correctly I even set the NVR4014-W to send email on IVS event of the IPC-HDW4421... If your supplier cannot help you, ask for support directly from Dahua (at least ask the question of IVS compatibility for your specific models yourself), maybe they will confirm and not just forward your request directly to your supplier again... If you consider using "obscure" firmware links for your NVR to update, please don't. Better to be safe than sorry, some firmware files are specifically compiled for specific models, and you could end-up with a non-booting device.

Any analog system from Dahua does record the image "as is". Even the "no video" type of signal, when the sync is lost is recorded as a black image with the OSD (channel name and time) on it. The HDCVI system cannot be used to receive analog signals. HDCVI cameras cannot be used to send image through A/V wireless systems, so the options here are pretty limited. Use a standard analog system if the cameras are on pure analog format. And there's the "tribrid" option where you can record analog/HDCVI/IP signals on same unit...

First, congrats on your purchase! Now, let's find an answer for each question: A1: If the schedule for recording is set to "Normal", then all you see in the playback interface are the green lines (regular record). If you want to record by motion, or alarm, or intelligent, then in the schedule section you should choose the corresponding option for the corresponding channel in the corresponding interval. A2:Check if there is a "Log enable" option for the desired event in the event setting window A3: The snapshot option is enabled? If so, then you should receive at least 3 emails: start_event, snapshot_email, stop event A4: If the IVS section is not in your NVR, then check with your seller for last firmware version, because Dahua does not offer direct support for end-user. If the section is available in your nvr, then you should have pretty much the same options to trigger on intelligent detection as for motion detection, alarm input, etc. P.S.: your hunch is true: the NVR does NOT analyse motion detection, intelligent, etc. Only alarm inputs are analyzed, the rest is the camera job to detect AND report to NVR. So in the connection stream of the camera to the NVR you can find video and audio data along with supplementary information containing events, control, etc. Then, based on that "extra info" the NVR decides what to do in case of event (based on your setting it will activate alarm output, send mail, beep, etc). Hope this info helps...

The battery replacement should fix the default date/time after power failure. If it does not, check for NTP, DST options to get the real time/date from NTP server (always precise). Most of the IDE to S-ata converters do a good job, except for the ones adapting a real large capacity drive on a real old DVR unit, where the drive would not be recognized at all - this is only a try-until-success method (mostly based on luck). So, Good luck on this one!

http://reversatronics.blogspot.ro/2015/03/sunluxy-dvr-mkii-telnet-root-password.html Check this site. It will explain it pretty easy...

That kind of serial port has GND, Vcc, Tx and Rx. Considering you have a multimeter at hand, you can easy find the GND and the Vcc. And you're left with only 2 possibilities for the Tx and Rx. Good Luck!

Did you try telnet port connection on it? What's the exact prompt message? there a re several "default" passwords that you could use to access internal OS (try even without password).

Hi, you should first check the power supply specs. Basically, if the noise of the hard drive is like it's trying to start but then it stops and try to start again, then the power supply is to blame (defective or maybe underrated). (I have already excluded from the options list the disconnected cables).