Welcome to Impro.net /
Support /
Frequently Asked Questions
Please click on a Title below to view more information.
I cannot get the software to run. The User logon
screen appears, but it will not let me logon.
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.
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.
The software autoID's the DT terminals but does
not identify the remote attached.
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.
Is it possible to AutoID a controller without doing an AutoID to the whole site?
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.
When I Try to Do an AutoID from my IXP120 system, the AutoID Fails.
1. This is generally caused by a typing error when entering the fixed address of the controller on Local (non-TCP/IP) sites. Often users put an 8 instead of a B, or a 5 instead of a 6. This can be edited in the “Sites Directory” part of the IXP120 Software.
2. Check that the correct com port has been selected in the software if the IXP120 controller connects via a com port.
3. Check that you can ping the terminals using the firmware upgrade program.
When I do an autoID, the engine does not find any controllers.
Ensure that the RS485 communications cable is connected to the Host Port on the Controller (RS485 port 2). Power the Controller up and ensure that the Controller identifies itself as an ImproX Controller.
When I do an autoID, the engine does not find any terminals.
Make sure the terminals are connected to the Terminal Port on the Controller (RS485 port 1). Also ensure that the communications cable is not crossed over between the terminals (i.e. A connected to B). On potted units, the yellow wire is A comms and the green is B comms.
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.
Is it possible to AutoID a controller without doing an AutoID to the whole site?
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.
When I Try to Do an AutoID from my IXP120 system, the AutoID Fails.
1. This is generally caused by a typing error when entering the fixed address of the controller on Local (non-TCP/IP) sites. Often users put an 8 instead of a B, or a 5 instead of a 6. This can be edited in the “Sites Directory” part of the IXP120 Software.
2. Check that the correct com port has been selected in the software if the IXP120 controller connects via a com port.
3. Check that you can ping the terminals using the firmware upgrade program.
When I do an autoID, the engine does not find any controllers.
Ensure that the RS485 communications cable is connected to the Host Port on the Controller (RS485 port 2). Power the Controller up and ensure that the Controller identifies itself as an ImproX Controller.
When I do an autoID, the engine does not find any terminals.
Make sure the terminals are connected to the Terminal Port on the Controller (RS485 port 1). Also ensure that the communications cable is not crossed over between the terminals (i.e. A connected to B). On potted units, the yellow wire is A comms and the green is B comms.
New biometric templates have been added to the
database. You present your finger to the MAxxx biometric unit, the MAxxx units
accepts your finger, but the relay to open the door/turnstile does not drive.
In transaction viewer you find an unknown tag transaction with your tag number.
i) The AC/EC or EC² Controller does not recognize the tag because the Wiegand settings on the MAxxx have not been setup correctly.
ii) The Dip switches for the TRT/PT have not been set correctly.
When I present my Finger to the MA100/200/300/500/520 the MA unit says I’m allowed but the door doesn’t let me in.
Two possibilities:
1. Check the Tagholder Access Groups to make sure the Tagholder actually does have access to that door/location
2. Also make sure Distributed Templates have been setup correctly.
If my finger template does not have access to a location, is there a way to inform me that my finger template is “Access Denied” but not “Unknown”?
Bypass distributed templates. Refer to document (Setting up the Sagem Unit for authentication by the ACS)
When presenting a finger to the MAxxx biometric units, a transaction with the following code is displayed in the transaction viewer "Denied - unknown tag" code "65535".
There are three reasons for the “65535” wiegand code being transmitted by the MAxxx unit.
1. The Wiring between the MAxxx unit is not grounded correctly. Make sure the MAxxx unit and the PT/TRT have a common ground reference.
2. There are no Biometric tags in the Database.
3. The finger presented is not recognized by the MAxxx unit.
i) The AC/EC or EC² Controller does not recognize the tag because the Wiegand settings on the MAxxx have not been setup correctly.
ii) The Dip switches for the TRT/PT have not been set correctly.
When I present my Finger to the MA100/200/300/500/520 the MA unit says I’m allowed but the door doesn’t let me in.
Two possibilities:
1. Check the Tagholder Access Groups to make sure the Tagholder actually does have access to that door/location
2. Also make sure Distributed Templates have been setup correctly.
If my finger template does not have access to a location, is there a way to inform me that my finger template is “Access Denied” but not “Unknown”?
Bypass distributed templates. Refer to document (Setting up the Sagem Unit for authentication by the ACS)
When presenting a finger to the MAxxx biometric units, a transaction with the following code is displayed in the transaction viewer "Denied - unknown tag" code "65535".
There are three reasons for the “65535” wiegand code being transmitted by the MAxxx unit.
1. The Wiring between the MAxxx unit is not grounded correctly. Make sure the MAxxx unit and the PT/TRT have a common ground reference.
2. There are no Biometric tags in the Database.
3. The finger presented is not recognized by the MAxxx unit.