Most customers may download the binary file through Velocity and do not need to physically replace their CCM.

Customers that may benefit from this DIGI*TRAC release have one or more of these:

• Velocity 3.0 (note: CCM vn. 7.4.06 will also work on earlier versions of Velocity) [7.4.02]
• Globalized alarm-cancel [7.4.02]
• Globalized Anti-Passback or Globalized Absentee Rule, especially on a large high traffic site with more than 42,000 globalized events per hour. Globalized events = number of access grant transactions per hour times the number of controllers. For example, 1200 access grants per hour x 35 controllers = 42,000. [7.4.06]
• Large credential databases (with memory expansion card) with Temp Days, Absentee Rule, or Globalized Anti-Passback in use [7.4.02]
• Large user populations that have to be deleted to make room for more; or if they have experienced user database problems in the past. [7.4.02]
• 2-Person Rule Disable on Occupancy Threshold in multiple-Passback Zone topology [7.4.02]
• Using RQE set to Mask Only. [7.4.05]
• Entry/Exit delay on Expansion Inputs 17-32 [7.4.02]
• "Normally open" inputs monitored via the status viewer. (Most inputs are configured for normally-closed.) [7.4.02]
• M8s with 16 ScrambleProx [7.4.02]
• Long card numbers (longer than 8 digits) and keypad programming mode [7.4.02]
• Weigand pass-through cards [7.4.02]
• GSA 75-bit (FIPS 201) format cards [7.4.02]
• DTA (LCD DIGI*TRAC Annunciator) [7.4.02]
• Keypad programming [7.4.02]
• ScramblePad Sharing AND Custom Card Mapping (This is a rare combination.) [7.4.02]
• Local printer connected to controller, either parallel or via SCIB.  [7.4.06]

Defects fixed:

• Buffers no longer print repeatedly - defect 268 [7.4.06]
• Globalized Anti-Passback in large facilities not going offline - defect 267 [7.4.06]
• "RQE triggered twice doesn't work"  When set to Mask Only, DOTL alarm was not reporting if a second RQE was sent in 8 to 12 seconds - defect 265 [7.4.05]
• All 14 digits of GSA 75-bit format reading correctly - defect 240 [7.4.02]
• Number of people inside disables two-person rule working correctly for multiple Passback Zones - defect 236 [7.4.02]
• Weigand pass-through reading correctly - defect 233 [7.4.02]
• Entry/Exit Delay on Expansion Inputs 17-32 implemented - defect 225 [7.4.02]
• Command 310 & 311 functional in keypad programming with longer card codes - defects 208, 209 [7.4.02]
• Globalized passback working with expansion users - defect 197 [7.4.02]
• MEB/BE clears host buffer limits when removed - defect 85 [7.4.02]
• "Cards don't work after an upgrade." A database mismatch was causing MATCH to read card codes as 00000000. This was fixed in version 7.4.00, but any customers that had experienced the database mismatch potentially had to go into each reader of each controller to change settings after the fix had been implemented. Version 7.4.02 fixes the database mismatch AND resets the customer's reader settings for them, provided the CCM is upgraded via Velocity binary download - defect 233 [7.4.02]
• M8s with 16 ScrambleProx were previously having intermittent and rare match offline messages during periods of inactivity - defect 276 [7.4.02]

Known bugs and limitations:

• "Print ACBs not at factory default" command may print additional ACBs that are at their Velocity default values after a Velocity configuration download - defect 248 (Note: Velocity vn. 3.0 fixes this issue.) [7.4.02]

• 98*53*86*YY*MM*DD# will cold-start the controller from the host or keypad - request 275 [7.4.05]
• New messages logged for clock changes, and whenever Velocity logs onto the  controller, previous to Velocity version 3.1. - request 274 [7.4.06]
• Note that you will see two or three "Undefined Misc Messages" every time Velocity connects to the controller.  You can use Customization Manager to change message 8083 to say "Clock Updated" and message 8087 to "Controller Logged On."
• Globalized User Management optimized to only update the other controllers when the credential's user record is updated. In other words, if the user went from one PZ to the same PZ, and their use count or absentee info didn't change, the access grant transaction won't be globalized to the other controllers - request 273 [7.4.06]
• Globalized Alarm Cancel - request 239 [7.4.02]
• Relay state change logic inverted - request 232 [7.4.02]
• New message format for threat level status - request 224 [7.4.02]
• Controller cold-start and power cycle messages added - request 223 [7.4.02]
• Conditional unmask by input - request 205 [7.4.02]