(23/37)'0'-'1'(30h, 31h): 1|'1'-'E'(31h, 45h): 30(=1Eh)'1'-'F'(31h, 46h): 31(=1Fh)WW: weekdays'0'-'0'(30h, 30h): Sunday'0'-'1'(30h, 31h): Monday'0'-'2'(30h, 32h): Tuesday'0'-'3'(30h, 33h): Wednesday'0'-'4'(30h, 34h): Thursday'0'-'5'(30h, 35h): Friday'0'-'6'(30h, 36h): SaturdayHH: Hours'0'-'0'(30h, 30h): 0|'1'-'7'(31h, 37h): 23 (=17h)MN: Minutes'0'-'0'(30h, 30h): 0|'3'-'B' (33h, 42h): 59 (=3Bh)DS: Daylight saving (Summer time)'0'-'0'(30h, 30h): NO'0'-'1'(30h, 31h): YESETX (03h): End of MessageCheck codeBCC: Block Check CodeRefer to the section 4.5 “Check code” for a BCC calculation.DelimiterCR (0Dh): End of packet10. Schedule read and write10.1 Schedule ReadThis command is used in order to read the setting of the Schedule.1) The controller requests the monitor to read Schedule.Header Message Check code DelimiterSOH-'0'-Monitor ID-'0'-'A'-'0'-'8' STX-'C'-'2'-'1'-'3'-PG-ETX BCC CRHeaderSOH (01h): Start Of Header'0' (30h): ReservedMonitor ID: Specify the Monitor ID of which you want to get status.Ex.) If Monitor ID is '1', specify 'A'.'0' (30h): Message sender is the controller.'A' (41h): Message type is "Command".'0'-'8'(30h, 38h): Message lengthMessageSTX (02h): Start of Message'C'-'2'-'1'-'3' (43h, 32h, 31h, 33h): Schedule read request command.PG: Program No. The data must be ASCII characters strings.ETX (03h): End of MessageCheck codeBCC: Block Check CodeRefer to the section 4.5 “Check code” for a BCC calculation.DelimiterCR (0Dh): End of packet