LabWindows CVI GUI problems on XP Embedded

Similar Questions

• JNI and Labwindows/CVI linking problem

  I am trying to connect to the server in Java through LAbwindows CVI DataSocket.

  I am able to create a dll. Everything works fine with no error in compilation or execution, but when I run the DS_OpenEx cannot return a native class.

  If anyone can help me with the problem.

  Thank you

  Hello

  Could you better clarify the implementation that works properly and implementation that does not work properly?

  1 are you connected to the DataSocket with Java source code and you are trying to communicate through this source of Java through LabWindows/CVI?

  2 are. what environment you able to successfully create a DLL?

  3. can indicate you what environment survey code error and what this code?

  ADri - K

• LabWindows/CVI myDAQ

  Hello I need to know if someone used the myDAQ nor for sampling audio, I saw an example of make but in labVIEW and I want to do on labWindows/CVI, the problem here is that I try to use the DAQmxCreateAIMicrophoneChan and the audioInputLeft of channel or audioInputRight are not supported...

  can someone help me?

  This discussion has been posted in the Spanish forum too where received messages: see here.

  If possible, additional contributions should follow to avoid the spread of the very argument on several boards of Directors.

• problem with LabWindows CVI

  Hello I m trying to create a Setup program for an application created in a previous version of Labwindows CVI which one don't know locks I get just the file sources, I m working with the 2010 version, the problem is that the application is running in debug mode but when I run in release mode the application does not work only the icon in the taskbar is indicated but the GUI never appears, someone can help me with this

  Thanks for your help, the problem was not with the code and was not with the RT engine version, was a misconfiguration in the compilation release configuration, I myself do not add external sources dll´s and lib´s in the plug-ins option in the settings of the target

• Suddenly have a problem starting LabWindows CVI 7.0 on XP system

  I've been using LabWindows CVI version 7.0 on a Windows XP operating system.  Earlier in the day, I changed my system screen resolution and was working with the applications.

  Everything seemed to work, but at some point, I finished the session, then restarted.   Instead of leaving, I have a Message popup that says "Index passed is out of reach" and the CVI application closes.

  I tried to reinstall CVI original cast CD.  When everything was installed I get the same message when you attempt to start the CVI.

  Anyone have any idea what could be wrong?

  I vaguely remember having a similar problem a few years ago, because I think that something in the windows registry fixed - but I'm not sure.

  Thank you

  Sweeney

  Well, I tried to remove the entries from registry for National Instruments.  After starting and seem to work.

  PROBLEM SOLVED

• Call of CVI GUI

  Hello

  I am doing a program in Teststand combined with cvi and I have 3 problems:

  1. I have a program on Teststand this is GUI runs in CVI, in this interface graphic I have 2 buttons and I want each button to run a different sequence in TestStand.

  2. How do I make sure the MISTLETOE will remain open and visible, and TestStand will run sequences, I told her in the "background".

  3. where can I find a guide for TS_ in CVI functions?

  Thank you

  Kobi

  You can look at the following example to see how to develop a CVI GUI:

  Dynamically control a GUI of LabWindows/CVI through several TestStand steps

  What is a call from a GUI CVI sequence, you want to use the application manager, as shown in this document:

  Loading program from a file of sequence in a TestStand operator Interface

  You will find a guide for ts_ functions by opening the function for the simple function Panel and right-click in the box of ablank.

• Why can I not use my labview controls created dll in labwindow CVI?

  I created a DLL in LabVIEW for run of LabWindows/CVI.  The DLL is started very well but I have no control on the GUI.  Why and how can I use this GUI controls?

  I found the solution on the following thread.

  http://forums.NI.com/NI/board/message?board.ID=180&message.ID=36951&query.ID=314335#M36951

• difference of initial value of string between the steps in the process and an external instance of LabWindows/CVI

  Hello

  I'm curious to know what I see using TestStand, LabWindows/2013 2013 with regard to initial in TestStand string values when you perform the steps in the process or an external instance of LabWindows/CVI.

  I have a step (CVI) string value that is used to check an array of characters stored in an EEPROM to test.  I pass on the Step.Result.String in the CVI by reference.  I then read the table charater of the EEPROM in the chain (Step.Result.String).  The string is then compared against the limit as specified in the test step breast.

  When I run this test step to perform the steps in the process selected in the popup Configuration of the adapter of LabWindows/CVI, it seems that the memory allocated for the string is filled with null characters.  Which is what I expected.

  When I run this test step to execute the steps in an external instance of LabWindows/CVI iselected of the Configuration of the adapter of LabWindows/CVI popup, it seems that the memory allocated for the string is filled with something else.  That is not what I expected.  For example what I see in the memory, it's the first characher is one byte NULL but the remaining bytes are some other values, as shown below:

  F0 00 AD BA 0D F0 AD BA 0D F0 AD BA 0D AD BA 0D AD BA 0D BA 0D AD F0 F0 F0
  F0 AD BA 0D F0 AD BA 0D F0 AD BA 0D F0 AD 0D AD BA 0D AD BA 0D F0 F0 F0 BA...

  In my code I make sure to write a null character in the following location table charater I just write in the chain so I have no problem with the test is working properly.  I have remove the writing from my code null character and was able to verity that the test passes when executing the steps in the process and fails during execution of the steps in an external instance of LabWindows/CVI.

  The returned string contains what I wrote for her, and then the rest of the string is filled with the values that are in the memory allocated for the string.

  Here's my Question: is this the expected behavior for the original string values in TestStand between both types of stage performances?

  Thank you

  Chris Young

  In general teststand not Initializes the unused portion of the string buffer, so it is expected that the values of the memory after character no endpoint will be different, or even to each call. If you happen to be get zeros after the null terminator which was probably due to random character (i.e. the memory allocated just arrived already having zeros in there) or perhaps a debug setting you use perhaps in the Visual C runtime (if you are debugging the process in visual studio or modify visual C runtime heap parameter). TestStand is not initializaing memory after the null terminator character in both cases (I checked the code).

  -Doug

• Passing a struct LabWindows/CVI TestStand

  I'm passing a struct in a dll written in CVI.

  Here's the problem: the code is written in CVI (c code) if I use "struct MyStruct * MyData" as the definition of parameter in the TestStand dll works fine. But if I set my struct using a typedef (i.e. typdef struct MyStruct) then use MyStruct * MyData as TestStand parameter generates a warning.

  I have a way to the adapter C\C ++.

  It's too late in the programming in order to go back and remove the typedef.

  So, how do TestStand accept the typedef?

  Thank you

  Carmine

  In ANSI C, struct names and type names belong to separate namespaces. You can declare the structs several different ways:

  (1) struct structName {int x ;};

  (2) typedef struct {int x ;} typedefName;}

  (3) typedef struct structName {int x ;} typedefName;} Note: structName may be identical to typedefName.

  I assume you are using the 2nd example above in which case LabWindows/CVI automatically generates a struct name (something like __unknown_1) which uses Testand.

  Even if you said it's too late to remove the typedef, you can add a struct name as in example 3 above? You can use the same name as the typedefName and TestStand will recognize.

• DLL for LabWindows/CVI 8.0 with the bool data type

  Hello

  I want to use a new SWIR camera in LabWindows/CVI 8.0 (Windows XP 32bits).

  The company delivered with the camera produced a 32-bit dll by using Microsoft Visual C++ 2010. The .dll and .lib and .h files include a working SDK/API (some functions with the bool data type)

  Compilation-online syntax error, variable Boolean is not a data type in LabWindows/CVI 8.0

  Generate the import of DLL-online syntax error library

  I tried to convert bool char (typedef unsigned char bool => no more syntax error but the functions does not work.)

  What can I do?

  Martin

  Hello again, Naumann!

  Microsoft Visual C++ 2010 represents Boolean using 1 byte, as stated by MSDN: https://msdn.microsoft.com/en-us/library/tf4dy80a(v=vs.100).aspx

  I guess that you import C++ functions using the syntax for extern "C". Otherwise, because of the C++ name mangling wouldn't you able to bind C++ library against your code CVI.

  You can also specify how you import C++ functions?

  In addition, because you have not described the problem as a corruption of heads or runtime error, I guess the C++ library function is called correctly the CVI. That said, I tend to believe that the problem is not really in the mechanism of interaction of C/C++, but in the C++ library. If you would start calling a dummy C++ function returning an integer from a simple CVI application that should work, because redefine bool in CVI 1 byte must ensure that settings are correctly transferred onto the stack.

  If you need to create a wrapper function of C++ that is not using bool and calls the C++ function, I expect to return the same result.

  Maybe you are missing a few prior initialization steps required? The provider of the camera also comes all example code?

  Best regards!

  -Johannes

• passage of data container of teststand labwindows/cvi handle error

  Hello

  I'm moving a container of teststand parameter to labwindows/cvi using this UI API messages following this code created by Peter-r. example:

  https://decibel.NI.com/content/docs/doc-23332

  It is a great example to start with, but as I run using worldwide debbugging lying on the build options, I see that the handle of the containerData object is not released. If I add the CA_DiscardObjHandle (containerData) anywhere in the project, it gives me a FATAL_RUN_TIME_ERROR. This handle must be released? If I call a bunch of these user interface Messages, it will cause memory problems? My code runs right now, great, but I don't want to face a problem of memory later.

  Any help on this will be great!

  Thanks in advance.

  -Luis

  When you add throw it? Maybe you add it to the wrong place. You must add it just after the CA_FreeMemory() called as follows:

  CA_DiscardObjHandle (containerData);

  It should work.

  You can also try the following instead of the functions:

  CA_CreateObjHandleFromInterface (var, & IID_IUnknown, 1, LOCALE_NEUTRAL, 0, 0, & containerData);

  I think that you will still need to get rid of the objhandle when using this API.

  -Doug

• Opal kelly builders and LabWindows/CVI

  Hello, all.

  I try to get a Council Opal Kelly XEM3005 running with LabWindows/CVI 8.5.

  I have been in touch with Tech Suppt of OK and overthrew the original questions of type 'bool '.  After (at the recommendation of OK) with "char" types, I can now include the headers without errors.

  There are, however, a new problem:

  When I call the constructor function, which should return a pointer to a type of "okFrontPanel_HANDLE", I get an error for a prototype missing for initialization.

  Dredged in the .c (pp) file I found the following:

  //----------------------------

  Hi tomii,.

  Looks like you posted another very similar thread on the compilation of mistakes with the DLL of your Opal Kelly here. I follow upward in this thread to help get traction with those questions.

• Question of curiosity: several versions of LabWindows CVI can be installed on the same PC?

  I'm curious.  Several versions of LabWindows CVI can be installed on the same PC?

  I'm used to LabVIEW, where Yes, it is possible.  However, with CVI, other than the additional support with newer versions, there may not be a problem to return to an earlier version.  I still wonder.  Several versions can coexist in the same PC?  Or they affect each other?

  Curious...

  R

  You can, BUT only one (the last) version of the CVI runtime will be installed - this behavior began with CVI 6 or more.  Before that date, you have completely installed parallel to several versions of the CVI.

  This can be a problem if you ever find that you have applications depend on a particular version of the RTE.  Theory of NI is that this editor is always backward compatible.

  And you might ask what is simply the RTE - the answer is that it is a set of DLLS and stuff that NEITHER really cares to list for you.

  Menchar

• NOR tkds5000 LabWindows/CVI IVI driver not work for TDS5104, TDS5054B

  I'm trying to get the driver NI LabWindows/CVI IVI (tkds5000 version 1,212) working for the Tektronix TDS5054B scope.  When I execute the following functions, I have the warning 'Is not a valid value for the parameter or property' of 0xBFFA0010:

  IviScope_InitiateAcquisition

  IviScope_GetAttributeViInt32 for IVISCOPE_ATTR_TRIGGER_SCOPE and IVISCOPE_ATTR_ACQ_TYPE

  IviScope_ActualRecordLength

  This is not an exhaustive list of the functions that do not work, but just that I currently see.  There are several functions that work (see this joint SPY OR file).

  The strange thing is that everything works fine when I have an oscilloscope Tektronix TDS5104 connected (file SPY OR see attachment).  The code also works when I have an oscilloscope connected and selected through MAX TDS3054 driver tkds30xx IVI of NOR.

  Is it possible that the driver of version 1,212 tkds5000 does not support fully the TDS5054B?  I looked through the files tkds5000.c and tkds5000.h, but has not seen any dependencies on the model of the oscilloscope for these functions.  Any ideas?

  Thank you!

  Dave

  So, then I thought about it.  The tkds5000 driver AND works very well.  The problem is that the Tektronix TDS5054B scope do not "initialize" some of the attributes.  For example, I had a problem reading the value of the attribute of slope of relaxation because an invalid value was returned.  If I set the slope of the trigger, first of all, then read it, it works fine.

  Its strange because most of the attributes is set to the correct value corresponding to what is displayed on the oscilloscope screen and the Panel, but not ALL of them.  In addition, other Tektronix oscilloscopes did not require a writing before reading.

  Anyway, thanks a lot NathanT.  I appreciate your help.  You saved me a bunch of time to have to go back and add in a dedicated driver.

  -Dave

• LabWindows/CVI 8.5.1 for Windows 7

  I LabWindows/CVI version 8.5.1 running on XP that I use to develop with a target operating system from XP.  Now with Microsoft no longer provides XP, new sales for our product will go on Windows 7.  I guess I could use virtual XP environment in Win7, but I'd rather build my application as a native application for Win7.  I searched the forum and found some answers in fragmentary, and based on these points, here's my question:

  I want to use the version 8.5.1 of LabWindows/CVI to develop an application for Windows 7.  I see where install the runtime newest (2009 SP1) should be on the target (Win7) machine, and everything should be good; in other words, the application developed on XP with CVI 8.5.1 machine must run under Win7 with upgrade TEN 2009 SP1.  Is this correct?

  Are there problems with the update of the RTE on the development computer?

  Basically I'm asking if there is a problem do the following:

  PC 1: software development, XP, LabWindows/CVI 8.5.1, engine of execution of update for SP1 RTE2009, NOR-DAQmx 9.2.1 installed

  PC 2: computer application, Windows 7, SP1 Runtime Engine RTE2009, NOR-DAQmx 9.2.1

  Given this configuration, would be my application developed on PC1 work natively on PC2?

  One option would be:

  PC1: software development, Windows 7, LabWindows/CVI 8.5.1, engine of execution of update for SP1 RTE2009, NOR-DAQmx 9.2.1 installed

  PC2: no change

  Did anyone see any problems with any of these options?  (The big question is if CVI 8.5.1 would have had trouble with the RTE2009 SP1 for development).  Thank you!

  Hello

  You shouldn't have a problem of developing an application on a Windows XP computer to use on a Windows 7 computer. If you use the Windows SDK functions you may need to modify your code a little differences in BONE but other than that you should be ok as long as you take in the review on the connections. Have a great day!

  Best regards

  Adam G