Most Digital Video Recorder (DVR) products - especially those which are PC-based - have inaccurate internal clocks which can drift by many seconds per week. It is crucial that all CCTV recordings are accurately time-stamped, especially for evidential purposes.
#Veracity timenet vtnus gps receiver pro#
TIMENET Pro is a low-cost solution for accurately synchronising computer system clocks Time Synchronisation Most network installations require a reference time signal for synchronising system clocks to ensure they are always set precisely to the correct time. Simple browser interface allows fast installation Ideal for mobile or vehicle-based applications Ideal for synchronising VMS + ACS servers & clients TIMENET Pro supports all NTP compatible devices Considering that DVR systems may be left unattended for months on end, it is easy to see that the time settings can end up being in error by many minutes. Many DVR products, especially those which are PC-based, have inaccurate internal clocks which drift by many seconds per week. It is crucial that all recordings are accurately time-stamped, especially for evidential purposes. TIMENET Pro is an accurate, low cost, extremely compact universal atomic clock reference for network time synchronisation.ĬCTV and digital video recorder (DVR) installations require accurate reference time signals for synchronisation of system clocks to ensure that they are always set at the precisely correct time. TIMENET Pro is a Master NTP reference clock for Ethernet networks
TIMENET Pro supports all NTP compatible devices.(All of our hard drives come fitted and are CCTV specific from one of the major brands)
#Veracity timenet vtnus gps receiver full#
You may only require the full 25 frames per second on certain cameras if things are fast moving. Finally you can often make your storage space last a lot longer by enabling motion detected recording rather than continuous, especially if there are long periods of no activity.ĭays of storage provided by 1TB per cameraĭays of storage provided by 1TB per 4 camerasĪs a rule of thumb we recommend a minimum of 2 Terabytes per 4 x 2-4MP HD cameras, as this should give you 2 weeks to a month with a few adjustments on motion detected recording. The amount of hard drive space you require is dictated by how many cameras, as well as their resolution and frame rate settings. Zooms in significantly more to look at a gate, entrance or adjascent building Narrows down the angle and zooms in to look past the immediate area a little to gain more detail - down a driveway for example from higher up See below to give you some idea on angles of Megapixel HD Cameras:įor seeing as much of the immediate area as possible such as above a doorway/low down/garage soffits (edges can appear slightly warped/distorted) - clearly "zoomed out"Ī great general purpose option giving great coverage still in the corner of a room or higher up on second floor soffits with less distortion - more of a natural "zoom" A smaller lens will give you a wider angle but will be "zoomed out more", while a bigger lens will narrow the angle down and "zoom in more". Great for accuracy and redundancy but still has ntp packets traversing the WAN when not needed or desired.Unless selecting a vari-focal camera (with an adjustable lens) It is important to select the correct camera lens option for where the camera is to be positioned. In better news the "prefer" statement now works perfectly and pins the snowflake as intended and the stratum 1 pps is the master clock. I'm not sure if the absence of a RTC in my router is influencing the "true" statement or not. The "True" statement doesn't seem to work (at least for my Debian router) - it accepts the statement but nothing seems to change and all servers, internal & external, remain in regular use. Back then the "prefer" statement did little to prevent the snowflake moving to the best "+" server and blending the results. In the past I could achieve my aim by using the "true" statement on my own ntp, which pinned the snowflake on the correct address and the external providers remained dormant. For routine use I do not wish for any external ntp traffic unless the internal one has failed. However, I have run into a few snags in the effort to configure a genuine fallback-only external ntp set. My new ntp server (an ebay bargain) does not offer its own fallback external servers, so I am configuring them on my router. In recent days I bought a new modern ntp server which is GPS+PPS bound but no heater or stabilised crystal.
My ancient ntp server had to go a while back due to its size and power consumption.
0 kommentar(er)
