Campbell CR3000 Micrologger, Руководство оператора

Страница: 444 / 644

Section 8. Operation
444
CR3000 Memory Allocation
External
CompactFlash
(p. 532)
(Optional)
CRD: drive
(p. 613)
— FAT32 recommended. Holds program files. Holds
a copy of final-storage table data as files when TableFile() instruction
with Option 64
(p. 218)
is used (replaces CardOut()). When data are
requested by a PC, data first are provided from SRAM. If the requested
records have been overwritten in SRAM, data are sent from CRD:.
Alternatively, CRD: data can be retrieved in a binary format using
datalogger support software
File Control
(p. 456).
Binary files are
converted using CardConvert software. 10% of card memory
(whichever is smaller) is reserved for program storage. Memory card
can facilitate the use of Powerup.ini
(p. 460).
1
See TABLE: CR3000 SRAM Memory
(p. 444,
http://www.)
2
Flash is rated for > 1 million overwrites.
3
Serial flash is rated for 100,000 overwrites (50,000 overwrites on 128 kB units). CRBasic program
functions that overwrite memory should use the CRD: or USR: drives to minimize wear of the CPU: drive.
CR3000 SRAM 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. 543)
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-Storage 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.