| Electronic Components Datasheet Search |
|
PCD5013 Datasheet(PDF) 49 Page - NXP Semiconductors |
|
|
|||||||||||||||||||||||||||||
PCD5013 Datasheet(HTML) 49 Page - NXP Semiconductors |
|
49 / 76 page ![]() 1999 Apr 12 49 Philips Semiconductors Product specification FLEX ™ roaming decoder II PCD5013 8.7.8.4 Hex/binary message FLEX ™ hexadecimal/binary messages may be encoded using any word size (blocking length) in the range 1 to 16 bits. Words are placed in codewords along with additional information about the message as described in Tables 55 and 56 and these definitions. The message data in Tables 55 and 56 have blocking lengths of 4 bits; words are designated lower case letters a, b, c, d etc. Hexadecimal/binary messages can be sent as fragments. See Section 8.8.6 for a description of message fragmentation. Messages and message fragments are terminated, or interrupted in the case of a non-terminating fragment, on the last full character boundary in the last codeword. Unused bits are cleared if the last valid data bit is logic 1, or set if the last valid data bit is logic 0. If the terminating fragment exactly fills its last codeword, an additional codeword is sent to indicate the location of the last character. This codeword is filled with logic 0s if the last valid data bit is logic 1 and filled with logic 1s if the last valid data bit is logic 0. Fields K to N make up the first word of a message and the first word of every fragment in a long message. K: 12-bit fragment checksum (Tables 55 and 56). See Section 8.8.7 for a description of message checksums. C: 1-bit message continued flag (Tables 55 and 56). When this bit is set, fragments of this message are to be expected in following frames. See Section 8.8.6 for a description of message fragmentation. F: 2-bit message fragment number (Tables 55 and 56). This is a modulo 3 message fragment number which is incremented by 1 in successive message fragments. See Section 8.8.6 for a description of message fragmentation. N: message number (Tables 55 and 56). See Section 8.8.8 for a description of message numbering. H: 1-bit header message flag (Table 55). It is a header message only when this bit is set, otherwise it is a data message. A header message is a displayable tag associated with a non-displayable data message. The header message (which is sent first) and the data message, both have the same message number. The second codeword of the first fragment of a hex/binary message contains fields R to S. These fields are only transmitted in the first fragment of a message. R: message retrieval flag (Table 55). When this bit is set, the pager expects this message to be numbered. See Section 8.8.8 for a description of message numbering. s: 5-bit field reserved for future use (Table 55). Default value = 00000. M: 1-bit mail drop flag, see Table 55. When this bit is set, the message is to be stored in a special area in memory to overwrite existing data in the same memory space. D: 1-bit display direction field (Table 55). D = 0 display left to right, D = 1 display right to left (valid only when data sent as characters i.e. blocking length not equal 0001). B: 4-bit blocking length (Table 55). Indicates bits per character. B3B2B1B0 = 0001 = 1-bit per character (binary/transparent data), 1111 = 15 bits per character, 0000 = 16 bits per character. Data with a blocking length other than 1 is assumed to be displayed on a character by character basis (default value = 0001). Note: Tables 55 and 56 show B = 4-bit blocking length. S: 8-bit signature field (Table 55). The 1’s complement of the binary sum, taken 8 bits at a time, over the total message prior to formatting into fragments. The first 8 bits following the signature field are summed with the following 8 bits, b3b2b1b0a3a2a1a0 +d3d2d1d0c3c2c1c0, etc. continuing to the last valid data bit in the last word of the last fragment (the sum does not include termination bits). The 8 LSBs of the result are inverted (1’s complement) and transmitted as the message signature. 8.7.8.5 Secure message FLEX ™ secure messages are encoded using the 7-bit FLEX ™ alphanumeric character set (Section 8.7.8.3). These characters are placed in codewords along with additional information about the message as described in Table 57 and the following definitions. In Table 57, 7-bit characters of the message are designated lower case letters a, b, c, d etc. Secure messages follow the same fragmentation and termination rules as alphanumeric messages (Section 8.7.8.3). K: 10-bit fragment checksum (Table 57). See Section 8.8.7 for a description of message checksums. C: 1-bit message continued flag (Table 57). When this bit is set, fragments of this message are to be expected in following frames. See Section 8.8.6 for a description of message fragmentation. |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |