*Fore! Manual
Fore!box
Installation Manual | IM-20220201-LG-01 Access Control | Mobile Access | Cosmos Access | |
- 1 Fore!box
- 2 Fore! Manuals
- 2.1 Access
- 2.1.1 Discovery
- 2.1.2 Settings
- 2.1.3 Advanced options
- 2.1.4 I/Os
- 2.1.5 Anti pass-back
- 2.1.6 Office mode time schedule
- 2.1.7 Latching
- 2.2 Cameras
- 2.2.1 Discovery
- 2.2.2 Settings
- 2.2.3 NVR / DVR / Encoders
- 2.3 Card codings
- 2.3.1 Card codings for Sirius readers
- 2.3.2 All card codings
- 2.3.3 Fore! default card
- 2.3.4 UID
- 2.3.5 Card codings for Wiegand readers
- 2.3.6 Wiegand 26
- 2.3.7 Wiegand other
- 2.3.8 PX007A
- 2.3.9 Custom
- 2.4 Custom Fields
- 2.5 Custom I/O
- 2.6 Email messaging
- 2.7 Employees
- 2.8 Event search
- 2.9 Holidays
- 2.10 Image storage
- 2.11 Intercom groups
- 2.12 Intercom
- 2.12.1 Direct calling
- 2.12.2 Call routing
- 2.13 Intrusion Detection
- 2.13.1 Discovery
- 2.13.2 Supported Intrusion detection
- 2.14 Notification handling
- 2.15 Push messaging
- 2.16 Presence
- 2.17 Relations
- 2.18 Remote Access
- 2.19 Reports
- 2.19.1 Door transactions
- 2.19.2 User login time
- 2.19.3 Time registration
- 2.19.4 Presence
- 2.20 Site information
- 2.21 Sound
- 2.22 System Users
- 2.23 Time schedules
- 2.24 Video search
- 2.25 Visitor cleanup
- 2.26 Visitor profiles
- 2.27 Visitors
- 2.1 Access
- 3 Troubleshooting
- 4 Hardware manuals
- 4.1 Polyx NF+ Manual
- 4.1.1 Mounting
- 4.1.2 Power
- 4.1.3 External power supply
- 4.1.4 Connect common
- 4.1.5 Power over Ethernet
- 4.1.6 Emergency battery
- 4.1.7 12V Emergency power
- 4.1.8 24V Emergency power
- 4.1.9 LAN
- 4.1.10 Card readers
- 4.1.11 I/O
- 4.1.12 Door relay and lock
- 4.1.13 Door relay for 12V door lock
- 4.1.14 Door relay for 24V door lock
- 4.1.15 Door contact
- 4.1.16 Door open too long (DOTL) alarm
- 4.1.17 Arm intrusion switch
- 4.1.18 Request to exit button
- 4.1.19 Detection loop
- 4.2 Technical data
- 4.3 Compliance
- 4.4 RoHS
- 4.5 CE Marking
- 4.6 Change ip address Polyx NF+ to Static ip address
- 4.7 Sirius F80/F80P Manual
- 4.7.1 Location
- 4.7.2 Mounting
- 4.7.3 Wiring
- 4.7.4 Pinpad operation
- 4.7.5 Technical data
- 4.1 Polyx NF+ Manual
- 5 Wiegand Converter Manual
- 5.1 Wiring
- 5.2 Technical data
Start Fore!box
Unpack the Fore!box and power up the Fore!box and put the network cable in.
The standard IP Adress of the Fore!box is https://192.168.1.150.
Login with Username and Password.
(the username and password are included in the instruction manual)
Open the Network tab.
Change the Network Settings in the settings you prefer.
Save the Settings.
After saving the setting the Fore! is approachable on the new IP Adress.
Date / Time
Select the right timezone.
If you want to change the time , select the arrow. The time will be displayed in box below.
Adjust the date and time and Save the settings
If you want to set a NTP Server, select the checkbox an fill in the ip address of the NTP Server.
For GMT+1:00 hour you can use this ip address 193.67.79.202
Install Fore! upgrade package
Download the latest Fore! package
Browse to https://192.168.1.150 to open the Fore!Box webinterface (when 192.168.1.150 is the ip address of your Fore!box)
Login with Username and Password
Open the Update tab
Click Browse to select a Fore! package
Click Update to start the update.
You can follow the update in the messages tab ( system log ). Update is ready when the system says 'Upgrade ending'
After 5 minutes you will be redirected to the new Fore!box maintenance page.
(If you are not redirected automatically you can open it yourself by browsing to https://192.168.1.150)
Note
if your Fore! version is below 1.7.0.1335, use this package. * http://www.keyprocessor.com/remove_AUDIT_data.taz
the package will erase the audit data en restart the Fore!box . If you don't upload the package the upgrade will take a hour.
Go to the update tab , choose file and upload remove_AUDIT_data.taz.( it will restart the database , wait 4 min.)
Backup / Restore
Use the System backup / restore page to create and restore Fore! backups. A Fore! backup contains all configuration data and historical transactions. Camera images are not included in a backup.
Fore! creates a daily backup to usb only at the time specified in the Start field. The default backup directory is /media/usb but this location can be changed by clicking the browse button and selecting a different directory. The backup will result in a file named data.taz and will overwrite the previous backup.
Use the Backup now button to start a backup immediately.
To restore a previously made backup you can upload it by using the Restore button.
Reboot / Shutdown Fore!box
Go the IP Adress of the Fore!box (standard https://192.168.1.150).
Login with Username and Password.
(the standard username and password are included in the instruction manual)
Open the System tab.
If you want to Shutdown the Fore!box use the Shutdown Button
If you want to Restart the Fore!box use the Restart Button
Fore! Manuals
Access
In Fore! all access control features are centered around card readers. Each card reader has a set of 6 default I/Os that are used to interact with the door. In case a door has two card readers (one inside and one outside) the card readers will share the 6 I/Os. At the access settings page you can discover and add card readers to your system.
Discovery
Use the Discover button to automatically discover all card readers that are present in your installation. Fore! will not detect Polyx NF+ network controllers which have no readers connected. If your reader is not discovered you can the Reader troubleshooting guide to fix common issues with your installation.
Note After discovering and adding a card reader to Fore! the firmware of the Polyx NF+ and the card reader will be updated. The update takes about 5 minutes and during this time both card readers on that Polyx NF+ do not work.
Settings
The Status field is used to set the current state of the reader. The three options are:
Open: The door is open and can be opened by anyone.
Close: The door is closed and can not be opened using an access card.
Auto: The door is normally closed but can be opened by presenting an access card with sufficient privileges.
The Area change setting indicates how the area of a person should be changed when he uses this card reader. By default Fore! has two access areas: a person can be Inside or Outside. The three options are:
To in: Area of the person is set to Inside.
To out: Area of the person is set to Outside.
No change: Area of the person is not changed.
When PIN code required is checked a person will be asked to enter a pincode after presenting his card to the card reader. This option only works in combination with Sirius F80P pincode readers.
Advanced options
The Polyx MAC settings shows the MAC address of the Polyx NF+ of this card reader.
The Function setting can be used when a door outfitted with two card readers: one inside and one outside. The two options are:
Normal: The card reader uses it's own set of 6 I/Os.
Secondary reader: The card reader acts as a secondary reader and uses the same 6 I/Os as the primary card reader. The primary card reader should always be the other card reader on the same Polyx NF+ and should have its function set to Normal.
I/Os
Each card reader has 6 I/Os reserved on the Polyx NF+. See the Polyx NF+ Manual for wiring instructions for each I/O. You can select which of the 6 I/Os you have connected for this door:
Detection loop: Indicates that a (car) detection loop is connected to this input. When checked the reader will only grant access when the input is closed, for example only when a car is present on the detection loop.
Request to exit: Indicates that a request to exit button is connected to this input. When checked the door will open when the button is pushed.
Door contact: Indicates that a (magnetic) door contact is connected to this input. When checked the system knows whether a door is actually opened or closed.
Arm intrusion: Indicates that an arm intrusion button is connected to this input. When checked the reader will go in arming mode as long as the button is pressed.
Door relay: Indicates that a door relay is connected to this output. This output is used to open the door.
Door open too long: Indicates that a door alarm (light or buzzer) is connected to this output. When checked the output will activate when the door has been opened too long (someone blocked the door).
The Door open limit sets the time in millisends a door can be open before the Door open too long alarm will be actived.
Tip: I/Os that are not used by the reader can be used as Custom I/O
Anti pass-back
Anti pass-back is a mechanism preventing an access card from being used to enter an area a second time without first leaving it (so that the card can not be passed back to a second person who wants to enter). If the area change is set to in only persons which are currently outside will be granted access. If the area change is set to out only persons which are currently inside will be granted access.
Warning: In order for anti pass-back to work correctly all exterior doors of your building should be equipped with both ingoing and outgoing card readers. Persons should not be able to enter or leave your building without using their access card.
The three options are:
No: No anti pass-back is activated.
Normal: Hard anti pass-back is activated. A person will first have to go outside before he is granted access inside again.
Time: Time anti pass-back is activated. Within a certain time limit a person will first have to go outside before he is granted access inside again.
The APB time limit sets the time limit for Time anti pass-back.
When you want to reset the Anti pass-back of a person , go to the Presense list on your dashboard and stand on the name of the person and a cross ( X ) will be showed. You can click on the cross and the persons Anti pass-back will be reset to outside.
Office mode time schedule
With office mode time schedule you can set a door in open or normal modus with a card with office rights in the selected Time schedules. When you present a card for the first time the door will go in open modus en stay open. When you present a card again the door will go in normal modus. The door will only go in the office modus during the selected Time schedules. When the Time schedules ends, the door will go in normal modus.
Latching
Unlatch time is the time in milliseconds which the door relay is activated when the door is opened. Alternative unlatch time is the time in milliseconds which the door relay is activated when the door is opened by a person requiring an alternative unlatch time. This can be set at the employees or visitors settings page.
Latch on time schedule can be used to change the Status of a door to open or closed according to a time schedule.
Cameras
Fore! integrates with IP security cameras, DVR's, NVR's and encoders that have implemented the ONVIF standard. Fore! can also act as a small scale network video recorder (NVR) for maximum 4 cameras.
Discovery
Use the Discover button to detect all available ONVIF cameras in your network. If your camera is not discovered you can use the Camera troubleshooting guide to fix common issues with your installation.
Settings
The Login and Password are used to login to the camera using the ONVIF protocol.
When a camera is set to Active Fore! will fetch live video images from the camera and show them it the interface. When Store video is checked Fore! will also store the video images on the harddisk. Fore! will try to create its own (M)JPEG ONVIF profile on the camera. If this fail it will use the highest quality (M)JPEG profile it can find.
Fore! stores video as a series of JPEG images in a folder on the harddisk. The location of the folder can be set at the image storage settings page. To reduce the file size Fore! by default uses motion detection to determine which images to store. For each camera the motion detection sensitivity can be set from 0% (no images stored) to 100% (all images stored).
Use the Video max storage days setting to set the maximum number of days video images are allowed to be stored.
Note The actual number of days of video storage of your Fore! server depends on harddisk size, number of connected cameras, the used bitrate and the amount of motion.
NVR / DVR / Encoders
ONVIF devices with multiple channels will be shown with the following icon:
. These devices will have an additional Discover button on the settings page that can be used to add their individual channels to Fore!.
Card codings
On the card coding settings page you can select which card coding Fore! should use as default card coding when adding new cards.
You can you use 6 types of access card codings with Fore!:
Fore! default card
UID
Wiegand 26
Wiegand other
PX007A
Custom
Card codings for Sirius readers
The Fore! default card and UID are used in combination with Sirius F30, Sirius F80 and Sirius F80P card readers. When a card is presented to a Sirius reader it will first try to read it as a Fore! default card. If this fails it will try to read the UID of the card.
All card codings
Check the All card codings checkbox when you want to use all card coding. The readers will automatic choose the rights card coding when the card is present to a reader.
Fore! default card
The Fore! default card coding is used when you are using Fore! Mifare encoded cards. Fore! Mifare cards can only be created by Keyprocessor / Fore! and use an 8 digit decimal card number e.g. "21208521".
All manufactured Fore! Mifare access cards (and tags) have a unique card number encoded in their sector. The card numbers are generated in random order. The Fore! Mifare card uses a Mifare Classic chip. This card is the default option in Fore! and currently offers the highest level of security.
UID
When you prefer to use your own access cards you can use any ISO/IEC 14443 Type A 13.56 MHz contactless smart card. Fore! will then use the unique identifier (UID) also known as card serial number (CSR) as a card number. Fore! uses a 14 digit hexadecimal byte swapped representation of the UID, for example "1a2b3c4d5e6f78" for a 7 byte UID or "0000001a2b3c4d" for a 4 byte UID.
You an use this option with most types of Mifare and Desfire access cards.
Card codings for Wiegand readers
If the Wiegand converter retrieves an input it will use the lenght of the input to determine which card coding should be used: if the input is 26 bit long a Wiegand 26 card number will be returned. If the input lenght is not equal to 26 bit it will return a Wiegand other card number.
Wiegand 26
A 26 bit input to the Wiegand converter is interpreted as a Wiegand 26 standard encoded access card. The format has one parity bit, 8 bits of facility code, 16 bits of ID code, and a trailing parity bit for a total of 26 bits. In Fore! this card is is represented using a 8 digit decimal number, e.g. "01200345" for a card with facility code "012" and card number "00345".
Wiegand other
All other input lenghts to the Wiegand converter are interpreted in the following way. The first and last bits are considered parity bits and not used. From the remaining bits the last 56 are converted to a 14 digit hexadecimal number e.g. "1a2b3c4d5e6f78".
Note In most cases this representation will not match the number that is printed on the card.
PX007A
Custom
The Custom card coding can be use with card with a Secret and Offset. Set the right Secret parameter en Offset parameter and the card will start to count form 0001 till ....
Custom Fields
Custom fields can be used to add your own input fields to the employees and visitors page.
Custom I/O
When an I/O in your installation is not in use by a card reader it can be used for other purposes as a custom I/O. Please refer to the Polyx NF+ Manual for wiring instructions.
Discovery
You can use the Discover button to find available I/Os. Fore! will only discover I/Os of Polyx NF+ network controllers that have at least one card reader configured.
Settings
The Polyx MAC and the I/O address can be used to identify the I/O on the Polyx NF+.
There are two Types of I/O: Input and Output.
Input
Each input has a NO/NC setting which can be set to Normally open or Normally closed.
When an input is activated a transaction is generated in Fore! For each configured custom input a special notification handling setting is created. Using this setting a notification or alarm can be triggered and messaging can be activated.
Output
Each output has a NO/NC setting which can be set to Normally open or Normally closed.
An output can have one of three modes:
Manual: The output is triggered manually using the I/O widgets. Use Set output status to set the initial state of the output: Always high or Always low.
Follow input: The output follows the state of another input. Use Follow this input to set the input which should be followed. You can select any input available in Fore! including the inputs used by readers. You can not follow an output.
Follow time schedule: The output follows a time schedule. Use Follow this time schedule to set the time schedule which should be followed.
Email messaging
Use email messaging to send emails when a notification or alarm occurs.
Note: In order to actually send email messages you have to enable messages for a notification in the notification handling settings.
You can configure an SMTP server that Fore! will use to send its email.
Configure a return email address in the Send from field. Enter the email addresses of one or more recipients to the Send to field. You can add multiple recipients to the Send to field separated by a semicolon ;. Enter the SMTP Host, a Port, Username and Password and select the type of Security that is used by the server.
Tip: Use the Send test message button to send a test message using the saved settings.
Employees
Employees in Fore! are persons who have a access to card readers during selected time schedules.
On the employee page a name and key number can be set for each employee. Optionally a PIN code can be defined for each employee for installations that include pincode readers.
Tip You can automatically add a key number to an employee by presenting an unknown card to a reader when the employee page is opened.
When the Override anti pass-back checkbox is checked the key number of this employee will not be limited by the anti pass-back mechanism that can be configured on readers. This setting is especially useful for employees designated to organize emergency evacuations of a building.
Use the Alternative unlatch time checkbox to indicate that this employee requires doors to be opened longer than normally. You can set the lenght of the alternative unlatch time at the access page of each reader.
Check the Arm/disarm intrusion checkbox to allow the employee to arm and disarm the intrusion system using the card readers. An employee can only arm and disarm at readers where he has access at that time.
Check the Office checkbox to allow the employee do set a door in office modus. The door can only be set in office modus if the time schedule is set at the the reader.
You can add your own fields to the employee (and visitor) form using Custom fields.
In the access table all card readers are listed with a checkbox for every time schedule. Check the checkbox to give an employee access to that card reader during that time schedule.
Tip You can use drag-and-drop to copy the access settings from one employee to another employee.
Event search
Use the event search page to search for transactions in your Fore! system.
Select a From and To date and time to filter the list of the results. Select All types to get all transactions or select and object to get only transactions related to that object. Use the Export events (CSV) button to export the filtered list of events to CSV.
Holidays
Holidays can be configured in Fore! to act as an exception to a time schedule during certain days. This allows you to restrict access or to keep doors shut during special days of the year. Holidays in Fore! are not recurring and have to be separately configured for each year.
Do not forget to check the Follow holiday schedule checkbox at the time schedule in order for it to follow your configured holidays.
Depending on the time configuration holidays function in the following way:
When no start time and end time are configured time schedules (that are configured to follow holidays) will stay inactive the whole day during the configured dates (indicated in red on the time bar).
Example: during Christmas 2014 time schedules are inactive for the whole day.
When start time and end time are configured time schedules will follow their normal schedule between the start time and end time (indicated as green on the time bar). Outside of the start time and end time the time schedules will be inactive.
Example: on Queensday 2014 the building is closed in the afternoon. In the morning time schedules follow their normal routine.
Image storage
Using the image storage settings you can select where on the server you want to store the camera images and how much disk space you want to use. Fore! can only store camera images to a local disk on the server.
The Max disk usage sets the maximum size of all stored video images as a percentage relative to the size of the harddisk.
Tip You can set a maximum number of days that camera images are stored for each camera individually at the camera settings.
Use the Alternative location to set a path on the server where the camera images should be saved. The default image store directory is \home\dvrec.
Intercom groups
Intercom groups are used to group intercom stations. Fore! uses intercom groups and their Time Schedules to route intercom calls.
Intercom
Fore! has an integrated SIP intercom server. Intercoms and VOIP-phones that support the SIP protocol can connect to Fore!.
The SIP protocol does not support automatic discovery of intercom devices. Instead, for each intercom an account has to be created at the server. An account consists of a phone number (also known as Station ID or user name) and a password. Intercom stations can register themselves using this Station ID and password to the server.
Direct calling
After an intercom station is successfully registered you can call it directly from another intercom stations using the Station ID (or stationID@ip.of.fore.server) as its phone number, e.g. 1001 or 1001@192.168.1.150.
Call routing
In order to let Fore! route your intercom calls to the correct intercom stations you have to set the Type and Intercom groups.
Type has the following two options:
Master: Use for intercoms stations where calls are received.
Slave: Use for intercoms stations where calls are started.
Add the intercom to one or more intercom groups using the intercom group checkbox list.
When a Slave intercom calls fore@ip.of.fore.server (e.g. fore@192.168.1.150) all Master intercom stations that are in the same intercom group as the Slave intercom will start ringing, but only when the intercom group is active according to its time
Example If you want a different intercom to be ringing depending on the time of the day you create two intercom groups each with a different time schedule. You add the Slave intercom to both groups and the Master intercoms each to a different intercom group.
Note You can use any unknown phone number instead of fore@ip.of.fore.server to route your calls with Fore!
Intrusion Detection
the supported hardware list for compatible intrusion panels.
Discovery
Use the Discover button to automatically discover compatible intrusion panels that are present in your network. Fore! will scan all ip addresses in the same /24 subnet as the server (e.g. server 192.168.1.150 will scan 192.168.1.1 till 192.168.1.254). If the MAC address of an intrusion panel is detected Fore! will try to load the intrusion driver specific to that intrusion panel.
Supported Intrusion detection
Alphatronics
AlphaVision XL ( > version 2.4 )
AlphaVision ML ( > version 3.51)
GE
Advisor MASTER ATS 3000
Advisor MASTER ATS 4000
Advisor MASTER ATS 4500
Honeywell
Galaxy Dimension series
Satel
Integra series
Jablotron
Jablotron 100
Notification handling
Using the notification handling settings a user can determine which events should result in a notification or an alarm.
Use Event to set if the transaction should results in a Notification or Alarm or None. When Messaging is enabled Fore! will also try to send notifications and alarms by email or to your mobile phone using Push messaging.
Push messaging
Using push messaging you can send messages to the Fore! app on your smartphone.
Push messages are delivered over the internet to registered smart phones even if they are not directly connected to your network. You can register your smart phone using the Fore! app on that smart phone only. Use the Remove registration button to remove a registred smart phone.
Note: In order to actually send push messages you have to enable messages for a notification in the notification handling settings.
Presence
Presence can be showed on the dashboard.Presence can be showed for :
Visitors
Employees
Overall - Visitors and Employees
Go to your dashboard and unlock it with the little pin at the left bottom corner of your dashboard.Click on one of the + and select the presence list you want.You can make the list bigger or smaller at the right bottom corner of the list.
When a person is in the presence list and you want to delete this person out of the list, you can select the person anda cross will appear. Click on the cross and the person will be deleted from the list. Anti pass-back will also be reset.
Relations
Relations are used to connect cameras, card readers, intrusion detectors and intercom stations to each other.
The possible relations and their effect in Fore! are listed below:
Camera - Card reader: Camera images will be shown at the card reader widget. Access transactions will be related to video clips.
Camera - Intrusion detector: Camera images will be shown with intrusion alarms. Intrusion transactions wil lbe related to video clips.
Camera - Intercom: Live camera images will be shown at the video intercom widget when the intercom calls.
Card reader - Intercom: Related door can be opened at the intercom widget.
Remote Access
Fore! can help you to set up remote access to your Fore! installation.
Fore! uses the following ports:
6061: Fore! http interface. (Do not forward this port)
8444: Fore! https interface.
4040: Camera images.
554: Camera RTSP streams.
You can use one of three options:
No automatic portforwarding: No automatic portforwarding.
Automatic portforwarding: Fore! will try to use uPnP to set up portforwarding to your system.
Manual portforwarding: Use this option if you configured port forwarding by hand. Fore! will use this URL when sending you notifications. Remote URL should have format "https://XXX.XXX.XXX.XXX:8444"
Warning: When choosing No automatic portforwarding remote access is not blocked! If you are directly connected to the internet or if you manually set up portforwarding the Fore! interface will be accessible from outside your network.
Use the Test connection button to test your connection. Fore! will use an external server to test if your Current remote URL is working.
Reports
Use the report page to generate reports about the usage of your Fore! system.
Use the from and to date time selectors (or the presets) to select the scope of the report. Three Report formats are supported:
PDF
CSV
XML
Door transactions
A report with all door transactions during the selected time period. The report will list Transaction time, Reader name'and transaction Description.
User login time
A report showing all Fore! logins during the selected time period. The report will list Transaction time, Login name and Name.
Time registration
A basic time registration report showing the presence of employees during the selected time period. The report will show a line for each person for each day that they used at least one reader.
Each line has the following data: Transaction time, Name, Key number, time of First check in of that day, time of the Last check in of that day, Duration which is the time difference between the first and last check in.
Note: Everytime a person is granted access at a reader this counts as a check in, regardless of the Area change of the reader. It is not possible to filter specific persons or card readers.
Presence
A report showing the Presence from Visitors, Employees or Overall.
Site information
Use the site information settings page to set the name of the site of your Fore! installation. The sitename is used when sending email notifications.
Sound
Use the sound settings page to set whether a notification or alarm sound should be played. Use the Test buttons to test if playing sounds is possible in your browser.
System Users
System users are employees who can login to the Fore! user interface.
Fore! distinguishes three system user roles: Technical manager, Facility staff and Secretary. After installation the first technical manager is made using the setup wizard. This user always has username root and cannot be deleted.
The three roles have the following application rights:
| Technical manager | Facility staff | Secretary |
Add, edit and remove readers, intrusion detection, intercoms, video sources, relations, system users, custom I/O | ✔ | ✘ | ✘ |
Add, edit and remove time schedules, holidays and visitor profiles | ✔ | ✔ | ✘ |
Advanced settings | ✔ | ✘ | ✘ |
Manage backup / restore | ✔ | ✘ | ✘ |
Set notification handling | ✔ | ✘ | ✘ |
Create and edit own dashboard | ✔ | ✔ | ✘ |
Create and edit other dashboard | ✔ | ✘ | ✘ |
Add, edit and remove employees | ✔ | ✔ | ✘ |
Add, edit and remove visitors | ✔ | ✔ | ✔ |
View video streams | ✔ | ✔ | ✔* |
View and handle notifications and alarms | ✔ | ✔ | ✔ |
View and control door access | ✔ | ✔ | ✔* |
View and control intercoms | ✔ | ✔ | ✔* |
Monitor presence | ✔ | ✔ | ✔* |
View intrusion detection status | ✔ | ✔ | ✔* |
Arm and disarm intrusion zones | ✔ | ✔ | ✔* |
Bypass detectors | ✔ | ✔ | ✔* |
Generate reports | ✔ | ✔ | ✔* |
Search historic events | ✔ | ✔ | ✘ |
* Only for widgets added to their dashboard by a technical manager.
Time schedules
All time related settings in Fore! use weekly time schedules. A time schedule is either active or inactive at a certain point in time.
Each weekday can have at most two time periods where the time schedule is active, for example on tuesdays from 8am to 11am and from 3pm to 6pm.
During holidays or other special days exceptions to a time schedule can be made using a holiday. When the Follow holiday schedule checkbox is checked the time schedule will follow all configured holidays.
Tip You can use drag-and-drop to copy the settings of a particular day to another day.
Tip You can drag-and-drop a time schedule from the list on the right to copy all days of that time schedule.
Video search
The video search page can be used to search and view all camera images that are stored by Fore! or by a connected NVR / DVR.
Use the From and To timewheels to select a timerange and click the Select button to view stored video for that camera in the selected timerange. Use the Export button to export a zip file with the camera images (not available when using a NVR/DVR for image storage).
Video player
1. Currently video time. | 7. Next frame. |
2. Previous motion frame. | 8. Next motion frame. |
3. Previous frame. | 9. Blue areas of the progress bar indicates movement detected by Motion detection . |
4. Play backward. | 10. Change video play speed. |
5. Pause video. | 11. Enable full screen mode. |
6. Play forward. |
|
Visitor cleanup
Using visitor cleanup you can automatically remove expired visitors.
When Remove expired visitors is checked every night all expired visitors will be removed. This removal happens at the same time as the daily backup. You can choose to keep the visitors for a set amount of days after they are expired.
Visitor profiles
A visitor profiles is a set of predefined access rights that can be assigned to a visitor.
In the access table all card readers are listed with a checkbox for every time schedule. Check the checkbox to give a visitor access to that card reader during that time schedule.
Tip You can use drag-and-drop to copy the access settings from one visitor profile to another visitor profile.
Visitors
Visitors in Fore! are persons who have only access during their visit and whose access settings can be set using a Visitor profile.
On the visitor page a name, key number and visited person can be set for each visitor. Optionally a PIN code can be defined for each visitor for installations that include pincode readers. Visitors can only be given access using visitor profiles and have only access between the visit start date and the visit end date. Visitors can be automatically removed after the visit end date using the visitor cleanup settings.
Tip You can automatically add a key number to a visitor by presenting an unknown card to a reader when the visitor page is opened.
Use the Alternative unlatch time checkbox to indicate that this employee requires doors to be opened longer than normally. You can set the lenght of the alternative unlatch time at the access page of each reader.
You can add your own fields to the visitor (and employee) form using Custom fields.
Troubleshooting
Camera troubleshooting
My camera is not discovered
Check network settings.
Check ONVIF compatibility.
Use an ONVIF tool to discover.
My camera shows no images in Fore!
Check Username and Password.
Set camera on MJPEG or install a VLC player to see the image in H264.
Reader troubleshooting
.
My reader is not detected
Possible causes:
Polyx NF+ network issuesThe Polyx NF+ requires a DHCP server in your network to obtain an ip address. Use a network scanning tool (e.g. Netscan to check if your Polyx has a network connection. (The MAC address of a Polyx NF+ will start with 001ED1______). You can check if the webinterface of the Polyx is running by opening the ip address in a web browser.
Reader not correctly wiredCheck if the reader is wired correctly. An often made mistake is the bundling of the orange with the orange-white and the green with green-white. The correct bundling is orange with green and orange-white with green-white.
Check Sirius F30 Manual
Check Sirius F80/F80P Manual
Check Wiegand Converter Manual
Sirius F30
Sirius F30 | RJ45 T568B color | RJ45 T568B pin | |
7 VCC (+) | Blue | 4 | |
6 GND (-) | Brown | 8 | |
5 |
|
|
|
4 |
|
|
|
3 |
|
|
|
2 | White/Orange andWhite/Green | 13 | |
1 | Orange andGreen | 26 |
Hardware manuals
Polyx NF+ Manual
The Polyx NF+ is a versatile network controller that is specifically designed to be used with Fore! security management software. The Polyx NF+ can either be powered using an external power supply or using Power over Ethernet, is equipped with an emergency battery circuit and has an onboard 12V lock power supply. Each Polyx NF+ can connect two Sirius card readers (Sirius f30, Sirius f80, Sirius f80P) or two Wiegand card readers using the optional Wiegand converter.
Mounting
Mount the Polyx NF+ using 35 mm mounting rail (NEN-EN 50022).
Power
There are two ways to supply power to a Polyx NF+:
using an external 24V power supply;
using Power over Ethernet (PoE);
External power supply
Connect a 24V external power supply to the power supply connector:
Connect common
When using an external power supply the common of the I/O section should be connected to the common of the power supply.
Connect the common of the power supply with one of the commons of the I/O section
Power over Ethernet
Use an Ethernet cable to connect the Lan/PoE+ port to a network switch with a PoE+ class 3 (max. 30mA) power output.
Emergency battery
The Polyx NF+ can be outfitted with an emergency battery to ensure the Polyx NF+ and the connected readers and door locks can keep working during a power outage.
Depending on the voltage requirements of your door locks there are two ways to connect your batteries:
When you are using the 12V onboard lock power supply to power your locks you can use the battery circuit of the Polyx NF+;
When you are using an external power supply to power your locks you can use the battery circuit of the external power supply;
12V Emergency power
Connect the emergency battery to the battery connector of the Polyx NF+:
24V Emergency power
Connect a 24V battery (or two 12V batteries) to the battery connector of your external power supply.
LAN
The Polyx NF+ is equipped with a 10/100Mbit Ethernet port (Gigabit Ethernet tolerant).
Connect an Ethernet cable to the Lan/PoE+ port of the Polyx.
Card readers
The Polyx NF+ can be used to connect one or two Sirius card readers or two Wiegand converters using port Reader 1 and port Reader 2. The readers are connected using a RJ45 connector and use a RS485 connection.
Connect a Sirius reader or Wiegand converter to port Reader 1.
Connect a Sirius reader or Wiegand converter to port Reader 2.
See the instruction manual of the Sirius reader or Wiegand converter for instructions on the pin layout of your reader.
I/O
The Polyx NF+ is outfitted with 12 common collector I/Os. Each I/O can switch a maximum of 1A/28VDC and is short-circuit proof. The I/Os are solid state relays (FET) which operate as “Normally open”.
The I/O are assigned to the two readers as follows:
Reader 1 | 1 | Detection loop |
2 | Request to exit | |
3 | Door contact | |
4 | Arm intrusion | |
5 | Door relay | |
6 | Door open too long | |
Reader 2 | 7 | Detection loop |
8 | Request to exit | |
9 | Door contact | |
10 | Arm intrusion | |
11 | Door relay | |
12 | Door open too long |
Door relay and lock
Although it is technically possible to switch door locks directly using the I/O it is highly recommended to use an additional relay switch. Depending on the power requirements of your lock you can wire the lock in two ways:
Using the onboard 12V lock power supply for 12V door locks with a combined power consumption lower than 600mA
Using the external 24V power supply for 24V door locks
Depending on your requirements you can connect the lock to the Normally open or the Normally closed output of the relay.
Important: Unless your lock comes with a build-in flyback diode it is strongly advised to install a flyback diode (i.e. 1N4001) as close to the lock as possible.
Door relay for 12V door lock
Connect the door relay of Reader 1 to output 5 (Door relay). Use the onboard 12V lock power output to control the relay switch.
Connect the door relay of Reader 2 to output 11 (Door relay). Use the onboard 12V lock power output to control the relay switch.
Connect the + output of the onboard 12V lock power to the common of the relay switch;
Connect the + connector of the door lock to the Normally open or Normally closed output of the relay switch;
Connect the – connector of the door lock to the common of the onboard 12V lock power;
Door relay for 24V door lock
Connect the door relay of Reader 1 to output 5 (Door relay). Use the external 24V power supply to control the relay switch.
Connect the door relay of Reader 2 to output 11 (Door relay). Use the external 24V power supply to control the relay switch.
Connect the + output of the external power supply to the common of the relay switch;
Connect the + connector of the door lock to the Normally open or Normally closed output of the relay switch;
Connect the – connector of the door lock to the common;
Door contact
The door contact input can be used to send feedback to Fore! about the physical status of the door: open or closed. When a door contact is installed Fore! can monitor the status of the door and can raise an alarm when the door is open too long or when the door is opened without authorization.
The door contact input uses a Normally open configuration: when the door is closed the circuit should be open, when the door is opened the circuit should be closed. You can achieve this by using a Normally closed switch that is held open by the closed door.
Connect a door contact switch to input 3 (Door contact) and common for Reader 1.
Connect a door contact switch to input 9 (Door contact) and common for Reader 2.
Door open too long (DOTL) alarm
The Door Open Too Long (DOTL) alarm output is used to activate an alarm light or buzzer to indicate that a door has been open for too long. The DOTL alarm will only work in combination with a door contact.
In most cases you can use the onboard 12V lock power to power the alarm. If a higher voltage is required you can use the 24V external power supply or an additional relay switch and wire it similar to the door relay switch.
Use output 6 (Door open too long) to connect an alarm light or buzzer for Reader 1.
Use output 12 (Door open too long) to connect an alarm light or buzzer for Reader 2.
Arm intrusion switch
The arm intrusion switch can be used to temporarily switch the card reader into arm intrusion mode. When the switch is closed the card reader will be quickly flashing red / green indicating it is ready to arm the intrusion system by presenting an accesscard.
Connect a normally open push button between input 4 (Arm intrusion) and common for Reader 1.
Connect a normally open push button between input 10 (Arm intrusion) and common for Reader 2.
Request to exit button
The request to exit button can be used to open the door from the inside when the door is not equipped with a door handle.
Connect a (normally open) push button to input 2 (Request to exit) and common for Reader 1
Connect a (normally open) push button to input 8 (Request to exit) and common for Reader 2
Detection loop
When the detection loop input is used the reader will only accept accesscards when a car is standing on the detection loop.
Connect a (normally open) detection loop to input 1 (Request to exit) and common for Reader 1
Connect a (normally open) detection loop to input 7 (Request to exit) and common for Reader 2
Technical data
Housing | |
Description | Aluminium extrusion profile, electronics cast into PUR synthetic resin. |
Measurements board | 273 x 16 x 118 x 16 mm (W x H x D) |
Measurements profile | 280 x 30 x 120 mm (W x H x D) |
Power supply | |
Voltage | 24VDCPoE+ class 3 power supply up to 30W output performance |
Consumption | 1.5 Watt excl. readers |
Charging current to battery: | Max. 105 mA |
Reader 1 and Reader 2 ports: | 12V, 250 mA |
RS232 Port | 12V, 100mA |
Inputs/outputs | |
12 IO | Max. 1A DC / 28V, default Normally Open |
Lock feed | 12V, 600mA |
Environment | |
Temperature | 20°C tot +60°C (in operation) |
Humidity | 0 to 95% (not condensing) |
Compliance
RoHS
Polyx NF+ complies to the „Directive on the Restriction of the Use of Certain Hazardous Substances in Electrical and Electronic Equipment 2002/95/EC‟ (RoHS).
CE Marking
The Polyx NF+ complies with the European requirements for safety, health and environment for the user.
Change ip address Polyx NF+ to Static ip address
By default the Polyx NF+ is set to DHCP
This can be changed using the terminal settings of the Polyx NF+ controller
Note Polyx NF + delivered before 17 March 2015 cannot be set to static and will have to be updated by Keyprocessor
In order to change the IP address you will need an adapter. You can make it yourself or order it from Keyprocessor BV.
How to
Connect your PC for example to port “Console” from the Polyx.
Open the terminal program and make a connection. Use Hyperterminal of Teraterm
Select the COM-port of the PC connected to the Polyx.
Choose a baud rate of “115200” and choose flow control “none”.
Restart the polyx
Wait until “Welcome To Diags press a key within 5 seconds to enter” appears.
Press any key. The diagnose main menu opens after 5 seconds.
Press 1 “Environment settings”.
Press 2 “Set environment settings”. The environments which can be set are:
ip_address= ip addressgateway_address= gateway addressnetmask_address= netmask addressdhcp=0 ( 0 is dhcp off / 1 is dhcp on)
Enter the environment address and press Enter. Then set dhcp=0
When finished, go back to the main menu.
You must reboot the Polyx for the changes to take effect, press “r”.
Sirius F80/F80P Manual
The Sirius F80 and F80P are card readers that are specifically designed to be used with Fore! security management software. The Sirius F80 and F80P card readers can read MIFARE Classic and DESFire EV1 access cards that use a Fore! encoding and the UID (or CSN) of Mifare and DESFire cards without a Fore! encoding. The Sirius F80P is equipped with a pinpad.
Location
Choose a location for the card reader that meets the following constraints:
The distance between the card reader and the Polyx NF+ door controller is less then 120 meter.
There is at least 20cm space between two card readers.
Mounting
The Sirius F80 and F80P are designed to be mounted on top of a 80mm junction box.
Pull the cable through the mounting plate.
Mount the back plate using two screws.
Connect cable to the 7-pin screw connector.
Remove the thin orange film from the buzzer.
Attach the top of the reader to the back plate and push the bottom towards the back plate
Close the reader using the enclosed 3mm screws.
Wiring
You can use a standard CAT5 UTP or CAT6 UTP network cable with RJ45 T-568B connectors to connect the card reader to the Polyx NF+.
Plug the RJ45 connector of one end of the cable in port Reader 1 or Reader 2 of the Polyx NF+.
Cut off the RJ45 from the other end of the network cable.
Remove the isolation and untwist the wires.
Combine the orange and green wires and connect them to pin 1 (A).
Combine the white/orange and white/green wires and connect them to pin 2 (B).
Connect the brown wire to pin 6 (GND).
Connect the blue wire to pin 7 (VCC+).
The white/brown and white/blue wire are not used.
Sirius F80 | RJ45 T568B color | RJ45 T568B pin | |
7 VCC (+) | Blue | 4 | |
6 GND (-) | Brown | 8 | |
5 |
|
|
|
4 |
|
|
|
3 |
|
|
|
2 | White/Orange andWhite/Green | 13 | |
1 | Orange andGreen | 26 |
Pinpad operation
To open a door using your access card and a pincode:
Present your access card to the reader.
The LED will start blinking red/green slowly
Enter your pincode.
Door will open.
To arm the intrusion using card and pincode:
Press *
The card reader is now in arming mode. The LED will start blinking red/green quickly
Present your access card to the reader.
The LED will start blinking red/green slowly
Enter your pincode
The LED will start blinking red/green quickly. When the intrusion alarm is armed correctly the LED starts blinking red/green slowly.
Tip When entering your PIN code, remove your finger at least 1 cm from the panel between each digit.
Technical data
Interface | RS485 (Polyx NF+) |
Supported cards | Mifare 1K, Mifare 4K, Mifare DESFire 0.6, Mifare DESFire EV1 8k, ISO14443A compatible |
Power consumption | 5-16 VDC, 0,7W average, 1,4W peak |
LED consumption | 12VDC, max. 1,8W |
Dimensions | 80mm x 80mm x 13mm (HxWxD) |
Reading distance | 5mm-70mm ISO14443A Mifare card |
Environmental rating | IP64 |
Operating temperature | -31º to 150º F (-35º to 65º C) |
Storage temperature | -67º to 185º F (-55º to 85º C) |
Operating humidity | 5% to 95% relative humidity non-condensing |
Transmit frequency | 13.56 MHz |
Standard | ISO14443 A |
Indicators | 2x RGB LED and 1 buzzer |
Connection | 7-pin screw connector |
Certifications | CE |
Wiegand Converter Manual
The Wiegand/ClockData converter is used to connect a Wiegand or Clock/Data card reader to the Polyx NF+ door controller.
Wiring
Connect the card reader to the Wiegand converter using standard UTP or 6x0,34mm2 cable.
Use a standard UTP network cable with RJ45 T-568B connectors to connect the Wiegand converter to the Polyx NF+.
Pin | Description |
1 | Data / D0 |
2 | Clock / D1 |
3 | LED / Tamper |
4 | IO / Buzzer |
5 | GND |
6 | VCC (output) |
Technical data
| Wiegand | ABA / Clockdata |
Maximum cable distance (Polyx - converter) | 600m | ? |
Maximum cable distance (Converter - reader) | 100m | ? |
Output voltage | 13-14 VDC | |
Output current | 20mA average, 50mA peak | |
Dimensions (mm) | 57x26x21 | |
Operating Temperature | -25 to +65 °C / -15 to 150 °F | |
Operating Humidity | 0 – 95% non condensing | |
Connection | RJ45 connector,and 6 pin not removable connector | |
Certifications | CE, FCC |