DController with firmware (1.19.4), Input 1 becomes inactive or non-responsive.

/in /by

Issue: DController with a specific build of firmware (1.19.4), Input 1 becomes inactive or non responsive and does not report any change of state.

Applies to: DNA Fusion SSP Firmware 1.19.4

Summary: If you experience this issue please use the link below to download an updated version of firmware for the DController.

http://ooaws.openoptionsinc.com/Installs/DNA/V6.2.2.14/SSPD1.crc

Once downloaded, replace the current file (with same name) in the binaries folder:

  • C:\Program Files (x86)\DNAFusion\CRC\

or

  • C:\Program Files (x86)\NPowerDNA\CRC\

Open DNA Fusion and load firmware to any affected DControllers.  The version will still display 1.19.4 in DNA Fusion, however the internal build number is different and the issue should no longer be present.

 

 

New default login security enhancements

/in /by

Issue: New default login security enhancements.

Applies to: DNA Fusion SSP Firmware 1.19.4

Summary: These enhancements are being done to restrict the conditions under which the default login account is enabled exposing the SSP controllers to unauthorized access.

Download PDF w/images: 

Old Firmware
The proper configuration to ensure that the default user account is disabled would be to make sure that at least one user account is been created on the controller’s webpage and that dipswitch 1 is set to the OFF position.

Prior to these security enhancements the default login account was available under the following conditions:

● If no other user accounts had been created the default login account was always enabled.

● If Dipswitch 1 was set to ON then the default login account was enabled.

● It was also possible to create a user account that used the same login and password as the default login account

 

New 1.19.4 Firmware
The Open Options controllers have been modified to ensure that the default login account cannot be left enabled indefinitely. The following changes have been made:

● The default login account is no longer enabled based on the fact that no user accounts have been created.

● To enable the default user account, transition dipswitch 1 from OFF to ON. This will give the user a 5 minute login window.
-A single log in within the 5 minutes or rebooting the board will disable the ability to use the default login account again until dipswitch 1 is transitioned again.

● A user with the password of “password” can not be created. This prevents the addition of a user account with the same credentials as the default user account.

● If attempting to log in using the default credentials prior to dipswitch 1 being transitioned, an error message will be displayed.
-If no user accounts have been created and the default account is used, a warning message will be displayed.

● The controller will perform two verification checks when attempting to apply settings and/or log out. If applicable, warnings will be displayed.
-Validate that the controllers dipswitches have been set to the normal operating mode.
-Verify that at least one user account has been created.
-If either or both of these conditions apply, a warning message will be displayed. To proceed, the warning must be acknowledged

NOTE: If using the ZeroConfig application to configure the controller, an Authentication dialog will appear. Dipswitch 1 must be toggled in order to log in through ZeroConfig the first time; afterwards, the ooAdmin account is added to the Users section. ZeroConfig will need to be closed and reopened for the account to be created as a User.

Installing DNA to Workgroup Peer-to-Peer Network without Domain

/in /by

Issue: Installing DNA to a Workgroup Peer-to-Peer Network without a Domain

Applies to: All versions of DNA Fusion & NPowerDNA

Summary: Follow instructions below. Also see http://www.microsoft.com/resources/documentation/windowsnt/4/
server/reskit/en-us/net/sur_lmh.mspx?mfr=true for more information.

Download PDF w/images: 

Follow the steps below to Install DNA to a Workgroupp Peer-to-Peer Network without a domain:

  1. All computers must have the same User Name & Password. NOTE: A password must be set or the configuration will not work.
  2. All computers must be joined to the same workgroup.
  3. File and Print sharing must be turned on.
  4. Turn OFF simple file sharing in the folder options.
  5. Edit the lmhost file to enable computer name resolution between the Workgroups computers. NOTE: Static IP addresses will need to be set for all of the workgroup computers.
  6. Add the User Name(s) to the DNAUSERS group on all of the workgroup computers.
    To add a user, click the Add button, check the Location and ensure that the workstation is pointed to the proper workgroup, type in the user Log On Name and click Check Names. If it locates the account in question, it will resolve to include the configured information in the name field. Click OK.
  7. Verify that the DNAShare folder is Shared. Locate the file (default location: C:\Program Files (x86)\DNAFusion or C:\Program Files\NPowerDNA), right-click on the folder and select Sharing & Security.
  8. Open the Component Services dialog by selecting Control Panel / Administrative Tools / Component Services.
  9. Double click Component Services and expand the Component Services option.
  10. Expand the Computers options.
  11. Right-click on the My Computer icon and select the Properties menu option.
  12. Select the COM Security tab.
  13. Under Access Permissions, click the Edit Limits button and add the DNAUSERS group.Click the Add button then the location button and select the Local PC Name, click OK, type DNAUSERS in the names field and click Check Names. After the name resolves click OK.
  14. Verify that the ANONYMOUS LOGON & DNAUSERS have the Allow option checked for both Local and Remote Access in the permissions box and click OK.
  15. Add the DNAUsers group to the Edit Limits & Activation Permissions. Click the Edit Limits button and repeat step 13 and 14. Verify that all the Local and Remote access options are checked and click OK.
  16. Double click Component Services and expand the Component Services option until you reach the COM+ Applications level.
  17. Right-click on the DNAFusion (or NPowerDNA) icon and select the Properties menu option.
  18. Select the Identity tab and check the This User radio button, enter a Local Machine Administrator User Name and Password and click OK.
  19. From the Console Root menu, double click Services.
  20. Right-click on the DNAdrvr32 service and select Properties from the menu.
  21. Select the Log On tab.
  22. Select This Account, enter a Local Machine Administrator User Name and
    Password and click OK.
  23. Open the lmhosts file (C:\\Windows\System32\drivers\etc) using Notepad.
    Right-click on the file and select Open With. Choose Select the program from a list and click OK. Select the Notepad
    option from the list.
    By default, Hidden folder cannot seen since they are system folders. To show hidden folders in Windows 7, press the ALT key while in Explorer to open the File menu. Click on Tools and select Folder Options.
    Click the View tab and select the Show hidden files, folders, and drives radio button under Hidden files and folders.
    Note that this method for editing the Hosts file may not work. If a error message regarding permissions is received, the file will have to be edited using the following method:

    1. Click the Start button, in the Search dialog type Notepad.
    2. Right-click on Notepad and select Run as Administrator.
    3. Navigate to the folder again and verify that the All files for File Types is selected.
    4. Make the changes below to the Host file.
    5. Click File and Save to save all changes.
  24. Add the following script to the bottom of the text in the file. This will allow the workstations to resolve the computer names in the workgroup. You can add as many workgroup computers as needed.
    xxx.xxx.xxx.xxx <workgroup computer name> #PRE
    xxx.xxx.xxx.xxx <workgroup computer name> #PRE
    xxx.xxx.xxx.xxx <local computer name> #PRE
    #BEGIN_ALTERNATE
    #INCLUDE\\<local computer name>\public\lmhosts
    #INCLUDE\\<workgroup computer name>\public\lmhosts
    #INCLUDE\\<workgroup computer name>\public\lmhosts
    #INCLUDE\\<workgroup computer name>\public\lmhosts
    #END_ALTERNATE
  25. Save the file and close the window.
  26. Select Start \ Run.
  27. In the Run dialog box, type regedit and click OK. The Registry Editor will open. NOTE: Be careful to not delete any vital information from the registry.
  28. Expand the following path: HKEY_LOCAL_MACHINE \ SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters.
  29. Double click the NullSessionShares option.
  30. Type Public under the last entry in the Edit Multi String window and click OK.
  31. Close the Registry Editor.
  32. Repeat steps 24-32 for all workstations.
  33. Test the setting by pinging the other computers using the computer name instead of the IP address.
    Ping <workgroup computer name>
    If a response is received, install DNAFusion (or NPower DNA) on the client machines.
    If a response is not received, verify that all the workstations are members of the same workgroup and verify that the lmhosts file was saved after editing.

 

Changing Door Mode with Double Swipe of a Card

/in /by

Issue: Changing the Door Mode with a Double Swipe of a Card

Applies to: DNA Fusion version 6.0 and above

Summary: Use the following information to configure DNA Fusion for Door Mode Card Control via a card double swipe.

Download PDF w/images: 

Follow the steps below to resolve common troubleshooting methods:

  1. Configure the SSP to Store Triggers Codes. Since Trigger Codes will be utilized for this example they must be stored in the controllers.
    1. Locate the desired SSP and double-click to open the Properties.
    2. Select the Stored Quantities option from the menu on the left.
  2. Create the Trigger Codes to associate with the Triggers.
    1. From the Main Menu, select Hardware / Trigger Codes. The Trigger Codes dialog will open.
    2. Click the New button and enter a Description for the Trigger Code.
    3. Click OK to save the information.
  3. Create the first Macro to effect the Trigger Variable and change the Door Mode to Unlocked.
    1. From the Triggers & Macros Browser, expand the Macros header until the the desired SSP is displayed.
    2. Right-click on the SSP and select Add Macro. The Macro Editor dialog will open.
    3. Click the Add button and create the Macro Command(s). The Macro Editor opens.
    4. Enter a Description for the Macro.
    5. Click the Add button and create the Macro Command(s). The Macro Editor opens.
    6. Enter a Description for the Macro Command.
    7. Under the Command drop down, select the Reader Mode: Unlocked item.
    8. Select the desired Door.
    9. Click the OK button to save the Macro Command.
    10. Click the Add button and create the Macro Command. The Macro Editor opens.
    11. Enter a Description for the Macro Command.
    12. Under the Command drop down, select the TM: Set Trigger Variable.
    13. Select the desired Trigger Variable. For this example, Trigger Variable 5 has been selected.
    14. Select ON from the Var Setting.
    15. Click the OK button to save the Macro Command.
    16. Click OK to save the Macro.
  4. Create the second Macro to change the Door Mode to Card Only.
    1. Right-click on the SSP and select Add Macro. The Macro Editor dialog will open.
    2. Click the Add button and create the Macro Command(s).
    3. Enter a Description for the Macro Command.
    4. Under the Command drop down, select the Reader Mode: Card Only item.
    5. Select the desired Door.
    6. Click the OK button to save the Macro Command.
    7. Select the desired Trigger Variable. For this example, Trigger Variable 10 has been selected.
    8. Select ON from the Var Setting.
    9. Click the OK button to save the Macro Command.
    10. Click the Add button and another create the Macro Command.
    11. Enter a Description for the Macro Command.
    12. Under the Command drop down, select the TM: Delay Command.
    13. In the Delay field, enter 30 (or the desired delay time).
    14. Click the OK button to save the Macro Command.
    15. Click the Add button and create the Macro Command. The Macro Editor opens.
    16. Enter a Description for the Macro Command.
    17. Under the Command drop down, select the TM: Set Trigger Variable.
    18. Select the desired Trigger Variable. For this example, Trigger Variable 5 has been selected.
    19. Select OFF from the Var Setting.
    20. Click the OK button to save the Macro Command.
    21. Click OK to save the Macro.
  5. Create the Trigger for the Unlock Macro.
    1. Expand the Triggers header until the desired SSP is displayed.
    2. Right-click on the SSP and select Add Trigger. The Trigger dialog opens.
    3. Select the Trigger Event - Door: Double Swipe Event (Controlled).
    4. Select the Door that must be used to Trigger the Macro or select None and any door used by the cardholder will execute the Macro.
    5. Specify the Time Schedule in which the Trigger should operate.
    6. Select the Macro created in step 4.
    7. Select Trigger Variable 5 and check the OFF condition.
    8. If desired, from the Operation drop down, select Require Match 3 or any other value. This location will be referenced in the Cardholder’s
      Record.
    9. If needed, select the Trigger Code created in step 2.
    10. Click the OK button to save the Trigger.
  6. Create a second Trigger for the Card Only Macro.
    1. Right-click on the SSP and select Add Trigger. The Trigger dialog opens.
    2. Select the Trigger Event - Door: Double Swipe Event (Uncontrolled).
    3. Select the Door that must be used to Trigger the Macro or select None and any door used by the cardholder will execute the Macro.
    4. Specify the Time Schedule in which the Trigger should operate.
    5. Select the Macro created in step 4.
    6. Select Trigger Variable 5 and check the ON condition.
    7. If desired, from the Operation drop down, select Require Match 3 or any other value. This location will be referenced in the Cardholder’s Record.
    8. If needed, select the Trigger Code created in step 2.
    9. Click the OK button to save the Trigger.
  7. Assign the Trigger Codes to the desired Cardholder(s).
    1. From the Personnel Browser, open the Cardholder’s Record and select the Card tab.Right-click on the SSP and select Add Trigger. The Trigger dialog opens.
    2. Select the correct referenced Trigger Code, created in step 2, from the Code drop down list.
    3. Select the correct referenced Trigger Code, created in step 2, from the Code drop down list. Verify that the Trigger Code is selected in the correct location (referenced in step 4-7).
    4. Update the Cardholder’s Record.

Changing Door Mode with Double Swipe of a Card while adding delay

/in /by

Issue: Changing the Door Mode with a Double Swipe of a Card while adding delay

Applies to: DNA Fusion version 5.4 and above. For version 6.0, it allows for the use of adding a delay to the command without having to trigger off the
Double Swipe event.

Summary: Use the following information to configure DNA Fusion for Door Mode Card Control via a card double swipe.

Download PDF w/images: 

Follow the steps below to resolve common troubleshooting methods:

  1. Configure the SSP to Store Triggers Codes. Since Trigger Codes will be utilized for this example they must be stored in the controllers.
    1. Locate the desired SSP and double-click to open the Properties.
    2. Select the Stored Quantities option from the menu on the left.
  2. Create the Trigger Codes to associate with the Triggers.
    1. From the Main Menu, select Hardware / Trigger Codes. The Trigger Codes dialog will open.
    2. Click the New button and enter a Description for the Trigger Code.
    3. Click OK to save the information.
  3. Create the first Macro to effect the Trigger Variables.
    1. From the Triggers & Macros Browser, expand the Macros header until the the desired SSP is displayed.
    2. Right-click on the SSP and select Add Macro. The Macro Editor dialog will open.
    3. Enter a Description for the Macro.
    4. Click the OK button to save the Macro.
  4. Create the Trigger (Type 1) for the Macro.
    1. Expand the Triggers header until the desired SSP is displayed.
    2. Right-click on the SSP and select Add Trigger. The Trigger dialog opens.
    3. Select the Trigger Event - Door: Access Granted: (Any Condition).
    4. Click the Add button and create the Macro Command. The Macro Editor opens.
    5. Enter a Description for the Macro Command.
    6. Under the Command drop down, select the TM: Set Trigger Variable.
    7. Select the desired Trigger Variable. For this example, Trigger Variable 10 has been selected.
    8. Select ON from the Var Setting.
    9. Click the OK button to save the Macro Command.
    10. Click the Add button and another create the Macro Command.
    11. Enter a Description for the Macro Command.
    12. Under the Command drop down, select the TM: Delay Command.
    13. In the Delay field, enter 30 (or the desired delay time).
    14. Click the OK button to save the Macro Command.
    15. Click the Add button and create the Macro Command.
    16. Enter a Description for the Macro Command.
    17. Under the Command drop down, select TM: Set Trigger Variable.
    18. Select the desired Trigger Variable. For this example, Trigger Variable 10 has been selected.
    19. Select OFF from the Var Setting.
    20. Click the OK button to save the Macro Command.
    21. Click OK to save the Macro.
  5. Create the second Macro to effect another Trigger Variable.
    1. Right-click on the SSP and select Add Macro. The Macro Editor dialog will open.
    2. Enter a Description for the Macro.
    3. Click the Add button and create the Macro Command(s). The Macro Editor opens.
    4. Enter a Description for the Macro Command.
    5. Under the Command drop down, select the TM: Set Trigger Variable.
    6. Select the desired Trigger Variable. For this example, Trigger Variable 11 has been selected.
    7. Select ON from the Var Setting.
    8. Click the OK button to save the Macro Command.
    9. Click the Add button and another create the Macro Command.
    10. Enter a Description for the Macro Command.
    11. Under the Command drop down, select the TM: Delay Command.
    12. In the Delay field, enter 30 (or the desired delay time).
    13. Click the OK button to save the Macro Command.
    14. Click the Add button and create the Macro Command.
    15. Enter a Description for the Macro Command.
    16. Under the Command drop down, select the TM: Set Trigger Variable option.
    17. Select the desired Trigger Variable. For this example, Trigger Variable 11 has been selected.
    18. Select OFF from the Var Setting.
    19. Click the OK button to save the Macro Command.
    20. Click OK to save the Macro.
  6. Create another Macro to change the Door Mode to Card Only.
    1. Right-click on the SSP and select Add Macro. The Macro Editor dialog will open.
    2. Enter a Description for the Macro.
    3. Click the Add button and create the Macro Command.
    4. Enter a Description for the Macro Command.
    5. Under the Command drop down, select the Reader
      Mode: Card Only item.
    6. Select the desired Door.
    7. Click the OK button to save the Macro Command.
    8. Click OK to save the Macro.
  7. Create the first Trigger for the Trigger Variable 10 Macro.
    1. Expand the Triggers header until the desired SSP is displayed.
    2. Right-click on the SSP and select Add Trigger. The Trigger dialog opens.
    3. Select the Trigger Event - Door: Access Granted: (Any Condition).
    4. Select the Door that must be used to Trigger the Macro or select None and any door used by the cardholder will execute the Macro.
    5. Specify the Time Schedule for the Trigger.
    6. Select the Macro created in step 3.
    7. Select Trigger Variable 10 and check the OFF condition.
    8. From the Operation drop down, select Require Match 2 or any other value. This location will be referenced in the Cardholder’s Record.
    9. Select the Trigger Code created in step 2.
    10. Click the OK button to save the Trigger.
  8. Create a second Trigger for the Unlock Macro.
    1. Right-click on the SSP and select Add Trigger. The Trigger dialog opens.
    2. Select the Trigger Event - Door: Access Granted: (Any Condition).
    3. Select the Door that must be used to Trigger the Macro or select None and any door used by the cardholder will execute the Macro.
    4. Specify the Time Schedule in which the Trigger should operate.
    5. Select the Macro created in step 5.
    6. Select Trigger Variable 10 and check the ON condition.
    7. From the Operation drop down, select Require Match 2 or any other value. This location will be referenced in the Cardholder’s Record.
    8. Select the correct Trigger Code created in step 2.
    9. Click the OK button to save the Trigger.
  9. Create the next Trigger to execute the Trigger Variable 11 Macro.
    1. Right-click on the SSP and select Add Trigger. The Trigger dialog opens.
    2. Select the Trigger Event - Door: Access Granted: Unlocked.
    3. Select the Door that must be used to Trigger the Macro or select None and any door used by the cardholder will execute the Macro.
    4. Specify the Time Schedule in which the Trigger should operate.
    5. Select the Macro created in step 4.
    6. Select Trigger Variable 11 and check the OFF condition.
    7. From the Operation drop down, select Require Match 2 or any
      other value. This location will be referenced in the Cardholder’s Record.
    8. Select the correct Trigger Code created in step 2.
    9. Click the OK button to save the Trigger.
  10. Create the last Trigger to execute the Card Only Macro.
    1. Right-click on the SSP and select Add Trigger. The Trigger dialog opens.
    2. Select the Trigger Event - Door: Access Granted: Unlocked.
    3. Select the Door that must be used to Trigger the Macro or select None and any door used by the cardholder will execute the Macro.
    4. Specify the Time Schedule in which the Trigger should operate.
    5. Select the Macro created in step 6.
    6. Select Trigger Variable 11 and check the ON condition.
    7. From the Operation drop down, select Require Match 2 or any other value. This location will be referenced in the Cardholder’s Record.
    8. Select the correct Trigger Code created in step 2.
    9. Click the OK button to save the Trigger.
  11. Assign the Trigger Codes to the desired Cardholder(s).
    1. From the Personnel Browser, open the Cardholder’s Record and select the Card tab.
    2. Select the correct referenced Trigger Code, created in step 2, from the Code drop down list.
    3. Select the correct referenced Trigger Code, created in step 2, from the Code drop down list. Verify that the Trigger Code is selected in the correct location (referenced in step 4-7).
    4. Update the Cardholder’s Record.

 

Using a Card to Change Door Mode (V5.4)

/in /by

Issue: Using a Card to Change the Mode of a Door

Applies to: DNA Fusion version 5.4 only

Summary: Use the following information to configure DNA Fusion for Door Mode Card Control.

Download PDF w/images: 

Follow the steps below to use a card to the change the mode of a door:

  1. The SSP will need to be configured to Store Triggers Codes. Since Trigger Codes will be utilized for this example they must be stored in the controllers.
    1. Locate the desired SSP and double-click to open the Properties.
    2. Select the Stored Quantities option from the menu on the left.
  2. Create the Trigger Code to associate with the Trigger.
    1. From the Main Menu, select Hardware / Trigger Codes. The Trigger Codes dialog will open.
    2. Click the New button and enter a Description for the Trigger Code.
    3. Click OK to save the information.
  3. Create the Macro to change the Door Mode.
    1. From the Triggers & Macros Browser, expand the Macros header until the the desired SSP is displayed.
    2. Right-click on the SSP and select Add Macro. The Macro Editor dialog will open.
    3. Click the Add button and create the Macro Command(s).
    4. Click the OK button to save the Macro.
  4. Create the Trigger for the Macro.
    1. Expand the Triggers header until the desired SSP is displayed.
    2. Right-click on the SSP and select Add Trigger. The Trigger dialog opens.
    3. Select the Trigger Event - Door: Access Granted: (Any Condition).
    4. Select the Door that must be used to Trigger the Macro or select None and any door used by the cardholder will execute the Macro.
    5. Specify the Time Schedule in which the Trigger should operate.
    6. Select the Macro created in step 3.
    7. From the Operation drop down, select Require Match 1 or any other value. This location will be referenced in the Cardholder’s Record.
    8. Select the Trigger Code created in step 2.
    9. Click the OK button to save the Trigger.
  5. Assign the Trigger Code to the desired Cardholder(s).
    1. From the Personnel Browser, open the Cardholder’s Record and select the Card tab.
    2. Select the Trigger Code, created in step 2, from the Code drop down list. Verify that the Code is selected in the correct location (referenced in step 4-7).
    3. Select the Host Macro Edit button. The Host Based Macro dialog will appear
    4. Select the desired Action 1-4 Event ID from the drop down list.
    5. If desired, select an Internal Time Schedule.
    6. Specify the Door Address in the Remote Object fields.
    7. Click OK to save the Host Based Macro. The Host Based Macro is added to the Cardholder’s Record.
  6. If additional hardware control is desired, add additional Commands to the Macro. Remember to create a separate Trigger for the additional Macro command.

 

Using a Card to Change Door Mode (v6.0 and Above)

/in /by

Issue: Using a Card to Change the Mode of a Door

Applies to: DNA Fusion version 6.0 and above

Summary: Use the following information to configure DNA Fusion for Door Mode Card Control.

Download PDF w/images: 

Follow the steps below to use a card to change the mode of a door:

  1. The SSP will need to be configured to Store Triggers Codes. Since Trigger Codes will be utilized for this example they must be stored in the controllers.
    1. Locate the desired SSP and double-click to open the Properties.
    2. Select the Stored Quantities option from the menu on the left.
  2. Create the Trigger Code to associate with the Trigger.
    1. From the Main Menu, select Hardware / Trigger Codes. The Trigger Codes dialog will open.
    2. Click the New button and enter a Description for the Trigger Code.
    3. Click OK to save the information.
    4. Repeat this process to add an additional Trigger Code.
  3. Create the Macro to change the Door Mode.
    1. From the Triggers & Macros Browser, expand the Macros header until the the desired SSP is displayed.
    2. Right-click on the SSP and select Add Macro. The Macro Editor dialog will open.
    3. Click the Add button and create the Macro Command(s). As an example: a Type 1 Macro can be added to change a reader mode to Unlock and Trigger Variable 1 to turn ON. A Type 2 Macro would be created to change the reader mode to Card Only and turn Trigger Variable 1 OFF. Trigger Variables provide the Triggers another condition to look for before executing the Macro.
    4. Click the OK button to save the Macro.
  4. Create the Trigger (Type 1) for the Macro.
    1. Expand the Triggers header until the desired SSP is displayed.
    2. Right-click on the SSP and select Add Trigger. The Trigger dialog opens.
    3. Select the Trigger Event - Door: Access Granted: (Any Condition).
    4. Select the Door that must be used to Trigger the Macro or select None and any door used by the cardholder will execute the Macro.
    5. Specify the Time Schedule in which the Trigger should operate.
    6. Select the Macro created in step 3 and select execute Type 1.
    7. Select Trigger Variable 1 and check the OFF condition.
    8. From the Operation drop down, select Require Match 1 or any other value. This location will be referenced in the Cardholder’s Record.
    9. Select the correct Trigger Code created in step 2.
    10. Click the OK button to save the Trigger.
  5. Create the Trigger (Type 2) for the Macro.
    1. Right-click on the SSP and select Add Trigger. The Trigger dialog opens.
    2. Select the Trigger Event - Door: Access Granted: Unlocked.
    3. Select the Door that must be used to Trigger the Macro or select None and any door used by the cardholder will execute the Macro.
    4. Specify the Time Schedule in which the Trigger should operate.
    5. Select the Macro created in step 3 and select Execute Type 2.
    6. Select Trigger Variable 1 and check the ON condition.
    7. From the Operation drop down, select Require Match 2 or any other value. This location will be referenced in the Cardholder’s Record.
    8. Select the correct Trigger Code created in step 2.
    9. Click the OK button to save the Trigger.
  6. Assign the Trigger Codes to the desired Cardholder(s).
    1. From the Personnel Browser, open the Cardholder’s Record and select the Card tab.
    2. Select the correct referenced Trigger Code, created in step 2, from the Code drop down list.
    3. Select the correct referenced Trigger Code, created in step 2, from the Code drop down list. Verify that the Trigger Code is selected in the correct location (referenced in step 4-7).
    4. Update the Cardholder’s Record.

 

Common Troubleshooting Methods

/in /by

Issue: Common Troubleshooting Methods

Applies to: Flex API / DNAFusion v.6 and above

Summary: Use the following information to troubleshooting the Flex API.

Download PDF w/images: 

Follow the steps below to resolve common troubleshooting methods:

  1. The Flex API Windows Driver is missing from the Windows Services. If the DNA Fusion Flex Service is not installed using the FlexAPI setup follow the steps below:
    1. Open a Windows Command Console dialog. Start/Search/cmd
    2. Type the command below and click Enter: C:\>”C:\Program Files (x86)\Flex API\OpenOptions.dnaFusion.Flex.exe” install. The dnaFlex Service will be installed.
  2. The dnaFusion Flex Service will start and stop. If the Log File (C:\ProgramData\Open Options, Inc\Flex\Log Files\Flex.sil) is opened, there will be two lines indicating an error opening the database.
    OpenOptions.DUST.OpenAccess.DUST.Execute
    OpenOptions.DUST.OpenAccess.DUST.Execute

    1. Run the dnaFusion Flex service with an account with sufficient rights to the database. The dnaFusion Flex service is typically configured to run using same account that the DNADrvr32 windows service utilizes.
    2. If needed, create a service account and grant db_datareader, db_datawriter, and db_ddladmin roles to the DNAFusion database.
    3. See Configuring the FlexAPI Service in the FlexAPI manual.
  3. The Flex API Configuration Tool crashes when launched. This is normally caused when the Bindings are invalid or are already in use by another program.
    1. Edit the app.config file in NotePad.exe to remove the bindings. Default location: C:\ProgramData\Open Options, Inc\Flex\app.config
    2. Delete the bindings and save the file.
    3. See Configuring Site Bindings in the FlexAPI manual.

 

Upgrading with 500,000 rows in transaction table.

/in /by

Issue: Upgrading to version 6 with more than 500,000 rows in the transaction table.

Applies to: DNAFusion v.6 and above

Summary: During the upgrade process, a new Transactions table will be created and the existing Transaction table data will be moved.

Download PDF w/images: 

Follow the steps below to upgrade with more than 500,000 rows in the transaction table:

  1. The DNAFusion 6.0 upgrade determines that there are more than 500,000 rows in the TRANSACTIONS table, a dialog box will appear.
  2. Click the Next button. This step will do the following:
    1. The existing TRANSACTION table will have all the indexes (except the Primary Key) and constraints removed.
    2. The TRANSACTION table (TRANSACTIONS5x) and Primary Key (PK_TRANSACTIONS ) are renamed.
    3. The most recent 50,000 transactions will be moved from the TRANSACTIONS5x table to the TRANSACTIONS table.
  3. Restart the DNAdrvr32 driver. Once the driver is restarted, the remaining balance of the transactions will start to be moved.
    By default this process will run between 1:00am and 4:00am every day. During this period 1,000 records will move from the TRANSACTIONS5x table to the TRANSACTIONS tables every 30 seconds. This process will move approximately 360,000 transactions per day. When the TRANSACTIONS5x table
    is empty, it should be dropped automatically. There is currently no user interface to change the default values.

 

Controlling Reader LED Mode

/in /by

Issue: Controlling reader LED Mode

Applies to: All version of DNA Fusion

Summary: Configuring a reader to control 3 different LED colors based on various events. There are 3 items that must be configured to complete the LED control setup: verify the reader is wired correctly, create the Macros and setup the Triggers.

Download PDF w/images: 

Follow the steps below to configure LED Mode on reader:

  1. Verify that the reader is wired correctly.
  2. Locate the desired Reader under the Door in the Hardware Browser.
  3. Double click on the Reader to open the Properties.
  4. From the Templates Name field, select the Proximity.rtp and click the OK button.
  5. Open the desired Door Properties and select the Door Objects item from the menu on the left.
  6. Click the Edit button next to the LED Mode field.  The LED Configuration dialog opens.
  7. Change the values for the desired Reader Modes and click the OK button.  The color options are Red, Green and Amber for each function.  For this example, the setting for the Card Only options are follows:
    1. Short Red Pulse: Download=Yes, On Color=Amber, Off Color=Amber, On Time=x ms, Off Time=x ms
    2. Solid Red Short Pulse: Download=Yes, On Color=Red, Off Color=Red, On Time=x ms, Off Time=x ms
    3. Solid Green Short Pulse: Download=Yes, On Color=Green, Off Color=Green, On Time=x ms, Off Time=x ms

    NOTE: This is a global change across all controllers and there is a maximum of three LED tables that may be
    used.

  8. When the Download dialog appears, click Yes to continue.
  9. From the LED Mode drop down list, select the Short Red Pulse option and click OK.  The reader will now follow this color scheme when in Card Only mode.
  10. When the Download dialog appears, click Yes to confirm.
  11. Open the Triggers & Macros Browser, expand the Macros header and right-click on the desired SSP.
  12. Right-click on the desired SSP under the Macros header and select Add Macro.  The Macros Editor opens.
  13. Enter a Description for the Macro and click the Add button.  The Macro Command Editor opens.
  14. Select the following options:
    1. Command = Reader LED Control
    2. ACM = Select the desired Door.
    3. LED Index = 116. Click OK to save the Macro Command.  The command is added to the Macro.
  15. Click the Add button again and use the following settings.
    1. Command = Set Trigger Variable
    2. Trigger Var = Variable 1
    3. Var Setting = OFF
  16. Click OK to save the Macro Command.
  17. Click Add and use the following settings for the Macro Command.
    1. Command = CP: Deactivate
    2. Control Point = Select the desired Output.
  18. Click OK to save the Macro Command.  The command is added to the Macro.
  19. Click the OK button to save the Macro.  The Macro is added to the SSP’s Macros list.
  20. Right-click on the SSP under the Macros header and select Add Macro.  The Macros Editor opens.
  21. Enter a Description and click the Add button.  The Macro Command Editor opens.
  22. Use the following settings:
    1. Command = Reader LED Control
    2. ACM = Select the desired Door
    3. LED Index = 2
  23. Click OK to save the Macro Command.  The command is added to the Macro.
  24. Click the Add button again and use the following settings.
    1. Command = Set Trigger Variable
    2. Trigger Var = Variable 1
    3. Var Setting = ON
  25. Click OK to save the Macro Command.
  26. Click the Add button and use the following settings.
    1. Command = CP: Activate
    2. Control Point = Select the desired Output.
  27. Click OK to save the Macro Command.  The command is added to the Macro.
  28. Right-click on the SSP again and select Add Macro.  The Macros Editor opens.
  29. Enter a Description and click the Add button.  The Macro Command Editor opens.
    Use the following settings:

    1. Command = Reader LED
    2. ControlACM = Select the desired Door
    3. LED Index = 331.
  30. Click OK to save the Macro Command.  The command is added to the Macro.32. Click the Add button again and use the following settings.
    1. Command = Set Trigger VariableTrigger
    2. Var = Variable 1
    3. Var Setting = ON
  31. Click OK to save the Macro Command.
  32. Click OK to save the Macro Command.  The command is added to the Macro.
  33. Repeat the above steps above to create the macros to control the LED colors on the readers based on the different desired scenarios.  These steps will need to be completed for each door that will utilize the LED color change feature so a macro will need to be created for the three different macros (one for each color).
    NOTE: When creating the other Macros, be sure to use a different Trigger Variable for each door.  Once the Macros have been configured, Triggers will need to created to execute the Macros.
    In this example, a valid card read will change the reader LED to green until a second card presentation returns the LED to yellow.  Once the first functional Trigger & Macro series is complete, the Triggers and Macros can be copied to speed up the programming process.
  34. To create the Trigger, right-click on the SSP under the Triggers header and select Add Trigger.  The Triggers Editor opens.
  35. Enter a Description and use the following settings:
    1. Trigger Event = Access Granted
    2. ACM = Select the desired Door or select None to use any door.
    3. Schedule = If desired, select a time schedule. This will limit the timeframe the trigger will fire.
    4. Macro ID = Select the Green LED Macro created earlier.
    5. Trigger Variable (Slot 1) = Variable 1 OFF (This will change for each door)
  36. Click OK to save the Trigger.  The Trigger is added to the list.
  37. Right-click on the SSP again and select Add Trigger.  The Triggers Editor opens.
  38. Enter a Description and use the following settings:
    1. Trigger Event = Access Granted
    2. ACM = Select the desired Door or select None to use any door.
    3. Schedule = If desired, select a time schedule. This will limit the timeframe the trigger will fire.
    4. Macro ID = Select the Yellow LED Macro created earlier.
    5. Trigger Variable (Slot 1) = Variable 1 ON (This will change for each door).
  39. Click OK to save the Trigger.  The Trigger is added to the list.
  40. The last command will be configured so if the door is forced open (while the reader’s LED is yellow), the reader LED will turn red and a designated output will be activated.
  41. Right-click on the SSP and select Add Trigger.  The Triggers Editor opens.
  42. Enter a Description and use the following settings:
    1. Trigger Event = DOOR: ALARM (Forced, Held or Both)
    2. ACM = Select the desired Door.
    3. Schedule = If desired, select a time schedule. This will limit the timeframe the trigger will fire.
    4. Macro ID = Select the Red LED Macro created earlier.
    5. Trigger Variable (Slot 1) = Variable 1 OFF (This will change for each door).
    6. Alarm Msg = Forced Open Only (held following forced does NOT trigger)
  43. Click OK to save the Trigger.  The Trigger is added to the list.