DIO port config.vi: Subvi is not executable

Similar Questions

• Open specific WorkBook.vi: Subvi is not executable error

  Hello

  I'm trying to programaticaly change, some cells of a specific spreadsheet, then saving it on a new file.

  But I can't launch the VI because I get the Open WorkBook.vi specific error: Subvi is not executable.

  I have atteched a printscreen of my VI.

  Any tips?

  Daniel Coelho

  
  

• Error 10461 / 10008 @ DIO Port Config (legacy, lvdaq.dll)

  Hello!

  In my company, we have many tests in Paris, all controlled by an extraordinary Labview (compiled) program and the PCI-DIO-96 cards.

  I changed and compiled the program several times in the past and did not have a unsolvable problem before.

  But now the Port Config.vi DIO (lvdaq.dll) always shows me an error 10461 (recource not availabe) when I want to run it.

  It is used to control the DIO-96 cards.

  So I thought that it is a problem with my DAQ / DAQmx Config on my computer that had changed several times. But the strange thing is that the Version compiled on the Paris test shows the same error today and their configuration has changed.

  I have checked and double-checked everything at least twice (numbers device ect.) but I don't know how to solve this problem!

  My Cfg.: DAQmx 8.9, 7.4.4, Labview 8.6.1 DAQ & compiler

  Thanks in advance for any help with this problem

  There is a known compatibility issue between the traditional DAQ driver and DAQmx 8.8/8.9 with old devices DIO. The DAQmx 8.7.2 driver rather than the more recent installation should solve.                                                                                                                                                                                                                                                                                                                                                                                                       http://Joule.NI.com/nidu/CDs/view/p/ID/1087/lang/de

  Andrea Perin

• Error-10001 occurred at DIO Port Config

  This error started to appear on several machines with a (version 5, Win98) .vi older we would still like to use (and do not have to re - write).  We have tried to reinstall LabView (versions 6 and 7) and NiDaq - including legacy download.  We try now all this on a Windows 2000-based computer. The problem can began to appear after a new version of Max was performed on machines

  This is the message that appears:

  NOR-DAQ LV: An error was detected in the input string; the agreement or the order of the characters in the string does not match the expected order.

  It is not clear (to me) what is the exact nature of the complaint.  It seems that I am reluctant to re - write the entire program without having exhausted all remedies to oher first a simple mistake.  Help, please.

  Thank you.

  I wanted to point out that we have solved the problem.  Believe it or not, somehow, the entry of 'Digital Channel' to the Digital i/o Config changed color function, which requires that the entry be now redone with a box having the same color - fushia.  The only thing we could find with this color is a traditional DAQ box that says "I/o.  There are obviously differences between some of the original features and their counterparts 'traditional '.

• ADO error: SQL execute.vi is not executable.

  Thanks for all those who are willing to help me out of this problem which intrigued me several days, I can't find a similar one of Google or another forum...

  Problem:

  When I was with LabSQL, he came a mistake:

  Sub - VI "execute SQL": Subvi is not executable. and then I looked for the source of the error, it finally turned the

  "ADO Recordset GetString.vi":

  ' invoke the method node: invalid '.

  ' invoke the node: invalid refnum class.

  What I have used is Windows 7 and LabVIEW7.1.

  The details of this problem, which includes the vi and a few photos of the error and ADO functions, I used is attached.

  Ute.VI' is

  Hi FedorLeon,

  I opened the LabSQL library, and no VI is broken in it. Which brings me to think about 2 possibilities:

  -Your TEEN of ActiveX on your computer is not installed properly or not using is not the same version, as expected by the library.

  -Your LV 7.1 on Win7 fails. That wouldn't be surprising, because the first version of LabVIEW to support Win7 is LV 2009SP1 ;-) Make a test on a machine XP LV or a LV 2012 on your Win7 machine!

  Kind regards

• System Subvi is not

  Hello. We try to run some vi.s our colleagues wrote (Labview 7.1, we two). There is this problem with a "a.i": whenever it is open, three situations may occur:

  1 pop on the slot loading caution against "Config data Get Key Value", "Reading Key.vi' called"a.i"(this .dll is a user-generated library made by our colleagues using Labview)

  

  2. a lot of the 'Config data Get Key Value","reading Key.vi' in the block diagram have been replaced by the question mark.

  

  But this vi can actually work.

  Then, when we try to open and run "b.vi', which includes 'a.i' as a Subvi, when it loads comes out with the same warning message and will not work. The error message stated "a.i": not executable Subvi. And when I opened "a.i" of "b.vi", it will not work.  The error message indicates that all the question mark "Get Key data Config" and "reading Key.vi' Subvi Value is not executable.

  After that I have everything close and reopen a.i, individually, it becomes viable.

  I'm new to Labview, and what seems to me, is that the program confuses the situation of the Subvi.  But 'Reading Key.vi' comes from the path system, which really could not miss.  Could someone enlighten me on this issue?

  (PS: is it possible to specify an absolute path to your sub vi included?) I may be wrong, it seems that in 8.6 you can easily do so in "call setup", while 7.1 does not come with this option.  This may seem desperate, who I am right now. )

  Thank you very much.

  It almost seems your b.vi contains subVIs that have the same name as a system of screws, but are also loaded (a dll). When you open then a.i, it will use the screws already in memory instead of loading the correct location.

  If you open a.i, first of all, the reverse occurs, and b.vi will be broken.

  It seems faulty screw loaded from a dll built using LabVIEW. Perhaps you lack the appropriate runtime? Can you show us a code? You should maybe change b.vi and replace the dll with the system calls correct Subvi?

  Many things have improved in this respect in the new versions of LabVIEW. Frankly, I don't remember how these things have been treated to the stone age (LabVIEW 7.1).

• Tecra S3: Port LPT - EPP mode is not available

  How can I change mode of LPT port to EPP in Toshiba TECRA S3?
  In the settings BIOS only ECP and PSP are available, but I programmer memory which must be connected to the LPT working as EPP port.

  It does not in the ECP or SPP.

  Hello

  Well, if this option is not available in the BIOS if it of not possible to put it.
  You can also change the parallel port settings in the Toshiba HWSetup:

  There are also only 2 options available:
  ECP and two-way standard

• Under VI 'DAQ Assistant': Sub VI is not executable

  Salvation OR engineer,

  My task is to acquire and record data of input voltage analog with PCI-MIO-16-1 and BNC-2110 connector. I can get the signal via MAX, but as soon as I drop down the function palette DAQ assistant in FASHION Lab blocks diagram, my run button becomes broken. I got the error message like "Sub VI"DAQ Assistant": Sub VI is not executable. How can I overcome this?

  Thank you

  Yvette.

  Hi Paul,.

  Unfortunately, SignalExpress is a different license than LabVIEW. However, you don't need a SignalExpress to acquire and record data. LabVIEW has every ability to SignalExpress and many more.

  Kind regards

• TO RESET THE GRAPH AND TABLE SEQUENCE EVEN STRUCTURE IS NOT EXECUTED.

  Hello everyone, I made this vi which runs automatically at the beginning and I can't use my power butoon to control this vi. Now, I want to clear the table and graph vi even when the structure of sequence is not executed as the start/stop button. And I want also when I run the program both the graph and the table should be cleared. I tried a lot of things, but as I'm new to labview I can't do. Thanks in advance.

  
  

• Problem on asynchronous call: façade Subvi is not pop up when it is called.

  Dear all,

  I'm new to LabVIEW, and this is the first time I try to use the asynchronous call.

  I'm using LabVIEW 2011.

  I want to build a directory for several screws, and it should enable users to open more than one of the screws at the same time pressing the buttons. Before the construction of this directory, I just tried asynchronous call allows you to call a form of VI VI, but found a big problem.

  I followed the steps described in the help file, created a strictly typed reference, set the option on 80 x because I need not return. When I run it for the first time, it worked fine: the Subvi popped up and run. Then I closed the Subvi. But for the second time and, when I run the appellant VI, the Subvi does not pop up, instead it seemed to work silently on background because when I manually opened from the file that I found running. In fact, I have found no option as "display front when it is called" of the asynchronous call.

  The appellant VI and Subvi are attached. The address of Subvi calling VI should be amended accordingly.

  What should I do to make it work correctly? Thanks a lot for any idea!

  Linjxz,

  If you have ever thought a solution via the property node, then you can ignore this response.  However the easist if not the best method practice to do what you want is to: with your PS open press ctrl + I, with an "appearance of the window" selected in the drop-down window, click Customize.  Check the box "Display front panel when called" and then the correspondent "close front after ward initially closed".  Mind you as your under VI must begin execution closed to make it work while programmaticly you can over come this obstacle.

  Looking to do more with less code.

  Mark R

• Why an asynchronous call would lead to "the VI is not executable. The full development version... »

  I built a labview moderately complex program to connect with a new parser that I build.  To briefly describe the application, the main VI is a user interface which, in an initialization step, asynchronously calls a dozen other screws each called VI is a state machine that handles communication with a component specific for my parser, whether heat controllers, regulators debit, NI DAQmx channels, a SQL database, etc..  I use the VFG and/or EI to communicate information between the main VI and each component. The system works well when it passes through NI Labview 2012 SP1 (full development Version).  I build the project successfully, but when I run the construction (on the same development machine), I encounter the "the VI is not executable.  The full development of LabVIEW version is needed to correct errors"message.

  My first troubleshooting step that was supposed to isolate the problem.  I removed all the asynchronous calls, rebuilt and the program works without errors (granted, no State machines that handle I/O bundles are running). This gave me the impression that my UI screws are not the problem.

  The next step that I took was to create a test project with a simplified user interface to call asynchronously, and control a single component.  The first part, I tried to control a heating unit, and it works perfectly.  I have build it and run without errors or problems.

  Thinking that the component should not be a problem, I add the async call for this component in my main VI, to test it.  This works well in the built environment of Labview development, without errors, but alas, I get the same message as the "VI is not executable' when I try to run the build.

  I am at a loss on how to make trouble, or it could be the cause of the problem.  Why an asynchronous call to the VI even break the construction of an executable project, but don't cause problems in an executable of side projects?

  
  

• subVIs does not function when it is called by main secondary to vi

  Hi all

  I have a main.vi that loads the façade into a secondary four subVIs when selected. Like most applications, everything works fine up to come to build the project (.exe). Program works as expected when run it from .exe but when all the vi.lib functions (for example reading png Subvi) is included in one of the subVIs called, the façade is loaded correctly, but the Subvi is not running and the invoke node (perform a VI generates error 1003).

  I've included the subVIs in 'Always include' in the specification to build under the heading Source files.

  Help, please

  Thank you

  I made a significant change to your "called" sub - VI (I created an icon for it - you'll see why it's important in a minute) and again your main VI.  This code snippet is saved in LabVIEW 2015, but it is simple enough that you should be able to recreate it in any LabVIEW version you are using.

  

  I like to use references static VI (the first thing on the block diagram) because, especially if they are associated with a Subvi with an icon, they provide a mnemonic, robust and easy to get a lot of useful sub - VI 'properties' (for example the path) without worrying about the execution environment.  In particular, they work very well with the Start function Asynchronous Call, I think it's much simpler to use than the VI server method.  I'll walk you through it...

  1. Start with a static reference of VI to the Subvi to run asynchronously.  If your Subvi has an icon, it will appear (as shown here) in the body of the static VI reference, which makes it slightly better documented.  Notice the Red Star on top of the static reference - which indicates a reference strictly - type (right click and choose strictly typed), you need to the asynchronous call start.
  2. This reference gets first wired to a property node - the unusual appearance of the node ('VI Interface Type 2') comes from the strictly typed reference.  We choose the Path property.
  3. The path gets plugged into an open VI reference function.  Because we use asynchronous Start Call (Forget), we specify Option 0 x 80 (glance using reference VI open for further explanation).  We also wire the Strict Type of step 1 at the entrance to this function Type.
  4. The VI reference resulting is wired to Start Asynchronous Call, which starts the called sub - VI.
  5. We also spend it to Insert Secondary VI method, which shows the sub - VI running in the Sub panel.
  6. Now, we interact with the sub - VI in the Sub panel as much as we want to.
  7. In the main routine, we now run the while loop, waiting simply Stop pressing.  I placed a 100 msec waiting here to give priority to the Subvi.
  8. When leaving us, we remove the sub - VI of the Sub panel, he abandoned and get out.  I see no need to put a function exit here - if you want to automatically close the main façade, just do it.

  Bob Schor

  P.S. - I've tested (LabVIEW 2015) and it works fine.

• Open vi FPGA gives error xnode (Lv 8.6) (not executable)

  Hello

  I wrote my description of the error also here: http://forums.ni.com/ni/board/message?board.id=280&message.id=5055&jump=true#M5055

  When using "run vi on the development computer" I get an error broken pointing me to the "open FPGA vi function", the problem

  be 'an xnode object is not executable. I have not found this problem under discussion anywhere, I tried uninstalling FPGA and Rio soft.

  and resinstalling, but not help. All ideas are welcome.

  Thank you

  Staffan

  Hello

  JMota wrote:

  "Here's something to try. I think that the configuration of your FPGA target to run on the development computer (with simulation of IO) will not work if you try to run your host VI on RT. test by dragging the VI to my computer and run it from there. Altenatively, you can reconfigure your FPGA target for not performing on the development computer (what used to be called emulation).

  Hope that explains why the VI has broken. »

  And it solved the problem - works fine now - if this issue is resolved.

  Staffan

• my modem STC (Saudi Arabia) SAGEM 007 has 4 ethernet ports. two of them do not work. (in red)

  my modem STC (Saudi Arabia) SAGEM 007 has 4 ethernet ports. two of them do not work. (in red)

  Hello

  You should check with the help of the manufacturer modem and if it is provided by your ISP support.

  Not really a Windows problem.

  I hope this helps.

  Rob Brown - Microsoft MVP<- profile="" -="" windows="" expert="" -="" consumer="" :="" bicycle=""><- mark="" twain="" said="" it="">

• I removed the nano-receiver to the USB port & back the mouse did not.

  I have 2.4 GHz Wireless Nano Mouse (model MP2375BLK) optics.  I removed the nano-receiver to the USB port & back the mouse did not.  Batteries are fine, if I remove the battery and put it back in the red light flashes once, but the mouse will not turn on.  I checked the State of the mouse in Control Panel control (devices & printers) and it indicates that the device is functioning!

  I thank God for warranties.  Just bought itOn June 3.  Summer works fine until I removed the nano-receiver of the laptop, did not work again!  Let's get back to the store.