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

[????????? ?????????]

1. Your FTP issue seems to be accepting your FTP login from the camera but not allowing a new folder/directory to be created where any new snapshots will reside received via FTP. Which of course then would cause no snapshots to be sent via FTP. Since these snapshots sent via FTP would need to reside in a folder that is currently being denied from being created by your FTP server. Example:

Sat May 9 18:40:00 2015 [pid 30086] [ftp] OK LOGIN: Client "192.168.0.110"
Sat May 9 18:40:02 2015 [pid 30090] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3"
Sat May 9 18:40:03 2015 [pid 30090] [ftp] FAIL MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09"

Because of this. You may wish to check the FTP User rights for the FTP User you are using and also for the Group/User that owns the top level folder where the new folder is trying to be created under and failing, by this FTP user.

2. Does your Email provider require SSL? If so. Please try checking the "Need SSL" checkbox and then clicking the "ok" button and try again.

Don

Hello Don!

Please find my response below:
1. Take a look at the beginning of the log:
Sat May 9 18:39:50 2015 [pid 30077] CONNECT: Client "192.168.0.110"
Sat May 9 18:39:51 2015 [pid 30076] [ftp] OK LOGIN: Client "192.168.0.110"
Sat May 9 18:39:53 2015 [pid 30080] [ftp] OK MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3"
Sat May 9 18:39:54 2015 [pid 30080] [ftp] OK MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09"
Sat May 9 18:39:55 2015 [pid 30080] [ftp] OK MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09/01"
Sat May 9 18:39:56 2015 [pid 30080] [ftp] OK MKDIR: Client "192.168.0.110", "/volume1/EMule/Cam/192.168.0.110_0012129310f3/2015-05-09/01/pic"

Initially at the first login it creates these dirs. But not to upload there anything. Later it tries to make the same dirs again.

2. As to e-mail - the provider doesn't require to use SSL. This is a special pure SMTP server that is designed especially for such devices.
Here is a sniplet from Yandex help:
Configure MFP or scanner as follows:

Specify the following SMTP:
Server - smtp-devices.yandex.ru
Port - 25
Including authentication (authentication).
Specify in the fields your username and password.
Caution Be sure to enter your username and password manually. If you choose the authentication similar to the incoming mail server, sending will not operate.

Limitation. Send letters so you can address only served Yandex.Mail (domain yandex.ru addresses or mail for domains). On the other boxes the postal services sent by the server will not receive any.

 

[????????? ?????????]

While I thought it was possible that the same folders were trying to be re-created. What I find odd at best is that if those folders are in fact already present in those locations. Then where are the failed snapshot image creation attempts in your server logs? Like the failed folder creation attempts, in your server logs.

Which still leads me to believe in your case. That at the moment, you have a folder/file FTP user security issue. That's not allowing you to write the snapshot images. I say this because your logs are showing that the camera is successfully logging into your FTP server yet failing on folder/file creation.

In other words. Do those folders allow read/write and file creation by the FTP user you are logging in with? If not, then you are dealing with FTP folder/file security and will need to rectify that or change FTP users so that the FTP user is allowed to write/read and create files in those folders.

For your Email issue. I would contact your Email provider Yandex and ask them to trace your email attempts from the camera so they can tell you where they see things failing. Since you are saying that this is not a SSL issue.

Don

Hi Don!

1. I also thought about permission errors so spent half of the day trying to solve that. With no success. From my side it looks like the FTP user can upload files at FTP serever. See the log from Windows FTP-client (it is a little bit long because I had to drill through these tricky folders names):
C:\Users\Владислав\AppData\Local\Far Manager x64>ftp j1800
Connected to j1800.KVVDACHA.
220 (vsFTPd 3.0.2)
User (j1800.KVVDACHAnone)): ftp
331 Please specify the password.
Password:
230 Login successful.
ftp> ls -l
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
drwxrwxrwx 3 114 0 4096 May 09 18:49 192.168.0.110_0012129310f3
226 Directory send OK.
ftp: 87 bytes received in 0.00Seconds 29.00Kbytes/sec.
ftp> cd 192.168.0.110_0012129310f3
250 Directory successfully changed.
ftp> ls -l
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
drwxrwxrwx 3 114 0 4096 May 09 18:49 2015-05-09
226 Directory send OK.
ftp: 71 bytes received in 0.00Seconds 23.67Kbytes/sec.
ftp> cd 2015-05-09
250 Directory successfully changed.
ftp> ls -l
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
drwxrwxrwx 3 114 0 4096 May 09 18:49 01
226 Directory send OK.
ftp: 63 bytes received in 0.00Seconds 31.50Kbytes/sec.
ftp> cd 01
250 Directory successfully changed.
ftp> ls -l
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
drwxrwxrwx 2 114 0 4096 May 09 18:49 pic
226 Directory send OK.
ftp: 64 bytes received in 0.00Seconds 32.00Kbytes/sec.
ftp> cd pic
250 Directory successfully changed.
ftp> put z:\aaa.txt fff.txt
200 PORT command successful. Consider using PASV.
150 Ok to send data.
226 Transfer complete.
ftp: 3 bytes sent in 0.00Seconds 3.00Kbytes/sec.
ftp>

So I managed to upload a file to the server. If I understand you in the right way that is exactly the same you mention under "create a file".

2. As to E-Mail. It is pitty - I can't see the log from the camera side or sniff its traffic.

 

[????????? ?????????]

Did you setup your FTP configuration for the camera as shown here:

http://www.ipcamtalk.com/showthread...P-Cam-So-Far-!!)?p=28481&viewfull=1#post28481

If so as a test, can you try using a higher level FTP user that would not encounter any folder/file security issues in the cameras FTP configuration?

Don

The config for the FTP is below:

I also tried to use different user that is myself as FTP user for the camera. It seems that the result is the same.

 

[lojix]

@????????? ?????????

As mentioned, the account used to login to the server needs to have the permission to the folders. A good starting point is to give all users full access to the folders, and eliminate access permissions from there.

sudo chmod -R 777 /var/www

Next, check that any form of FTP write command is enabled.
Open the vsftpd.conf file ..(eg. /etc/vsftpd.conf).

sudo nano /etc/vsftpd.conf

Check for the following in the .conf file:

# Uncomment this to enable any form of FTP write command.
#write_enable=YES

Uncomment the line write_enable=YES as directed...

Restart your FTP daemon:

service vsftpd restart

...and hopefully it's working as expected.

 

[????????? ?????????]

Not sure what to say about your FTP situation. If you review your detailed FTP log located here and shown below/ You can see that your FTP server is not allowing the camera to change folders to /192.168.0.110_0012129310f3/2015-05-09/01/pic where the snapshots would reside if they could.

Which lead me to believe as stated in my prior posts here that there is a FTP security issue not allowing that folder to be created or accessed by the FTP user(s) which you have tried to access them with. Since you can tell that your FTP login is taking place the login is not failing:

http://www.ipcamtalk.com/showthread...P-Cam-So-Far-!!)?p=30025&viewfull=1#post30025

Sat May 9 19:04:34 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "CWD /volume1/EMule/Cam"
Sat May 9 19:04:34 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "250 Directory successfully changed."
Sat May 9 19:04:34 2015 [pid 31589] [ftp] FTP command: Client "192.168.0.110", "CWD /192.168.0.110_0012129310f3/2015-05-09/01/pic"
Sat May 9 19:04:34 2015 [pid 31589] [ftp] FTP response: Client "192.168.0.110", "550 Failed to change directory."

So. If that/those directories are/were really there? Then why is your FTP user not being allowed to go to them?

I would check ("All") the folders you say are already created and make sure they are in fact present. I would check each and every folders Group/Owner and their security settings as well and see if the FTP user(s) you have used have the folder/security to delete/add folders and files under each one of them as well. Because there is something currently wrong with your folder/file security and the user rights your FTP user(s) have to access and delete and add to them.

Don

Hello Don,

I've check the issue with changing the dir from the camera via FTP connection. From my point of view it is connected with CWD command. See the log below from Windows FTP-client:
Z:\Soft>ftp j1800
Connected to j1800.KVVDACHA.
220 (vsFTPd 3.0.2)
User (j1800.KVVDACHAnone)): ftp
331 Please specify the password.
Password:
230 Login successful.
ftp> ls -l
200 PORT command successful. Consider using PASV.
150 Here comes the directory listing.
drwxrwxrwx 4 114 0 4096 May 10 00:06 192.168.0.110_0012129310f3
226 Directory send OK.
ftp: 87 bytes received in 0.00Seconds 29.00Kbytes/sec.
ftp> cwd 192.168.0.110_0012129310f3
Invalid command.
ftp> cd 192.168.0.110_0012129310f3
250 Directory successfully changed.


As I understand CWD command is invoked when a active directory is changed for the user. And FTP server doesn't understand this command. I've just checked the same situation with Unix-based commercial hoster FTP service. It also disallow to change active directory via CWD command (but it allows me to do that with ordinary CD command) - returned error that CWD is not a Unix-like command.

Here is more:
ftp> help
Commands may be abbreviated. Commands are:

! delete literal prompt send
? debug ls put status
append dir mdelete pwd trace
ascii disconnect mdir quit type
bell get mget quote user
binary glob mkdir recv verbose
bye hash mls remotehelp
cd help mput rename
close lcd open rmdir

CWD command is missing

But this command works:
ftp> quote cwd 2015-05-09
250 Directory successfully changed.

So I think the problem is in the camera firmware that uses CWD (that works well with some of Windows FTP-servers) and doesn't work with vsftpd and proftpd servers... And it seems that we can't do anything here :-/

I was thinking about the permissions to the fresh created dirs. So I used local_umask=000 in vsftpd.conf in order to get accessed to everyone permissions. So as you can see in the log there is drwxrwxrwx permission for the dir.

 

[????????? ?????????]

@????????? ?????????

As mentioned, the account used to login to the server needs to have the permission to the folders. A good starting point is to give all users full access to the folders, and eliminate access permissions from there.

sudo chmod -R 777 /var/www

Already done via umask in vsftpd.conf

Next, check that any form of FTP write command is enabled.
Open the vsftpd.conf file ..(eg. /etc/vsftpd.conf).

sudo nano /etc/vsftpd.conf

Check for the following in the .conf file:

# Uncomment this to enable any form of FTP write command.
#write_enable=YES

Was done before

Uncomment the line write_enable=YES as directed...

Restart your FTP daemon:

service vsftpd restart

...and hopefully it's working as expected.

sudo chmod -R 777 /var/www

Already done via umask in vsftpd.conf

# Uncomment this to enable any form of FTP write command.
#write_enable=YES

Was done before

No result due to CWD instead of CD issue.

 

[????????? ?????????]

Here are example log entries from my vsftpd logs when I tested the instructions on how to send snapshots on motion detection alarms for Email and FTP for this series of mini IP Cameras from this manufacturer. Which I posted at the link below. After first testing the instructions, using a Ubuntu 14.04.2 LTS (GNU/Linux 3.8.0-29-generic i686) DigitalOcean VPS cloud server:

http://www.ipcamtalk.com/showthread...P-Cam-So-Far-!!)?p=28481&viewfull=1#post28481

Thu Apr 30 05:27:51 2015 [pid 17870] CONNECT: Client  "**.**.**.**"
Thu Apr 30 05:27:52 2015 [pid 17869] OK LOGIN: Client "**.**.**.**"
Thu Apr 30 05:27:54 2015 [pid 17873] FAIL MKDIR:  Client "**.**.**.**", "/foscam"
Thu Apr 30 05:27:55 2015 [pid 17873] FAIL MKDIR:  Client "**.**.**.**", "/foscam/192.168.1.10_11111111111d"
Thu Apr 30 05:27:56 2015 [pid 17873]   OK MKDIR:  Client "**.**.**.**", "/foscam/192.168.1.10_11111111111d/2015-04-30"
Thu Apr 30 05:27:57 2015 [pid 17873]   OK MKDIR:  Client "**.**.**.**", "/foscam/192.168.1.10_11111111111d/2015-04-30/01"
Thu Apr 30 05:27:59 2015 [pid 17873]   OK MKDIR:  Client "**.**.**.**", "/foscam/192.168.1.10_11111111111d/2015-04-30/01/pic"
Thu Apr 30 05:28:04 2015 [pid 17873]   OK UPLOAD: Client "**.**.**.**", "/foscam/192.168.1.10_11111111111d/2015-04-30/01/pic/042744-2704.jpg", 62985 bytes, 80.30Kbyte/sec

Thu Apr 30 06:55:41 2015 [pid 18413] CONNECT: Client  "**.**.**.**"
Thu Apr 30 06:55:43 2015 [pid 18411] OK LOGIN: Client "**.**.**.**"
Thu Apr 30 06:55:47 2015 [pid 18415]   OK UPLOAD: Client "**.**.**.**", "/foscam/192.168.1.10_11111111111d/2015-04-30/01/pic/0555355629.jpg", 63970 bytes, 84.60Kbyte/sec
Thu Apr 30 06:55:52 2015 [pid 18415]   OK UPLOAD: Client "**.**.**.**", "/foscam/192.168.1.10_11111111111d/2015-04-30/01/pic/0555394790.jpg", 70045 bytes, 91.80Kbyte/sec

Don

There can be a difference in the firmwares at our cameras.

Here is something more that can help in understanding the problem with CWD command. Here is set-up of the ftp user that logins to FTP-server:

So the folders three looks like the following:
/volume1/EMule/Cams <- here is the main dir for ftp user and here it should create some folders and upload pictures. Actually all the folders are created here:

I reviewed vsftpd log once more and found something interesting:

First of all - mkdir fails sometimes - it is OK because these folders already created. Then when camera tries to change directory through CWD sometimes it works sometimes doesn't. It works when it uses CWD to change dir without the full path. And it doesn't work when it uses the full path for CWD.

 

[????????? ?????????]

If you can't find this similar ("11111111111 would be different for your camera") directory ("Ending with the pic folder") for a specific day of your testing on your FTP server. Example:

/192.168.0.110_111111111113/2015-05-09/01/pic

Then I stand by my original statement. That for whatever reasons. You are having some security issues with the folders and files you are trying to add/delete/create/go to with the FTP User Id that you are trying to use. Because working with your theory that sometimes this or that is failing would mean that the pic directory for a specific day during your testing is present. Because creating that directory ("You say") is not always failing. Which means that it should be present at some point during testing for any given day.

Secondly. Using some other FTP client besides the FTP client in this mini IP Camera might be giving you false results because it's not doing exactly as the FTP client which is being used in the mini IP Camera is.

Last but not least. If you truly believe or accept that a difference in your mini IP Cameras firmware could be the cause of your mini IP Camera experiencing these FTP issues. Why not upgrade to the most current firmware for your version of this mini IP Camera series if needed. By checking what the most current firmware for your mini IP Camera is in the table linked to here:

http://www.ipcamtalk.com/showthread...P-Cam-So-Far-!!)?p=19499&viewfull=1#post19499

Don

Hi Don,

As I wrote before - camera creates all the folders if they are not there. And I can see all the folders it creates. But later it instead of uploading pictures just starts to recreate the same folders that leads to the Error state. And it also tries to change the folders with a not supported command CWD (instead of supported CD). That causes errors depending on the command arguments. Sometimes it works sometimes it doesn't. Anyway in ftp log file I don't see any attempts for picture uploads (at all). I'm not sure that cam firmware analyzes FTP server responses (that will be too sophisticated behavior).

I can't imagine more rights than 777 + ftp user is added to root group and btsync group (the owner group for the folder three).

The cam has the latest firmware available (I believe):

 

[????????? ?????????]

I still feel that you have some security issue here. Because my logs for my mini IP Camera. Which is the same version as yours, using the same firmware as yours and using the same vsftpd FTP server program as yours. Don't show repetitive attempts to create folders that are already present once found and my logs don't show CWD commands being used as well. My logs:

http://www.ipcamtalk.com/showthread...P-Cam-So-Far-!!)?p=30058&viewfull=1#post30058

You could try to reset this mini IP Camera using the reset utility you can find at the link below if you wish to see if that makes any difference. At least it would reset your mini IP Camera to factory defaults:

http://www.ipcamtalk.com/showthread...P-Cam-So-Far-!!)?p=19499&viewfull=1#post19499

At this stage. I can only suggest that you contact your seller to see how they say to proceed since you don't want to try the suggested tests in my prior post here.

Maybe your seller will replace your mini IP Camera?

All I can say is that I have the same version of this mini IP Camera which is using and on the same firmware version. I also am and have been using vsftpd, with no issues with this same mini IP Camera with sending snapshots during motion detection via FTP.

Don

Hello Don,

2. I've managed to solve the issue with e-mail sending. The problem was in wrong DNS servers. They were from the old provider and couldn't resolve the mnemonic address of the mail servers at yandex. That was the reason.
1. I created a new user 'test' for checking the problem with the access rights. I didn't switch the access path for this user. So when I login with it I get directly to its home directory. But the behavior is the same. Camera creates necessary dirs but no files in the them.

The only thing to do is to run vsftpd with root credentials (to date it is run under vsftpd user). But I don't have an idea how to change the user to run the service.

I was wrong - it is already under root.

PS. Returning the camera back to the seller is not a good idea. It works perfect with the provided CMS. And with Windows FTP as well.

 

[????????? ?????????]

Checked it with FileZilla FTP server under Windows - it works:
(000029)10.05.2015 17:05:09 - test (192.168.0.110)> PWD
(000029)10.05.2015 17:05:09 - test (192.168.0.110)> 257 "/" is current directory.
(000029)10.05.2015 17:05:10 - test (192.168.0.110)> CWD /
(000029)10.05.2015 17:05:10 - test (192.168.0.110)> 250 CWD successful. "/" is current directory.
(000029)10.05.2015 17:05:10 - test (192.168.0.110)> CWD /192.168.0.110_0012129310f3/2015-05-10/01/pic
(000029)10.05.2015 17:05:10 - test (192.168.0.110)> 550 CWD failed. "/192.168.0.110_0012129310f3/2015-05-10/01/pic": directory not found.
(000029)10.05.2015 17:05:11 - test (192.168.0.110)> MKD 192.168.0.110_0012129310f3
(000029)10.05.2015 17:05:11 - test (192.168.0.110)> 257 "/192.168.0.110_0012129310f3" created successfully
(000029)10.05.2015 17:05:11 - test (192.168.0.110)> CWD 192.168.0.110_0012129310f3
(000029)10.05.2015 17:05:11 - test (192.168.0.110)> 250 CWD successful. "/192.168.0.110_0012129310f3" is current directory.
(000029)10.05.2015 17:05:12 - test (192.168.0.110)> MKD 2015-05-10
(000029)10.05.2015 17:05:12 - test (192.168.0.110)> 257 "/192.168.0.110_0012129310f3/2015-05-10" created successfully
(000029)10.05.2015 17:05:12 - test (192.168.0.110)> CWD 2015-05-10
(000029)10.05.2015 17:05:12 - test (192.168.0.110)> 250 CWD successful. "/192.168.0.110_0012129310f3/2015-05-10" is current directory.
(000029)10.05.2015 17:05:13 - test (192.168.0.110)> MKD 01
(000029)10.05.2015 17:05:13 - test (192.168.0.110)> 257 "/192.168.0.110_0012129310f3/2015-05-10/01" created successfully
(000029)10.05.2015 17:05:14 - test (192.168.0.110)> CWD 01
(000029)10.05.2015 17:05:14 - test (192.168.0.110)> 250 CWD successful. "/192.168.0.110_0012129310f3/2015-05-10/01" is current directory.
(000029)10.05.2015 17:05:14 - test (192.168.0.110)> MKD pic
(000029)10.05.2015 17:05:14 - test (192.168.0.110)> 257 "/192.168.0.110_0012129310f3/2015-05-10/01/pic" created successfully
(000029)10.05.2015 17:05:15 - test (192.168.0.110)> CWD ..
(000029)10.05.2015 17:05:15 - test (192.168.0.110)> 250 CWD successful. "/192.168.0.110_0012129310f3/2015-05-10" is current directory.
(000029)10.05.2015 17:05:15 - test (192.168.0.110)> CWD ..
(000029)10.05.2015 17:05:15 - test (192.168.0.110)> 250 CWD successful. "/192.168.0.110_0012129310f3" is current directory.
(000029)10.05.2015 17:05:16 - test (192.168.0.110)> CWD ..
(000029)10.05.2015 17:05:16 - test (192.168.0.110)> 250 CWD successful. "/" is current directory.
(000029)10.05.2015 17:05:16 - test (192.168.0.110)> CWD /192.168.0.110_0012129310f3/2015-05-10/01/pic
(000029)10.05.2015 17:05:16 - test (192.168.0.110)> 250 CWD successful. "/192.168.0.110_0012129310f3/2015-05-10/01/pic" is current directory.
(000029)10.05.2015 17:05:17 - test (192.168.0.110)> size 170517-9930.jpg
(000029)10.05.2015 17:05:17 - test (192.168.0.110)> 550 File not found
(000029)10.05.2015 17:05:17 - test (192.168.0.110)> TYPE I
(000029)10.05.2015 17:05:17 - test (192.168.0.110)> 200 Type set to I
(000029)10.05.2015 17:05:18 - test (192.168.0.110)> PASV
(000029)10.05.2015 17:05:18 - test (192.168.0.110)> 227 Entering Passive Mode (192,168,0,18,236,210)
(000029)10.05.2015 17:05:19 - test (192.168.0.110)> appe 170517-9930.jpg
(000029)10.05.2015 17:05:19 - test (192.168.0.110)> 150 Opening data channel for file upload to server of "/192.168.0.110_0012129310f3/2015-05-10/01/pic/170517-9930.jpg"
(000029)10.05.2015 17:05:19 - test (192.168.0.110)> 226 Successfully transferred "/192.168.0.110_0012129310f3/2015-05-10/01/pic/170517-9930.jpg"
(000029)10.05.2015 17:05:20 - test (192.168.0.110)> QUIT
(000029)10.05.2015 17:05:20 - test (192.168.0.110)> 221 Goodbye

Then drop the camera to default condition via its interface.

 

[????????? ?????????]

One more attempt:

Clean installation of Ubuntu 14.02 LTS x32 to a virtual machine. Clean installation of vsftpd. Sole user, no directory redirects. write_enable=yes. The user is parked to its home dir. The same situation - the folders are created no pictures inside

 

[????????? ?????????]

And one more attempt:

Another clean installation of Ubuntu 14.02. LTS x32 to a virtual machine. Clean installation of proftpd-basic. Sole user, no directory redirects. The user is parked to its home dir. The same situation - the folders are created but no pictures uploaded. But the log is a little bit different from vsftpd.

I'm completely lost

 

[????????? ?????????]

And a final attempt.

Clean installation of Linux Mint x32. Clean installation of vsftpd. write_enable=on. Single user. Default path to the home dir.

Absolutley the same. Dirs are created but no files uploaded.

 

[lojix]

Note: Personally. I don't agree with allowing all users on a server or all FTP users on a server, being given full access to a servers www area via FTP. Way too risky IMHO to go that far.

Neither do I... But it would be 'blanket' starting point to determine if permissions issues were in the mix. Then eliminate and tighten back up the security.

Cheers!

 

[cogtx]

I purchased this model on amazon a few months back hoping to use it outside with an external IR lighting. However, it appears to not have the IR capabilities. Does the camera have an IR filter that needs to be removed or is it a software issue? Any solutions or feedback would be appreciated..thanks

 

[ruppmeister]

I purchased one of these off of Amazon also and I found that this camera is capable of "seeing" the IR spectrum, but mine needed a different lens to do so (the lens mine shipped with has the IR filter on the back of the lens (purplish looking film)). The big problem with this was the color during the day is WAY off because there is IR cut filter. This might be something acceptable to you, but it wasn't to me. I ended up putting the camera in a location that I was only looking for daytime recording.

 

[cogtx]

I purchased one of these off of Amazon also and I found that this camera is capable of "seeing" the IR spectrum, but mine needed a different lens to do so (the lens mine shipped with has the IR filter on the back of the lens (purplish looking film)). The big problem with this was the color during the day is WAY off because there is IR cut filter. This might be something acceptable to you, but it wasn't to me. I ended up putting the camera in a location that I was only looking for daytime recording.

Thanks for the quick reply....I removed the original 3.6mm lens and installed a 2.8mm(?) for better FOV and works well in daytime...still have no night vision from IR. Can I remove the IR filter on the lens to get the IR function?

 

[ruppmeister]

I have not removed the IR filter from a lens before, and in some cases I don't think you can. In the pic below, the lens on the right has an IR filter on the back which I don't think can be removed. Notice the purple color to the lens. The one on the left does not have the filter (it came like this) and is a lens that would allow this particular camera to see the IR light. If you look at the back, some lenses have a square IR where you can visually see the filter which might be capable of being removed, but like I said, I have not done it before.

 

[????????? ?????????]

I purchased one of these off of Amazon also and I found that this camera is capable of "seeing" the IR spectrum, but mine needed a different lens to do so (the lens mine shipped with has the IR filter on the back of the lens (purplish looking film)). The big problem with this was the color during the day is WAY off because there is IR cut filter. This might be something acceptable to you, but it wasn't to me. I ended up putting the camera in a location that I was only looking for daytime recording.

My camera has LED IR lights and IR filter. The camera turns on or off the filter depending to the light conditions. So it works more or less good at night. In the camera interface you can manually switch on or off the IR filter.

 

[alastairstevenson]

My camera has LED IR lights and IR filter

In the TOP-201 case format?
It sounds like you have the mechanical shutter IR filter, as opposed to the fixed film filter in the lens.