Home |  Products |  Training |  Support |  About Us |  Contact   
  Predator Products

Minimum Systems Requirements

Windows Requirements

Support for the following Microsoft® Windows versions is included with Predator applications:

  • Windows 2016 Server
  • Windows 10 - Requires v11
  • Windows 2012 Server
  • Windows 8
  • Windows 7
  • Windows 2008 Server
  • Windows Vista
  • Windows 2003 Server
  • Windows XP

Includes support for 32-bit and 64-bit versions. Predator versions prior to V10 are 32-Bit applications, although they must run in 32-Bit mode they can be installed and will operate properly on a 64-Bit operating system. The installation for the application places the executable and all of the necessary support files in the proper folder to run in 32-Bit compatibility mode. For Vista systems, It is highly recommended to use Vista Home Premium or higher for performance reasons.

The latest service packs for each OS should be installed. Previous versions of Predator supported earlier versions of Windows. Existing customers running Windows 3.1, Windows 95, Windows 98, Windows ME, Windows NT or Windows 2000 must upgrade to a newer OS prior to upgrading Predator.

Predator v9 applications require the .Net 2.0 runtime while most v10 applications require the .Net 3.5 runtime with the exception of Predator CNC Service v10 and Predator Import Service v10 which requires .Net 4.0 runtime. Finally, Predator FLM v10 requires .Net 3.5 runtime and .Net 4.0 runtime. Predator MDC Executive v11 requires .Net 4.5 runtime. All Predator installs include the appropriate .Net runtimes automatically.

Until Fanuc FA releases official support for Windows 2016 Server and 2012 Server, Predator DNC, Predator RCM, Predator CNC Service and the Predator Fanuc Focas Tester's support of Fanuc Focas will be made on a best effort basis on Windows 2012 and 2016 Server.

Minimum PC Client Hardware Requirements

Support for the following minimum computer hardware is required for Predator v11, v10 and v9 applications:

  • Intel® 4, AMD® Athlon or newer Processors
  • 10Gb or larger hard drive
  • 1Gb or more RAM
  • 1280 x 960 Minimum Graphics Resolution
  • 128Mb Graphics Adapter supporting OpenGL 1.1
  • Mouse
  • USB Port
  • Serial Ports & Ethernet Ports - As required for DNC, MDC & FLM

Lower screen resolutions are supported for Predator Touch HMI and other Predator utilities and testers.

A nVidia, AMD or 3DLabs based graphics card is highly recommended for Predator Virtual CNC. Like most CAD/CAM systems Predator Virtual CNC will often require high end PC components to support large and complex 3D simulations for optimum performance.

Predator RCM requires the Fanuc Robot Server / PCDK Runtime to be purchased from Fanuc Robotics. This PC option needs to be installed on the same PC running Predator RCM.

Recommended PC Server Requirements

We recommend the following additional minimum PC server requirements for Predator v11, v10 and v9 implementations:

  • Windows 2008 or newer OS
  • Intel i5 Series or newer CPU
  • 64Gb or larger hard drive
  • 8Gb or more RAM

Not all implementations require a PC server.
 

Ethernet Port Requirements

Predator applications utilise the power of Ethernet. For proper operation the following default Ethernet ports should be opened up on all switches and firewalls where Predator applications operate:

Port Predator Hardware
23 Telnet style Configuration
80 Browser style Configuration
771 Predator Flex/N Hubs
4000 Predator DR 2x2 and Flex/W Hubs - Firmware
950-955 Predator DR 2x2 and Flex/W Hubs - Data
966-981 Predator DR 2x2 and Flex/W Hubs - Command
1029 Predator DR 2x2 and Flex/W Hubs - Status
   
Port Predator CNC Editor Enterprise
80 Browser & Viewer
1433 Microsoft SQL Server and Microsoft SQL Server Express
1521 & 1630 Oracle and Oracle Express
   
Port Predator DNC and DNC Enterprise
21 FTP Client & Server Terminators
25 Email Terminators
80 Browser & Viewer (Enterprise Only)
445 File Read Terminator
445 File Write Terminator
1433 All Microsoft SQL Server based Links
1521 & 1630 All Oracle based Links
8008 DMG Mori Terminator
8190 & 8191 Predator Secure DNC
8192 & 8193 Fanuc & Fanuc Data Terminator - Fast & Embedded
10000-60000 Client & Server Terminators (per Configuration)
10000-60000 Predator DNC Connect (per Configuration)
   
Port Predator MDC Express, MDC & MDC Enterprise
80 Browser & Viewer
1433 Microsoft SQL Server and Microsoft SQL Server Express
1521 & 1630 Oracle and Oracle Express
   
Port Predator MDC Executive
443 HTTPS - Optional
1433 Microsoft SQL Server and Microsoft SQL Server Express
1521 & 1630 Oracle and Oracle Express
4194 Predator MDC Executive
   
Port Predator PDM and PDM Enterprise
80 Browser & Viewer
1433 Microsoft SQL Server and Microsoft SQL Server Express
1521 & 1630 Oracle and Oracle Express
   
Port Predator CNC Service
80 Elexa, Fanuc Robot, MTConnect & XML
1433 Microsoft SQL Server and Microsoft SQL Server Express
1521 & 1630 Oracle and Oracle Express
4840 OPC UA
500# 3rd Party MTConnect Agents and Adapters
7878 3rd Party MTConnect Agents and Adapters - SHDR
8192 & 8193 Fanuc & Fanuc Backup - Fast & Embedded
8194 Predator Secure HID
8195 Predator Secure CM100
8195 Predator Secure Gerber
8195 Predator Secure OPC
8195 Predator Secure Siemens
10000-60000 per configuration
   
Port Predator FLM
1024 Predator FLM
   
Port Predator Tracker
80 Browser & Viewer
1433 Microsoft SQL Server and Microsoft SQL Server Express
1521 & 1630 Oracle and Oracle Express
10001 Predator RFID Writer
   
Port Predator Travelers Express and Travelers
80 Browser & Viewer
1433 Microsoft SQL Server and Microsoft SQL Server Express
1521 & 1630 Oracle and Oracle Express
   
Port Predator RCM and RCM Express
21 FTP Transfers
21 Email Notifications
1433 Microsoft SQL Server and Microsoft SQL Server Express
8192 & 8193 Fanuc - Fast & Embedded
10000-60000 Only when used with Predator DNC or Predator MDC
   
Port Predator Touch HMI
10001 RFID
10000-60000 Only when used with Predator DNC or Predator MDC

Every implementation does not need to open every port listed, just the ones that are used. The above default values may have been changed. Always refer to any implementation specific documentation or the actual configuration to determine the exact port numbers that are specified.