CuddeLinkManual
Version 2.20.2017 Page 9 of 24
Step 5. Network Control - Program CL DELAY (Remote only)
CL DELAY is somewhat like Camera Delay, except it controls how often images are transmitted.
Let’s use an example to demonstrate how this feature works:
<Insert diagram>
Let’s assume you set a CAMERA DELAY of 5 seconds and a CL DELAY of 30 seconds.
The camera takes a picture at 00 seconds and the image is transmitted and the 30
second CL DELAY is started.
A second picture is taken at 10 second, this picture is not transmitted because the CL
DELAY has not gotten to 30 yet.
A third picture is taken at 33 seconds, this image is transmitted because it is more than
30 seconds since the last image was transmitted.
CL DELAY has settings of 5 seconds to 1 hours. It is important to understand that a
combination of a short CL DELAY (5 seconds) and many images taken per day (100s) will create
a situation where 100s or even thousands of images are queued to transfer, which could require
days to be transmitted home. For this reason we recommend using a reasonable CL DELAY to
limit the number of images sent home. (Daily throughput is about 1000 images combined
across all cameras on the network).
Recommendations:
Trails
– CL Delay of 5 seconds. Most likely a trail will not have much activity in a day so
you may want to send every image home.
Fields and Plots
– CL Delay of 30 seconds or more. In fields the camera may record
dozens to hundreds of images in a day. You will want to use a longer CL Delay to limit
the number of images the camera transmits.
Feed Site
– CL Delay of 1 or even 5 minutes or more. Feed sites are where a camera can
record 100s of images in a day. We recommend you use a longer CL Delay to
compensate for all the images recorded.
To Next Page
Loading...
