starting rio service automatically

[JK1]

Hai all,

I have an application where i download the FPGA directly from the host pc (RIO version 3.0).  When i install the exe in a new system the problem am facing is that, RIO service doesnt start automatically and i need to start it manually by myself.  Is there a way to launch this service from LabVIEW.  Please help me out coz its not great to advice the customer to start the service when he installs it.

Thanks for all help,
JK

[griffindore]

Hi JK1,

Thanks for posting to the NI Discussion Forum. First we'll need some basic information. What version of LabVIEW and LabVIEW FPGA Module are you using? You also mentioned that you have NI-RIO 3.0, but the latest version is 2.3.1. Do you mean that you have NI-RIO 2.3.0 or are you referring to a different driver? What type of FPGA target do you have (cRIO, PXI R-Series, PCI R-Series)?

---

@JK1 wrote:
When i install the exe in a new system...

---

Which executable are you referring to, the NI-RIO driver or some other executable? What happens if you don't manually start the NI RIO Service? Does it affect your ability to target the FPGA? Please feel free to post as much relevant information as possible. Have a great weekend!

[Jimmie_A.]

Hello,

Mike has correct that we need some additional information here regarding which SW and drivers that are involved.

If I understood things correctly you want to have a Windows/FPGA setup where a Windows Host VI directly controls the FPGA and you would like to be able to distribute this setup. When distributing this setup the client computer need the following SW installed:

• LabVIEW Run-time engine
• NI-RIO

Another option some customers make use of is that they only distribute the bitfile and let the end customer create the Host VI themselves.The end customer then need LabVIEW Development Environment and NI-RIO.

What happens when you distribute your system to the client machine and start the executable?

If some service need to be started you should be able to do it programmatically using 'System Exec.VI' for an example as described here:

http://digital.ni.com/public.nsf/allkb/87FCE111FD854484862572FF007D252A?OpenDocument

[JK1]

Hi,

Thanks for the response.

Sorry the RIO Version is 2.3.0 and not 3.0. 
FPGA 8.5
LabVIEW 8.5

Am using a cRIO target - 9101 to which i need to download the FPGA bitfile and there is no RT application since am going to control the FPGA directly from Host PC.  I have included Runtime engine and NI RIO with my Installer.

The National Instruments RIO server thats responsible for identifying the FPGA targets in a network is set to manual and doesnt start automatically (its described in MAX help too). 

The attached link helped me in starting the service. ie., net start "niriorpc" but the service is configured with startup type "manual".

i need to change the start mode to "automatic" so that it starts automatically each time without need to start each time when the software starts.

Please help.

With regards,
JK

[Bassett_Hound]

JK1,

You really only need the RIO Server running on your host PC if your intending communicate with RIO devices on the host system from other systems on the network.  For any cRIO real time controllers the RIO server is already started.  If you are wanting to communicate to RIO devices on your PC from another PC on the network your absolutely right that you'll need to either start the RIO server manually or set it to automatically start ( which you've already mentioned ).  How to do this is explained in MAX help but I put and image below just for completeness.

So was the question really, How do I make my installer set the Service to Automatic during the install?  For this my first thought was you could have the installer run a .bat file after finishing and use a command line to set the windows setting for it, or possibly set the registry key ( if you knew it and knew what Windows version it would be installed on), some info might help here.

Bassett

Message Edited by Bassett Hound on 01-17-2008 10:54 AM

[JK1]

Hi Bassett,

Thanks a lot for your response.

My intention was the same to run a batch file after the installation but there was no "net" command line arguements that can accompolish the task.

Your idea of changing the registry key is great and i found the key, am able to change the startup type with registry vi's

Thankyou for the idea.

With best regards
JK