IC-Controllers Cards Capacity and Dynamic Buffer Size

1. Cards Capacity

The cardholders’ capacity depends on the ROM as shown in the following table:

Note 1: ROM xxx9 with 512K memory and ROM xxxE with 2M memory supports card code of 8 digits only and restricted to 2 doors only.

2. Optimising the Event Buffer Size
For 128K and 512K controllers, the default allocated event buffer space holds 1935 transactions and for 2M RAM controllers, this space holds 24860 events. Cardholders’ Database and the Event Buffer share the same memory space in the controller. By default, the Cardholders’ Database is maximised in order to support the highest card number authorised (also called the maximum “Num_Badge”). As the Cardholders’ Database depends on the RAM, the maximum “Num_Badge” is 8934 for 128K controllers, 44670 for 512K controllers and 163790 for 2M RAM controllers.

Note: the ROM defines how many cardholders may be recorded in the database whereas the Cardholders’ Database size fixes the highest card number authorised.

However, if none of the controller of a site needs the highest card number authorised, because the maximum “Num_Badge” of a site corresponds to the biggest ROM capacity, this memory space can be optimised and adjusted to allow you to use the potentially unused space to increase the available Event Buffer size.

This adjustment will have a direct effect on the highest card number authorised. Because of this fact, this adjustment must be made according to the biggest ROM that will be in use on the site. This allows for the highest card number that could be used in all the controllers.

To increase the Event Buffer size of a controller, send the following command to the relevant controller from GPP (open the “Controller” screen, press Shift+F12 and write in the “Script” tab): 76 40 02 03 HGH 00 00

Where the ‘HGH’ value (‘00’ by default) defines the new buffer size.

Select the possible values according to the biggest ROM used in the site, as in the following table below:

HGH according to Event Buffer Capacity

Examples:
- If the biggest ROM of a site is xxx2 (20480 cardholders),
selecting HGH=0A will allow an Event Buffer of 18310
transactions for a 512K controller and
172235 for a 2M controller. (Command to send will be 76 40 02 03 0A 00 00)

- If the biggest ROM of a site is xxxB (81920 cardholders),
selecting HGH=26 will allow an Event Buffer of 80535
transactions for a 2M controller. (Command to send will be 76 40 02 03 26 00 00)

- If for example you have a site with a 128K IC1000 with ROM xxx5 (2048 cardholders) and a 512K IC2000/4000 with ROM xxx6 (6400 cardholders).

Selecting HGH=03 will allow the highest badge number of 6400 for both controllers. Meaning the IC1000 will still be able to accept a badge containing the number 6399 on it, while still limited by the ROM for a total number of badges to 2048. (Command to send will be 76 40 02 03 03 00 00)

Note 1: Default Values
Note 2: if, for a HGH value selected, the ‘-‘ symbol appears in a column, and the corresponding controller is present on the site, this means that the HGH value is not available. Select then, for the same ROM capacity, another HGH value. (For example, for ROM=xxx6, value HGH=02 is not available for a 512K or 2M controllers. Select then HGH=03).

If you add any new controller(s) to GPP, do not forget to include the script.