Specifications

Section 12. Memory and Data Storage
12-3
TABLE 10-2. CR1000 SRAM Memory
“Static” Memory used
by the operating
system regardless of
the user’s program.
---------------------------
Operating Settings
and Properties
---------------------------
User’s Program
operating memory
---------------------------
Variables
Constants
---------------------------
Auto-allocated final
storage tables
---------------------------
Fixed- size final
storage tables
---------------------------
COMMS Memory 1
---------------------------
COMMS Memory 2
---------------------------
USR: Drive
SRAM 2 or 4 MB
The operating system requires some memory in which to
operate. This memory is rebuilt at power-up, program re-
compile, and watchdog events.
Also known as the “Keep”, memory used to store Device
Configuration settings such as PakBus Address, Station
Name, Beacon Intervals, Neighbor lists, etc, as well as
dynamic properties such as the Routing Table,
communications time outs, etc.
Compiled user program currently running; rebuilt on
power-up, recompile, and watchdog events.
Memory for the public variables in the user’s program.
These values may persist across power-up, recompile,
and watchdog events if the PreserveVariables instruction
is in the running program.
Auto-allocated tables fill whatever memory is left over
from all other demands.
Memory for user’s fixed-size final storage tables.
Compile error occurs if insufficient memory available.
Construction and temporary storage of PakBus packets.
Constructed Routing Table: List of known nodes and
routing to them. Routers take more space than leaf nodes
because must remember routers’ neighbors. Increasing
the PakBusNodes field in the Status Table will increase
this allocation.
Memory manually allocated for use in storing files such
as images and FileRead/FileWrite operations. Shows up
as “USR:” in LoggerNet’s File Control screen. Status
Table field – USRDriveSize.
Notes