User manual AMX I!-SCHEDULE

[. . . ] instruction manual i!-Schedule i n t e g ra t i o n !S o l u t i o n s Software Limited Agreement LIMITED WARRANTY LIMITED WARRANTY. AMX Corporation warrants that the SOFTWARE will perform substantially in accordance with the accompanying written materials for a period of ninety (90) days from the date of receipt. Any implied warranties on the SOFTWARE and hardware are limited to ninety (90) days and one (1) year, respectively. [. . . ] The current Date and time can easily be calculated form this value. However, the number of seconds in this protocol is provides as a 32 bit unsigned number, which can represent a maximum value of 4294967295 (2 ^ 32). 4294967295 seconds from January 1st, 1900 occurs on Feb 7, 2036 at 6h 28m 16s. Therefore, this protocol can only accurately represent time before this date. Many of the NIST servers, as well and many Unix, Linux and Windows programs, can provide this time protocol, and it can be reliably used up until Feb 7, 2036. The last two Time protocols share the same message format but differ in their connection scheme. SNTP stands for Simple Network Time Protocol, a subset of NTP or Network Time Protocol, is based on RFC2030. It is a highly accurate measure of time and date and also measures Date and Time as the number of seconds from January 1st 1900. However, the number of seconds is provided in two parts: the number of whole seconds, with a range of 4294967295 (2^32) and fractions of a second also with a range of 4294967295 (2^32). The Netlinx master is not able to take advantage of 8 i!-Schedule Using i!-Schedule the fractions of a second offered by SNTP and therefore has the same accuracy as the Time protocol but SNTP also provides information about the integrity of the data supplied. This makes the SNTP protocol more accurate than the Time protocol. RFC2030, which defines the SNTP protocol, has also made a provision for Dates and Time after Feb 7, 2036. SNTP message can represent a Date and Time accurately until some time in the year 2104. Most of the NIST servers also provide Date and Time information in SNTP format. The difference between SNTP (123/udp), SNTP Broadcast (123/udp) is simply one of connection. It is possible to configure an SNTP server to broadcast the time in SNTP format to an entire network or node of a network. The Time Manager in i!-Schedule can be configured to actively retrieve the time in SNTP format from an SNTP server (protocol number 3) or simply listen for SNTP broadcasts on the network (protocol number 4). Although SNTP broadcasting may sound like an ideal solution for Date and Time information, the Network Administrator should make this decision. So why did we implement so many time protocols?Which timeserver protocol should you use?This depends on your Network configuration and your Network administrator. It is probable that your network already provides some form of Date and Time information, and that information is probably obtained from a highly accurate source. [. . . ] The "%s" is a placeholder for a string specified in the DTS rules section. dTmTzGmtOffset A floating point number containing the GTM offset in hours. The common US offsets are: Eastern = -5, Center = -6, Mountain = -7, Pacific = -8. Location such as Newfoundland, which runs 3 hours 30 minutes behind GMT would use a GMT offset of -3. 5. This information is used for calculating sunrise and sunset times and for calculating local time when communicating with an Internet timeserver. Continued 20 i!-Schedule Programming i!-Schedule i!-ScheduleMod Module Parameters (Cont. ) strTmTzDstRules A string containing 1 or more daylight saving rule strings. [. . . ]