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

I got TOP-201 with a lens like this one (no IR-Cut filter, no IR night LEDs) installed inside premises, and have some strange image quality issues. During most of the day, when the premises are well lit with indirect sun light, and also in the evening, when they're half lit with electric lamps from inside, the IP Cam image is clear color of relatively good quality. But when the premises are lit with direct sun light from outside, the IP Cam image becomes almost black-n-white, mostly dark-to-black, with some white spots in brighter lit areas. Why this happens, and what camera image settings would deliver consistent quality image 24/7?

The IP Cam doesn't seem to have IR-Cut filter based on the board and seller's specs. But I opened the case, and found a small glass glued to the Board sensor. What is the purpose of this glass, if not IR-Cut? Can such image distortions be caused by lack of IR-Cut filter?

Another issue is, I can manually record video by pressing Record button in IE Control with latest ActiveX installed. But the Control doesn't record any video on Motion Detection, only pops up a log alert on screen, despite Record Channel and Snapshot are both selected in Video Motion settings tab, and of course the correct folder passes are set for videos and pictures, and the cam is added to Trusted Sites in IE. What settings did I miss?

And the IP Cam "can't connect to Gmail server" with all the right settings, so email notifications don't work, despite the latest firmware loaded General_HZXM_IPC_HI3518E_50H10L_S38_V4.02.R12.Nat.OnvifS.20160615_ALL. Can a user do anything to fix that? Some reported above, gmail alerts are working. May be it depends on the board model, since firmware for some boards may get a fixed Linux email module, and others don't?
 
Last edited:
With shaded areas and bright sunlight in the same shot, any cam with a limited dynamic range will show the same thing. It has to darken down the shaded areas enough that they're basically black when the bright areas aren't totally blown out. That's where a really wide dynamic range is useful. You might be able to help a bit by adjusting where the camera points, like mostly in the shaded area if that's usually most important, or in the bright area. That's a kludge to compensate for a poor camera though. Some cameras have regional exposure preferences so that it'll adjust exposure properly on the shaded side and ignore the sometimes too bright side. I doubt that toy does though.
 
How to change password of the rtsp stream rtsp://192.168.1.30:554/user=admin_password=xxxxxxx_channel=1_stream=0.sdp?real_stream
I tried with CMS and ONVIF Device Manager
rtsp is only way to watch video from wan, so to prevent unwanted watching I must change password
 
Based on your board FW version, it uses same CPU as TOP-201. Download and install current IE ActiveX Control as a program (don't install it from within IE), then start IE and login to the Cam WebUI (default 192.168.1.10), open DeviceCfg - Advanced - Account - Admin - Modify PW (default "empty"). The latest ActiveX couldn't capture stream for my cam board, so I installed an earlier 2015 version that works well. You might be able to do the same from CMS, I can't check since deleted it. Downloads should be available from your cam make website, as many China companies make similar to reference design boards in various feature configs, and looking at photos yours is the basic.
 
Last edited:
These password is only for entering into camera through Cam WebUI (which is the same as CMS).
Password in rtsp remain the same.

Is there any way to watch video from WAN on android tablet. Now I'm using VLC and rtsp link

It's possible, that password is unique and fixed, so I dont need to worry.
I get these link rtsp://192.168.1.30:554/user=admin_password=xxxpasswordxxx_channel=1_stream=0.sdp?real_stream in ONVIF Device Manager without entering password

I could send my link with pass to somebady tgrough DM
 
Last edited:
Passwords for WebUI and RTSP stream are the same. I can't view the cam RTSP stream in VLC with old or default password after changing IE WebUI password. Your cam may require a different ActiveX version, if it doesn't save ANY settings changed through IE to on-board ROM, but only saves ActiveX Control settings locally on your hard drive. You probably use open source Onvif Device Manager, since the factory DM doesn't show links like that.

Try vMEYE mobile app for Android.
 
Last edited:
Strange, ONVIF Device Manager work without entering new password and show old pass in rtsp link. At same time vlc require new password.
Thanks, now everything is OK.
Localy on Android I can get picture also with Onvifer
 
ONVIF DM might read previously cached data from your PC instead of the cam. Try updating firmware with it. ;) What do you mean under "locally on Android"? Can you view the stream on a smartphone over WAN - with what app?
 
sp9dlm said:
If anyone needs to have a soft gmail works and wifi !!!

General_MHKWIFI_IPC_HI3518E_50H10L_S38_RT3070_V4.02.R12.Nat.OnvifS.20160604_ALL.bin
Click to expand...

Hi sp9dlm

Not sure how you got this, but I suspect you are a skilled guy who unpacked both the 20160604 and 20150317 firmware files, copied over the rt3070.mod, and repacked it. Or someone like you.
In which case, great respect!

And also a humble request:

Can you add the 3070 modules also to this firmware file?

General_HZXM_IPC_GM8135S_QQ_50V10PL-S_V4.02.R12.Nat.OnvifS.QQ.20160407.bin
Its for the 17502 camera boards, which seem to suffer the same fate.

Link for sohu download
Currently entry 2 on page 3 of all latest firmwares of manufacturer
(the 6510 camera is currently entry 10 on page 4, but I am sure you have this already)

Warning to others: DO NOT TRY THIS LINKED FIRMWARE on a 6510 camera!!

Thanks

Edit: never mind: I binwalked, unzipped and scramfs-loop-mounted the firmware file, found the entire linux file structure, and no modules at all. Everything is compiled into the kernel, so its all or nothing when it comes to repacking.

I am also somewhat surprised it seemed to have scramfs rather then squashfs. Maybe despite the very similar UI, Sofia code and firmware naming, the 17502 is quite different from the 6510.
 
Last edited:
Good day everybody. Does anyone have information why not work ResetTool oat all types cameras with new firmware after 6/2016? At cameras with firmware before 6/2016 work at 100%. Thank you for help. Benny from Czechia
 
I never used the reset tool, so have no idea, but please be aware that the "Generic Device Manager" search and IP set tool for these Sofia camera's also has a device factory reset button.
 
Hi everybody.
I've just got a "TOP-201 IR" camera which seems faulty, don't know if the one I'm experiencing it's a known issue: maybe someone can help me to sort it out...

Let me explain: the camera body looks fine (although there are some scratches, maybe it was refurbished even if sold as new), when powered using an adapter^ it goes on fine (power led works). So far so good...
The trouble starts when I try connecting it to the router using an ethernet cable: the networking led of the camera starts blinking but it doesn't get recognized by the router (the cable isn't faulty because it works with other devices and the router's ethernet port led blinks too)^^; even after waiting a lot that led doesn't stop blinking.

I thought this may be a software issue so I disassembled the camera and managed to connect to the serial interface. The connection works fine, I've even managed to dump the romfs.cramfs filesystem image as explained here^^^.

Code: 
U-Boot 2010.06-svn (Oct 14 2015 - 15:07:23)

DRAM:  256 MiB
Check spi flash controller v350... Found
Spi(cs1) ID: 0xC2 0x20 0x17 0xC2 0x20 0x17
Spi(cs1): Block:64KB Chip:8MB Name:"MX25L6406E"
envcrc 0xadaa5f5e
ENV_SIZE = 0xfffc
In:    serial
Out:   serial
Err:   serial
Press Ctrl+C to stop autoboot
CFG_BOOT_ADDR:0x58040000
8192 KiB hi_sfc at 0:0 is now current device

### boot load complete: 1973968 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:    1973904 Bytes = 1.9 MiB
   Load Address: 80008000
   Entry Point:  80008000


load=0x80008000,_bss_end=80829828,image_end=801e9e90,boot_sp=807c7168
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Code: 
bootcmd=setenv setargs setenv bootargs ${bootargs};run setargs;fload;bootm 0x82000000
bootdelay=1
baudrate=115200
bootfile="uImage"
da=mw.b 0x82000000 ff 1000000;tftp 0x82000000 u-boot.bin.img;sf probe 0;flwrite
du=mw.b 0x82000000 ff 1000000;tftp 0x82000000 user-x.cramfs.img;sf probe 0;flwrite
dr=mw.b 0x82000000 ff 1000000;tftp 0x82000000 romfs-x.cramfs.img;sf probe 0;flwrite
dw=mw.b 0x82000000 ff 1000000;tftp 0x82000000 web-x.cramfs.img;sf probe 0;flwrite
dc=mw.b 0x82000000 ff 1000000;tftp 0x82000000 custom-x.cramfs.img;sf probe 0;flwrite
up=mw.b 0x82000000 ff 1000000;tftp 0x82000000 update.img;sf probe 0;flwrite
ua=mw.b 0x82000000 ff 1000000;tftp 0x82000000 upall_verify.img;sf probe 0;flwrite
tk=mw.b 0x82000000 ff 1000000;tftp 0x82000000 uImage; bootm 0x82000000
dd=mw.b 0x82000000 ff 1000000;tftp 0x82000000 mtd-x.jffs2.img;sf probe 0;flwrite
ipaddr=192.168.1.10
serverip=192.168.1.107
netmask=255.255.255.0
bootargs=mem=${osmem} console=ttyAMA0,115200 root=/dev/mtdblock1 rootfstype=cramfs mtdparts=hi_sfc:256K(boot),3520K(romfs),2560K(user),1280K(web),256K(custom),320K(mtd)
ethaddr=00:12:16:aa:xx:xx
HWID=8043420004048425
NID=0x0005
osmem=44M
appSystemLanguage=SimpChinese
appVideoStandard=PAL
stdin=serial
stdout=serial
stderr=serial
verify=n
ver=U-Boot 2010.06-svn (Oct 14 2015 - 15:07:23)

Environment size: 1308/65532 bytes

Does anybody know if there's a way to solve this issue?
In case I've left out important details do not hesitate to ask me, I'll provide you all information I can get...

Thanks in advance!

^ I've tested it: its output is 12.4 VDC, the declared amperage is: 1A (so it should be OK).
^^ I've also tried it against another router by a different brand (this time LAN only without Internet connectivity).
^^^ As the dump was done exploiting the ethernet connection I think it can be ruled out that this is an hardware defect.
 
Last edited:
Have you tried a telnet session to the (U-boot IP address at least, may get changed later) IP address of 192.168.1.10 ?
If you let U-boot boot the kernel, can you ping the camera at that address?
 
alastairstevenson said:
Have you tried a telnet session to the (U-boot IP address at least, may get changed later) IP address of 192.168.1.10 ?
Click to expand...
No, I'll try it now.

alastairstevenson said:
If you let U-boot boot the kernel, can you ping the camera at that address?
Click to expand...
I don't think that's possible: when I start the camera normally [no serial, 1) power adapter, 2) ethernet cable (connected to the router)] the device doesn't get recognized (it isn't listed in the connected clients sections of the router).
 
chorizo said:
No, I'll try it now.
Click to expand...
The camera replies to the ping requests.

chorizo said:
I don't think that's possible: when I start the camera normally [no serial, 1) power adapter, 2) ethernet cable (connected to the router)] the device doesn't get recognized (it isn't listed in the connected clients sections of the router).
Click to expand...
I was wrong: same as above (it replies to the ping requests).
 
Try reconfiguring the IP address with the device manager software that it would have come with. I have had at least one that was non responsive on any IP, and the device manager was able to assign it an IP and then I could get into its web UI and set it up. Without that there was nothing on the IP the box had, which was also what device manager found it at. Yes I had an IP on the PC in the same subnet before anyone suggests that ;)
 
  • Like
Reactions: alastairstevenson
richms said:
Try reconfiguring the IP address with the device manager software that it would have come with.
Click to expand...
You mean the one in the CD, right (General DeviceManage)?
The PC I'm testing from is in the same subnet of the ipcamera.

Anyway, I've just tried viewing the stream with ffmpeg:
Code: 
ffplay rtsp://192.168.1.10:554/user=admin_password=_channel=1_stream=0.sdp?real_stream
and it's indeed streaming (images are garbage, at the moment, because the camera is still disassembled and the sensor is apart from the lens).

Tomorrow I'll try following richms' advice to see if it improves the current behavior. Now, at least, it seems to be streaming... did anybody encounter the same issue?

Thanks everybody!
 
Possibly I am misinterpreting what I read here, especially as your serial link shows you are not a complete digi-noob. But it sounds as if the camera simply had a hardcoded IP and you expected it to have DHCP hence "it isn't listed in the connected clients sections of the router". More of a misunderstanding then an issue. If so, a bit of a pity you went as far as bared its guts.
 
You must log in or register to reply here.
Top Bottom