User Tools

Site Tools




11 FPGA Compile Tools

  • Compile Worker starts, connects to Compile Server, registers with his functions
  • Compile Server is waiting for jobs
  • Dev. Env. is sending jobs to Compile Server
    • Compile Server hands jobs to Compile Worker
  • Compile Server has to be publicly available
  • Compile Worker doesn't have to be available via name/IP

Compile Farm Server

For our internal HSE Compile Farm:
Build Server VM for LV2016-19: ip address == .43
Build Server VM for LV2020: ip address == .45
For credentials see 1Password NI Compile Farm Servers

  • FPGA Compile Farm Server must be configured to accept ext. connections

Managing External Connections

  • Open the FPGA Compile Farm Console: Open a Web browser and enter http://localhost:3580
  • Click the Login link and enter a username and password to log into the console. By default, the username is admin and the password is left empty.
  • Click the Security Configuration button in the left-hand pane to access the Security Configuration page.
  • Click the Help link in the top-right corner of this page for information about configuring security.
  • If you want to disallow external connections to the compile server, remove the checkmark from the Allow External Connections checkbox in the FPGA Compile Farm Console window.

Port forwarding

With LabVIEW 2013 the FPGA Compile Farm Server uses port 3582. You will need to verify that his port isn't being blocked by adding an exception to the Windows Firewall or other port blocking software.

Compile Worker

  • installed on CentOS7 Compile-Worker
  • connects to Compile-Server (see above)

How to install

…on an ESXi Server specifically, but applicable to any computer

For outdated versions of CentOS, use the archives to download the needed OS version

  • Setup the host OS
    • Upload iso to ESXI server and register a new VM, while attaching it as a new optical drive
    • For ISE workers, use the 32bit version, for Vivado use 64bit
    • Install CentOS with the wizard
    • Don't forget your root password!
  • Download the required LabVIEW FPGA Compile Tool
    • Select the corresponding Application Bitness from the drop-down:
      • 32bit for ISE
      • 64bit for Vivado
  • Upload and mount the iso to the now installed CentOS
  • Copy all the files to another directory, because mounted isos are read-only
  • Run chmod +x on the install script and then run it with root permissions
If you run of disk space midway, assign the VM more memory from ESXI and grow the root partition with the systemctl rescue mode


Compile Machine Benchmark

A simple comparision of the FPGA compile time on some machines.



  • Repository: hagemonitor-master
  • File:
  • Commit Hash: 6d6b379d85bc127e677d4f52d015843b206961e4
  • Commit Info: 6d6b379d reworked PNIO for track settings


  1. vSphere Server (ESXi) [4.0 GHz Core i7-6700, 16 GB 1600 MHz DDR3] - Compile worker on CentOS in VM [2 processors, 4 GB RAM].
  2. iMac 27“ (Late ´15) [3.3 GHz Core i5, 24 GB 1600 MHz DDR3] - Compile worker on Win 7 in VM [2 processors, 8 GB RAM].
  3. MacBook Pro 15” (Early ´13) [2,7 GHz Core i7, 16 GB 1600 MHz DDR3] - Compile worker on Win 7 in VM [1 processor 4 GB RAM].


  • vSphere Server: 14m
  • iMac (1. Lauf): 24m
  • iMac (2. Lauf): 24m
  • MacBook (1. Lauf): 50m
  • MacBook (2. Lauf): 52m
kb/ni-fpga/compile-tools.txt · Last modified: 2020/09/23 10:30 by joerg.hampel