Jump to content
reeves1985

Mini nvr questions

Recommended Posts

Hello Mike

 

I noticed that my Escam cameras work with motion detection using their own CMS 3.0 software.

Camera setting are below. I tried i12 with 34567 port and UDP/TCP transport - in both modes there is no movement detection :/ Any other idea? What is Dev.XM protocol compared to NVR protocols?

 

CMS user manual says:

Dev.XM: Old Hisilicon solution DVR/HVR/NVR,produced before June,2013.

 

 

Hi, i think this is a customized software version for ESCAM camera. Dev.XM is their own code but I think the "Dev. XM" means "it is origionally from XMeye company" so the protocol is i12.

Could you please also attach a picture of your motion detection recording configuration page in NVR system?

Share this post


Link to post
Share on other sites

Hi Mike,

 

I have a firmware that is very bad. Please, can you tell me if your firmware can be installed in my mini dvr?

 

I'm not using xvision, please I need help, because my firmware is the worst firmware in the world!!!

 

Also I can see a an Axis Camera..... I can undestand why??? For sure is onvif....

 

I need your help!!

 

Hi, This is the latest firmware version we have.

I am sorry I don't understand which part you meant this firmware is bad? What problem you met with this NVR?

 

Hi,

 

The problem is this version that I have, the webserver has the same skin than when you connect directly. At the begin, when was new, had other version, that was better than this one. Was HD-NETWORK skin.

 

Other thing is not possible to see an axis camera, its amazing...???? I'm using RSTP protocol to see it, but the only I can see is the recorded video..... why?????

 

Also, the view of the webserver si like the second image that I share, can you see anything?

 

I don't know what happend with my NVR. I'm sure is about my firmware, that is why I'm asking to update my NVR, at least with my first firmware.

 

Thanks all and please help me!!

HD-NETWORK.jpg.70bb6f3fb6af6f0c2d127116e48bab4a.jpg

3.JPG.76d1c6ee1851d177dd702762d50a2d2f.JPG

Share this post


Link to post
Share on other sites
Hello Mike

 

I noticed that my Escam cameras work with motion detection using their own CMS 3.0 software.

Camera setting are below. I tried i12 with 34567 port and UDP/TCP transport - in both modes there is no movement detection :/ Any other idea? What is Dev.XM protocol compared to NVR protocols?

 

CMS user manual says:

Dev.XM: Old Hisilicon solution DVR/HVR/NVR,produced before June,2013.

 

 

Hi, i think this is a customized software version for ESCAM camera. Dev.XM is their own code but I think the "Dev. XM" means "it is origionally from XMeye company" so the protocol is i12.

Could you please also attach a picture of your motion detection recording configuration page in NVR system?

 

The main problem is that this devices are not i12 compatible. If i chose i12 there is no video at all. ONVIF is the only working option :/ Without proper private protocol there is no way to use motion detection.

Share this post


Link to post
Share on other sites

Hi Mike,

 

I'm also having problems with motion detection and modifying camera settings from the NVR. It looks like the Onvif protocol in the camera's is compatible with the NVR.

 

I'm using the NVR with this camera's:

 

http://www.aliexpress.com/item/Support-Iphone-and-Andriod-3-7-mm-Korea-Pinhole-Lens-1920-1080-H-264-1080P-Micro/1859184041.html

 

and

 

http://www.aliexpress.com/item/2-8-12-mm-Varifocal-Lens-H-264-2-0-Megapixel-Waterproof-Vandalproof-Dome-1080P-2MP/1260729632.html

 

Here are screenshots of the firmware versions I'm currently using.

 

Ik hope you can help me.

236602123_Screenshot2014-10-20at09_20_02.png.1df54726333cba1902cb11945f93afe2.png

1449930717_Screenshot2014-10-20at14_02_20.png.20bbe88408ce37d9b57be1d237bf3b55.png

1110693104_Screenshot2014-10-20at13_59_04.png.ca4b107d6d4c8a8b987dee9fbf0a5fb5.png

Share this post


Link to post
Share on other sites

Has anyone gotten remote access with a pc to work? I have no problem accessing the system with a pc when I am on the same network. I assigned the device a port and forwarded that port (actually 2 ports) in my router. I do get a log in page when I am remote and I can log in but everything is very very slow and the cameras panes just show a black square no matter how long I wait. Not sure if I need to forward other ports or if I am going about this the wrong way.

 

I have the Escam labled 8 ch one, I had no problem getting my cameras to work and setting up the hd and the video is recording fine. I would just like to be able to log in and check on things thing while I am on the road.

Share this post


Link to post
Share on other sites

Hello to all...Newbie here.

I just got the latest Super Mini PVR which has 20140417? firmware...I'm hoping someone can help me...I went through all 19 pages but still having a heck of a time.

Of course this unit doesn't recognize ANY of my older IP cams...except ONE.

I DO get preview video, but it will not record for some reason. I can take a snapshot but no recording. The max res. for this cam is 740X480 or something...

Can anyone please tell me WHY it won't record or how to set it so it does? Is it because it will only record 720p and above...?

Also, does anyone know of a reletively non expensive PTZ camera that this unit will recognize?

Thanks in advance for your help.

Share this post


Link to post
Share on other sites

what models cameras will it not detect?

 

to setup recording have a look at this video, ignore the motion record bit just look how to get into the menu for setting up record:

 

 

you want to set it to schedule record fill the box with blue

Share this post


Link to post
Share on other sites
what is the latest firmware available?

 

The latest firmware is 20140417. Hopefully you are using this version.

We are developing the next version now and believe it will be ready before Christmas.

 

 

Hi

I have the Escam K108 with the 20140417 firmware. the PC client software that came with the unit is corrupt where can I find a good working copy. Tried IE(IE 11 &win7) but the unit does not always save the changes, having to repeat the same steps several time to get it to save.

what website to i check for firmware updates and guides/how too's

 

also having issues getting a Wanscam JW09 connected to my unit, any ideas

Share this post


Link to post
Share on other sites
what is the latest firmware available?

 

The latest firmware is 20140417. Hopefully you are using this version.

We are developing the next version now and believe it will be ready before Christmas.

 

 

Hi

I have the Escam K108 with the 20140417 firmware. the PC client software that came with the unit is corrupt where can I find a good working copy. Tried IE(IE 11 &win7) but the unit does not always save the changes, having to repeat the same steps several time to get it to save.

what website to i check for firmware updates and guides/how too's

 

also having issues getting a Wanscam JW09 connected to my unit, any ideas

 

PM me with you email and i will send you whole cd copy.

 

Mike is there any hope that this nvr will start to work under linux with FF or any other webbrowser?

Edited by Guest

Share this post


Link to post
Share on other sites

Hi again all.

No matter what I try, this will not start recording.

I get a preview picture but no matter what type of recording I try, it will not actually START the recording.

It shows the HDD being present and I am able to take a snapshot, but no recording.

Does anyone know if my cam resolution might not be compatible...? It is only 704X480......I have no idea, but I think it might be this.

Thanks.

Share this post


Link to post
Share on other sites

Today my NVR stopped to discover my HDD. Hdd is 100% ok, connected via external usb power supply and esata cable. After two weeks of flawess work BANG! No hdd at all.

 

HDD connected to win pc, and formated with surface test is OK!

Belowe dmesg from device.

 

Linux version 3.0.8 (root@sqy-desktop) (gcc version 4.4.1 (Hisilicon_v100(gcc4.4-290+uclibc_0.9.32.1+eabi+linuxpthread)) ) #68 Tue Apr 22 21:53:49 CST 2014
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
On node 0 totalpages: 37632
free_area_init_node: node 0, pgdat c03c9410, node_mem_map c0416000
 Normal zone: 294 pages used for memmap
 Normal zone: 0 pages reserved
 Normal zone: 37338 pages, LIFO batch:7
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
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: 144916k/144916k available, 5612k 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 - 0xc0023000   ( 108 kB)
     .text : 0xc0023000 - 0xc03ae000   (3628 kB)
     .data : 0xc03ae000 - 0xc03c9aa0   ( 111 kB)
      .bss : 0xc03c9ac4 - 0xc0415fa0   ( 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
libata version 3.00 loaded.
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
no ack
sha204_sn is 1
sha204_sn is 23
sha204_sn is 5a
sha204_sn is 85
sha204_sn is 92
sha204_sn is 7b
sha204_sn is 48
sha204_sn is bc
sha204_sn is ee
no ack
count is 255
no ack
no ack
no ack
no ack
no ack
no ack
encryption ok
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler deadline registered (default)
io scheduler cfq registered
brd: module loaded
loop: module loaded
ahci: SSS flag set, parallel bus scan disabled
ahci ahci.0: AHCI 0001.0200 32 slots 2 ports 3 Gbps 0x3 impl platform mode
ahci ahci.0: flags: ncq sntf stag pm led clo only pmp pio slum part ccc sxs boh
scsi0 : ahci_platform
scsi1 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x10080000-0x1008ffff] port 0x100 irq 52
ata2: SATA max UDMA/133 mmio [mem 0x10080000-0x1008ffff] port 0x180 irq 52
Spi id table Version 1.22
Hisilicon Spi Flash Controller V350 Device Driver, Version 1.10
Spi(cs1) ID: 0x01 0x02 0x19 0x4D 0x01 0x80
SPI FLASH start_up_mode is 3 Bytes
Spi(cs1):
Block:64KB
Chip:32MB
Name:"S25FL256S"
spi size: 0x33554432
chip num: 1
6 cmdlinepart partitions found on MTD device hi_sfc
Creating 6 MTD partitions on "hi_sfc":
0x000000000000-0x000000050000 : "uboot"
0x000000050000-0x0000001d0000 : "kernel"
0x0000001d0000-0x0000005d0000 : "rfs"
0x0000005d0000-0x000001f00000 : "app"
0x000001f00000-0x000001fc0000 : "config"
0x000001fc0000-0x000002000000 : "logo"
Fixed MDIO Bus: probed
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: both IDENTIFYs aborted, assuming NODEV
himii: probed
Invalid HW-MAC Address: 00:00:00:00:00:00
Set Random MAC address: 86:1F:F7:71:0C:65
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
hiusb-ehci hiusb-ehci.0: HIUSB EHCI
hiusb-ehci hiusb-ehci.0: new USB bus registered, assigned bus number 1
hiusb-ehci hiusb-ehci.0: irq 53, io mem 0x100b0000
hiusb-ehci hiusb-ehci.0: USB 0.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
hiusb-ohci hiusb-ohci.0: HIUSB OHCI
hiusb-ohci hiusb-ohci.0: new USB bus registered, assigned bus number 2
hiusb-ohci hiusb-ohci.0: irq 54, io mem 0x100a0000
ata2: SATA link down (SStatus 0 SControl 300)
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usbcore: registered new interface driver cdc_wdm
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
mousedev: PS/2 mouse device common for all mice
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP cubic registered
NET: Registered protocol family 17
802.1Q VLAN Support v1.8
Registering the dns_resolver key type
registered taskstats version 1
VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Freeing init memory: 108K
udevd (486): /proc/486/oom_adj is deprecated, please use /proc/486/oom_score_adj instead.
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01376c8c: 0x53a4 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01376c90: 0x10d2 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01376c94: 0x264c instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01376c98: 0xc96d instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01376c9c: 0xb208 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01376ca0: 0x9720 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01376ca4: 0x0f90 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01376ca8: 0xfb92 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01376cac: 0xb7e4 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01376cb0: 0x88c5 instead
Further such events for this erase block will not be printed
Hisilicon Media Memory Zone Manager
hi3520D_base: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
Hisilicon UMAP device driver interface: v3.00
load sys.ko for Hi3520D...OK!
Load tde.ko ...OK!
load venc.ko for Hi3520D...OK!
load group.ko for Hi3520D...OK!
load chnl.ko for Hi3520D...OK!
load h264e.ko for Hi3520D...OK!
load rc.ko for Hi3520D...OK!
load jpege.ko for Hi3520D...OK!
load viu.ko for Hi3520D...OK!
load vou.ko ....OK!
load vpss.ko ....OK!
load vda.ko ....OK!
load region.ko ....OK!
load vdec.ko ....OK
load vhd firmware.ko OK
load hdmi.ko ....OK!
Load jpeg6b.ko success.         (SDK_VERSION:[jpeg6bv1.0] Build Time:[Jul 30 2013, 17:13:35])
HISI_IRDA-MF @Hi3520Dv100R00
hiir: init ok. ver=Nov 26 2013, 15:14:13.
USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
rtusb init rt2870 --->
usbcore: registered new interface driver rt2870
PPP generic driver version 2.4.2
PHY: himii:03 - Link is Up - 100/Full
[GPIO] GPIOGET_WATCHDOG Enable chardata = 1!!!
PHY: himii:03 - Link is Up - 100/Full
#

Share this post


Link to post
Share on other sites
Hello,

 

I want to set the Email Settings (Config / Network Parameters / Email Settings)

but it doesn't work.

 

I want to define the "(send)SMTP Server:" but I always get the error message "(send)SMTP Server Input illegal!"

 

And where can I define user and password for SMTP server?

 

Thank you!

 

You are using Gmail?

Please send me a private message with your setting screen print.

 

Mike Mahon

maybe you can explain to us what is the different protocols i7, i8, i12, i13?

 

My unit from Escam has Onvif, i8, i9, RTSP, and i12, i have seen people listing others such as i13, i18, i16..... why aren't all of these protocols in ALL the units, instead of bits and pieces in various units.

 

can such cameras and the foscam and Wanscam ip cameras connect to this nvr?

Share this post


Link to post
Share on other sites
Hello,

 

I want to set the Email Settings (Config / Network Parameters / Email Settings)

but it doesn't work.

 

I want to define the "(send)SMTP Server:" but I always get the error message "(send)SMTP Server Input illegal!"

 

And where can I define user and password for SMTP server?

 

Thank you!

 

You are using Gmail?

Please send me a private message with your setting screen print.

 

Mike Mahon

maybe you can explain to us what is the different protocols i7, i8, i12, i13?

 

My unit from Escam has Onvif, i8, i9, RTSP, and i12, i have seen people listing others such as i13, i18, i16..... why aren't all of these protocols in ALL the units, instead of bits and pieces in various units.

 

can such cameras and the foscam and Wanscam ip cameras connect to this nvr?

 

Hi, Sorry for late reply.

have been busy those days, exhibition season, going everywhere for exhibitions.

Onvif is a standard protocol we use worldwidely, when the devices are with onvif protocol, they can work together. (not all function work well but most of it do)

the other I8,I9,I12,I36 etc protocols are private protocols we worked out with some original IP camera manufactures, like Dahua(I33), D-Link(I28) etc.

When those cameras are working with our NVR, we can upgrade the NVR to those protocols then cameras can work well with NVRs.

 

 

By the way, 20140804 firmware is ok for 4CH and 8CH mini NVR now.

Share this post


Link to post
Share on other sites

Hi!

 

Mike, which brand would you advise to order to be sure the Firmware you are providing will be compatible? Is there a brand which is "OEM" stock?

Share this post


Link to post
Share on other sites
i have that same camera, works fine with the mini nvr

 

Thank You Ghostrider for the quick reply, did it work with onvif or rtsp

Share this post


Link to post
Share on other sites
Hi Mike Mahon

is there firmware updates to add the individual protocols or batches of protocols,

 

(unsure of model) is this camera compatible with this unit http://www.ebay.com/itm/251688591071?_trksid=p2059210.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT

 

what website would we check for firmware updates

 

Only see a camera housing there, can not tell what chip board they are using so unable to make sure if they are compatible on Motion detection.

Anyway, it is an Onvif camera, you can use most of the function.

Due to flash memory limitation we are unable to upload all protocols into NVR. We need to know who is the original manufacturer of IPC(by checking their PC or IE software) then send protocol accordingly.

 

Always contact your NVR seller for firmware updates and always ask them if the motion detection works with the camera you have.

we have 20140804 now, you can PM your email then I can send, please tell me it is a 4ch or 8ch one, different update files.

Share this post


Link to post
Share on other sites
Hi!

 

Mike, which brand would you advise to order to be sure the Firmware you are providing will be compatible? Is there a brand which is "OEM" stock?

 

If it is a customized NVR (Customized Software, not just a logo printed), you need to contact seller for the latest update.

If it is a neutral NVR, all firmware is same. 20140417 etc.

Share this post


Link to post
Share on other sites
Hi again all.

No matter what I try, this will not start recording.

I get a preview picture but no matter what type of recording I try, it will not actually START the recording.

It shows the HDD being present and I am able to take a snapshot, but no recording.

Does anyone know if my cam resolution might not be compatible...? It is only 704X480......I have no idea, but I think it might be this.

Thanks.

 

PM me your teamviewer account and password, I will forward it to our tech team to check if they can help.

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

×