User manual

Toolbox 32 User Manual 1.47d www.cse-semaphore.com/mykingfisher
Page
24
Network Reg. Blocks: Set to 1 or greater to allow the RTU to store data from a remote RTU. 1K per
outstation RTU is usually enough. If the network data is overflowed, a Netblocks Overrun error will be
triggered (please see #YFLAGS.9) and displayed in the RTU Status. When the RTU is cold-started, all the
network blocks are cleared.
Calculating the Network Register Blocks Required
Analog, digital and local register information is all stored in separate network register blocks. For
analog data (#AI or #AO), 8 registers are used to store each module's inputs or outputs while for
digital data (#DI or #DO) a single register is used for each module's inputs or outputs. Each network
block contains 64 registers (128 bytes). This means that one network block can store the data for 8
consecutive analog modules or for 64 digital modules or for 64 consecutive local registers. The first
network block contains registers 1 to 64, the second network block contains registers 65 to 128 and so
on. This means that in order to store #R64 and #R65, two network blocks would be required as the
first block is used to store #R64 and the second block is used to store #R65. Similarly, with analog
registers, the first network block contains the data for analog modules 1 to 8, the second network
block contains the data for analog modules 9 to 16 and so on. Example:
Data To Be Stored Network Blocks Required
#DI1, #DI4, #DO5 1
#AI1.4, #AI3.1 to #AI3.8, #AI9.1 2
#R1, #R2, #R100 2
Optimize For Speed: (For CP-xx only) When ticked, the RTU optimizes the network register (#NR…)
access speed by using a lookup table. This will allow the scan rate of IO modules and ladder logic to be
vastly improved (up to twice as quick) if ladder logic uses a lot of network registers. Note: when using this
option, ensure at least 17K of memory is allocated for Network Reg. Blocks as 16K of this memory is used
for the lookup table. The remaining memory is used for storing network registers. Does not apply to Network
Analog (#NA…) or Network Digital (#ND…) registers.
Image Buffer: (For image capture option boards only). A medium quality image uses 10 kB of memory. It is
recommended that at least 100 kB be allocated for image storage to allow buffering before the images are
uploaded. When the buffer is filled, the oldest image is over-written by the newest image. When using an
MC-xx for image capture, 256kB of memory is automatically allocated for image storage in the MC-xx and
the Image Buffer setting can be set to O kB.
Firmware Drivers: If there is not enough room in flash memory, drivers can also be downloaded to Static
RAM (SRAM). Firmware drivers stored in SRAM are erased after a cold start (drivers are not affected by a
cold start when stored in flash memory). LP-1/2/3 RTUs only store drivers in SRAM.
LP1/2/3 Exp. Memory: An LP-1/2/3 has 384K of SRAM available for user allocation (128K of the 512K total
SRAM is reserved for RTU use). Some LP-1 RTUs and all LP-2/3 RTUs are fitted with 4 MB of expanded
flash memory. This expanded flash memory can be used for storing event logs by ticking the LP1/2/3 Exp.
Memory box. When ticked (enabled), all event logs are stored in flash memory only (SRAM is not used).
Note: event logs stored in expanded memory can only be uploaded using Toolbox 32. They cannot be
uploaded using the Citect or Wonderware Kingfisher driver.
Store ladder logic (.LL) files in RTU: When ticked, every time ladder logic is downloaded to the RTU, the
compiled logic and the ladder source file will both be downloaded. This ensures the latest copy of the ladder
source file is always stored in the RTU. Future changes can be made by uploading the ladder source file
from the RTU using Toolbox, performing the changes, compiling the ladder logic and then downloading the
compiled logic and the ladder source file again. Memory space is automatically allocated for the ladder
source file by Toolbox. (To determine the amount of memory that will be allocated, simply view the size of
the ladder source file (FILENAME.LL) on the PC using Windows Explorer).