SI1
What is the procedure for migrating ADI to a new computer?   
Follow these steps to move your existing ADI data files and settings to a new computer:

• On the old computer, set the ADI password to [blank], if one exists.
  
• Shut ADI down.
  
• Copy ADI's \Local and \Logs folders from the current directory to a network or temporary storage device such as a thumb drive. Depending on your version of ADI, the default installation location is either C:\FDCMS\Alarm Data Interface or C:\Program Files\FDCMS\Alarm Data Interface.
  
• On the new computer, completely disable Windows User Account Control.
  
• Install ADI on to the new computer. You can either use your existing archived version of ADI or download the current version from www.fdcms.com.
  Note: You will need an active service agreement to run the currently published version of ADI.
  
• Start ADI and enter your assigned Agency Key in order to activate it.
  
• Once you have successfully activated ADI, close the application.
  
• Copy the \Local and \Logs folders from your thumb drive to the \Alarm Data Interface folder on the new computer. You will end up overwriting the existing folders.
  
• Restart ADI and verify that all of your incident data and settings are intact. Re-enter a password, if desired.

Affected Programs : ADI
Applicable Operating Systems: All
Applicable Territories:   All

Last Reviewed: 1/26/20

SI2
Some newly-added incident types do not trigger a notification   
Follow these steps to allow all selected incident types to be sent as a notification:

• Shut ADI down.
  
• Update ADI to the latest version.
  
• Using Windows File Explorer, delete ADI's Local database. The default path is 'C:\FDCMS\Alarm Data Interface\Local\adiLocal.mdb'
  Note: If you have custom entries in the NFIRS column of the NFIRS Incident Type Codes table then they will be defaulted and will need to be re-entered.
  
• Start ADI.
  
• Log in to the Full Menu and click Notification / Incident Types...
  
• Select the first Group Name (usually 'All Calls')
  
• Click the [Initialize All] button and then acknowledge.
  
• Click the [Enable All] button.
  
• Click the yellow [Save] button.
  
• Perform this procedure in the Notification Incident Type Assignment form for other Group Names, if desired.
• Click the green [OK] button when finished.

Affected Programs : ADI
Applicable Operating Systems: All
Applicable Territories:   All

Last Reviewed: 9/26/20

SI7
Our ADI computer is kept out in the open where our members have access to it. We want to keep our members from using the computer to surf the web. What is the best way to prevent this while allowing ADI to do its job?   
The best way to prevent unauthorized users from accessing the computer's Desktop is to just lock the computer when you are not using it. Do not sign out of the Windows account. To lock the computer press the key + "L". This will lock the computer and only allow an administrator or the owner of the account that locked it to unlock it. ADI will function normally while the computer is locked.

Affected Programs :ADI
Applicable Operating Systems: All
Applicable Territories:              All

Last Reviewed: 1/26/20

SI10
We often see garbage characters come through in the middle of our data received from the dispatch center.   
Extraneous characters in data can cause ADI to misinterpret what it receives from your dispatch center. This issue can range from strange characters in your printouts to actually causing your received data to be ignored by ADI, thus not properly processing as it should. This is most likely caused by a weak data radio signal. If you are using a data radio to receive your dispatch information you may need to either relocate the receiver or add an external antenna. Once the signal reception has improved your data will be cleaner and ADI will be able to function properly.

Affected Programs : ADI
Applicable Operating Systems: All
Applicable Territories:   Montgomery, PA

Last Reviewed: 1/26/20

SI11
What is the longest cable length that can be used with my LED Sign?   
IDEx Controller uses serial RS-232 to send data to any connected Alpha LED sign boards. The RS-232 standard was originally written to allow a cable length of 50' or a length that did not allow the capacitance of the cable to exceed 2500 pF (pico farads). Because the cable that we use has an inherent low capacitance per foot, we are able to safely exceed the 50' standard. Our custom made cables are rated at 17 pF per foot, The original RS-232 standard was based on a maximum Baud rate of 20,000. FSID is only allowed to transmit data at a maximum Baud rate of 9600 so, at that rate, a cable length of 300' feet is not out of the question. It should also be noted that as the transmitted Baud rate is reduced, the cable length can be proportionally increased.

Affected Programs : IDEx Controller
Applicable Operating Systems: All
Applicable Territories:   All

Last Reviewed: 1/26/20

SI13
I am getting a message that says 'A password mismatch was detected' and ADI will not start.   
This condition is usually the result of ADI's password not being cleared (reset to blank) prior to upgrading to version 8.xx or higher. However, it can also occur if your computer's time setting is out of sync by more than 30 days or if your Internet Explorer core files are corrupt. To resolve the IE issue perform the following steps:

• In Internet Explorer, click the 'Tools' or gear icon.
• Click 'Internet Options' from the menu.
• Click the 'Advanced' tab.
• Click the 'Reset...' button.
• Click the 'Reset' button and then close the form.

Affected Programs : ADI
Applicable Operating Systems: All
Applicable Territories:   All

Last Reviewed: 1/26/20