Table 85. CR1000 Main Memory
Use
Comments
Static Memory Operational memory used by the operating system. Rebuilt at power-up,
program re-compile, and watchdog events.
————————————
Operating Settings and Properties
"Keep"
(p. 519) memory. Stores settings such as PakBus address, station name,
beacon intervals, neighbor lists, etc. Also stores dynamic properties such as the
routing table, communication timeouts, etc.
————————————
CRBasic Program
Operating Memory
Stores the currently compiled and running user program. This sector is rebuilt on
power-up, recompile, and watchdog events.
————————————
Variables & Constants
Stores variables used by the CRBasic program. These values may persist
through power-up, recompile, and watchdog events if the PreserveVariables
instruction is in the running program.
————————————
Final-Data Memory
Stores data. Fills memory remaining after all other demands are satisfied.
Configurable as ring or fill-and-stop memory. Compile error occurs if
insufficient memory is available for user-allocated data tables. Given lowest
priority in SRAM memory allocation.
————————————
Communication Memory 1
Construction and temporary storage of PakBus packets.
————————————
Communication Memory 2
Constructed Routing Table: list of known nodes and routes to nodes. Routers use
more space than leaf nodes because routes to neighbors must be remembered.
Increasing the PakBusNodes field in the Status table will increase this allocation.
————————————
USR: drive
<= 3.6 MB (4 MB Mem)
<= 1.5 MB (2 MB Mem)
Less on older units with more
limited memory.
Optionally allocated. Holds image files. Holds a copy of final-data memory
when TableFile() instruction used. Provides memory for FileRead() and
FileWrite() operations. Managed in File Control. Status reported in Status
table fields "USRDriveSize" and "USRDriveFree."
373
To Next Page
Loading...
Need help?
General
