LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Get Target Image.vi and Set Target Image.vi requires password?

I am running LabVIEW 8.5 with NI-RIO3.2.1 and LabWindows/CVI Real Time Module 8.5. I am trying to do system replication, replicating an image of the CRIO-9014 I've loaded with a Real-Time VI to identical multiple target machines. I would like to use the example VIs like "Apply Image to Formatted Target.vi", "RT System Deployment Utility.vi" and "RTcopy.vi" . Some of these VIs and other VIs I would like to write myself require using "Get Target Image.vi" and "Set Target Image.vi." When I place these two on the LabVIEW Block Diagram, I get a broken arrow which can be traced to the error, "Set Target Image.vi is password protected," and "Get Target Image.vi is password protected." The other five subVIs in the System Replication folder, such as "Format Target.vi" do not have this problem. I  called NI Support, but they told me that the VIs in question need to be put in a project rather than in a naked new VI, or they said that I am not using the VI the right way, because NI password protects lots of VIs whose internals they which to keep confidential. But I am not trying to poke inside Get Target Image.vi and Set Target Image.vi, I am only trying to place them inside a VI for inside a project. And I cannot.

 

Are there other users out there who have succeeded doing system replication, who have also encountered this problem, and have a solution?

 

I would appreciate your sharing your hard-earned knowledge with me.

 

Thanks,

Ben

0 Kudos
Message 1 of 3
(2,674 Views)

Hi Ben,

 

Are you able to run the executable that comes with the download? Also, when you first placed the Get Target Image VI on your block diagram did it search for any subVIs that were missing?

Tanya Visser
National Instruments
LabVIEW Group Manager
0 Kudos
Message 2 of 3
(2,655 Views)

Dear Tanya,

 

I lack ready reply to your questions. However, I applied after submitting the question to LAbVIEW Forum the earlier suggestions make to me by another NI Engineer, who suggested reinstalling the Real Time 8.5 Module, and NI-RIO Server3.4 in place of NI-RIO Server3.2.1.  This suggestion corrected the problem.

0 Kudos
Message 3 of 3
(2,645 Views)