NEC UN552S External Controls - Page 136

Get Proof of Play Status

Get NEC UN552S PDF manuals and user guides View all NEC UN552S manuals
Add to My Manuals
Save this manual to your list of manuals

Page 136 highlights

26.3 Get Proof of Play Status This command is used in order to get Proof of Play Status. 1) The controller requests the monitor to get status of Proof of Play. Header SOH-'0'-Monitor ID- '0'-'A'-'0'-'8' Message STX-'C'-'A'-'1'-'5'-'0'-'2'-ETX Check code BCC Delimiter CR Header SOH (01h) : Start of Header '0' (30h) : Reserved Monitor ID: Specify the Monitor ID from 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 length is 8 bytes. Message STX (02h): Start of Message 'C'-'A'-'1'-'5 6': Proof of Play command '0'-'2' (30h,32h): Get Proof of Play Status command ETX (03h): End of Message Check code BCC: Block Check Code Refer to the section 4.3 "Check code" for a BCC calculation. Delimiter CR (0Dh): End of packet 2) The monitor replies the status of Proof of Play to the controller. Header SOH-'0'-Monitor ID'0'-'B'-'1'-'4' Message STX-'C'-'B'-'1'-'5'-'0'-'2'-ST1-ST2ST3-ST4-ST5-ST6-ETX Check code BCC Delimiter CR Header SOH (01h) : Start of Header '0' (30h) : Reserved Monitor ID: Specify the Monitor ID from 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". '1'-'4' (31h, 34h) : Message length is 20 bytes. Message STX (02h): Start of Message 'C'-'B'-'1'-'5': Proof of Play reply command '0'-'2' (30h,32h): Get Proof of Play status command ST1: Error status 00h (30h, 30h): No Error 01h (30h, 30h): Memory full (some date has been lost) 02h (30h, 30h): other error (other error has priority ver 01h error) ST2: Total Number-High byte (How many log data items are currently used.) ST3: Total Number-Low byte (How many log data items are currently used.) '0','0','0','0' - 'F','F','F','F' (30h,30h,30h,30h - 46h,46h,46h,46h): 0-65535 (136/145)

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
(136/145)
26.3 Get Proof of Play Status
This command is used in order to get Proof of Play Status.
1) The controller requests the monitor to get status of Proof of Play.
Header
Message
Check code
Delimiter
SOH-'0'-Monitor ID-
'0'-'A'-'0'-'8'
STX-'C'-'A'-'1'-'5'-'0'-'2'-ETX
BCC
CR
Header
SOH (01h) : Start of Header
'0' (30h) : Reserved
Monitor ID: Specify the Monitor ID from 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 length is 8 bytes.
Message
STX (02h): Start of Message
'C'-'A'-'1'-'5
6': Proof of Play command
'0'-'2' (30h,32h): Get Proof of Play Status command
ETX (03h): End of Message
Check code
BCC: Block Check Code
Refer to the section 4.3
“
Check code
”
for a BCC calculation.
Delimiter
CR (0Dh): End of packet
2) The monitor replies the status of Proof of Play to the controller.
Header
Message
Check
code
Delimiter
SOH-'0'-Monitor ID-
'0'-'B'-'1'-'4'
STX-'C'-'B'-'1'-'5'-'0'-'2'-ST1-ST2-
ST3-ST4-ST5-ST6-ETX
BCC
CR
Header
SOH (01h) : Start of Header
'0' (30h) : Reserved
Monitor ID: Specify the Monitor ID from 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".
'1'-'4' (31h, 34h) : Message length is 20 bytes.
Message
STX (02h): Start of Message
'C'-'B'-'1'-'5': Proof of Play reply command
'0'-'2' (30h,32h): Get Proof of Play status command
ST1: Error status
00h (30h, 30h): No Error
01h (30h, 30h): Memory full (some date has been lost)
02h (30h, 30h): other error (other error has priority ver 01h error)
ST2: Total Number-High byte (How many log data items are currently used.)
ST3: Total Number-Low byte (How many log data items are currently used.)
'0','0','0','0' - 'F','F','F','F' (30h,30h,30h,30h - 46h,46h,46h,46h): 0-65535