Jump to content
reeves1985

Mini nvr questions

Recommended Posts

Hi i have a CT-N6200-8EL Mini NVR 2. the firmware is 8CH_Mini_NVR_V4.0_20150124_Firmware.

 

I read in a post on here that a newer firmware version is available that doesn't require activex and works with other browsers like Safari, Chrome, etc. I use a mac so I hate to drag out the old Dell to look at stuff.

Can anyone verify this? I don't see one available on the URCCTV download page.

 

also, has anyone put together a good walk thru directions on setting one of these up? The manuals aren't great. I have mine working with the exception of it won't record even though it says it is.

 

thanks!

 

Im not sure about the firmwares but with your issue of it not recording, are you using a USB harddrive, USB flash drive or SATA?

 

I tried a USB flash drive but it wouldnt recognise it. Now im using a USB 2.5" harddrive but you have to check to make sure its connected.

 

Go to

Config>System Management>Storage management

 

Make sure your hard drive is showing up.

 

Also when i added my cameras onto the NVR for some reason each camera showed up on the search twice. I have to make sure that i select the ONVIF one otherwise the recording doesnt work and motion detect settings do not save.

 

So i got recording working. I can look at it through the monitor and mouse directly from the NVR. When I try to view it on the MacBook, the unit must only work with Flash or ActiveX to show it.

 

one other weird issue: if I set the date and time in the device menu, when I go to the playback screen and then return to the main screen the date will change to 1/2/1970. Any idea how to fix that?

I do have the NTP setup with time.nist.gov instead of the chinese NTP server originally listed. anybody have it again?

Share this post


Link to post
Share on other sites

Hi Roman,

 

go to: http://www.urcctvstore.com/Download.html

 

and scroll down to the recovery file section, download the files and follow the instructions on how to use rebooting tools

---------------------------------------------------------------------- Recovery File ------------------------------------------------------------------------------------------------------

 

I have a N6200-16EH (Centronics brand) and I didn't see it listed as being supported under the recovery file section. I tried it with the firmware available for that model and the USB stick flashes away like it is booting but after a delay it boots into the NVR still in its corrupted state.

 

The NVR lets you login but you cannot access any of the settings other than the "Log file" search dialogue or the play back module. If any one can help I would most grateful.

 

I've been struggling with these NVR's for some months and they seem like they should be a great product. I have three N6200-16EH's and a variety of the 8 channel versions with and without SATA drive support which have worked OK but with some outages and losing cameras occasionally but we have managed stabilise them and they do the job.

 

I have a second N6200-16EH that is almost completely dead. The blue LED comes on, the hard drive is powered and if you have a USB flash drive in it blinks once and then nothing. No boot! No Beep!

 

This particular one had been lightly used but after being deployed it died after two days. We replaced it with the one that has the faults I outlined above and we didn't use an internal HD, we attached to the Esata port.

 

That one has now been replaced with 3rd one which has been upgraded to the latest firmware. So it is fingers crossed with the final one.

 

I'd really like to revive these other two, so if anyone has any ideas please shout out.

 

Bryn

Share this post


Link to post
Share on other sites

@Mike Mahon, running 4CH mininvr with latest firmware version cannot connect my 4 QD320 escam cams with I12 protocol... On the camera log it keeps writing wrong login(username/password)... cameras also run latest firmware. Where I can find I12 protocol to work with them?

Share this post


Link to post
Share on other sites
@Mike Mahon, running 4CH mininvr with latest firmware version cannot connect my 4 QD320 escam cams with I12 protocol... On the camera log it keeps writing wrong login(username/password)... cameras also run latest firmware. Where I can find I12 protocol to work with them?

 

 

Finally again due to the f@#$ protocols bricked my 4ch NVR again!!!... now its dead... I have only access from serial port and also tried TFTP upload through uboot tools... but again stops in booting Linux image at "encryption fail" point... ANY HELP would be appreciated... maybe I am using wrong recovery files?

 

THANKS IN ADVANCE!!

 

Here is what i get in boot:

                                                                                                                                                                   

U-Boot 2010.06 (Dec 05 2013 - 16:53:16)

Check spi flash controller v350... Found
Spi(cs1) ID: 0xC2 0x20 0x19 0xC2 0x20 0x19
Spi(cs1): Block:64KB Chip:32MB Name:"MX25L25635E/735E/635F"
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
32768 KiB hi_sfc at 0:0 is now current device

mmu_enable
<<imgwidth=1024, imgheight=768, linebytes=2048>>
decode success!!!!
dev 0 set background color!
dev 2 set background color!
dev 0 opened!
dev 2 opened!
graphic layer 0 opened!
graphic layer 2 opened!
(Re)start USB...
USB:   scanning bus for devices... 1 USB Device(s) found
      scanning bus for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
32768 KiB hi_sfc at 0:0 is now current device

## Booting kernel from Legacy Image at 82000000 ...
  Image Name:   Linux-3.0.8
  Image Type:   ARM Linux Kernel Image (uncompressed)
  Data Size:    1554460 Bytes = 1.5 MiB
  Load Address: 80008000
  Entry Point:  80008000
  Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.0.8 (root@localhost.localdomain) (gcc version 4.4.1 (Hisilicon_v100(gcc4.4-290+uclibc_0.9.32.1+eabi+linuxpthread)) ) #35 Tue Dec 31 12:16:31 HKT 2013
CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: hi3520d
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 37338
Kernel command line: mem=147M console=ttyAMA0,115200 root=/dev/mtdblock2 rootfstype=squashfs mtdparts=hi_sfc:320K(uboot),1536K(kernel),4M(rfs),25792K(app),768K(config),256K(logo)
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 147MB = 147MB total
Memory: 144932k/144932k available, 5596k reserved, 0K highmem
Virtual kernel memory layout:
   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
   fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
   DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
   vmalloc : 0xc9800000 - 0xfe000000   ( 840 MB)
   lowmem  : 0xc0000000 - 0xc9300000   ( 147 MB)
   modules : 0xbf000000 - 0xc0000000   (  16 MB)
     .init : 0xc0008000 - 0xc0025000   ( 116 kB)
     .text : 0xc0025000 - 0xc03aa000   (3604 kB)
     .data : 0xc03aa000 - 0xc03c5940   ( 111 kB)
      .bss : 0xc03c5964 - 0xc0411ea8   ( 306 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:128 nr_irqs:128 128
sched_clock: 32 bits at 82MHz, resolution 12ns, wraps every 52060ms
Console: colour dummy device 80x30
Calibrating delay loop... 1318.91 BogoMIPS (lpj=6594560)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Serial: AMBA PL011 UART driver
uart:0: ttyAMA0 at MMIO 0x20080000 (irq = 40) is a PL011 rev2
console [ttyAMA0] enabled
uart:1: ttyAMA1 at MMIO 0x20090000 (irq = 41) is a PL011 rev2
uart:2: ttyAMA2 at MMIO 0x200a0000 (irq = 42) is a PL011 rev2
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource timer1
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (double precision)
L2cache cache controller enabled
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
squashfs: version 4.0 (2009/01/31) Phillip Lougher
JFFS2 version 2.2. (NAND) Β© 2001-2006 Red Hat, Inc.
fuse init (API version 7.16)
msgmni has been set to 283
encryption fail







Share this post


Link to post
Share on other sites

Ok, after many hours trying from U-boot and USB sticks, i managed to get to the Update menu. Then loaded the 24-1-2015 version and voila!!!! make it ALIVE again!!!!!!! I am not sure what exactly files i used but something was wrong with kernel & rfs... Now it seems ok, i only wish i could load the I12 for ESCAM QD series and play with it!!!

 

Also for anyone who is interested, i have FULL backed up the 5 partitions so now recovery is possible in ANY way, and also find a very easy way to replace the Logo Screen...

 

Just using the USB recovery stick in which we have also included a jpeg image 1024X768 (strict 256K!), and when it prompts for update we just telnet into the device and write the following:

 

# cd /mnt

# ls (to check that we are in usb file system, we should see the picture name)

#flashcp -v [image filename] /dev/mtd5

#reboot

 

and we remove the usb stick. After the reboot we see the new logo!... In case anyone needs the original i have backed up already.

Share this post


Link to post
Share on other sites

Mike Mahon, are you still visiting this forum?

I have read all 66 pages of this thread and to be honesty I'm impressed of M.M. work. I have done for my own over 500 lines of notes

Sad, there is a no "list" (even done by users) which cameras and disks are working ok with particular update/hardware. This hardware (I mean mini NVR v1) is a unexpensive and look so promising.

Personally I have NVR6200-8E and ESCAM QD900 wifi cameras (based on Hi3518 chip. I suppose this should work with I13- Hichip setup.

I have ordered few more ESCAM's - for test - QD520 and QD300.

 

Next: Back to issues with motion detection there was few tips done by M.M. and other persons. If you want to test definitely use WHOLE area (select all) - not selected regions only and try to remove all passwords (for tests). Next thing - access, menu and provilegs from web user and directly connected user (mean VGA/HDMI + mouse) are NOT same.

 

I'm not sure if this will help, but probability to have working motion detection is a higher.

 

Good luck lads, keep trying - and if you will found something - dont forget to say

Share this post


Link to post
Share on other sites
Mike Mahon, are you still visiting this forum?

I have read all 66 pages of this thread and to be honesty I'm impressed of M.M. work. I have done for my own over 500 lines of notes

Sad, there is a no "list" (even done by users) which cameras and disks are working ok with particular update/hardware. This hardware (I mean mini NVR v1) is a unexpensive and look so promising.

Personally I have NVR6200-8E and ESCAM QD900 wifi cameras (based on Hi3518 chip. I suppose this should work with I13- Hichip setup.

I have ordered few more ESCAM's - for test - QD520 and QD300.

 

Next: Back to issues with motion detection there was few tips done by M.M. and other persons. If you want to test definitely use WHOLE area (select all) - not selected regions only and try to remove all passwords (for tests). Next thing - access, menu and provilegs from web user and directly connected user (mean VGA/HDMI + mouse) are NOT same.

 

I'm not sure if this will help, but probability to have working motion detection is a higher.

 

Good luck lads, keep trying - and if you will found something - dont forget to say

 

Thanks for the info... I have never managed till now to make it work with I12 included in latest version and QD320 cameras!!... also trying to downgrade managed to brick it hard two times!!! But what do you mean by privileges from web and directly connected user?

 

Thanks

Share this post


Link to post
Share on other sites

You can connect to mini NVR directly (mouse connected to USB port and HDMI/VGA) and you can connect through IE/FF from your local LAN network. You will have NOT identical settings/access.

 

I got answer from escam about setting up their cams and miniNVR - will test this next week and come back with results to forum.

Share this post


Link to post
Share on other sites

Aha ok I got it. I will check if maybe from Vga it can connect with I12 protocol... Because according to escam it should work...

Share this post


Link to post
Share on other sites
Hi

I have a problem with a super mini nvr 4 CH N6200-4E , this nvr has a old firmware (20143011) so i have tried to upgrade with a newer (20150124) but during the upgrade nvr have freezed so now when i reboot the nvr show me only the boot image.....i downloaded in the download area (urcc store) the recovery file , puted in a pendrive but when i restart the nvr with pendrive connected on USB not appear the upgrade menu.....i have opened the nvr box and i can see that nvr have hi3515 chipset , the file for recovery is signed for 3520d , is this the problem that's do not boot in recovery? there is a recovery for N6200-4E with chipset 3515?

 

help me please

I have the same problem but with the N6100-16HE, which comes with the Hi3535 and the recovery file from URCTTV, is not recognized by the NVR. Can some one help with this issue or point us in the right direction? Regards, Angelo

Share this post


Link to post
Share on other sites

I spent too much time for the same reason... No one said anywhere that the usb stick should be formatted in specific way... Except from Fat16/32 it should be marked as boot active which I managed to do only from a Linux system

Share this post


Link to post
Share on other sites
I spent too much time for the same reason... No one said anywhere that the usb stick should be formatted in specific way... Except from Fat16/32 it should be marked as boot active which I managed to do only from a Linux system

But even after doing all that still won't work, at least for me.

Share this post


Link to post
Share on other sites
I spent too much time for the same reason... No one said anywhere that the usb stick should be formatted in specific way... Except from Fat16/32 it should be marked as boot active which I managed to do only from a Linux system

But even after doing all that still won't work, at least for me.

 

The fact that you see the logo picture (right?) means that bootloader is still there which is the one and only part needed for the CPU to boot. I bricked mine also at this stage and i thought it was impossible to recover... after that i attached a serial cable which if you have will tell you 100% the current state, and then i noticed that it didn't found the right partition from USB to boot... then i put the stick on a linux system, formated, made it active, and the voila... it was booting every time!!!.. although it took me several hours more to find the RIGHT image to load as the CPU has some kind of encryption keys to load the firmware which if it is not right it never loads...

Share this post


Link to post
Share on other sites
I spent too much time for the same reason... No one said anywhere that the usb stick should be formatted in specific way... Except from Fat16/32 it should be marked as boot active which I managed to do only from a Linux system

But even after doing all that still won't work, at least for me.

 

The fact that you see the logo picture (right?) means that bootloader is still there which is the one and only part needed for the CPU to boot. I bricked mine also at this stage and i thought it was impossible to recover... after that i attached a serial cable which if you have will tell you 100% the current state, and then i noticed that it didn't found the right partition from USB to boot... then i put the stick on a linux system, formated, made it active, and the voila... it was booting every time!!!.. although it took me several hours more to find the RIGHT image to load as the CPU has some kind of encryption keys to load the firmware which if it is not right it never loads...

Thanks a lot for your help! Yes, I see the logo picture. I got the usb formatted and recognized/booting. All I have to do now is to find the right image for my system. I don't think is going to be easy finding the correct image, I have spent hours looking for it to no avail. Regards Angelo

Share this post


Link to post
Share on other sites

Nice to hear that it boots... I think you are near to success... Yes now it's a matter to find the right binary file. Try to look for older firmware versions for your model...

Share this post


Link to post
Share on other sites
Nice to hear that it boots... I think you are near to success... Yes now it's a matter to find the right binary file. Try to look for older firmware versions for your model...

 

I dont think there is one available, the closest I have come is the file named rfs.yaffs.3535 that I got from a Russian site http://forum.videon.spb.ru/viewtopic.php?f=20&t=7815 of someone with the same problem and device, but the only place available for download is from a Chinese site and it won't let me get it.

Share this post


Link to post
Share on other sites
Nice to hear that it boots... I think you are near to success... Yes now it's a matter to find the right binary file. Try to look for older firmware versions for your model...

 

I dont think there is one available, the closest I have come is the file named rfs.yaffs.3535 that I got from a Russian site http://forum.videon.spb.ru/viewtopic.php?f=20&t=7815 of someone with the same problem and device, but the only place available for download is from a Chinese site and it won't let me get it.

Up and running! I was able to get the right recovery file and a newer firmware for the Hi3535 chipset the 015a_015c_3535_LG_1&2HDD.20150808.update From this site http://www.camseen.com/SUPPORT/Software/ it works good, the only problem is the boot screen is in Chinese but I can live with that.

Share this post


Link to post
Share on other sites

Hello All,

I appreciate all the reply on this thread, I would not have been able to get as far as I did without it. I hate to add more to this thread but I have searched most of it and cannot figure out what I am doing wrong. I can access the video flawlessly when at home. I can login remotely via a browser but I cannot get any live or recorded video to play (same computer, i doubt plugins are the issue.) Below are the ports that I have forwarded and a screenshot of the network configuration. I have seen some post that seem to allude to a remote port 35499 or something. I cannot find that anywhere in V4.0. Additionally I changed my ports around to make it harder to sniff out. Is that my issue? Must I use the default settings?

 

 

Derek L.

282407150_ScreenShot2015-12-08at12_36_02PM.png.c22f3312d797e7316706d0c68086470d.png

1231490113_ScreenShot2015-12-08at12_36_29PM.png.242ff88a98e2d3e43800e5f2f67be5ac.png

Share this post


Link to post
Share on other sites
Nice to hear that it boots... I think you are near to success... Yes now it's a matter to find the right binary file. Try to look for older firmware versions for your model...

 

I dont think there is one available, the closest I have come is the file named rfs.yaffs.3535 that I got from a Russian site http://forum.videon.spb.ru/viewtopic.php?f=20&t=7815 of someone with the same problem and device, but the only place available for download is from a Chinese site and it won't let me get it.

Up and running! I was able to get the right recovery file and a newer firmware for the Hi3535 chipset the 015a_015c_3535_LG_1&2HDD.20150808.update From this site http://www.camseen.com/SUPPORT/Software/ it works good, the only problem is the boot screen is in Chinese but I can live with that.

 

Nice work there!!!! Very glad to hear that as I also spent a lot of hours trying to make it alive too!!!.. If only Chinese products had better support!!!.. Now as for the logo it's a piece of cake if you like to change it... I am describing the procedure some posts before I have also backed up the default blue logo if you like. I wish I could find a solution for I12 protocol... as it seems to be a bug to the new versions.. but ESCAM support just sucks!!!.... too pitty as they work fine even on onvif...

Share this post


Link to post
Share on other sites

@Derek L. you need the following ports for the NVR to work out of home with or without the activeX plugin...

 

282122_1.png

 

** I am just changing the 80 port to listen to 8041 from out..

 

282122_2.png

Share this post


Link to post
Share on other sites
@Derek L. you need the following ports for the NVR to work out of home with or without the activeX plugin...

 

282122_1.png

 

** I am just changing the 80 port to listen to 8041 from out..

 

282122_2.png

 

 

I have copied your settings but I still do not get any video showing from a remote computer. the web GUI can be accessed but no video plays.

Share this post


Link to post
Share on other sites

Check for proper installation of rtsp plugin.. Maybe some settings doesn't allow it to run.. Check if enabled or reinstall... Mine works fine from Mozilla or IE on windows 8.1 and from goo link software on iOS

Share this post


Link to post
Share on other sites

i bought 2 mini nvr and 2 64gb usb sticks.. but usb sticks are not found by nvr. i really want to use them as motion detection drives

Share this post


Link to post
Share on other sites

 

Nice work there!!!! Very glad to hear that as I also spent a lot of hours trying to make it alive too!!!.. If only Chinese products had better support!!!.. Now as for the logo it's a piece of cake if you like to change it... I am describing the procedure some posts before I have also backed up the default blue logo if you like. I wish I could find a solution for I12 protocol... as it seems to be a bug to the new versions.. but ESCAM support just sucks!!!.... too pitty as they work fine even on onvif...

 

What firmware are you using on your NVR? The latest update (20150805 includes i12 by default) seems more stable (at least on i13 protocol) on my opinion. version

Share this post


Link to post
Share on other sites

Yes even the fact I am running latest version both on nvr and cameras i12 keeps logging wrong login password!! If I load some older versions on nvr i12 works... It was supposed to be built for cooperation of manufacturers!!! Escam support sucks... Too pitty as the cameras are very cheap and have nice pic...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×