Real-Time Measurement and Control

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to connect to the fpga compile server

Hi Emmanuelol,

 

Did you turn off the firewall or add an exception for the compile server?  Sometimes turning off the firewall alone won't solve the problem.  An exception is necessary in those cases.  Try manually adding an exception to the firewall if you haven't done that already.

Jared S.
Applications Engineering
National Instruments
0 Kudos
Message 11 of 31
(5,189 Views)

yes i did that, but doesn't work 😞

0 Kudos
Message 12 of 31
(5,180 Views)

Hi,

Im having the same problem as Calvus and Emmanuelol, I tried everything: uninstalling compile server and whole LabVIEW environment with all addons, manually cleaning all of its remains on HDD and installing it again. Disabled firewall, antivirus (AVAST!) adding compile server to the exceptions wherever it was possible.

Long story short, tried every fix I could find and nothing works.

Im using LabVIEW 2009 Prof, Windows 7x64

PS. Month(ish) ago the compile server did work, it started not to about a week ago.

0 Kudos
Message 13 of 31
(5,014 Views)

Hi,

 

What error are you getting? Are you trying to compile on a remote server or on your local machine? 

 

The first thing I would try is to make sure that the NI System Webserver is started. It is located here: Control Panel > Administrative Tools > Services. If it is already started. try restarting it and then compiile.

 

Thanks,

Message 14 of 31
(4,995 Views)

Hi,

 

I have a few more questions. Are you using LabVIEW 2009 or LabVIEW 2009 SP1? Also, are you using 32-bit LabVIEW or 64-bit LabVIEW? If you are using 64-bit LabVIEW, then it is probably not compatible with the FPGA module. 

 

If you could attach screenshots of the error as well as your compile logs (National Instruments\FPGA\CompileWorker), that also might help us find out what is happening.

 

Thanks,

0 Kudos
Message 15 of 31
(4,986 Views)

Hi, and thanks for the reply.

 

1. Im getting 'unable to connect to fpga server' (screenshot) error message while compiling on local machine.

2. The NI System Webserver service is NOT running. Moreover its not even listed in the services.(screenshot)

3. Im using 32-bit version of LabVIEW ver. 9.0f3 (screenshot) and have installed "LV2009_f3DevAndRTEPatch" - I'm not sure if SP1 is installed.

4. Mentioned directory where compile logs should be kept (National Instruments\FPGA\CompileWorker) seems not to exist on my HDD.

 

 

Download All
0 Kudos
Message 16 of 31
(4,981 Views)

What version of the Xylinx tools do you have installed?


Go to Start>>programs>>National Instruments>>FPGA>>FPGA compile worker. Then, in the bottom right hand corner of windows (by the clock), right click on the compile worker and select open. This screen will show the versions you have installed.

 

You can also look at c:\NIFPGA*\Programs to see this, but I would prefer to have you manually open the compile worker.

*you have 2009, so this should have a different name reflecting that version.

 

If you go into MAX and expand software, it should show you whether or not you have SP1 installed. However, given that screenshot I think you do not. You can get that download from ni.com/src.

 

After you install sp1, and if you still do not have that NI System Web Server service, you should do a full repair of LabVIEW. Just make sure every option is checked. My worry is that some sort of corruption happened with all of the web services, which might possibly effect commucation with the compile server.

 

Thanks,

D Smith

0 Kudos
Message 17 of 31
(4,929 Views)

Hey, sorry, it didn't quite register that you were using 2009. 2009 does not have the system web server, it has the NI Service Locator.

 

Can you check this document, especially this link:

http://localhost:3580/dumpinfo?

 

Can you also take a look at these documents if that service isnt running:

http://digital.ni.com/public.nsf/allkb/2F55B93405ED07AA862574A300826580?OpenDocument

http://digital.ni.com/public.nsf/allkb/8C00F1144B2CD73E86256DEF00698AC3?OpenDocument

 

2009 also means that you will not have a compile worker. Can you instead navigate to your c:\fpga\programs folder and check which xilinx compilers are installed.

 

Thanks, and sorry about the confusion.

 

D Smith

0 Kudos
Message 18 of 31
(4,923 Views)

I appear to be having similar difficulties with compiling a FPGA VI remotely with LabVIEW 2010.

 

The remote compilation server is a PC running XP 64 bit. I have configured the compilation worker to allow remote connections and it lists it registered capabilities as Xilinx 10.1, Xilinix 11.5 and Xilinx 11.5 (64-bit). This can be seen in the attached png.

 

My development system is running XP 32 bit with LabVIEW 2010. It is connected to the server via a local area network.

 

The process I have been following is as follows;

 

1.) Log onto the server PC and start the compile worker (this is either physically or by connecting via remote desktop and then disconnecting but leaving the PC logged in with compile worker on)

 

2.) Set up the FPGA compilation settings on the development computer to be the server (hostname, domain\username, password)

 

3.) Try and rebuild the target VI

 

I then receive an error stating that the user name is too long or invalid (see png).

 

I have set the exceptions in the server firewall to allow port 96 as I found that this is the default port used for earlier version of the compile server but I am unsure if this is applicable in 2010. I need to check with my IT services that exceptions I add are actually applied.

 

If I go into the compile worker settings on my development PC and try and set them to that of the compile server then it also fails to connect.

Download All
0 Kudos
Message 19 of 31
(4,859 Views)

Hi John,

 

To start off, this should give you the settings you need for the firewall:

http://zone.ni.com/devzone/cda/tut/p/id/12402

 

From the error, it looks like you do not have the username configured correctly. I would suggest walking through this tutorial and ensuring that you have everything configured correctly:

http://digital.ni.com/public.nsf/allkb/6D3C5B99BF37247A86257770006982FF?OpenDocument

 

As a final note, we prefer that you create a new thread for each new incident. Your problem is a new error on a remote compile worker while this thread is about a specific error when connecting to local compile workers. Keeping these issues separate makes it easier for customers to resolve future, similar issues.

 

Thanks,

D Smith

0 Kudos
Message 20 of 31
(4,830 Views)