Review - TOP-201 Super Mini 720P HD IP-Cam (The Cheapest IP Cam So Far !!)

Interesting model, HI3516C + IMX322 is a not bad, did you try teardown the camera ? you could simply pull off LED wire's connectors, that's what I do if firmware don't allow to turn IR off.

IR Led close to Lens attract flying bugs too much (one of the problem among others).
 
Interesting model, HI3516C + IMX322 is a not bad, did you try teardown the camera ? you could simply pull off LED wire's connectors, that's what I do if firmware don't allow to turn IR off.

IR Led close to Lens attract flying bugs too much (one of the problem among others).

Yes, I've already checked inside, power can be removed from IR, but I did not wanted to climb up to the roof :D
I'm interested about that how it can handle low light situations without IR, so I have to climb tonight. :D
 
Yes, I've already checked inside, power can be removed from IR, but I did not wanted to climb up to the roof :D
I'm interested about that how it can handle low light situations without IR, so I have to climb tonight. :D
According to tech spec on description's page CMOS is Sony IMX322 not bad, picture show F1.2 Lens so it is (should be) good too but why do you want to turn IR it off ? I mean by night your camera will see nothing or very noisy or ghosted movements but may be you have sreet lights that may help ?
 
Hi, has anybody ever tried mounting this camera on a tripod? My standard 1/4" tripod mount doesn't fit. I could widen the the hole in the camera bracket but I would rather not if there is some kind of an adaptor.
 
Hello everybody. The problem happened with the IP camera. I can not connect via CMS. He writes that "the user is blacklisted" I tried to reset the settings with Reset Config and DeviceManager, Onvif, but the camera did not connect.
The RTSP protocol using the VLC program, the camera image is clearly visible.
Is it possible to reset the camera to factory settings and how?
Help please, in advance, thankscamera.jpg User.jpg User .jpg
 
not sure what i'm doing wrong i have looked through this thread and still got something not quite right.
for the path i'm using rtsp://192.168.1.10:34567/user=admin_password=S994269s_channel=1_stream=0.sdp?real_stream
upload_2017-4-7_10-44-39.png
 
Yes, here RTSP protocol, it operates the camera.
But I can not connect the camera to the CMS program. He writes That "the user is Blacklisted" ?!
 
for the path i'm using rtsp://192.168.1.10:34567/user=admin_password=S994269s_channel=1_stream=0.sdp?real_stream

Just to be sure is it the correct parameters seperation characters your are using ? an underscore ? of course it is acceptable if the app behind the server knows how to split each parameter based on "_" (or doing some mod_rewrite for example) but usually it is a "&" that is used and a very first "?" to specify that everything that follow this question mark are parameters and not par of the url itself.
 
Dodutils thanks. for some reason my BI didn't like the default camera rtsp port of 34567 when i changed the camera port to the BI standard 554 it worked fine.
 
in my case I flashed back to the old firmware version (General_HZXM_IPC_HI3518E_50H10L_S38_V4.02.R12.20150910_ALL)
in attachment last stable firmware for this board. internally it's a zip archive, after downloading check the consistency.

about this firmware:
View attachment 16323

I have ipcam HI3518E_50H10L_S39, but problem with rtsp, can not stream, I tried some firmware but the result is same
i try firmware
- General_HZXM_IPC_HI3518E_50H10L_S38_V4.02.R12.20150910_ALL
- General_HZXM_IPC_HI3518E_50H10L_S38_V4.02.R12.Nat.OnvifS.20160304_ALL
- General_HZXM_IPC_HI3518E_50H10L_S38_V4.02.R12.Nat.OnvifS.20160615_ALL
 

Attachments

  • ScreenHunter_52 Apr. 30 03.52.jpg
    ScreenHunter_52 Apr. 30 03.52.jpg
    124.3 KB · Views: 56
  • ScreenHunter_53 Apr. 30 03.53.jpg
    ScreenHunter_53 Apr. 30 03.53.jpg
    135.1 KB · Views: 48
Last edited:
As alastairstevenson pointed out, you can mount (temporarily) NFS share to /tmp/nfs (I suggest NOT to mount on /tmp, as there may be open files in it)...

Thanks for this. I have a similar camera using the same firmware that I'm trying to get working and it got me a long way.

If you or (anyone else who knows) is still following this thread, I'm able to do everything up to the point of running various executables. I get an error related to "libcryp" and nothing happens from there. For example, if I try to run Sofia or various other non-system commands, the result will be:

libcryp:Open device file successful
[ERROR] libcryp : FILE -> crypto/crypto.c, LINE -> 131: CryptoRead failed,ret=1

So I'm guessing that something somewhere is corrupted.

Is there any way to recover short of TTY'ing to the board? I seem to have the same 3 connections on one of the boards so it's likely the same process.
 
Hello, IP cam users and experts!
I have two TOP-201 cameras and unfortunately one of them stopped working. It is not bricked, as a can ping it, but no video is streamed. I guess this forum thread contained some instructions on recovering firmware via a serial connection. I think this would be a solution for me! But all the links are dead, and I guess some forum posts were deleted. Could anyone please provide instructions, firmware images and maybe tools for recovering TOP-201 cameras. Any help would be really appreciated. Thanks.
 
Hello, IP cam users and experts!
I have two TOP-201 cameras and unfortunately one of them stopped working. It is not bricked, as a can ping it, but no video is streamed.
Can you at least telnet into it and if yes do you see any error in syslog ?
 
I can get this far but can't get it to break using Ctrl-C. Doesn't seem to be recognizing my keystrokes. I see no echo from any typing. Are there some specific keyboard or other settings that need to be used? Using putty as a terminal.

U-Boot 2010.06-svn (Mar 27 2014 - 10:49:35)

DRAM: 256 MiB
Check spi flash controller v350... Found
Spi(cs1) ID: 0xEF 0x40 0x18 0x00 0x00 0x00
Spi(cs1): Block:64KB Chip:16MB Name:"W25Q128B"
envcrc 0x868bd8ed
ENV_SIZE = 0x3fffc
In: serial
Out: serial
Err: serial
Press Ctrl+C to stop autoboot
CFG_BOOT_ADDR:0x58080000
16384 KiB hi_sfc at 0:0 is now current device

### boot load complete: 2306360 bytes loaded to 0x82000000
### SAVE TO 80008000 !
## Booting kernel from Legacy Image at 82000000 ...
Image Name: linux
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2306296 Bytes = 2.2 MiB
Load Address: 80008000
Entry Point: 80008000


load=0x80008000,_bss_end=808293d8,image_end=8023b0f8,boot_sp=807971d8
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
 
I can get this far but can't get it to break using Ctrl-C. Doesn't seem to be recognizing my keystrokes. I see no echo from any typing. Are there some specific keyboard or other settings that need to be used? Using putty as a terminal.
Had same problem with other camera's model but it was my TX that was not correctly connected but it was a non soldered I had to use some trick because pinholes were not fully accessible
 
Had same problem with other camera's model but it was my TX that was not correctly connected but it was a non soldered I had to use some trick because pinholes were not fully accessible

Thanks. Yeah, this one is very tight too. I just tacked things quickly. I'll have to try to see if I can get better solder connects and try it again.

So close! ; )
 
OK, I have a working serial connection now and can acesss the hisilicon prompt. I have what I think is the correct .bin file for my camera (any way to double check this?). I have and know how to run the tftp server. I know how to launch tftp on the camera. Where do I go from here?

Do I need to figure out the offsets in memory for the various mount points or is there an easier way to pull in the .bin as a whole?
 
Can you at least telnet into it and if yes do you see any error in syslog ?
Yes, I can telnet into it, but there is no /var/log directory. The firmware is General_HZXM_IPC_HI3518E_50H10L_S38_V4.02.R12.20140926_ALL.bin (it came on the CD).