Bosch 6000 User's Guide Page 28

  • Download
  • Add to my manuals
  • Print
  • Page
    / 268
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 27
Chapter 1. Programming Fundamentals
13
MEMORY
command
syntax
(example)
MEMORY8ØØØØ,7ØØØØ
Memory allocation for Compiled Profiles (bytes).
Storage requirements depend on the number of
segments
in the compiled profile (1 segment consumes
72 bytes). A segment could be one of these commands:
Memory allocation for
Programs (bytes).
Storage requirements
depend on the number of
ASCII characters in the
program.
PARCM
PARCOM
PARCOP
PARCP
PLIN
Contouring: Compiled Motion:
GOBUF
PLOOP
GOWHEN
TRGFN
POUTA
POUTB
POUTC
POUTD
GOBUF
commands
may require up to 4
segments.
The following table identifies memory allocation defaults and limits for 6000 Series products.
When specifying the memory allocation, use only even numbers. The minimum storage
capacity for one partition area (program or compiled) is 1,000 bytes.
Feature AT6n00 AT6n00-M AT6n50 AT6n50-M All Other Products
Total memory (bytes) 64000 1500000 40000 150000 150000
Default allocation
(program,compiled)
33000,31000 63000,1000 39000,1000 149000,1000 149000,1000
Maximum allocation for
programs
63000,1000 1499000,1000 39000,1000 149000,1000 149000,1000
Maximum allocation for
compiled profiles
1000,63000 1000,1499000 1000,39000 1000,149000 1000,149000
Max. # of programs 150 4000 100 400 400
Max. # of labels 250 6000 100 600 600
Max. # of compiled profiles 100 800 100 300 300
Max. # of compiled profile
segments
875 20819 541 2069 2069
Max. # of numeric
variables
100 200 150 150 150
Max. # of string variables 100 100 25 25 25
Max. # of binary variables 100 100 25 25 25
-M refers to the Expanded Memory Option
When teaching variable data to a data program (DATP), be aware that the memory required for
each data statement of four data points (43 bytes) is taken from the memory allocation for
program storage (see Variable Arrays in Chapter 3, page 120, for details).
CAUTION
Using a memory allocation command (e.g., MEMORY39ØØØ,1ØØØ) will erase all existing
programs and compiled profile segments. However, issuing the MEMORY command without
parameters (i.e., type MEMORY
<cr>
to request the status of how the memory is allocated) will
not affect existing programs or compiled segments.
Checking Memory Status
To find out what programs reside in your controller's memory, and how much of the available
memory is allocated for programs and compiled profile segments, issue the TDIR command (see
example response below). Entering the TMEM command or the MEMORY command (without
parameters) will also report the available memory for programs and compiled profile segments.
Sample response
to TDIR command
*1 - SETUP USES 345 BYTES
*2 - PIKPRT USES 333 BYTES
*32322 OF 33000 BYTES (98%) PROGRAM MEMORY REMAINING
*500 OF 500 SEGMENTS (100%) COMPILED MEMORY REMAINING
Two system status bits (reported with the TSS and SS commands) are available to check when
compiled profile segment storage is 75% full or 100% full. System status bit #29 is set when
segment storage reaches 75% of capacity; bit #30 indicates when segment storage is 100% full.
Page view 27
1 2 ... 23 24 25 26 27 28 29 30 31 32 33 ... 267 268

Comments to this Manuals

No comments