What are the Predator Software System Requirements?
Overview
System requirements for Predator applications are listed below. Most implementations can be done on either a desktop or server operating system.
Server Minimum Requirements
| Recommended
| Minimum
|
Operating System
| Windows 10 or Windows Server 2019
| Windows 7 or Windows Server 2012
|
CPU
| Intel or AMD at 2.0 GHz or Higher with 2 Cores
| Intel or AMD at 2.0 GHz
|
Memory
| 8 GB RAM or more
| 4 GB RAM
|
Disk Space
| 250 GB
| 120 GB
|
This is based on the assumption of a dedicated server without any other hosted applications. Should there be additional applications running on the server, including security applications, it is advisable to modify the setup to accommodate the requirements of those applications, in conjunction with the minimum requirements for Predator.
Additional Requirements
- USB Port
- 1280 x 960 Screen Resolution
- .NET Framework 3.5
Client Minimum Requirements
| Recommended
| Minimum
|
Operating System
| Windows 10 | Windows 7 |
CPU | Intel or AMD at 2.0 GHz or Higher | Intel or AMD at 1.5 GHz |
Memory | 4 GB RAM | 2 GB RAM |
Disk Space | 120 GB | 64 GB |
Additional Requirements
- USB Port (except for floating licenses)
- 1280 x 960 Screen Resolution
- .NET Framework 3.5
Database Requirements
Predator MDC, Predator PDM, and Predator Tracker require the use of a database. Microsoft SQL Server is recommended, but Microsoft Access and Oracle Database are also supported.
- Microsoft SQL Server 2019, 2017, 2016, 2014, & 2012, either Standard or Express editions
- Microsoft Access 2019, 2016, & 2013
- Oracle Database 19c, 18c, 18c Express, & 12c
- For applications that require the use of a database, SFA recommends using a dedicated server to host both the Predator applications and Microsoft SQL Server.
- Virtual Machines (VM) are supported, however, clients running on terminal servers require a Predator FLM server.
- VMs hosting server applications such as Predator DNC or FLM require a physical USB port, more information can be found here.
Virtual Machines are fully supported, however, please take the following statement into consideration. For most installations, it is imperative to allow select non-IT personnel access to the Predator system. The Predator DNC system is reliable, but like any other software, issues may arise. Since the Predator system is used 24/7, IT often times is not available if something stops working during 2nd and 3rd shifts and this might cause production to stop. Allowing someone during those shifts access to the Predator DNC server could save several hours of lost production due to the inability to transfer programs. Proper training can be provided by SFA to the personnel granted access.
Related Articles
What is the Predator Touch HMI Connect Timed Out Error?
Problem When attempting to use a Predator Touch HMI button, an error appears saying Connect timed out. Reason This error is due to the inability for Predator Touch HMI to reach the Predator DNC server. Solutions Predator DNC may be in the middle of a ...
Predator PDM IT Requirements
Overview IT requirements are minimal, but vital to a successful implementation. Software Installation Follow How to License a New Predator Installation guide to install the Predator PDM Vaults Folder The vault is stored in a folder and is located on ...
Why is Predator Touch HMI causing a Low Level Error 2, file not found?
Problem When an operator selects a program/file using Touch HMI, Predator DNC gives a Low level error 2, file not found error. Reason Predator Touch HMI v11 does not prevent a user from access other files, even when its specified in the ...
How to Install Predator MDC v11
Overview In order to utilize all the features of Predator MDC, a client must be used. Predator MDC includes three licenses, Administrator, Client, and Shop Floor, all of which act as a client. Enterprise versions of each license are also available. ...
Why is the Predator DNC service not starting up?
Problem The Predator DNC Service is unable to start or it has stopped suddenly with no apparent explanation. Reason Licensing is the likely culprit, but Windows user permissions can also prevent the service from starting Solutions Try the following ...