User's Manual

PIN Pad 791 Programmer’s Manual (PCI POS-A) UDN PM0103-U Rev. 06

Section 5 – Administration and maintenance messages 2015-04-20

Page54

Uniform Industrial Corp. Proprietary and Confidential Total 342 pages

Message flow:

HOST Direction PIN Pad

Message 18 request frame





<ACK> (Good LRC)

<NAK> (Bad LRC)

<EOT> (after 3 NAKs)



Message 18 Response Frame





Processing and send <EOT>

NOTE:

The followings describe that how to input a proper syntax of time zone enviorment variable.

The first format is used when there is no Daylight Saving Time in the local time zone:

std offset

The std string specifies the name of the time zone. It must be 3 ~ 6 characters long and must not contain a

leading colon, embedded digits, commas nor plus and minus signs.

The offset specifies the time value you must add to the local time to get a Coordinated Universal Time

value. It has syntax like [+|-]hh[:mm[:ss]]. This is positive if the local time zone is west of the Prime Meridian

and negative if it is east. The hour must be between 0 and 23, and the minute and seconds between 0 and

59. (for example, PST+8)

The second format is used when there is Daylight Saving Time:

std offset dst[offset],start[/time],end[/time]

The initial std and offset specify the standard time zone, as described above. The dst string and offset

specify the name and offset for the corresponding Daylight Saving Time zone. If the offset is omitted, it

defaults to one hour ahead of standard time.

The start field is when Daylight Saving Time goes into effect and the end field is when the change is made

back to standard time. The following formats are recognized for these fields:

This specifies the Julian day, with n between 1 and 365. February 29 is never counted, even in

leap years.

This specifies the Julian day, with n between 0 and 365. February 29 is counted in leap years.