Results Per Page | Showing 1-10 of 10 Results
| 1
Answer:
If the reader is configured for a BADGE VALIDATOR, it will disable the badge on the first swipe and then enable it on the next swipe. In almost all cases, the reader type should be configured for a DOOR.
View Answer
Answer:
If you are using facility codes, it will check the facility code and if that's correct, it will grant access no matter what the badge number is.
...
View Answer
Answer:
A "Panel Trouble - Test Fail" alert might be caused by a defective EPROM (Firmware Chip).
View Answer
Answer:
A trouble line fault is caused by a shorted input wire. You must verify if the input is being used and if there are wires on it. If so, you should remove the wires and place a jumper across the input. At this point, you need to verify if...
View Answer
Answer:
Summary: There are multiple reasons why an event would fail to display. In the CardAccess 3000 software, verify the following:
...
View Answer
Answer:
Summary: This alert message will display if there is a record of the badge in the database and the badge belongs to at least one reader on the panel but not the reader it was swiped at.
...
View Answer
Answer:
Summary: This alert message displays when the badge is programmed to be active at a given time, but the badge was swiped outside of the allowed time schedule. In the CardAccess3000 software, verify the following settings:
...
View Answer
Answer:
Summary: This error message means there is a record of the badge in the database, but the badge does not belong at any reader on the panel.
...
View Answer
Answer:
Summary: This alert message normally displays when the facility codes are configured properly, but the facility code is not a match. In the CardAccess 3000 software, verify the following settings:
...
View Answer
Answer:
Summary: This alert message normally means there is no CardAccess database record for the badge. In the CardAccess 3000 software, verify the following settings:
...
View Answer
40 Results Per Page | Showing 1-10 of 10 Results
| 1
