Gard pro

Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

Description
Fortress RFID Access Network Keys (FRANK)
Access control via RFID can be integrated into any Fortress PROFINET or Ethernet/IP enabled device. Existing site access
cards can be used by selecting the appropriate RFID reader. The FRANK industrial access control Software and Controllers
offer administrative management of who can perform certain tasks in access or machine control applications. FRANK
technology utilizes RFID cards and provides a web-based platform to assign permissions to device locations.

When an RFID card is presented to the RFID reader, the reader communicates with the FRANK System to determine
permission state. This is returned to the unit and allocated as an access control bit which is fed back to the PLC directly from
the Fortress (RFID enabled).

FRANK Systems use separated software for reliability. FRANK Local Software directly communicates with Fortress
PROFINET or Ethernet/IP enabled devices on a controls network, discovering devices and assigning them to a specified
location. FRANK Master Software communicates with any FRANK Local Controllers to update user-location permission
changes and record data.

Additional features allow the monitoring of I/O states, Combination of Locations, Access Count information amongst others;
please contact your Fortress representative for more information.

Any hardware running FRANK software is referred to as a “Controller”. Fortress provides FRANK Local Controllers with
FRANK Local Software installed. Fortress recommends customer install FRANK Master Software on a capable PC or VM,
Fortress does not provide dedicated hardware for FRANK Master Software. Small scale systems may allow both FRANK
Local Software and Master Software to be installed on a single controller - please contact your Fortress representative for
more information. These operating instructions relate to software version 1.5.1.0 & firmware version 3.6.15.
Contents
FRANK System Topology and Existing Control System Architecture & Topology
Technical Specification of the components of the FRANK system
• RFID Reader
• Local and Local-Master Controller (FACS-L1 & FACS-LM)
I/O Mapping your device with the Control System

1. Set Up of Devices – Installation of Fortress Hardware, IP address assignment and establishing PLC communication.
2. Configuration of Local Access Controller
• 2.1 Discovery and Administration of Fortress RFID enabled Devices
• 2.2 The Local Controller Menu
• 2.3 ACS (Access Control System) Info
• 2.4 Configure Devices
• 2.5 Create a Location
• 2.6 Editing a Saved Location
• 2.7 Creating a Linked Location and Accessing Count
• 2.8 Accessing Count via a WebAPI
• 2.9 Creating an I/O Monitoring Scheme
• 2.10 System Administration
3. Configuration of the Master Server
• 3.1 The Master Server Menu
• 3.2 Creating Users, Adding and Administration of Cards
• 3.3 Connections - Discovery of Local Access Server
• 3.4 Additional Permissions
• 3.5 Additional Information
4. Upgrading the Local or Local-Master Software
• 4.1 Local Software
• 4.2 Master Software
5. Installation of the Local or Local-Master Hardware
6. Managing Events
7. Service, Inspection, Disposal, and Liability

1
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

Existing Control System Architecture & Topology

FRANK can be fitted as an integrated system or as a retrofit to an existing system.
The existing system architecture must include a programmable logic controller.
Access control can be integrated into the design for any Fortress PROFINET or Ethernet/IP enabled device through the
addition of an RFID Reader. The reader acts as an intermediary between an operators’ card and access controller and allows
the association of RFID data to a user and controller defined permissions. Some examples are pictured below.

FRANK System Topology

A Fortress FRANK system is composed of three core elements:

RFID Reader Local Controller Master Controller

with a permissions database to provide a single point of
to ensure connectivity. permissions management &
data collection within a facility.

Topology combined local-master hardware – the Master & Local Controller can be combined into one piece of hardware for
small scale systems up to 15 devices controlled via a single PLC.

Topology Local hardware & Master software - In larger systems, the Master and local can be separated to support system
expansion. This is required where the FRANK Access Control Systems is deployed to Fortress devices across multiple PLCs
or zones.

Local controller provides robustness and Master controller syncs with local controllers
line-side communication for central management

2
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

Standard Functionality
The RFID reader is activated by presenting an RFID card to the front surface of the reader, to request access, authorisation
or register interaction. The user’s access permissions are checked against the database in the Local Access Controller.
If permission is granted, the device with the RFID reader will send the signal to the PLC. The PLC then instructions the
desired function. The RFID reader can be activated a second time by each operator who has gained access previously.
Once all operators have signalled they are out of the area, a ‘Cell Empty’ signal is sent to the PLC.

Features List
• Control access to Fortress enabled devices using unique RFID site cards
• Manage permissions of RFID cards to specific locations, functions, and actions
• View a live count of users who have presented their card to an RFID reader and received an access granted signal
• Link locations to allow users to perform actions from separate devices
• Collect date, time, user, and status on permission requests
• Collect date, time, and operation of non-safe inputs and outputs on the device
• Detect and record use of escape release and auxiliary/emergency override functions (N/A for devices without guard locking)
• Record a 32-bit numerical string of data to the event log assigned to a time and date
• Assign additional permissions to RFID cards to command external PLC instructions

FRANK Technical Specification

Fortress RFID Reader
Part No. Supported Standards RF Transmission Frequency Required Read Duration
RA RFID Card 1 13.56MHz ISO 15693 13.56MHz <100ms
R_ Other variations are available upon request

Options & Ordering Information

A control or access solution will require an integrated RFID reader within a PROFINET or EtherNet/IP enabled device.
Part No. Item No. Part Description Additional Information
Fortress RFID Reader
RFID reader supplied in amGardpro proNet
RA ITM-00321208 Proprietary RFID Card 1 13.56MHz ISO 15693
Devices and supplied with RFID cards
RFID reader supplied in amGardpro proNet
Fortress solutions offer compatibility with existing RFID site cards with a
devices
variety of 13.56MHz and 125kHz options – speak to our team to design a
solution which utilises these existing cards within the RFID reader.
Existing on-site cards utilised
Combined Local-Master Hardware
Combined Controller installation for small
FACS-LM ITM-00386430 Local & Master Controller System
systems
Local Hardware & Master Software
One Local Controller is required per PLC
FACS-L1 ITM-00339530 Local Controller System
network
Master Controller System - Software only for
FACS-M2 ITM-00339536 One software installation per facility
customer installation

Important:
All Fortress products and systems are designed for use according to the installation and operating instructions enclosed.
It must be installed by competent and qualified personnel who have read and understood the whole of the relevant
documentation prior to commencing installation. Please ensure that your current software is compatible with this version
of instruction. The Fortress Access Control System is an additional administrative layer providing access and authorization
control. It is not a safety solution. Fortress Interlocks Ltd accepts no liability whatsoever for any situation arising from misuse
or misapplication of this product.
IF YOU HAVE ANY QUESTIONS OR QUERIES OF ANY NATURE WHATSOEVER, PLEASE CONTACT THE SUPPLIER
WHO WILL BE PLEASED TO ADVISE AND ASSIST.

3
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

Environmental Data RFID Reader FACS-L1 / FACS-LM

Ingress Protection IP65 -
Ambient Temperature -5°C to +60°C 0°C to +55°C (with air flow 0.5m/2)
Connector Type N/A DC-in Jack Connector for power included
See relevant information for
Operating Voltage 12-24VDC
host unit
See relevant information for
Operating Current -
host unit
Environment Type Indoor & Outdoor Indoor

Tested in accordance with:

Shock and Vibration Resistance -
GS-ET-19

(Operating Humidity) 0% - 90% relative humidity,

Maximum Relative Humidity 80% at ≤31°C, 50% at 40°C
non-condensing
Maximum Operating Altitude 2000m -
Pollution Degree (IEC 664) Degree 2
Transient Overvoltages Installation Category III -
*Operational values are based on the 0.26 Grms profile. These values are tested for all operational orientations and are retrieved from two minutes per test
orientation with IO meter. NOTE: All screws are embedded with a Nylock seal to resist vibration and loosening.
**Non-operational values are based on the 1.54 Grms profile. These values are tested for all non-operational orientations and are retrieved every sixty
minutes per test orientation with IO meter.
***The values are tested for all operational orientations and are retrieved every five hours per test orientation with IO meter.

Local or Local-Master Controller (FACS-L1 / FACS-LM)

Note: these operating instructions detail information for the UPN Edge Pro controller hardware. For other hardware, please
contact your local Fortress representative for previous editions of the FRANK operating instructions
Ethernet Gb Ethernet (full speed) RJ-45 x2
Power DC-in Jack A-coded 5.5mm OD 2.1mm ID
Certification CE/FCC Class A, RoHS Compliant, REACH
Weight 982.5g (less mounting bracket)

Ethernet Port 1
Controls Network

Ethernet Port 2
Connection to Master
(Local hardware and Master software)
Connection to Local Network
(Combined Local-Master)

4
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

The FRANK system is implemented in multiple stages. A simplified process is detailed below. It is recommended that FRANK
systems are implemented by an approved installer.
Step 1 – Set Up of Devices – Fortress Networked (or proNet) devices must be installed, have assigned IP
addresses and established communication with the PLC
Please see the relevant ‘Fortress Ethernet IP - CIP Safety Configuration’ instructions or ‘PROFINET - PROFIsafe
Configuration’ instructions, available on the Fortress Website. For supply voltages and mounting guidelines see technical
detail.
The Fortress Access Control System is designed to be programmed as simple inputs to Fortress amGardpro proNet or
‘Networked’ devices. These additional inputs are shown below.
Bits
Description
0 1 2 3 4 5 6 7

Bit is set when the

Byte 0 Byte 0 - - - - - - - -
switch is pressed

Extended
Byte
I/O Data Reserved - - - - - - - -
1-4
1&2

Gate Bit is set when

Monitor Byte 5 the tongue is out Head Mon. - - - - - - -
Byte 0 of the head
Solenoid Bit is set when
Sol.
Monitor Byte 6 the gate is - - - - - - -
Mon.
Byte 0 unlocked
Byte
RFID RFID Unique ID
7 - 14
Access Control Inputs
Access
Control Byte Access Access
Error Cell Empty - - - -
Input 15 Granted Denied
Byte 0
Access
Additional Additional Additional Additional Additional Additional Additional Additional
Control Byte Additional
Permission Permission Permission Permission Permission Permission Permission Permission
Input 16 Permissions*
Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit 5 Bit 6 Bit 7
Byte 1
Non-Safe Outputs (7 Bytes)
Lamp is
Byte 0 Byte 0 illuminated when - - - - - - - -
bit is set
Extended
Byte Byte Monitoring
I/O Data - - - - - - - -
1-4 and Data Capture
1&2
Solenoid The solenoid is
Drive Byte 5 energised when Sol Drive - - - - - - -
Byte 0 the bit is set
Access Control Outputs
Access
Control
Byte 6 Reset - - - - - - -
Output
Byte 0
Safety Inputs (3 Bytes)
Byte 0 Byte 0 Reserved - - - - - - - -
Set this bit to
reset the relevant
QS bit if an Head/ Sol
Byte 1 Byte 1 - AUX QR - E-Stop QR - - -
invalid state has QR
been
experienced
Byte 2 Byte 2 Reserved - - - - - - - -
Access control bits will pulse high for 100ms as determined by the access control system. If a user is permitted to unlock the interlock, Access Granted will pulse high. If a user is
not permitted to unlock the interlock, Access Denied will pulse high. When the interlock is relocked, Cell Empty will pulse high.
Error Bit 0 will go high if unit is disconnected from a Local Controller.

*Additional permissions are set in the system software as a whole byte, giving 256 possible additional permissions. Alternatively, individual bits could be used.

5
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

Step 2 – Configuration of Local Access Controller

Perform electrical installation of Local Access Controller(s)
Access the Local Access Controller System via an Ethernet Connection and remote desktop with the Fortress provided
username and password. Set a static IP address for Ethernet Port 1 to the chosen address on the controls network – default
IP 50.47.43.250. Set a static address for Ethernet Port 2 for use with Master Access Controller Network* -
default IP 172.16.8.10.
* To navigate to this web page: 5000 should be added as a suffix to the IP address.
2.1 Discovery and Administration of Fortress RFID enabled Devices
2.1.1 Access the Local Access Controller web page at 172.16.8.10:5000 (default) or the address set during configuration (as
described above, using the address correlating to the Ethernet port you are currently connected to).
2.1.2 Access the Master Access Controller via web page at XXX.XXX.XXX.XXX using the same IP address as above.
2.1.3 Select ‘Login’, using the Fortress provided username and password and select the blue login button at the bottom of
the screen. If ‘Register’ appears instead of Login, see step 2.1.4
XXX.XXX.XXX.XXX:5000 (Local Access Controller) XXX.XXX.XXX.XXX (Master Access Controller)

2.1.4 Register Request

You may be asked to register this device instead of ‘Login’. If you select this button you will be re-directed to set up a new
username and password. Once set up, select the blue ‘Register’ button at the bottom of the screen.

2.2 The Local Controller Menu

The Local Controller Menu displays Events* (interaction with FRANK enabled devices), ACS Info (information about the
access control system), Devices (FRANK enabled devices configured to the network), Locations (physical positions within an
installation a FRANK device is associated with), Linked locations (to group locations together), I/O Monitoring (to set up what
additional information a device can share such as safe and non-safe inputs and outputs), and System (to control operation of
the system).

*Events are always displayed, even if the user is not logged in

6
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

2.3 ACS Info

2.3.1 Navigate to ‘ACS Info’ on the local controller menu

2.3.2 Check IP (Fortress Device Communication) to controls network address. This is the port on the controller connected to
the controls network and affects how device discovery occurs.
This will use default IP address 50.47.43.250

2.3.3 Check IP (Master Communication) to corporate network address.

This will use default IP address 172.16.8.10

2.3.4 If either of 2.3.3 or 2.3.4 appear incorrect, select the button at the bottom of the screen. Select the correct
address and click to save changes.

2.4 Configure Devices

To establish a connection between installed devices and the FRANK software, each relevant Fortress PROFINET or EtherNet/
IP enabled device on the network must be discovered and configured through ‘Devices’.

2.4.1 Navigate to ‘Devices’ on the local controller menu

2.4.2 Select ‘Discover’ to discover Fortress RFID enabled devices.

2.4.3 The list of discovered devices will appear greyed out below the section ‘Non configured devices’. Ensure all installed
Fortress devices have been discovered.

2.4.4 Select on each device to be configured on the network. If more than one device is being configured, you can
click the tick-boxes alongside the devices or you can click ‘configure all’. The Image pictured below shows an example device
discovery.

2.4.5 When successful, a message will appear on screen stating ‘success’. Check all installed
Fortress devices have been discovered on the controller and configured. You will see configured
devices will appear as ‘Assigned: Not Assigned’ as a location will need to be selected for this device.

Note: If an error message appears, this could be because the device is not recognised by the PLC
(pictured, example error message). For support, contact your local Fortress representative.

2.5 Create a Location

Locations are set up to differentiate physical locations with installed devices. Recording of device interactions and data
collection is associated with a location.

2.5.1 Navigate to ‘Locations’ on the main menu

2.5.2 Select ‘Create’ to create a new location

2.5.3 In the field, ‘Name’ enter a Name for this location

Under ‘Assigned Interlock Unit ID, select the reference of the interlock you wish to assign to this location
Under I/O Monitoring Scheme, select an existing I/O monitoring scheme (for more information, see the I/O Monitoring set up
section).
Select to complete set up of the location.

7
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

2.6 Editing a Saved Location

In the ‘Edit Location’ field, the following parameters can be altered;
Location Name : Locations can be renamed
Assigned Interlock Unit ID : Can be altered to the desired unit
I/O Monitoring Schemes : Can be set for specific locations

The following parameters will be visible; IP address, MAC address,

Fortress Version, Hms Version Abcc, and Hms Version T100.

At the bottom select ‘Enable’ to ensure this location is live

Select to stop the edit, and return the location to previous settings unsaved

Select to save the changes made to this location

Select to permanently delete this location

2.7 Create a Linked Location

Linked Locations (created from the Local Access Controller) provides a linkage between locations which provide access to the
same location. This function can be used to link operator counting in cases where operators enter through one interlock and
exit via another. Interlocks must be connected to the same Local Access Controller for linked locations.

2.7.1 Navigate to ‘Linked Locations’ on the main menu

2.7.2 Select Create to create a new location

2.7.3 Create a ‘Name’ for the Linked location under the field Name and select the doors to link at this location. Select Save to
create the linked location or cancel to remove unsaved changes.

8
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

2.7.4 A count is available for all ‘locations’ and ‘linked locations’ which allows systems to share the number of users who
have entered the linked location i.e. entering through either Door 1 or Door 2 of Zone 1, and the exact time of their entry.

2.7.5 To access the number of users in this location on the webpage, select ‘Count’. The count page can be shown even
when logged out of the system via a unique URL (this link can be bookmarked or set as the default webpage to display
automatically at power on). The number of users are listed under the ‘Count’ field, the users’ assigned name and Card Tag
listed underneath alongside the ‘Entry Time’ including both date and time fields. Select ‘Back’ to return to the Linked Locations
screen.

2.8 Accessing via a WebAPI

Access a webAPI for the user count via unit ID; http://[IP Address]:5000/api/usertracking/location?unitId=[unitId] or via location
name; http://[IP Address]:5000/api/usertracking/location?locationName=[location name].
Where ‘XXX.XXX.XXX.XXX’ is the IP address for the local controller and XXXXXXXX is the unit ID of the device. For example,
where the IP address is 172.16.8.10 and the unit ID is 21060092W, access can be achieved via;
http://172.16.8.10:5000/api/usertracking/location?unitId=21060092W

Data via a WebAPI will be outputted in the form;

{“count”:Number, ,”locationName”:“Location Name”,”locationId”:“Location ID”,”users”:[{“tag”:“User Tag ID”,”name”:“User
Name“, “entryTime”: “DD-MM-YYYY hh:mm:ss”}]}
2.9 Creating an I/O Monitoring Scheme

I/O monitoring schemes allow the operation or activation of safe and non-safe I/O to appear in the Events window as ‘True’
when a bit is set high, and ‘False’ a bit is set low following a high bit. I/O monitoring can also be used to share numeric data to
the FRANK system for data capture.

Navigate to ‘I/O Monitoring’ on the main menu. Select to create a new scheme and enter a name in to the ‘Name’ field

Two types of monitoring scheme can be created – Bits or Byte

Byte Monitoring; utilizes a 32 bit communication from an external source via non-safe outputs Bytes 1-4 (EtherNet/IP) or
Extended I/O Bytes 1 & 2 (PROFINET)

Bit Monitoring; provides event window capture of safe and non-safe I/O activation.

9
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

2.9.1 Data Capture – Byte Monitoring

Data capture utilises non-safe output bytes 1-4 (for EtherNet/IP devices) or Extended IO Data 1 & 2 (for PROFINET).
Bytes 1-4 (EtherNet/IP): 4 Bytes of 8 bits, totalling 32 bits
Extended IO Data 1 & 2: each 2 Bytes of 8 bits, totalling 32 bits

Bits
Description
0 1 2 3 4 5 6 7
Non-Safe Outputs (17 Bytes)
Extended
Byte Data Capture and
IO Data 1 - - - - - - - -
1-4 Byte Monitoring
&2

The 32 bit value encoded on the extended I/O is recorded in the event log as a decimal value.
2.9.2 Operator Controls Monitoring – Bit Monitoring – Non-safe Inputs
Note: A monitoring scheme is limited to monitoring a maximum of 32 bits. The I/O monitoring scheme will allow incoming data
to display use of different safe and non-safe I/O elements in the networked product. The following instructions for creating an
I/O monitoring scheme will use the pictured image for reference as an example.

The example product pictured overleaf is an EI2A6SRP11SVRALY0000NNDLGLRP6ETNPF10MPB1. Non-safe inputs on this

device include the (blue) push button, and the monitors on the actuator entry (Head Monitor) and solenoid locking (Solenoid
Monitor).

Select ‘Input on the I/O Monitoring Scheme. Names are listed in reference to their position on the Fortress Memory Map
where the name is in the format Input X_Y where ‘X’ is the Byte, and ‘Y’ is the Bit.
Bits
Description
0 1 2 3 4 5 6 7
Non-Safe Inputs (17 Bytes)
Bit is set when the Blue Push
Byte 0 Byte 0 - - - - - - -
switch is pressed Button
Gate Bit is set when
Monitor Byte 5 the tongue is out Head Mon. - - - - - - -
Byte 0 of the head
Solenoid
Bit is set when the Sol.
Monitor Byte 6 - - - - - - -
gate is unlocked Mon.
Byte 0

In the example below, Input 0_2 (byte 0, bit 2) is changed to ‘BLUE_RESET’.

Tick the box to select monitoring this Input.

10
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

When the Blue push button is pressed, Bit 2, Byte 0 will be set, creating an event on the Events dashboard. This appears as
(event 1) ‘Name : True’ when the button is pressed, followed by (event 2) ‘Name : False’ when the button is released.

Head and Solenoid Monitors for non-safe input of guard unlocking and guard opening are already pre-set.
When the guard is unlocked, Byte 5, Bit 0 is set (Input 5_0)
When the guard is opened, Byte 6, Bit 0 is set (Input 6_0)

Guard Unlocked Tongue Removed

2.9.3 Operator Controls Monitoring - Bit Monitoring - Non-safe Outputs
Bits
Description
0 1 2 3 4 5 6 7
Non-Safe Outputs (7 Bytes)
Lamp is illuminat- Green Yellow
Byte 0 Byte 0 Red Lamp Blue Lamp - - - -
ed when bit is set Lamp Lamp
Solenoid The solenoid is
Drive Byte 5 energised when Sol Drive - - - - - - -
Byte 0 the bit is set

To set up non-safe outputs, select ‘Output’ on the I/O monitoring Scheme.

Names are listed in reference to their position on the Fortress Memory
Map where the name is in the format Output X_Y where ‘X’ is the Byte,
and ‘Y’ is the Bit.

The Green, Red, Blue and Yellow lamps can be named to the relevant Byte/Bit position selecting the ‘Monitor’ with a tick.

2.9.4 Operator Controls Monitoring - Bit Monitoring - Safe Inputs

The safe inputs, including but not limited to ‘emergency stop’, ‘safety on guard locking (Head/Sol CH)’ and ‘safety on guard
(Head CH)’ are set up by selecting ‘Safety Inputs’ on the I/O monitoring scheme. Names are listed in reference to their posi-
tion on the Fortress Memory Map where the name is in the format ‘Safety Input X_Y’ where ‘X’ is the Byte, and ‘Y’ is the Bit.
Bits
Description
0 1 2 3 4 5 6 7

Safety Inputs (3 Bytes)

Bit is reset when
the relevant Head/S of Head/S of
Byte 0 Byte 0 - - E-Stop 1 E-Stop 2 - -
safety signal is CH1 CH2
broken
Bit is reset when
the relevant safe- Head/S of Head/S of
Byte 1 Byte 1 - - E-Stop QS E-Stop QS - -
ty signal is invalid QS QS
(latching)

11
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

To set the Head/Sol CH1 and CH2, enter into Safety Input 0_1 and 0_2 respectively. For a emergency stop component on
your Fortress device, enter the details into the Safety Input 0_4 and Safety Input 0_5 respectively.
Input
Safety Inputs

Section Name Byte Number Bit Number Monitor

Safety Input Unlocked _SC1 0 0 Yes

Safety Input Unlocked_SC2 0 1 Yes

Safety Input Safety Input 0_2 0 2 No

Safety Input Safety Input 0_3 0 3 No

Safety Input Estop_SC1 0 4 Yes

Safety Input Estop_SC2 0 5 Yes

2.9.5 Applying your Scheme

To complete the creation of an I/O monitoring scheme, select ‘Save’. To edit this scheme at any time, select ‘Edit’ next to the
relevant scheme. Select ‘Apply’ to apply the changes to the I/O monitoring scheme. A monitoring scheme will not apply until
there is a power cycle to a unit or the apply button is selected on the monitoring scheme. Please note the apply button will
interrupt comms during update.

When this is correctly applied, you will see a green message appear at the top of the screen as pictured below;

To assign the monitoring scheme to your location, select ‘Locations’ on the navigation menu at the top and edit on your
relevant location.

See page 17 for viewing event data in the event log.

IMPORTANT: On the local controller, navigate to ‘ACS Info’ and select edit. On the ‘Access mode’ change from
‘Diagnostic’ to ‘Enabled’. Diagnostic mode can be used for commissioning, to grant access to all users without
permission rules.
2.10 System

Set IP Address
See commissioning section page 6.

IMPORTANT Do not perform without Fortress guidance as you may permanently damage your system.

Restart FRANK service

To restart a FRANK service, navigate to ‘Restart FRANK
service’. This function is used for advanced diagnostic
purposes.

Shutdown FRANK service

To shutdown the FRANK service, navigate to ‘shutdown
FRANK service’. This function is used for advanced
diagnostic purposes.

Shutdown system
This function is used to shutdown the system safely without any possibility of data loss and without removing the power
supply. To repower hardware, physical access is required.

12
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

Step 3 - Configuration of Master Server

(Installing a FACS-M1) Access the following files.
Transfer ‘FRANK.Master.Installer’ to the required desktop.
Open ‘FRANK.Master.Installer’ and Run the file ‘FRANKMaster v1.5.1.0.exe

Access the Master Controller Software via an Ethernet Connection and remote desktop with the Fortress provided username
and password. Use default IP 172.16.8.10. Access to the Master Server should be protected as this platform is used to
manage permission assignment and system users.
3.1 The Master Server Menu

The Master Server Menu displays Users (operators assigned permissions on the FRANK system), Connections (Access
Control devices (or ‘Local Controllers’) connected to the network), Additional permissions (a feature to enable further logic
to be applied to particular system users), Interactions (recorded interactions with FRANK enabled devices via all established
local controllers), and Settings (General settings for further functionality).
3.1.1 Logging in and Registering an Account
Access the Master Controller using the default IP address or the address set during configuration. You may be asked to
register an account instead of ‘Login’. If you select this button you will be re-directed to set up a new username and password.
Once set up, select the button at the bottom of the screen.

3.2 Creating Users, Adding and Administrative Controls

The following section details how to add users & unique RFID references, and assign permissions based on locations.

3.2.1 To set up users, you must access via the master controller, located at the IP address [default IP Address].
Use your login and password to access the master server. Navigate to ‘Users’ on the top menu.

3.2.2 Manual User Addition

Select to create a new user on the system. In the fields enter the following information;

User ID : Enter a unique identifier for this individual. This field is non-editable once set.
Full Name : Enter a name reference for this individual. This is editable once set.
Card : Enter the unique RFID reference for this users’ ID card (this can be
found by either scanning a card to the FRANK enabled device to view in
the events field, or using an RFID scanning device). This field is editable if
a card requires replacing.
Enabled : to enable this user on the system, tick enabled.

13
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

3.2.3 Adding Permissions

Under Permissions, select ‘Granted’ where this user has permission. Leave the box unticked where permission is
denied to this user. In the example below, this user is given permission to use both the device at Zone 1 – Door 1 and the
device at Zone 1 – Door 2.

Ensure the user is granted access to the desired location(s).

Select “Save”.
Permissions sync every 60 seconds; to cause immediate sync, select “Apply Permissions”.
3.2.4 View and Restore Removed Users

3.2.5 Timed Access

A period of time can be specified in which the access permissions given to a user is valid, permission to access any location
will be automatically removed outside this defined period.
A common use case is when contractors will be on site for a certain period, the system admin can set this valid time period in
FRANK, outside of which the cards assigned to the contractors cannot be used to access the on-site locations.

View the current time limits for a user

The type of timed access of a user can be seen in the Manage Users table:
• Unrestricted – Permissions assigned to the user are always valid.
• Valid until [date] – Permissions assigned to the user are valid until the expiry date.
• Valid from [date] – Permissions assigned to the user will start taking effect on the start date.
• Expired on [date] – The user no longer has any access to the site.

14
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

To view the set time limits for a user, press ‘Edit’ on its row, and the currently set time limits will be displayed in the Valid From
and Valid Until fields.

3.2.6 Add Time Limits to a New User

When creating a new user, the time limits can be selected from a date picker after ticking the Limited Time Access checkbox.
Input rules:
• When Limited Time Access is ticket, Valid From and Valid Until fields cannot be empty.
• Start date cannot be later than the end date.

15
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

3.2.6 Add / Edit Time Limits

In the Users page, press ‘Edit’ of the user.

Within the Edit section, check the Timed Access checkbox, which will reveal the Valid From and Valid Until date pickers.
Select the desired dates and press Save.

3.2.7 Remove Time Limits from a User

In the Edit section of a user, uncheck the Timed Access checkbox, and press save. This will remove any time limits from a
user, the ‘Timed Access’ column of the user will appear as ‘Unrestricted’.

16
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

3.2.8 Bulk Import of users

Users can be bulk imported via a CSV instruction on screen. Select “Import” and follow CSV instruction on screen.
Note: If using Fortress supplied cards position curser in card number field, use a FACP-C1 card reader (or other appropriate
USB connected reader) to scan card. This number will then be populated in the field.

To mass import users, create a CSV file with a list of values with a delimiter or as pictured below with (case sensitive) column
headers; UserId**, Full Name, Access Card, Permission* (optional). Microsoft Excel is recommended for this dataset.
*A ‘Y’ for Yes and ‘N’ for No can be applied to the permission column to assign access to all or no locations, respectively.
** UserId must be a single string of text no spaces

Select File > Save As

Enter a File Name
Save as Type ‘CSV UTF-8 (Comma delimited) (*.csv))

On the Master Server, navigate to ‘Users’

Select Import & Browse to select the desired file.

When complete the success message will appear and users can be edited.
3.3 Connections - Discovery of Local Access Server (when using FACS-M1 only)

Note: this step must not be performed

when using a FACS-LM.

Navigate to ‘Connections’ on the Master Server and select to locate all Local Access Servers on the
network.
All Local Server systems should be listed in green below displaying these are online. Ensure the status is

To change the name of a given Local Access Server, select . Select to save changes or to delete changes.

Access to a specific Local Server system is possible by selecting on the relevant listed ACS.

17
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

3.4 Additional Permissions

Additional permissions are defined on the master server and provides an extra byte of information which can be attached
to a user per location. Navigate to Additional permission via the menu on the Master Server. Select ‘create new’ to build an
additional permission assigned to a whole byte.

Enter a name reference into the ‘Name’ field.

Enter an 8-bit value associated with the additional permission bits in the access control inputs referenced on page 3.
Select ‘Save’ to complete creation of this additional permission set.
To edit the additional permission select ‘Edit’ on the relevant field, or ‘Delete’ to remove this additional permission.

Under ‘Users’ on the main menu, select a user

to assign the additional permission to. Additional
permissions can be assigned to multiple users
and locations. This will allow this
Particular ‘additional permission’ to only be
accessible to this user.
3.5 Additional Information
Resetting a Cell Empty
If the count needs to be reset manually, additional options are available via reset pods, push buttons or key switches which
allow only authorised personnel to activate the reset via Byte 0.

Updating and Removing Users

To remove users select delete on the appropriate user. Confirm deletion by selecting “delete”. To edit users (change name,
change Access, update card or add additional notes), select “edit” on the appropriate user. When update cards, please delete
any existing data in field before applying new card information.

18
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

4.0 Upgrading the Local or Local-Master Software

For a FACS-LM both the Local and Master software are installed on the same device; for all other systems Local and Master
software are installed on separate devices. It is a requirement to upgrade both pieces of software at the same time.
The Local software is distributed as a single .exe file, whereas the Master software consists of an executable file and an
associated dependencies folder.
Upgrade LM: including local installer in the dependencies folder of master installer will give an option to install local alongside
master.

19
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

4.1 Local Software

Before upgrading it is necessary to first uninstall the existing local software

Go to Control Panel | Programs and Features

Select Frank Service (64bit) and click Uninstall and answer yes to all the prompts

Run FrankLocal v1.5.1.0.exe to install the update

20
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

4.2 Master Software

The same process is followed for both an installation or an upgrade; the installer will prompt for uninstalling the existing soft-
ware if required.

The Master software is compatible with 64 bit versions of Windows Server 2012 R2 or later, and 64 bit versions of Windows 10
or later.

Ensure that the Dependencies folder is present in addition to the installer file.

Run FrankMaster vx.x.x.x.exe to install the update

You may be requested to reboot the system during the installation, the installer should automatically restart after the reboot. If
this does not happen, locate the installer and run it again.

When the installation completes you will have the option to show the Master web page, this will allow you to check that the
system is running correctly.

21
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

5.0 Installation of the Local or Local-Master Hardware

Note: these operating instructions detail information for the UPN Edge Pro controller hardware. For Dell hardware, please
refer to details described in FRANK Operating Instructions – v1.0.8.x – August 2020

FACS-L1 / FACS-LM
Note: Mounting can be completed before or after configuring your FACS controller.
Note: Mounting instructions are available in the documentation shipped with the mounting device.

Align the fixing holes on the adapter plate (F51999553) with the two holes on the back of the FACS-LM or FACS-L1 controller.
Place the two M4x8mm screw fixings through the plate and secure the two components together.
Secure the DIN rail bracket (F72999357) to the adapter plate using two M4x6mm fixings and two M4 steel washers.

Place the FACS controller on the DIN-rail at an angle, and pull down to compress the springs in the top of the bracket. This will
secure the controller to the DIN-rail.

22
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

6.0 Managing Interactions on your Master Controller

Events are listed in both the local and master webpages. The local shows only 10 most recent events (intended for diagnostic
purposes). The Master displays the full list of events and contains additional fields for further analysis purposes.

Events are listed below for;

Permission Request
Access Granted (Enter) – (User with permission badges device)
Access Granted (Exit) – (User with permission badges out)
Access Denied – (User without permission requests entry)
Cell Empty – (No users remain in the safeguarded space)

Permission Events
Date Location User RFID Event Type Description
xx/xx/xx Zone 1 - Door 1 Akhila Hassan Reference Permission Request Access Granted (Enter)
xx/xx/xx Zone 1 - Door 1 Derek Parker Reference Permission Request Access Denied
xx/xx/xx Zone 1 - Door 1 Akhila Hassan Reference Permission Request Access Granted (Exit)
xx/xx/xx Zone 1 - Door 1 Akhila Hassan Reference Permission Request Cell Empty
Lock Status
Closed, Unlocked (device unlocked and closed)
Opened, Unlocked (device unlocked and opened)
Closed, Locked (device closed and locked)
Closed, Auxiliary Override (device unlocked with auxiliary means and closed)
Opened, Auxiliary Override (device unlocked with auxiliary means and opened)
Closed, Escape Release (device unlocked with escape release and closed)
Opened, Escape Release (device unlocked with escape release and opened)
Date Location User RFID Event Type Description
xx/xx/xx Zone 1 - Door 1 - - Lock Status Closed, Unlocked
xx/xx/xx Zone 1 - Door 1 - - Lock Status Opened, Unlocked
xx/xx/xx Zone 1 - Door 1 - - Lock Status Closed, Locked
xx/xx/xx Zone 1 - Door 1 - - Lock Status Closed, Auxiliary Override

xx/xx/xx Zone 1 - Door 1 - - Lock Status Opened, Auxiliary Override

xx/xx/xx Zone 1 - Door 1 - - Lock Status Closed, Escape Release

xx/xx/xx Zone 1 - Door 1 - - Lock Status Opened, Escape Release

Monitoring Status Received (for I/O monitoring)

Name : True (Input or Output sends high bit – i.e. button pressed (NO) or E-Stop reset (NC) or lamp illuminated)
Name : False (Input low – i.e. button released (NO), or E-Stop pressed in (NC) or lamp de-activated)

Date Location User RFID Event Type Description

xx/xx/xx Zone 1 - Door 1 - - Monitoring Status Received Access Granted (Enter)

xx/xx/xx Zone 1 - Door 1 - - Monitoring Status Received Access Denied

23
 Operating Instructions: FRANK - Industrial Access Control v1.5.1.0

7.0 Service and Inspection

Regular inspection of the following is necessary to ensure trouble-free, lasting operation:
• Correct operating function
• Secure mounting of components
• Debris and wear
• WD40 lubricant or equivalent, should be applied to each mechanical element every 10,000 operations, or sooner, to ensure
smooth product operation and function. There are no user serviceable parts in this product. If damage or wear is found with
an assembly, please contact your local Fortress stockist. The complete interlock must be replaced after 1 million switching
operations.
Disposal
Access Controller Hardware should be disposed in accordance to The Waste Electrical and Electronic Equipment Directive
(WEEE).
Liability Coverage is Voided Under the Following Conditions:
• If these instructions are not followed.
• Non-compliance with safety regulations.
• Installation and electrical connection not performed by authorised personnel.
• Non-implementation of functional checks.
Protection Against Environmental Influences
A lasting and correct safety function requires that the device be protected against the ingress of foreign bodies such as swarf,
sand, blasting shot, etc. The device is to be mounted away from the machine, or by the use of anti-vibration mountings, in
order to avoid the effects of vibration, shock and bump.
Use in Dusty Environments: Careful product selection is required, which is best performed under the guidance of a Fortress
Representative, in order to assess the dust type and product style required. It is normally accepted that the product performs
best in a dusty environment when mounted upside down.
Use in Corrosive Environments: Careful product selection is required, which is best performed under the guidance of a
Fortress Representative.
The manufacturer reserves the right to modify the design at any time and without notice.
This guide should be retained for future reference.

Fortress Interlocks Ltd, 2 Inverclyde Drive, Wolverhampton, WV4 6FB, United Kingdom, Tel: +441902349000, Web: www.fortress-safety.com August 2023 - v1.8

24