{"id":190,"date":"2019-01-24T20:46:33","date_gmt":"2019-01-25T02:46:33","guid":{"rendered":"http:\/\/home.iseeancestors.com\/blog\/?p=190"},"modified":"2020-06-08T14:47:14","modified_gmt":"2020-06-08T20:47:14","slug":"how-to-lorex-nvr-file-transfer-protocol","status":"publish","type":"post","link":"https:\/\/home.iseeancestors.com\/blog\/2019\/01\/24\/how-to-lorex-nvr-file-transfer-protocol\/","title":{"rendered":"How-To: Lorex NVR File Transfer Protocol"},"content":{"rendered":"\n
\"4KHDIP86\"<\/figure><\/div>\n\n\n\n

This is my review of the File Transfer Protocol (FTP) feature on a Lorex 4K IP Camera System. <\/span>1<\/sup><\/a><\/span><\/p>\n\n\n\n

Here is a quick way to review snapshots taken during motion detection events. I used the File Transfer Protocol (FTP) feature of the Lorex NVR. Basically I set the NVR to transfer snapshots to my web server, then I wrote a script that displays them. This is an advanced topic intended for those who manage their own website. Here\u2019s how I did it. <\/span>2<\/sup><\/a><\/span><\/p>\n\n\n\n\n\n\n\n

Create an FTP Account<\/h4>\n\n\n\n

First create an FTP account at your website hosting provider and create a user name and password. Set the root directory to be a directory under your \u201cpublic_html\u201d directory. This allows you to view the uploaded snapshots over the Internet. You will want to restrict access to that directory using \u201c.htaccess,\u201d either by requiring a password, or restricting it to only certain Internet Protocol (IP) addresses.<\/p>\n\n\n\n

The Lorex documentation suggests you download and install FTP server software on your computer. If you don\u2019t have a web server, you can do that instead. But, it means you must keep a computer on your local network running all the time. You must also use a package like XAMPP if you want to run a PHP script on your local PC. It has an Apache server.<\/p>\n\n\n\n

Enable FTP on the NVR<\/h4>\n\n\n\n

On your NVR, navigate to Network, FTP options. Enter your FTP server address, which is usually something like \u201cftp.yoursite.com.\u201d Enter the port number, usually 21, and the user name and password you chose when you created the FTP account at your server.<\/p>\n\n\n\n

\"Setup-FTP-FTP\"<\/figure>\n\n\n\n

Optionally specify a Remote Directory. The NVR automatically creates a directory structure in your root FTP directory, or under the Remote Directory name you choose. Here for example, I named the directory \u201cSun\u201d and the NVR created a sub-directory using the NVR\u2019s IP address as it is on my Local Area Network (LAN). It then creates sub-directories under that directory, one for each day. That\u2019s where the snapshots uploaded are stored.<\/p>\n\n\n\n

\"Directory<\/figure><\/div>\n\n\n\n

Keep the File Length at 0 to allow files of any size to be uploaded. Alternately you could cap the maximum length based on what you expect it to be. That depends on the snapshot image resolution and quality level. If you normally get 1 Megabyte files at quality level 4 out of 6, then you could enter 2 Megabytes. Daylight images are usually larger than nigh time images.<\/p>\n\n\n\n

Choose a particular Channel (camera number) or all cameras. It\u2019s either all or one, you cannot choose combinations of cameras. Then choose the weekday when FTP uploads are done, or all weekdays. Likewise, you cannot choose a combination of individual weekdays. <\/span>3<\/sup><\/a><\/span><\/p>\n\n\n\n

Leave\nthe check boxes for \u201cAlarm,\u201d \u201cMD,\u201d and \u201cContinuous\u201d\nunchecked<\/em>. That way, only snapshot images will be uploaded. \nIf you check a box, then video will be uploaded as well, which\nresults in enormous file sizes. Your Internet provider probably\nseverely restricts your upstream bandwidth. I noticed that if I\nenabled video upload over FTP, my Internet browser became very\nsluggish.<\/p>\n\n\n\n

Check the box for Enable to start FTP processing. Once FTP is enabled, as motion events occur, the snapshots generated will be transferred via FTP to your website.<\/p>\n\n\n\n

There seems to be a bug in the Lorex NVR. One night I disabled FTP uploads. The next morning when I enabled them again, no snapshots were being uploaded. I checking the settings on my web server, and I was able to manually transfer files. I restarted the Lorex NVR and the snapshots began to transfer once again.<\/p>\n\n\n\n

Snapshots for Motion Detection Events<\/h4>\n\n\n\n

Use these steps to enable snapshots for motion detection events, if you have not already done so.<\/p>\n\n\n\n

Navigate to Camera Setting, Recording, Snapshot. Choose the desired Channel (camera number). Choose the \u201cTrigger\u201d Mode so that snapshots are triggered on motion detection events. \u201cTiming\u201d mode refers to continuous snapshot recording, which is not what you want when using FTP transfer.<\/p>\n\n\n\n

\"Setup-CameraSetting-Recording-Snapshot\"<\/figure>\n\n\n\n

Choose an image Quality. This will require some experimentation. At the best quality, level 6, snapshots are over 2 Megabytes in size during daylight hours and about 1 Megabyte during night time hours. At the lowest quality, level 1, they are less than 1 Megabyte and less than a \u00bd Megabyte, respectively. But, the lowest quality snapshots at night are almost useless in terms of being able to detect people or cars.<\/p>\n\n\n\n

It depends on why you want to use snapshots. If you want a record of what the camera sees, you\u2019ll want higher quality. If you want to see enough to decide whether to review the video playback, you can get by with lower quality. It\u2019s a trade-off between disk storage capacity, transfer bandwidth, and image resolution.<\/p>\n\n\n\n

Snapshot Frequency is poorly documented. I\u2019ve yet to figure out what the abbreviation \u201cSPL\u201d stands for, but it is probably \u201cSeconds Per\u201d something, or \u201cSnapshots Per\u201d something. You can think of it as \u201cSeconds Per Snapshot.\u201d The camera starts taking snapshots when a motion detection event occurs. It continues taking snapshots at the Snapshot Frequency value all during the motion event.<\/p>\n\n\n\n

If you specify 2 SPL, then a snapshot is taken every 2 seconds. This value also requires some experimentation. You should coordinate it with the \u201cPost Record\u201d or \u201cPost_REC\u201d value you want for the motion detection event (see below). For example if you record 60 seconds of video when motion is detected, decide how many snapshots you want to save. If you want just the initial snapshot, you can specify 61 SPL and a second snapshot won\u2019t be taken unless the motion event continues longer than 60 seconds. If you want a couple snapshots during each event, then choose 30 SPL. If you want as many snapshots as possible, choose 1 SPL. You must consider the bandwidth used to transfer so many snapshots to your server and the space they will occupy.<\/p>\n\n\n\n

Motion Detect Event<\/h4>\n\n\n\n

Navigate to Event, Motion, Motion Detect and choose which camera to configure. Click the Enable checkbox. Set the Schedule to allow motion detection, then set the Area in the camera\u2019s field of view that will trigger an event when motion is detected. You\u2019ll have to experiment with the Sensitivity and Threshold settings there. Refer to the NVR manual.<\/p>\n\n\n\n

\"Setup-Motion-MotionDetect\"<\/figure>\n\n\n\n

Check the box to enable Channel recording, then set which camera or cameras should record when motion is detected. Usually you\u2019ll want camera 1 to record if camera 1 detects motion, but you can have other cameras record instead, or in combination. If you don\u2019t do this step, you won\u2019t see Motion Detect indications during playback if you use continuous video recording. Or if you don\u2019t record continuously, there will be no video at all to playback.<\/p>\n\n\n\n

Choose the number of seconds you want the motion detect event to last in the Post_REC field. Coordinate this value with the \u201cSnapshot Frequency\u201d value as I discussed above. Anti-dither is the number of seconds to wait before generating another motion detect event, when motion is detected again. <\/span>4<\/sup><\/a><\/span><\/p>\n\n\n\n

Check the Snapshot check box and set which camera or cameras should take snapshots. You will probably want camera 1 to take a snapshot when motion is detected on camera 1, but you can also set other cameras to take snapshots simultaneously.<\/p>\n\n\n\n

Motion Detect Event Schedule<\/h4>\n\n\n\n

Navigate to Storage, Schedule and check the yellow Motion Detect (MD) box. Then enable Motion Detect Events by filling in the schedule to allow them as desired. I recommend you also choose a Pre-record time to capture video just prior to whatever triggers a motion event. Sometimes a car will zoom by so fast, it will be out of view when the snapshot is taken. You can see it in the playback video if it includes sufficient pre-record time.<\/p>\n\n\n\n

\"Setup-Schedule-Record\"<\/figure>\n\n\n\n

Click over to the Snapshot tab (Storage, Schedule, Snapshot). Check the Motion Detect (MD) box and likewise enable when to allow snapshots when motion is detected. Be sure to disallow<\/em> continuous recording of snapshots or you will be transferring Megabytes and Megabytes of snapshots all the time. You will probably exceed the FTP bandwidth limit of your server. In this example, make sure there are no green lines representing continuous mode on your snapshot schedule.<\/p>\n\n\n\n

\"Setup-Schedule-Snapshot\"<\/figure>\n\n\n\n

For some reason there is yet another step to enable snapshots. Navigate to Storage, Record and click the Enable radio buttons to allow snapshot recording for your cameras as desired.<\/p>\n\n\n\n

\"Setup-Record-Record\"<\/figure>\n\n\n\n

I\u2019m not sure yet if the NVR starts an FTP session and keeps it open continually, or if it starts a connection, transfers a snapshot and closes the connection. At my web server, it doesn\u2019t show that an FTP session is currently active.<\/p>\n\n\n\n

Viewing the Uploaded Snapshots<\/h4>\n\n\n\n

In terms of automation, I wrote a script to display the snapshots uploaded from the NVR to my web server via FTP. The script generates a web page that shows snapshot images for a particular day. This provides a quick and easy way to see the snapshots. If I see something to investigate, I can note the time and use the playback feature back over on the NVR to review the actual motion event video. Most motion events can be dismissed by glancing at the snapshot. It is usually a bird or animal, or a car I already expected to see.<\/p>\n\n\n\n

The script reads the sub-directories created by the NVR during the FTP transfer to determine the dates of the days available. These dates are added to a drop-down list and I can select one date to view. Once selected, the script gets a list of snapshot files in that sub-directory. The snapshot file name is encoded with the channel number and date and time it was taken:<\/p>\n\n\n\n

NR908X_ch1_20190103152715_E.jpg<\/p>\n\n\n\n

Here, \u201cch1\u201d is the channel or camera number. This is followed by the date and time the snapshot was taken in year-month-day-hour-minute-second. The script parses the channel number and timestamp from the file name to construct a caption for each snapshot. The \u201c_E,\u201d which I ignore, seems to mean motion event. I\u2019ve also seen \u201c_T,\u201d which might refer to another event besides motion, like \u201cTamper.\u201d I have yet to investigate the different types of snapshots.<\/p>\n\n\n\n

Since snapshot images are relatively large, the script first resizes them to create thumbnails. Thumbnail images are displayed in a list and I can select one thumbnail to see in detail, which is the original snapshot. It can be further enlarged to examine the view in more detail. To view another snapshot, I simply click another thumbnail and the page reloads with that snapshot.<\/p>\n\n\n\n

Here is the simple user interface. The thumbnail highlighted in yellow corresponds to the large image shown at right. The images have been blurred for privacy.<\/p>\n\n\n\n

\"SnapScan\"<\/figure>\n\n\n\n

The use of thumbnails significantly reduces the time needed to load the web page. Only a single large snapshot image is shown at a time. But, generating thumbnails is computationally time-consuming. If the script hasn\u2019t run in a while and dozens of snapshots have been uploaded in the meantime, there is a long delay in loading the page. For this reason, I have a separate script that runs in the background. It attempts to generate thumbnail images for any new snapshots uploaded. This script runs every hour through an entry in my website\u2019s \u201ccrontab\u201d facility.<\/p>\n\n\n\n

The\nscript also checks the modification time of each snapshot. It skips\nprocessing a snapshot if the timestamp is too recent. This avoids\nprocessing a snapshot while it is actively being uploaded, which will\nresult in errors and incomplete thumbnails and\/or snapshots.<\/p>\n\n\n\n

The\nfinal step is to delete the older snapshots from the web server\nperiodically, say after a week. This gives me time to review recent\nactivity and it frees up server space.<\/p>\n\n\n\n

Fine-tune the Snapshot Frequency<\/h4>\n\n\n\n

You\nmay be surprised at the number of snapshots generated due to the\nnumber of motion detect events that occur. Experiment with various\nsettings to achieve an optimal frequency.<\/p>\n\n\n\n

Adjust\nthe four motion detect zones on each camera to avoid bushes and tree\nlimbs that sway on windy days. Adjust the sensitivity and threshold\nof each zone to detect what you want to see and ignore everything\nelse.<\/p>\n\n\n\n

Adjust\nyour motion-sensing outdoor lights to reduce their sensitivity to\nbugs, birds and windy conditions. Each time those lights go on and\ngo off, it causes a motion detection event.<\/p>\n\n\n\n

Fog causes Motion Events<\/figcaption><\/figure>\n\n\n\n

If\nyour camera is in infrared (IR) night vision mode, fog will appear\nlike a swarm of bugs flying around the lens. It causes continuous\nmotion detection events and your FTP server will be flooded with\nhundreds of snapshots. You may wish to disable FTP processing\naltogether on foggy or stormy nights.<\/p>\n\n\n\n

Likewise\nyou may get fewer snapshots than expected. Suppose you want to\ncapture every car that drives by. You could reduce the \u201cPost\nRecord\u201d or \u201cPost_REC\u201d field on the motion event. It then won\u2019t\nlast as long. You may need to decrease the \u201cAnti-dither\u201d time so\nanother motion event captures the next car that drives by. \nAlternately, you could reduce the \u201cSnapshot Frequency\u201d value\n(seconds per snapshot) so more snapshots are taken during a given\nmotion event, in case another car drives by right after the last one.\n That results in more snapshots though.<\/p>\n\n\n\n

Conclusion<\/h4>\n\n\n\n

The FTP feature is one way of saving snapshots taken during motion detection events. I sent mine to my website. I use a script to display them on a web page, and it is a simple matter to scroll through a list of thumbnail images. The date, time and channel (camera number) are shown. If necessary I can use the Flir Cloud Client program on my PC to see the corresponding video playback for any given motion detection event.<\/p>\n\n\n\n

UPDATE:<\/strong> The scripts I describe in this article are now available for download. See How-To: Home Automation Scripts<\/a>. <\/p>\n","protected":false},"excerpt":{"rendered":"

This is my review of the File Transfer Protocol (FTP) feature on a Lorex 4K IP Camera System. Here is a quick way to review snapshots taken during motion detection events. I used the File Transfer Protocol (FTP) feature of the Lorex NVR. Basically I set the NVR to transfer snapshots to my web server, … Continue reading “How-To: Lorex NVR File Transfer Protocol”<\/span><\/a><\/p>\n","protected":false},"author":65,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[35,17,9,16],"tags":[32,28,30,29,26,27],"class_list":["post-190","post","type-post","status-publish","format-standard","hentry","category-how-to","category-review","category-software","category-technology","tag-automation","tag-camera","tag-ftp","tag-lorex","tag-security","tag-surveillance"],"_links":{"self":[{"href":"https:\/\/home.iseeancestors.com\/blog\/wp-json\/wp\/v2\/posts\/190","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/home.iseeancestors.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/home.iseeancestors.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/home.iseeancestors.com\/blog\/wp-json\/wp\/v2\/users\/65"}],"replies":[{"embeddable":true,"href":"https:\/\/home.iseeancestors.com\/blog\/wp-json\/wp\/v2\/comments?post=190"}],"version-history":[{"count":9,"href":"https:\/\/home.iseeancestors.com\/blog\/wp-json\/wp\/v2\/posts\/190\/revisions"}],"predecessor-version":[{"id":273,"href":"https:\/\/home.iseeancestors.com\/blog\/wp-json\/wp\/v2\/posts\/190\/revisions\/273"}],"wp:attachment":[{"href":"https:\/\/home.iseeancestors.com\/blog\/wp-json\/wp\/v2\/media?parent=190"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/home.iseeancestors.com\/blog\/wp-json\/wp\/v2\/categories?post=190"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/home.iseeancestors.com\/blog\/wp-json\/wp\/v2\/tags?post=190"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}