B&K CT310 Bedienungsanleitung Seite 45

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 48
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 44
CT600/602/610 and CT300/310 BKC-DIP Product Specific Appendices
Version 2.00.09
Updated 12/15/06
Page 45 of 48
Note 6: There is 2000h, 8192 decimal, bytes allocated in non-volatile
memory for use by the serial macros. Each macro consumes:
1 byte Macro Number
2 bytes Macro Length
1 byte Macro Trigger ID
1 byte Macro Trigger Code
1 byte Macro Scrollable and BaudRate
1 byte Macro Output Mask
+
x bytes Macro Message Message Length
As an example, a macro message of “Hello World” would consume
7 + 11 bytes of memory.
Thus the amount of memory available for a macro is variable,
depending upon what other macros currently exist. In the one
extreme case of the largest single message, one could create a
single macro with a message length of 8185 characters.
NOTE: Although the Serial Macro structures can accommodate
very large string lengths, the practical limit for macro
message length is approximately 2000 bytes. This is due
to the fact that the receive buffer in the unit is only
2048 (2k) bytes long, and processing of the message
cannot occur until the entire message is received. Thus
it is not possible to send a valid BKC-DIP message to a
CT300/310/600/602/610 of length longer than 2048 bytes.
Taking into account the syntax overhead of BKC-DIP
(receive ID, checksum, open/close parenthesis, etc.)
leaves approximately 2000 bytes for an actual Serial
Macro message. Should this become an issue, create 2
independent macros with the same trigger IDs and trigger
codes. The macro number will determine the priority of
the macros with matching trigger conditions, with lower
macro numbers having the higher priority.
In the other extreme case of maximum number of macros (255,
macro numbers 0h through FEh), each macro would have a message
length of 25 characters.
NOTE: If a macro is too large for the available space, it is
not accepted. Monitoring the maximum free space is
recommended by reading the Macro Free Space MSB and LSB
(see Note 8 below) to indicate how much available macro
space is available before attempting to write a macro
message.
Seitenansicht 44
1 2 ... 40 41 42 43 44 45 46 47 48

Kommentare zu diesen Handbüchern

Keine Kommentare