Memory Expansion Board (MEB)

There are two different memory expansion boards available for Hirsch controllers: the MEB/CB64 and the MEB/CB128.

The MEB/CB64 supports 64,000 user records, expands the alarm and event buffers, or provides a combination of both records and buffers. This means that a portion of memory can be allocated to storing users while the remainder is used for buffering events. Normally, it takes twice as much space to store a user profile as it does to store an event (for example, the board can store two users or four events). Hirsch’s velocity security management program supports an option to allocate 20% of the board to alarm/event buffer usage. This option is irreversible.

The MEB/CB128 supports up to 128,000 users, expands the alarm and event buffers, or provides a combination of both users and buffers.

Install only one Memory Expansion Board type for code expansion in a controller at a time.

Open

Figure 3-1: Memory Expansion Boards (MEB/CB128 and MEB/CB64)

The newer CCM V7.0 can diminish the number of events that an expansion board can successfully buffer, because the event string is up to four times longer. For example, a buffer that could comfortably store 4,000 events with the previous CCM (V6.6 and earlier) now buffers only 1,000 events using the V7.0 CCM.

CCM 7.0 now supports increased User and Alarm/Event capacity for up 132,000 user records. With CCM 7.0, the capacities of the Expansion Boards are additive, rather than in lieu of the base memory.

Older boards—the MEB/CE4, MEB/CE16, MEB/CE32, and MEB/BE—still work with CCM 7.0, but at reduced capacities. If a controller has one of these boards and is upgraded to CCM 7.0, it might also be necessary to upgrade the memory expansion boards. Upgrading memory boards can provide the added benefit of increasing expansion board capacity, because the Code Expansion (CE) and Buffer Expansion (BE) can now reside on a single board—the MEB/CB64 or the MEB/CB128.

Table 3-1 describes the maximum user capacities for each memory board type as a function of both IDF and CCM version. Note that your system’s actual capacity could be less, as explained in “Velocity Features that Reduce Available Memory”.

The allocated user memory is the memory that is currently dedicated to users. The projected maximum user capacity is the amount of memory the CCM can auto-allocate to users as additional users are enrolled. 1024 is the base allocated user memory. If you add more than 1024 users, more memory is allocated in units of 256. So, if you add 1025 users, it increases the total memory to 1280; if you add 1281 users, it increases it to 1536, and so on.

There is a feature in Velocity that enables the operator to allocate 20% of MEB/CB expansion memory to the buffer. If the operator selects this setting, the host buffers increase the capacity and the projected maximum user capacity is slightly lower. The minimums are then 1560 buffer events and 1024 users. These values do not decrease, no matter how much extra memory is allocated.

For information about setup and installation of the memory expansion boards, see “Memory Expansion Boards Installation”.

Velocity Features That Reduce available Memory

There are several places in this document which list the capacity of the various controllers and memory expansion boards to support user records or alarms and events. These capacities assume that you are running a version of Velocity which only uses data structures of a certain size. Your system’s capacity could be reduced by up to 50% when using any of the following features (which require larger data structures):

Memory Expansion Boards Installation

The MEB/CB64 and MEB/CB128 boards provide an Mx or Mx-1-ME controller with enhanced capacity to store events and codes.

Open

Memory Board Setups

Memory expansion boards do not require any setup before installing.

Memory Board Mounting & Wiring

To install any of the memory expansion boards:

1.Turn all system power off and remove connectors for both AC power and the standby battery.

2. Install the board on the supplied standoffs and connect the EBIC cable, as described in “Connecting Expansion Boards”.

Because a memory board only communicates with the controller board, it has no inputs or outputs other than the EBIC cable. After a Memory Expansion Board (MEB) has been installed, removing it will instantly delete all codes or logged history records. Furthermore, a cold restart will be required, which will erase all additional information in memory and require complete system reprogramming or restoration from a backup.

Testing the Memory Boards

After installing the board, you can test it by following this procedure:

1.Attach a printer to the Controller or make sure the Controller is attached to a Host PC.

2. Power up the controller by first connecting AC then standby battery.
The system goes through its self-test. See this information printed out at a local printer.

If this is an MEB/CE4:

If this is an MEB/CE16:

and under the Options section, this line appears:

If this is an MEB/BE, see this line in the Options section:

If this is an MEB/CB64:

and under the Options section, these lines appear:

If this is an MEB/CB128:

and under the Options section, these lines appear:

3. If this is a networked system, view maximum user information using the Host PC software.

4. If the correct information doesn’t appear on the printouts, power down the Controller and recheck the EBIC-5 connections, then retry the test procedure. If it still doesn’t work, contact Hirsch.