fpga

[longbow]

I am trying to compile an FPGA app, but keep getting the "Cannot connect to compile server" error.

It is not a firewall, tcp or antivirus related problem.

I used netstat -anop TCP |grep LISTENING, and there when I start the compile server I get a port 4014 being opened (not the port 96 as promised).

How do I change this setting, or change something to get it working?

Notes : I have a clean install of LabView 2009, with all CRio, FPGA, etc, and after this I installed LabView 8.0.

Machine XP Pro, 3Gb RAM, 320Gb disk (200Gb free).

[mishkin]

The default port should be 96, like you mentioned (as specified in What Ports Do I Need to Open on My Firewall for National Instruments Software Products?)

The options you are looking for are in Tools > FPGA Module Options. I belive the option to specify a custom port for compile server used to be available in earlier versions of the FPGA module. What options do you have in this dialog box? 

It's not a good idea to install earlier versions of Labview on top of a more recent one. All the drivers (for example, NI-RIO) will need to be reinstalled in order to provide support for this other version of Labview you now have (8.0 in your case). Do you have FPGA module for 8.0 as well? 

[Donovan_B]

Beginning with LabVIEW FPGA Module 2009, communication between LabVIEW and the compile server now goes through the NI Service Locator, which will dynamically assign a port for the compile server to communicate through.  Make sure this service is running and nothing is blocking it or port 3580 (the port used by the NI Service Locator).

Previous versions of LabVIEW FPGA Module use a static port set in the options dialog Misha mentioned.

[tkreider]

Does this mean that the Service Locator on the client PC is talking to the Service Locator on the compile server PC via port 3580, then assigning random ports from there?  If so, firewalls should pick up on the traffic, but if the Service Locators are using random ports initially, how does everyone get started?  It would be nice if NI documented these things more than just, "use port 96"...

[David_L]

LabVIEW FPGA will request a port from the NI service locator.  The NI Service Locator uses port 3580 to communicate to the remote computer and ask for a port from IT's service locator.  The second determines an available port and sends this information back to the development PC via 3580.  Each then open up that specific port and communicate that way.  They are not linked so the firewall may not always determine that this new port is OK.  Because of this, it's better to just set your Firewall to allow LabVIEW access to all ports.  

Hopefully this helps to better understand how it works, but let me know if more clarification is needed. 

[tkreider]

David,

Thanks for the clarification.  The architectural limitiation of that approach is that if you don't own the firewalls between you and your compile server, you're toast.  For example, my PC at home is 2x faster than anything I'm allowed to purchase at work (3 hour build times and rising).  But since I don't have authority to just open the corporate firewall willie-nillie, I can't use my home PC to run the compile server.

Could you suggest a way to force the tools to use something like port 80, which is open?  Setting up a VPN is verboten on both the corporate policy level and my ISP provider contract.  I could set up some serious port forwarding on both ends to force the traffic through port 80, but I don't have time/knowledge to do that cost effectively...

Thanks, this has been very helpful.  If anything, I'm building my case to buy a real PC at work. 🙂

Thom

[David_L]

You can do this by setting an ini key in your LabVIEW.ini file.  This is discussed in AE KB 556H8L6C: How To Use a Static Port For a Remote Compile in LabVIEW FPGA 2009.  However, if it were me, I'd try and suggest your company to get you a 5 GHZ, 12-core supercomputer for the sole purpose of doing FPGA compiling.  Might help to shave a few hours off of your day 😄

[tkreider]

5GHz, 12 core supercomputer eh?  Like I said, I'm not allowed to buy a desktop without going through IT and they don't let us buy just any old thing we want, regardless of justification.

That's why I got a list of hardware in Newegg including the new 980X processor, a good overclocking motherboard, and decent memory.  I'm gonna call it 'test equipement'... 🙂

[David_L]

Sounds like a tax write-off to me haha