Velocity 3.5 Release Notes

Last updated on December 11, 2015.

Velocity 3.5 (Build 1390)

This DVD contains Velocity 3.5 (for NEW installations) and a Velocity 3.5 Upgrade (from Velocity 3.1 KB630). (Part number: VEL35-XXX, where XXX=the edition purchased, such as WS=Workstation edition).

Velocity is now available in different editions to suit the scale and scope of your project:

Workstation is for smaller systems with up to 32 doors.

Corporate is for larger scale installations with a server, up to 10 clients, and up to 128 doors.

Federal is for government organizations that require the scale of the Corporate edition and also require the Velocity Cert Service (optional on other certain editions) add-on for registration of TWIC, CAC, PIV-I, and CIV cards, and the monitoring of CAK and PAK.

Enterprise Level 1 is for full-scale installations with 25 or more clients, 256 or more doors, and advanced configurations.

For details, see the Velocity product page.

Upgrade Paths

Upgrading from 3.1 to 3.5

If Velocity 3.1 (KB630) is already installed, you can simply run the Velocity 3.5 Upgrade on this disc.

Upgrading from Older Versions to 3.5

If Velocity 2.6 SP2 or 3.0 is already installed, you must first upgrade it to Velocity 3.1 (KB630). The upgrade files are not on this Velocity 3.5 installation DVD. Note: If you are currently running a Velocity system older than 2.6 SP2 contact your local Hirsch Dealer or Hirsch Sales representative.

For an older version of Velocity (,,,,, other updates are required to first bring the installation to the Velocity 2.6 Service Pack 2 level.  If you are at version 2.0 ( then the upgrade sequence will be as follows: VEL-UPD25 > VEL-UPD26 > VEL-UPD26sp1 > VEL-UPD26sp2.

The service packs are available on the Hirsch Identive website. VEL-UPD25 and VEL-UPD26 must be purchased. Alternately, part number VEL-UPDSUITE can be purchased for installations at version 2.0 or older. It contains all the required upgrades from 2.0 to 2.6 SP2.

Note that your existing hardware, Velocity database, and operating system might not be compatible with Velocity 3.5. Contact Inside Sales or Technical Support if you are planning a major upgrade.

Installation Prerequisites:

Minimum Recommended Hardware Requirements


For Velocity servers:

• Intel Xeon® E3-1220 3.10 GHz Turbo Quad Core/4T processor with 8MB cache

(or equivalent)

• 4GB DDR3 SDRAM (1333MHz)

• 300GB 15K RPM SAS hard drive

• 16X DVD+/-RW drive

• Mouse/Keyboard

• 20-inch LCD monitor

• 1GB video card

• Sound card/chip and speakers

• 1 eSATA Port

• 1 GB Ethernet RJ-45 port


For Velocity workstations or clients:

• Intel Core i7 Quad Core 3.4GHz processor with 8MB cache

(or equivalent)

• 4GB DDR3 SDRAM (1333MHz)

• 250GB 6.0Gb/s SATA hard drive

• 16X DVD+/-RW drive

• Mouse/Keyboard

• 20-inch LCD monitor

• 1GB video card

• Sound card/chip and speakers

• 1 serial port

• 1 GB Ethernet RJ-45 port

Operating System and Service Pack Requirements

Server: Windows Server 2008 R2 64-bit Standard or Enterprise edition.

Workstation: Windows 7 SP1 32-bit or 64-bit Professional, Ultimate, or Enterprise edition.

Client: Windows 7 SP1 32-bit or 64-bit Professional, Ultimate, or Enterprise edition. Or Windows XP SP3 32-bit or 64-bit Professional edition.

Note: Velocity Web Console requires the Windows component IIS (Internet Information Services) to be enabled. Refer to the Velocity 3.5 Installation Guide.

Database Platform

Server: SQL Server 2008 R2 64-bit Standard, Workgroup, or Enterprise edition with SP1.

Workstation: SQL Server 2008 R2 Express (included with Velocity 3.5).

Client: Database connection to Server.

CCM Firmware Requirements

The Velocity 3.5 release requires that you be running DIGI*TRAC CCM Firmware 7.4.53 or higher. Updating to 7.4.53 will also update the CCM BIOS to the current version. Failure to perform this update may result in unpredictable product behavior. The most recent CCM firmware can be found in the \Velocity\Firmware\DIGITRAC directory on this Velocity 3.5 DVD.

CCM Update Information

Refer to the CCM release notes for more detailed information.

SNIB2 Firmware Requirements

Velocity 3.5 requires that you be running SNIB2 Firmware 5.99 or higher.

XBOX Firmware Requirements

Velocity 3.5 is optimized for communication over SNIB2, however for legacy installations ensure that any XBOX is running XBOX Firmware 2.45 or 3.15.

Installation Notes

Confirm all your installed hardware meets the required firmware revisions for Velocity 3.5:

·         CCM Firmware must be 7.4.53 or higher

·         SNIB2 Firmware must be 5.99 or higher (preferred host/controller connection)

·         XBOX Firmware must be at 2.45 or 3.15

Before installing Velocity, you must be logged into the Server with an "account" that has Administrator rights. If you attempt to install without such rights, the Installer will stop. During the installation process you will be prompted to enter a password for a Windows account the installer will create for the Velocity Services. This password must meet the complexity standards enforced by the Windows Administrator, and if it does not you may receive the following message: The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.

If you are installing Velocity Server Edition or are installing on a Windows Domain Controller, you must be logged into Windows with an account that has Domain Admin rights so the installer can create the domain user group "Velocity Users", the domain user account "VelocityServices", and the group "Velocity Services" which are needed to log in the Velocity services when the system starts. This is also required if the SQL Server database is on a remote machine. If you do not have Domain Admin rights, contact your System Administrator for assistance with creating these accounts and groups before you install Velocity.

What's New?

The following are new features in Velocity 3.5:

Enhanced UI

The user interface has been updated with Windows™ 7 user interface elements that provide numerous options for large format screen/multi-screen set-ups, with the ability to dock and undock multiple windows with the Velocity main window. The Velocity main window and the Badge & Graphic Designer now have a “ribbon” interface similar to that introduced by Microsoft in Office 2007. Some of the tools open in a movable pane within the Velocity main window, while other tools open in a separate window which still has the traditional menu bar and toolbars.

Velocity Web Console (VWC)

The VWC is a web interface that enables administrators and system users to access various functional elements of Velocity without the need for a dedicated machine. VWC allows enrollment, reporting, alarm monitoring and control, and override of controlled building systems (lighting, elevators, HVAC, etc.). Optimized for Internet Explorer 9 and FireFox 14, VWC can be accessed through fixed or mobile devices. Workstation, Corporate, Federal, and Enterprise Level 1 editions of Velocity can be accessed by an almost unlimited number of remote web-clients. However, VWC cannot connect to multiple servers simultaneously. For multiple server installations, contact Professional Services or Inside Sales and ask about the Enterprise Management Framework product.

Engine Optimization

‘Under the hood’ enhancements have been implemented that improve the speed and reliability of many of the core Velocity and DIGI*TRAC controller functions, including alarm monitoring and graphics.

XML Writer removed from Velocity’s Server Extensions

The XML Writer server extension (and its associated role permissions) has been removed from Velocity, starting with this release. If you were using the XML Writer, you will need to rewrite your application so it uses the Message Queue Writer instead. See the Interfaces Configuration > Writers (E-mail, Message Queue, and Serial Port) > Message Queue Writers topic in Velocity’s online help system. If you need additional assistance, contact Identiv’s Technical Support department.

3.1 KB Features Rolled Into 3.5

All the functionality added in 3.1 KBs has been incorporated into Velocity 3.5, including:

Support for 200-Bit Cards and Third-Party Keypad (KB630)

Velocity now has enhanced support for FIPS201 PIV cards, by supporting PIV readers outputting entire 200-Bit FASCN over Wiegand, including readers with Third-Party Keypads (non-ScramblePad versions) and readers with multi-technology capability (which output multiple Wiegand formats). To use this feature, you must be running the following:

• CCM firmware version 7.4.53 or later
• MATCH2 version 120411 or later

These enhancements are configured by using Velocity features within KB630 for enabling and setting up the 200-bit FASCN and its 9 fields, as well as defining ‘Special Handling’ and ‘Hex Pass-Though’ features when using multi-technology readers. For more information on using this feature, see Velocity Help.


Support for PIV cards and FASC-N on the same Reader as Wiegand Hex Pass-through (KB630)

Velocity now has improved support for blended environments which use multi-technology readers that concurrently read FIPS201 PIV credentials and other card types, such as commercial smartcards and traditional proximity cards. PIV card formats are specifically identified and accommodated with the ‘Special Handling’ feature. This is particularly useful when using the ‘Hex Pass-Through’ feature to accommodate commercial card formats that exceed 48 bits, such as DESFire CSN (56-bit). For more information on using this feature, see Velocity Help.


Support for 56-bit DESFire and MiFare ID cards—Wiegand Hex Pass-through (KB610)

Velocity now supports 56-bit DESFire Cards. Previously, card ids were limited to 48 bits. The Wiegand Hex Pass-through setting in Velocity’s Enrollment Manager enables a MATCH2 to read cards in a hexadecimal format. This feature enables the use of cards that carry up to 62 bits of information, including DESFire and MiFare cards. To use this feature, you must have:

• CCM firmware version 7.4.47 or later
• MATCH2 version 061030 or later

See the Velocity Administrator’s Guide or Velocity Help for more information on using this feature.


Ability to Customize Alarm Inputs to Report as Events Only (KB610)

You can now customize specific inputs to report as events only. Previously, all inputs would automatically register as alarms. These modified alarms can retain all alarm functions while reporting as an event. For more information on using this feature, see the Velocity Administrator’s Guide or Velocity Help.


Support for Custom Active Directory User Group and User Names (KB610)

Velocity now supports the use of custom user group and user names. This setting prevents the system from using the default “Velocity Users” and "Velocity Services" group in Active Directory, and the default "VelocityServices" user that starts Velocity Services. Use of this feature requires an advanced understanding of domain and database administration. Before implementing Custom Velocity Users Group Names, contact Hirsch Technical Support for instructions.

Known Issues

The following are known issues in the Velocity 3.5 release:






Velocity does not support computer names longer than 15 characters due to Microsoft's implementation of NETBIOS.



The SCM (Service Control Manager) cannot Start/Stop services unless the "Run as Administrator" property on the executable file has been manually set.



Intellex DVR video cannot be viewed from Windows 2008R2 Server.



Pelco DVR is currently not functioning.