Jump to content

skoubri

Members
  • Content Count

    26
  • Joined

  • Last visited

Posts posted by skoubri


  1. Hi to all, as i am trying to get this thing work have two main problems... to make activeX work on windows 11 and to find a way to download recorded video...

     

    Also is it possible for anyone to send me the included free CMS software for N6200?

     

    Thanks in advance!!!


  2. Hi to all, does anyone know what happened to URCCTVSTORE? I have some mini nvrs which where never used and now i am looking for latest firmware updates and protocols and i cannot find anything!!!

     

    Please anyone who has N6200-8E and N6200-4E latest firmwares and I12 protocols, who is kind to share..

     

    thanks in advance!


  3. Hi Eddie.. For storage it's not a matter of speed it's a matter for read/write cycles... Usb sticks are not designed as ssd's or hard disks... This is why the restriction exists... Ports 505x are the streaming for each channel. Now as for resolution if reset to default settings it usually starts at low resolution visible to any monitor or TV. For USB storage power was not enough for me... So I ordered an esata cable and make a Y-split to the 5V adapter... Now my Hdd works rock solid and through a more "physical" interface esata... Thanks

     

    Could you please show a photograph of your ESATA connector?

     

    Sure! Here is from the disk side

    282384_1.jpg

    and here from the NVR..

    282384_2.jpg

     

    From NVR side it had a USB connector which was for power supply of the disk. I cut this cable and connected DIRECT to the output of 5V 2A dc adapter... Except that is rock solid stable, the disk is working extremely cool...

     

    Here is the cable approx. 3$ from ebay

    282384_3.jpg


  4. Hi Eddie.. For storage it's not a matter of speed it's a matter for read/write cycles... Usb sticks are not designed as ssd's or hard disks... This is why the restriction exists... Ports 505x are the streaming for each channel. Now as for resolution if reset to default settings it usually starts at low resolution visible to any monitor or TV. For USB storage power was not enough for me... So I ordered an esata cable and make a Y-split to the 5V adapter... Now my Hdd works rock solid and through a more "physical" interface esata... Thanks


  5. 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

    Unfortunately this is not possible. It is designed not to use USB sticks as storage for video. Only for firmware upload..


  6. After many hours of research and bricking two times my NVR I am concluding that despite the bad support of Escam, the problem is with NVR firmware!!!..

     

    And its very simple to conclude to this, when I load OLDER NVR firmware version (including older I12) protocol, I have picture... all this without changing ANYTHING on the cameras...!

     

    SO that means that something is changed on the latest I12/NVR firmware which Escam cameras don't like (QD series)...

     

    I hope that someone will read this (from urcctv) and maybe can have a solution...


  7. 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...


  8. 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...


  9. 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...


  10. 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


  11. 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.


  12. @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
    
    
    
    
    
    
    
    


  13. @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?


  14. Hi I have the 4ch miniNVR working fine with 4 QD320 escam cams. I was sent the latest version of cameras firmware and updated. BUT even that nvr detects them as I12 they work only as onvif. Is there any newer I12 version to load? I tested a very old version for nvr and I12 worked... but I want to run the latest which works fine... thanks in advance!


  15. For me now second day and motion seems to work fine... I think I found the right sequence... (until something is fixed?)... if I alter ANYTHING from NVR, I have to go to all cameras individually and confirm motion settings (just get in and save).. after this if I restart the nvr motion detection works fine as it was setup.

     

    As for the SMTP I face same problems here... while I test my provider's smtp server and send test emails with TELNET, if I put exact the same settings on NVR it doesn't pass the mail test....!

     

    Finally, when I connect externally, (from the office) I have opened all the needed ports and in No Active X mode works, but never managed to make it to work in ActiveX mode... no picture and if I try to get some videos (backup) I get nothing. I am running latest version of firmware.

     

    Also my mod about current flow from USB and also some passive cooling (on the main chip) made it rock solid... no more reboots and keep low temp (around 38deg)

     

    Thanks


  16. I'm not able to see any recorded video in the 'Playback Menu'. Can some of you suggest what I should do to check what is wrong about it?

    The problem is the same as described in many other messages in this thread: it is the motion detection recording that does not work.

     

    Has anyone found a solution?

     

    Thanks

    giorgio

    One of my cameras (maygion) also even it supports onvif there is no way to make motion detection to work... its a matter of protocol that communicate with IP camera.. actually the camera detects motion and NOT the nvr, so the camera gives the alarm to nvr to start recording IF the nvr can read this alarm through the used protocol...

×