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:

• DTA (DIGI*TRAC Annunciator LCD unit)

Defects fixed:

• "Users deleted randomly from the controller on dial-up sites." if you're experiencing this symptom, with or without dial-up, please upgrade.
• "Incorrect timestamp" on transactions that happen on the cusp of the hour. For example an event happening between 16:59:59 and 17:00:00 incorrectly recorded as 16:00:00. (Test Track defect 162)
• Excessive "Clock change detected" messages. Clock change types 1-7 are normal (6 and 7 happen every time Velocity connects to the controller and sets the clock); 8 and above usually indicate hardware problems, probably either the crystal or the clock chip, especially if you get a string of these messages. There were some situations where type 8-12 ("unexpected clock change") appeared immediately after the normal type 6 and 7 ("deliberate clock change").
• "Indexed Command" functions now show as separate transaction types, such as Manual Holiday. They've also been changed from "Program"-class functions to "Control" as governed by the ScramblePad Options checkboxes. (They're still programmed under the "Indexed Command" function in Velocity's enrollment manager -- we just changed the event messages.) Requested by the Velocity development team.

Known limitations:

• DTA date/time format changed. Users will typically see "MM-DD HH.MM" in 12-hour time, i.e. 13:00 (1 pm) June 22 displays as 06-22 1:00. (The time has a colon " 1:00" when Velocity is logged onto the controller, and a period " 1.00" when Velocity is not.)
• "Indexed Command" functions may show as "unknown" in the event viewer when such credentials are presented at a reader. This is because the event message format has changed but your Velocity event viewer has not.
• Keypad programming of cards (CMD 310, etc.) only works at readers with odd-numbered addresses (1, 3, 5, etc.).

• Timed Antipassback support. Note that if you're using this for all users, your user capacity will be cut in half. Therefore if you have 2048 or more credentials and you haven't already installed a memory expansion board, you'll need one. Requested by the Velocity development team.
• PZ locations are tracked, even when Passback is disabled by TZ. In other words the controller still tries to remember the last place a user went, even if it's not checking for whether they're allowed to go there.
• Preliminary support for new annunciators TBA.
• Backwards compatibility for Velocity 2.6 and Velocity 3.0 in transaction formatting (Entry/Exit, indexed commands).