FAQs

The IXP220 controller has not been unlocked for “SYSTEM 2” or a “SYSTEM” controller, therefore blocking the terminal bus. If a Controller is a “Stand-alone” controller, the RS485 bus is locked.

The ImproX RS with the SYSTEM 3 (ISW903) unlock has been removed from the computer. This is because you have assigned more doors than allowed for the current license.

Unfortunately not. The web enrolment feature was only designed to add tags and PACs (Personal access codes) only.

Yes. The software can communicate to controllers via RS232,RS485,USB and Ethernet controllers at the same time. (Note: this applies to multiple controllers and not a single controller).

No, the IXP220 software suite is not designed to be installed on Linux.

No. Client-Server architecture is not supported; however it is possible to edit Tagholders using the Web QuickTag feature.

The “mode” on the controller has not been set to “Action”, this mode can be changed on the controller tab. Note: after changing this mode, a full upload has to be performed.

The Controller is not a system Controller. If a controller is a “stand-alone” controller and the site is higher than a “system 1”, all “stand-alone” controllers will be automatically disabled, and the Software will not communicate with them. If a controller is a “stand-alone” controller the RS485 Terminal bus of the controller is disabled.

• Check that the Windows Firewall is not blocking Web Reports connection.
• Make sure that IIS (Internet Information services) is disabled for Windows XP and Vista.
• In 'Control Panel', check that Firebird is installed and running.
• Make sure the port for Web Reports is not being blocked by other programs such as Skype or MSN.

• If you are using a Registration reader, make sure that it has been enabled in the software in the advanced configuration.
• Check the DIP switches on the Registration Interface if using the 3rd Party Port on the RS (ISW903).
• If you are not using a registration reader, check to see that the correct reader (Entry/Exit) has been selected in the advanced configuration on the Tagholder enrolment screen. Make sure you hold the tag in front of the reader long enough for the reader to read the tag. Occasionally you may need to click “read tag” before you present the tag to the reader.

• Make sure Firebird is running. Check to see if CAPSLOCK is on; if it is, turn it off.
• Make sure you are entering the username and password correctly.
• Make sure the Firebird port number is correct (3050) if you are connecting a port number other than port 3050, append a colon (:) to the server name i.e. localhost:3055.
• Check that the correct version of Firebird is installed (v2.1).
• Make sure the COM port for the USB device is not higher than COM16.
• Check that the database path is correct. The Database cannot reside on a shared folder on another PC, use the full server name and local path on the remote PC.

Yes, this is possible. Install the software first on the Client PC (the pc you want to run the software from), the software will automatically install the Firebird Service, just let the Software install as normal. Copy the “DB220.fdb” from the C:\IXP220\Database folder onto a Flash Drive. And take the IXP220 CD with you to the “Server” PC. Insert the IXP220 CD into the CD Rom, the Autorun will automatically launch, you do not install the software. Instead browse to the CD, through Windows Explorer. There is a folder called “database”, inside this folder is another folder called “firebird”, inside this folder run the firebird.exe. This will install the firebird service onto your PC, the standard firebird settings will be fine, and you should not need to change anything in this installation. Copy the DB220.fdb file to C:\IXP220\Database on the “Server” pc. Go back to the Client PC and run the IXP220 software, under “Server Name” enter either the “Host Name” or “IP address” in this box. If this does not connect try, disable any Firewall that may be installed.

What “Force Upgrade” actually means is that even though the version of the firmware on the unit is higher then the version selected to upgrade. The utility will still upgrade the unit to a lower version. If this checkbox is not selected, the upgrade utility will stop you from upgrading the terminal because the version of the unit it higher than the version being used to upgrade. This checkbox will not put the unit into a special mode; it’s essentially an “Ignore current firmware” switch.

When you want to create a schedule you go to the "schedule creator" option from the "configuration" drop down menu. When there, click on the blue "plus" to add a schedule and name it, once you've named your schedule, look at the table on the other side of the page where you have different measurements of time. Depending on how often you want your site to be polled you set them accordingly; say I wanted my site to be polled every month, on every week, every day, every hour, starting from the 15th min of the hour and stopping 20 minutes after it has started. I would set my months column to "Monthly" and the my dates column to "Every", my day column to "Daily", then the hours column to "Every", and my minutes column to "00:15" and then the connection limit to "00:20". The connection limit tells you what period of time the site can be polled after its start time.

A scheduler optimizes your site allowing you to dictate how often and for how long each site can be polled relieving unnecessary network traffic. The downside of this is if you are editing tags, the tags will only be uploaded once the scheduler kicks in.

• Java runtime environment is not installed on this PC. The Java Runtime environment can be found on the Installation CD – install this and try again.
• If Using Windows Vista, Try disabling the UAC (User Account Control). This occasionally interferes with the running of embedded webpages.

Yes, Internet is not necessary for Web-QuickTag however, at a minimum, there must be a LAN connection.

From Site A, Navigate to the Tag Holder Configuration. When Adding/Editing a Tag Holder, Click on the Tag Tab,  Select a Site from the “Site” Dropdown box (In this E.g. Site B) and then select an Access Group from the “Access Group” dropdown box.

Distributed Templates is the BioServer’s intelligent method of distributing Biometric Templates, whereby the BioServer determines which Biometric Templates are uploaded to specific Sagems provided that the user specifies which Sagem belongs to a specific Door.

Distributing of Biometric Templates is determined by Tag Holders belonging to their respective Access Group(s). E.g. Tag Holder “Jack Sparrow” has Access to “Marketing” Door which belongs to the “Marketing” Access Group and Tag Holder “Elizabeth Swan” has Access to “Reception” Door which belongs to the “Reception” Access Group. From BioServer a Sagem can be assigned to the Marketing Door and another Sagem can be assigned to the Reception Door. In this scenario only “Jack Sparrow” templates will be uploaded to the “Marketing” Sagem and only “Elizabeth Swan” templates will be uploaded to “Reception” Sagem. For this to work effectively, the Bioserver needs to know what door controller belongs to what Sagem.

In the past, all biometric Templates were uploaded to all Sagem devices irrespective of the Tag Holder having access to that Door. Using Distributed Templates uploads Tag Holder(s) Biometric Templates to specific Sagems only if Tag Holder(s) have access to that door. Hence, this reduces the number of templates uploaded which allows for more templates to be stored on the Sagem database per door. This also increases the upload speed seeing as templates are intelligently distributed. This also eliminates the issue of Tag Holder(s) present fingers on the Sagem and the Sagem indicates “Access Granted” but the door does not open.

System Unlocks and Features can be purchased from the “E-Store”.

http://www.impro.net/site/psu/users/login

Once an Unlock or feature has been purchased an email containing XML file(s) will be sent to you. Please save this XML and create backups of these file(s). If this email has not been sent please contact the Administrator.

If a Controller Unlock has been purchased:

If a System Unlock or Feature has been purchased:

You need to Login to the software first. Next, Click “Hardware” then “Communications”. It will bring up a dialogue that lists all your communications channels. To change the COM port that is wrong, simply double click the “wrong com port” and the box will become editable. You may now enter the correct COM port.

User: sysdba 
Password: masterkey

You may however setup other users in the IXP220 Software under the “Manage Operators” menu.

Newer software always has new features as well as some major Bug fixes. The IXP220 Readme.rtf contains all of the major bug fixes and displays all the new features. Download the Readme here

• When logging into Web-QuickTag, the software will automatically download the drivers from the PC running the software to the C:\IXP220\quicktag\USB directory, you just need to log in to the Web QuickTag once then navigate to C:\IXP220\quicktag\USB, and unzip the “USB_Device_Driver.zip” file. When plugging in the device, navigate to the directory when asked to.
• Alternatively the drivers can be located on the IXP220 V1.80 and above CD.

• Check that the correct communications interface (i.e. UDP multi/com port/TCP/IP) is selected.
• If com port, check the baud rate is set to 38400.
• Check the connection between the computer and the ImproX hardware.
• Check that the com port number is not higher than 16. Most ImproX systems cannot detect a com port higher than 16.
• There may be communications issues on the communications bus. Perform a comms test from the “System Tools” tab in the firmware upgrade program. If the result is below 100% contact your support network.

• The relay may be causing a dead short. This typically happens when the power supply is shared between the lock and the terminal and the power supply may go into short circuit protection mode. The terminal has a power on reset, and hence the double beep on the reader.
• There may not be a MOV on the lock protecting the relay from back EMF; connecting a MOV across the load should help.
• The locks current rating may be too high for the power supply to supply the required current.

• Check the distance of the cable between the reader and the terminal, make sure the distance is within the specified cable length.
• Use good quality cable as per user manual specifications.
• Use the correct tags for that specific reader.
• Check that there are no other devices that might be causing interference (e.g. readers are back to back, air conditioners etc.).
• Make sure the cables for the readers have not been run alongside power cables. This will cause interference and the readers will not work properly.
• If the L.E.D. is double flashing red it means that there is no communication between the controller and the terminal, and then you will need to check that one of the connections has not come loose or that the Rx and Tx have been swapped around.
• Sometimes grounding the shield on the cable can improve read range. Contact your support network for assistance with this.

There is a communications failure between the Controller and the terminal. Use the firmware upgrade utility to ping the terminals and use this utility while you are fault finding.
Check the cabling first - If the terminal was working, chances are the terminal bus has been damaged or tampered with.

• Make sure the device is supported by our software and hardware.
• Check that the cables are in the correct terminal blocks, specified by the user manual.
• Make sure that the dip switch settings are set correctly for that device.
• Make sure that the device has been setup correctly, specified by the user manual for that device.

Yes, it is possible. However the option has to be enabled in the door setup for the feature to work.

Yes, the software can communicate to controllers via RS232,RS485,USB and Ethernet controllers at the same time. (Note: this applies to multiple controllers and not a single controller).

The "mode" on the controller has not been set to "Action", this mode can be changed on the controller tab.
Note: after changing this mode, a full upload has to be performed.

• If you are using a Registration reader, make sure that it has been enabled in the software in the advanced configuration.
• Check the DIP switches on the Registration Interface if using the 3rd Party Port on the RS.
• If you are not using a registration reader, check to see that the correct reader (Entry/Exit) has been selected in the advanced configuration on the Tagholder enrollment screen. Make sure you hold the tag in front of the reader long enough for the reader to read the tag. Occasionally you may need to click “read tag” before you present the tag to the reader.

• Check that the dip switches on the controller have been set correctly - 2 and 3 UP, 1 and 4 OFF for 26/34/44bit.
• Make sure that the Wiegand readers have been configured for the correct mode by listening to the number of beeps when powering up – refer to the Wiegand reader manual for the correct number of beeps.
• Make sure that the reader has been wired into the controller correctly – refer to the Wiegand reader manual for the connections.
• Check that the door has been assigned to a Valid Access Group and that tagholder has been given access to that specific door.

Remotes are supported in the IXP220 system. The Remote has to be connected to a  terminal which supports remotes, e.g. TRT/TA. ImproX DT’s are not supported in an IXP220 system. Refer to the IXP220 section to get a list of supported terminals. The IXP220 controller does not support remotes connected directly to the IXP220 controller. Note: refer to product notice PN09-002.pdf for a list of all supported units.

With Force Upgrade selected you can upgrade the selected unit to a lower firmware version, even if the firmware version of the unit is higher than the selected version. If this checkbox is unchecked, the upgrade utility will abort the upgrade process if the version of the unit is higher than the for the upgrade selected version. This checkbox will not set the unit in a special mode; essentially it is a “ignore firmware version” switch.

Selecting "Firmware Check" will display all to the system connected units and thei firmware versions. Red highlighted terminals have to be upgegraded, their firmware is old or incompatible. Yellow highlighted terminals have an higher firmware version than the shipped firmware version. This can be intended and necessary – even after a "product notice".

• When logging into Web-QuickTag, the software will automatically download the drivers from the PC running the software to the C:\IXP220\quicktag\USB directory, you just need to log in to the Web QuickTag once then navigate to C:\IXP220\quicktag\USB, and unzip the “USB_Device_Driver.zip” file. When plugging in the device, navigate to the directory when asked to.
• Alternatively the drivers can be located on the IXP220 CD.

Firmware is an application that is embedded in a piece of hardware. You can think of firmware simply as "software for hardware." Devices that you might think of as strictly hardware such as Controllers and Terminals all have software that is programmed into special memory contained in the hardware itself.

If your Controllers and Terminals are having issues or you would like to add new functionality to it, your distributor should have the latest firmware update (if available) or alternatively you can obtain latest Firmware from the Impro Web Page.

http://www.impro.net/site/downloads

Controllers and Terminals can be upgraded with latest firmware via the Firmware Upgrade Utility which is bundled with IXP220 and ImproNet. To Download Firmware you have to Login with a valid Username and Password.

No, only an ImproX RS (ISW903) can be upgraded for use in the IXP220 software.

Upgrade the software to the latest version and run the database scripts to update your database.

The resolution of the image used for the tagholder is too large; the database tries to size the image down and causes distortion. The recommended image size for tagholders is 640x480 or smaller.

• The AC/EC or EC² Controller does not recognize the tag because the Wiegand settings on the Sagem MA-xxx have not been setup correctly.
• The Dip switches for the TRT/PT have not been set correctly.

• Check the Tagholder Access Groups to make sure the Tagholder actually does have access to that door/location
• Also make sure Distributed Templates have been setup correctly.

Bypass distributed templates. Refer to document (Setting up the Sagem Unit for authentication by the ACS)

Following reasons for the “65535” wiegand code being transmitted by the Sagem MA-xxx unit:

• The Wiring between the MAxxx unit is not grounded correctly. Make sure the MAxxx unit and the PT/TRT have a common ground reference.
• There are no Biometric tags in the Database.
• The finger presented is not recognized by the Sagem MA-xxx unit.

When setting up your MSO300 and Verif dongle for the first time, you have to run the setup file C:\ImproNet\driver\mso\setup.exe. This will load the MSO drivers at location C:\Program Files\SAGEM SA\MorphoSmart Drivers.
Once the correct drivers are loaded, plug your MSO300 unit into any USB port. Avoid connecting it to a USB hub. The MSO300 will be detected and ask for the drivers to be installed. Guide the driver install utility to C:\Program Files\SAGEM SA\MorphoSmart Drivers.
If you have a verif dongle, insert it in any USB port, and guide the driver setup utility to C:\ImproNet\driver\verif\I386. The unit will then be installed and ready to use.

If the system has been running fine for a while and an error message occurs, make sure a second separate version of the MSO300 drivers weren't installed with the installation of the M.E.M.S application. Both of these items can be found in the “Add and Remove Programs” utility in Control Panel.

Either the dongle has not been plugged into an available USB port, or the driver may be an old version. Check in the Device manager and make sure the verif dongle is installed properly, if not, update the driver and guide the installation to the following folder C:\ImproNet\driver\verif\I386.
If the problem still persists, run the Setupx86.exe from the C:\ImproNet\driver\verif folder. Select functions and then install sentinel drivers.

Make sure that Interbase and Interserver are loaded on the machine that ImproNet is running on. If you have them already installed, uninstall and reinstall them separately. Make sure that Interserver is configured for Windows startup.

Check that the wiring between the remote and the DT has been connected Rx to Tx instead of Rx to Rx and Tx to Tx.

It is possible to AutoID a single controller by clicking on the ADVANCED button in the ENGINE and type: start autoid xx (xx is the decimal number of the controllers LA) and the engine will AutoID only the controller you have specified.

• Make sure the Firebird/MSSQL service is started.
• Make sure you are typing the correct username and password into the dialogue.
• Can you log into the database from the database manager? If not, it is possible that the database maybe corrupt. If you have no recent backups of the database then you will need to get the database repaired. Contact your support network.
• If you can login to the database through your database manager, then check that the properties files contain the correct URL to the database.

It is possible that you do not have sufficient power to the unit or the current is not sufficient. This occurs when a strike lock or mag lock is connected to the same power source and when a relay is activated, the lock draws too much current thus resetting the unit. It is also possible that you do not have back EMF protection installed on the locks and the units are being reset. Read the manuals for instructions on installing back EMF protection. Another possibility is that certain sites where transmission lines are long or multiple star formations are used, may experience “time-outs” on certain ImproX controllers or terminals. These are caused by reflections on the RS485 lines. To solve the problem it may be necessary to terminate the lines. Termination resistors are only added at the end of a cable run and not at every terminal. The value of the terminating resistor will vary but values in the range of 100 ohms to 1K ohms will suffice.

This is when the time zone on the PC is not the same as the time zone setup for the site in “Site Directory”. Make sure the time zone on the PC is the same as the time zone on the Site Directory.

The firmware on the Controllers and Terminals must be upgraded to correspond with the software. The correct firmware will be on the same CD as the software. The database scripts must also be run to update the database tables.

• Make sure that the Engine is open (doesn’t have to be started).
• Check that windows firewall is not blocking web reports. If necessary, disable the firewall.
• Make sure that IIS(Internet Information services) is disabled for Windows XP and Vista.
• Check that Firebird is installed and running. Check in Control Panel for the Firebird Server Manager icon. Double click and the dialog will show the Firebird status.
• Make sure the port for web reports is not being blocked by other programs such as Skype or MSN.
• Check that the URL in the address bar is correct and that the URL points to the web service on the Engine Computer.
• On the Engine computer, the ImproNet Engine is not 100% compatible with computers running dual network interfaces.

The Network Discovery Utility is outdated; the required version is 1.9 or higher.

• Check that the correct communications interface (i.e. UDP multi/com port/TCP/IP) is selected.
• If com port, check the baud rate is set to 38400.
• Check the connection between the computer and the ImproX hardware.
• Check that the com port number is not higher than 16. Most ImproX systems cannot detect a com port higher than 16.
• There may be communications issues on the communications bus. Perform a comms test from the “System Tools” tab in the firmware upgrade program. If the result is below 100% contact your support network.

There is a communications failure between the Controller and the terminal. Use the firmware upgrade utility to ping the terminals and use this utility while you are fault finding. Check the cabling first. If the terminal was working, chances are the terminal bus has been damaged or tampered with.

• Make sure the device is supported by our software and hardware.
• Check that the cables are in the correct terminal blocks, specified by the user manual.
• Make sure that the dip switch settings are set correctly for that device.
• Make sure that the device has been setup correctly, specified by the user manual for that device.

Please refer to Hardware Notice HN07-005. A copy is available on the website.

• Check to see if the registration reader (ImproX RS/RH/RR/RM) drivers are installed properly.
• Make sure the tag is being presented long enough for the registration reader to read the tag.
• Make sure there is only one ImproX USB device plugged into the computer. Occasionally, 2 ImproX USB devices conflict with each other.
• Make sure the correct tag type is used for the reader. If it is, try a different tag in case the tag is faulty.

Contact Impro Support. (+27 31 700 1087 )

Upgrade the software to the latest version and run the database scripts to update your database.

When setting up your MSO300 and Verif dongle for the first time, you have to run the setup file C:\ImproNet\driver\mso\setup.exe. This will load the MSO drivers at location C:\Program Files\SAGEM SA\MorphoSmart Drivers. Once the correct drivers are loaded, plug your MSO300 unit into any USB port. Avoid connecting it to a USB hub. The MSO300 will be detected and ask for the drivers to be installed. Guide the driver install utility to C:\Program Files\SAGEM SA\MorphoSmart Drivers. If you have a verif dongle, insert it in any USB port, and guide the driver setup utility to C:\ImproNet\driver\verif\I386. The unit will then be installed and ready to use.

If the system has been running fine for a while and an error message occurs, make sure a second separate version of the MSO300 drivers weren't installed with the installation of the M.E.M.S application. Both of these items can be found in the “Add and Remove Programs” utility in Control Panel.

Either the dongle has not been plugged into an available USB port, or the driver may be an old version. Check in the Device manager and make sure the verif dongle is installed properly, if not, update the driver and guide the installation to the following folder C:\ImproNet\driver\verif\I386. If the problem still persists, run the Setupx86.exe from the C:\ImproNet\driver\verif folder. Select functions and then install sentinel drivers.

• Check to see if the registration reader (ImproX RS/RH/RR/RM) drivers are installed properly.
• Make sure the tag is being presented long enough for the registration reader to read the tag.
• Make sure there is only one ImproX USB device plugged into the computer. Occasionally, 2 ImproX USB devices conflict with each other.
• Make sure the correct tag type is used for the reader. If it is, try a different tag in case the tag is faulty.

Contact Impro Support. (031-700 1087 )

The engine may not have been running, or the tags may not have been cleared from the controller memory. Do a full upload.

The resolution of the image used for the tagholder is too large; the database tries to size the image down and this causes distortion. The recommended image size for tagholders is 640x480 or smaller.

• The relay may be causing a dead short. This typically happens when the power supply is shared between the lock and the terminal and the power supply may go into short circuit protection mode. The terminal has a power on reset, and hence the double beep on the reader.
• There may not be a MOV on the lock protecting the relay from back EMF; connecting a MOV across the load should help.
• The locks current rating may be too high for the power supply to supply the required current.

• Check the distance of the cable between the reader and the terminal, make sure the distance is within the specified cable length.
• Use good quality cable as per user manual specifications.
• Use the correct tags for that specific reader.
• Check that there are no other devices that might be causing interference (e.g. readers are back to back, air conditioners etc.).
• Make sure the cables for the readers have not been run alongside power cables. This will cause interference and the readers will not work properly.
• If the L.E.D. is double flashing red it means that there is no communication between the controller and the terminal, and then you will need to check that one of the connections has not come loose or that the Rx and Tx have been swapped around.
• Sometimes grounding the shield on the cable can improve read range. Contact your support network for assistance with this.

It is often found that the necessary hardware is ordered for installation at a new site, but the software is forgotten. Every software module is sold with a dongle that contains the necessary unlock code for that module of the software to run. Some sites may require more than one module of the ImproNet software to be running. For example, a site may be required to run ImproNet Access, and ImproTouch. In this instance the RR/PM (dongle) needs to be unlocked for both Access & ImproTouch. The dongle needs to contain unlock codes for both modules of the software.
It is possible for the dongle to run one module at first and be unlocked at some later date for the second module of software. This is achieved by ordering the correct unlock code from the supplier. When ordering an unlock code for an extra module on an existing site, the following information is required before the unlock code may be issued:

• Unit type: e.g. ImproX RH/RR/HI etc.
• Fixed Address of the unit, found on the silver label on the underside of the unit.

Biometrics (XXX960): commonly known as “Impro Touch”. If you are unable to click the “Biometric addresses/Biometric Enrolment” button in Access or Quicktag then your “Dongle” (ImproX RR/RM etc.) is not unlocked. This unlock is an enrolment unlock code, this means that the Unlock code only applies to the biometric enrollment station, and is not a server-based unlock code, if you have 5 enrollment stations, you will need 5 versions of “Impro Touch”. Therefore you will need to have 5 fixed addresses ready.

Unlock Tokens also often get confused with Unlock Codes. Unlock Tokens are actually a special form of tag, that register the Sagem (MA100,MA200,MA300,MA500,MA520) devices to a database. These tokens unlock the Bioserver to communicate with the Sagem devices. Unlock Tokens can be ordered from your nearest Impro distributor. If you have 20 Sagem Readers, you will need 20 Unlock Tokens. The Unlocking Procedure can be found in the ImproNet manual on page 24 of Part VIII.

CCTV (XXX930): Commonly known as ImproVision, this is also a “client-based” unlock code, and is only required to run on the PCs that want to view footage and alarms in the Graphics runtime module. This unlock can be applied to Registration Readers that have a built in reader (RR/PM/RM (to acknowledge alarms). This unlock cannot be applied to an ImproX HI. The CCTV Server does not require an Unlock Code.

Fire Panel and Alarms Modules: this is also a “client-based” unlock code, and is only required to run on the PCs that want to View alarms in the Graphics runtime module. This unlock can be applied to Registration Readers that have a built in Reader (to Acknowledge Alarms). This unlock cannot be applied to an ImproX HI. The Fire Panel Server and the Alarm Panel Server do not require Unlock Codes.
All Fixed addresses can be queried in a matter of seconds by the Impro Technical Support Team.

• Make sure there is only one ImproX USB device plugged into the PC while reading the tag.
• Make sure there are no power supplies or computer screens near the tag reader as these will cause interference.
• Hold the token over the reader until the token has been read. Only then can you remove it.
• If the token still does not unlock, check that the token is not too far from the reader or too close to the reader. Try to hold the token about one or two centimeters away from the reader and attempt to unlock the unit.
• You may have a faulty unlock token, check to see if the faulty token can be read as a tag, using Quicktag.

Contact Impro to obtain an Unlock Code for your Registration Host. This will allow you to run the software

• The AC/EC or EC² Controller does not recognize the tag because the Wiegand settings on the Sagem MA-xxx have not been setup correctly.
• The Dip switches for the TRT/PT have not been set correctly.

• Check the Tagholder Access Groups to make sure the Tagholder actually does have access to that door/location
• Also make sure Distributed Templates have been setup correctly.

Bypass distributed templates. Refer to document (Setting up the Sagem Unit for authentication by the ACS)

There are three reasons for the “65535” wiegand code being transmitted by the MAxxx unit:

• The Wiring between the Sagem MA-xxx unit is not grounded correctly. Make sure the Sagem MA-xxx unit and the PT/TRT have a common ground reference.
• There are no Biometric tags in the Database.
• The finger presented is not recognized by the Sagem MA-xxx unit.

• Make a backup of the database. Do a pump* on the database using the old ImproNet Installation.
• Uninstall the old ImproNet; install the new ImproNet then do an upgrade on the database using the database upgrade utility.
• Once the upgrade is complete do another pump* on the database.
• Remove the old ImproNet Software from all client machines and install client versions that are the same version as the Server Machine.
• Perform a firmware upgrade to all terminals and controllers.
• Warning: These procedures may take very long depending on the size of the database and number of controllers and terminals.

*a pump is necessary on a Firebird database; it is not possible to perform a pump on a SQL database.

Shut Down and Restart ImproNet Access. Do all your dragging and dropping of terminals before you do any editing of the terminals.

Edit the engine.properties files at the remote machines. Change all site specific settings to point to the second site. E.g. the 01000000 site numbers will all change to 02000000. Change the URL to point to that of the server machine or server IP address.