LabView donwconvert from 11.0 to 9.0

HI,
Can someone help me to downconvert Commtech FSCC LabView drivers from version 11.0 to 9.0 ?
Thank you
Attachments:
fscc-labview V1 driver support only(1).zip ‏773 KB

Saved in 2009.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
fscc-labview 2009.zip ‏1061 KB

Similar Messages

Is it possible to call a VI that is inside a LabVIEW executable from a TestStand sequence?

I have created a custom TestStand operator interface and have modified the default sequential process model to display a UUT information dialog that prompts for more information than just the UUT serial number. This UUT information dialog is a LabVIEW VI. To distribute the operator interface, I build it into an executable. As part of the build process, I make a copy of the UUT information dialog VI (which is part of my operator interface project) and place it in the same folder as the executable. I have then configured the sequential process model to call the dialog VI from this location. It would be really nice if I could embed the UUT information dialog VI inside the operator interface executable so that I could distribute just an executable instead of an executable and separate VIs. Is this possible? In other words, is it possible to call a VI that is inside a LabVIEW executable from a TestStand sequence just like a standard LabVIEW VI call?

Ryan,
The dialog that you've created isn't being directly called by the OI at all and shouldn't need to be included in the same directory as the OI for distribution. Since you are modifying the PreUUT of the default process model, you will give the path to the VI in that step, create a deployment and then manually copy the VI to the directory referenced in the step. The VI is considered a support file for the process model and is not related to the OI at all.
Test Engineer - CTA

How can I call a LabVIEW executable from within another LabVIEW executable?

I have a customer requirement for two LabVIEW executables. Based on their current setup, they need to run executable "A" or "B", both of which are under independent revision control. I have created a third "selection" executable that allows the operator to choose between one of the two, but I am receiving errors when I attempt to call a LabVIEW executable from within a LabVIEW executable using either the "System exec" VI or the "Run Application" VI. If I call a non-LabVIEW executable (such as Windows Explorer) everything works fine.

> I have a customer requirement for two LabVIEW executables. Based on
> their current setup, they need to run executable "A" or "B", both of
> which are under independent revision control. I have created a third
> "selection" executable that allows the operator to choose between one
> of the two, but I am receiving errors when I attempt to call a LabVIEW
> executable from within a LabVIEW executable using either the "System
> exec" VI or the "Run Application" VI. If I call a non-LabVIEW
> executable (such as Windows Explorer) everything works fine.
As with the other poster, I suspect a path problem. You might try the
path out in a shell window, and if it works, copy the complete absolute
path to LV to see if that works. LV is basically passing the comma
nd to
the OS and doesn't even know what is in it, so you should be able to get
it to work.
The other poster commented on subpanels, which is a good suggestion, but
without going to LV7, an EXE can have open more than one VI. You can
use the VI Server and the Run method to fire up another top-level VI.
The decision is whether you want both to be in unique processes.
Greg McKaskle

How to call a labview dll from excel-VBA?

How to call a simple Labview DLL from Excel VBA?
I have seen examples of DLL calls from VB but does it work the same way for VBA? I have 2000 excel and Labview 8.5. I created the DLL and tried to call it from VBA using the same type of code as in NI's website example(ofcourse its a bit diff with 8.5)
http://zone.ni.com/devzone/cda/tut/p/id/...
BUT it errors out when called from excel
ERROR: The object invoked has disconnected from its client

You would need to provide more details about the LabVIEW DLL, such as the prototypes of the functions (VIs) that you're trying to call, and your actual VBA code. Specifically, what object you're trying to create. You should also make sure the Run-Time Enginer is installed, as well as any required libraries such as the VISA Run-Time if you're using VISA. Have you made sure to enable the ActiveX server for the DLL?
A search yielded the following items that you may wish to peruse:
http://forums.ni.com/ni/board/message?board.id=170&message.id=261345&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=170&message.id=45099&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=170&message.id=299209&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=170&message.id=195846&requireLogin=False

Unable to load LabVIEW RT from drive

Trying to boot RT on PXI-8187 controller with original setup, what ever RT boot selection is used either hardware switch or BIOS RT boot option, the terminal will show the following:
Unable to load LabVIEW RT from drive!
Booting safe mode from ROM...
mount: Mounting /dev/Ma1 on /home/ftp/c failed: Invalid argument
Entering safe mode.
IP address is: 0.0.0.0
Of course after that you can't do any thing to configure the RT target from the MAX on the host computer.
Please Help.

Hi,
I used the recovery CD to change the file system to NTFS, it took a while and it installed windows XP from scratch differently from FirstWare that ghosts it (I think). And it didn't install any NI stuff what so ever.
At the end I got the same result as with using the remote system format disk option.
i.e. The RT controller boots in safe mode displaying the previous message without the mount error but this time I can configure the IP address.
Still I can't install software to it, I get the list of features to install, I select them and press next, then I get a dialog saying:
Cannot process install because other dependencies are required:
LabVIEW RT 1.0.1
LabVIEW RT 6.0.1
LabVIEW RT 6.1.0
LabVIEW RT 7.0.0
LabVIEW RT 7.1
Is this a host or RT Controller issue now?
What's next? Thanks for the help

Call LabVIEW VIs from MATLAB

Does anybody know of a simple way to call LabVIEW VIs from within a MATLAB m-file? I would like to be able to write VIs in LabVIEW and then script them (for stochastic analysis, etc.), and think MATLAB would be an awfully convenient way to do this (also useful for data analysis, etc.). I have looked at LuaVIEW, but it appears to have been largely abandoned.
Thanks!

Hello Erik,
Building it into a DLL as Altenback said is a solid way to do this, and here's a Knowledge Base article that also explains how to transfer data in binary or ASCII format, How do I Transfer Data Between The MathWorks, Inc. MATLAB® Software Development Environment and LabV...
Thank you,
Deborah Y.
LabVIEW Real-Time Product Marketing Manager
Certified LabVIEW Architect
National Instruments

How to call labview DLL from C#, passing char, char[], float[], long, short

Hi,
I'm having trouble calling labview dll from C# to perform certain function.
The function supposed to return the values in the float Analysis[] array. However, when I execute it it only returns zero values.
It seems that some parameters are not properly passed to the dll.
Below is the function in the header file:
void __stdcall Optical_Center(char FileDirectory[], long ImagePtr,
    short int Height, short int Width, char ReadFromFile, float Analysis[],
    long lenAnalysis);
and my corresponding dll import in c#:
[DllImport(@"SMIA.dll", CharSet = CharSet.Ansi)]
        public static extern void Optical_Center([MarshalAs(UnmanagedType.LPStr)]string FileDirectory, long ImagePtr,
            short Height, short Width,char ReadFromFile, IntPtr Analysis,
            long lenAnalysis);
string str = @"C:\SMIA.raw";
int len = 3;
long m_lenAnalysis = 3;
long m_ImagePtr = 0;
short m_Height = 2464;
short m_Width = 3280;
IntPtr m_PtrArray = Marshal.AllocHGlobal(len * Marshal.SizeOf(typeof(float)));
char m_ReadFromFile = '1';
Optical_Center(str,m_ImagePtr,m_Height,m_Width,m_ReadFromFile,m_PtrArray,m_lenAnalysis);
float[] m_Analysis = new float[len];
Marshal.Copy(m_PtrArray, floatArray,0,len);
Marshal.FreeHGlobal(m_PtrArray);
string printstr = "";
for (int i=0; i<len; i++)
    printstr = printstr + floatArray[i].ToString() + "\n";
MessageBox.Show(printstr);
Appreciate if anyone can help, thanks.
KL

I was just about to post the header file of the DLL, when
I noticed that there's a function called LVDLLStatus.
This little thingie turned out to be a rather handy tool.
With that function I found that in the DLL I had a problem
with another function that prevented the DLL to be correctly
loaded.
This other function in the DLL is for generating digital output
and it worked as it should, when tested from LV.
Anyway if someone is interested, I got it working by using
the LoadLibrary and GetProcAddress function, as in the
source code thatI posted earlier.
I will investigate what is wrong with that digital output, and
post into a another thread if I have problems with that.

How to call Labview DLL from VB2005

Dear all expert,
I'm a student and very new in Labview programming.
Currently i have build a simple vi and need to convert it to dll so that i can call it from my VB.net. But the problem is how to call the labview dll from my VB.net?
I know we must declare function something like this,
Auto function Bodeplot Lib"..\\Bodeplot.dll" (Byval Val1 as double, Byval Val2 as double,...) as double
but how to determine Val1, Val2 (and so on) is input for which data? if my vi have 10 input (frequency, Kc,Fcz,Fcp,Wzrhp,Wp,k,Wz,Beta and Operation) ? and how to select the output (my application have 3 possible output : magnitup loop,phase loop, and degree loop)
In addition, since I'm using Labview 8.0 , and as i know apllication builder for this version cannot convert vi to dll which contain Mathscript (but unfortunely, my vi all use Mathscript), so really hope someone can help me to convert my vi to dll using Labview 8.2 (which remove this limitation).
here I'm attach my Vi and really hope someone willing to help.
Thank you.
Attachments:
bodeplot.vi ‏1049 KB

On Sep 17, 6:40 am, cckoh <[email protected]> wrote:
> Dear all expert,
> I'm a student and very new in Labview programming.
> Currently i have build a simple vi and need to convert it to dll so that i can call it from my VB.net. But the problem is how to call the labview dll from my VB.net?
>  
> I know we must declare function something like this,
>  
> Auto function Bodeplot Lib"..\\Bodeplot.dll" (Byval Val1 as double, Byval Val2 as double,...) as double
>  
> but how to determine Val1, Val2 (and so on) is input for which data?  if my vi have 10 input (frequency, Kc,Fcz,Fcp,Wzrhp,Wp,k,Wz,Beta and Operation) ? and how to select the output (my application have 3 possible output : magnitup loop,phase loop, and degree loop)
>  
> In addition, since I'm using Labview 8.0 , and as i know apllication  builder for this version cannot convert vi to dll which contain Mathscript (but unfortunely, my vi all use Mathscript), so really hope someone can help me to convert my vi to dll using Labview 8.2 (which remove this limitation).
>  
> here I'm attach my Vi and really hope someone willing to help.
>  
> Thank you.
>  
>
> bodeplot.vi:http://forums.ni.com/attachments/ni/170/272124/1/bodeplot.vi
If you insist on using Labview with your project then you should
consider using ActveX in place of using a dynamic link library to
interface to your VB.net code. You don't need "Application Builder"
if you use ActiveX. The Student, Basic and Full development versions
of Labview for Windows come with ActiveX capability. For more
information on ActiveX look up the subject ActiveX in Labview's Help
File.
Howard

How to call LabVIEW dll from ATL COM dll

I have tried to call simple LabVIEW 8.6 Dll from win32 test application, class Library.
I have include LabVIEW generated SharedLib.h file and SharedLib.lib file in the test application which I created as simple win32 console project and also from win32 class Library. I was sucessfully able to call my LabVIEW dll funtion.
But when I create ATL COM project and try to add SharedLib.h file and SharedLib.lib file I used to get following erors
Error 1 error C2733: second C linkage of overloaded function 'StrCatW' not allowed d:\program files\national instruments\labview 8.6\cintools\extcode.h 463
Error 2 error C2733: second C linkage of overloaded function 'StrCpyW' not allowed d:\program files\national instruments\labview 8.6\cintools\extcode.h 464
Error 3 error C2733: second C linkage of overloaded function 'StrCpyNW' not allowed d:\program files\national instruments\labview 8.6\cintools\extcode.h 465
Error 4 error C2733: second C linkage of overloaded function 'StrCmpW' not allowed d:\program files\national instruments\labview 8.6\cintools\extcode.h 466
Error 5 error C2733: second C linkage of overloaded function 'StrCmpNW' not allowed d:\program files\national instruments\labview 8.6\cintools\extcode.h 467
these many errors.
Will some one explain me how to call LabVIEW dll from ATL COM dll.
Thanks & Regards,
Jay

I also had this problem. My application is unicode-aware, but I was attempting to link it to a library with primitive C-string arguments. You could dynamically load the DLL as suggested (more work), modify the header files (really not recommended), or if you are feeling lucky you could try fooling the compiler, as I was successfully able to do in Visual Studio 2010, by steering the preprocessor around those functions (assuming you're not using them, of course -- otherwise this probably wouldn't work):
// prepare for NI extcode.h inclusion. avoid linker errors for this project.
#define StrCatW(a,b)     IgnoreLinkError_StrCatW(a,b);
#define StrCpyW(a,b)     IgnoreLinkError_StrCpyW(a,b);
#define StrCpyNW(a,b,c) IgnoreLinkError_StrCpyNW(a,b,c);
#define StrCmpW(a,b)     IgnoreLinkError_StrCmpW(a,b);
#define StrCmpNW(a,b,c) IgnoreLinkError_StrCmpNW(a,b,c);
// header file for my LabView-built DLL (ASCII single-byte character arguments)
#include <MyLibraryHeader.h>
// clean up afterwards, put things back to 'normal'
#undef StrCatW
#undef StrCpyW
#undef StrCpyNW
#undef StrCmpW
#undef StrCmpNW

Need to convert to labview 11 from labview 12

hello
I need to convert the following Labview 12 VIs to Labview 11.
thank you in advance
Attachments:
QAM Demodulation.vi ‏30 KB
QAM Modulation.vi ‏30 KB
rx QAM.vi ‏57 KB

The conversion was done here: http://forums.ni.com/t5/Version-Conversion/need-to-convert-from-Labview-12-VI-to-Labview-11/m-p/3021...
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Labview graph from excel data

Hello,
I need some help. I have data in excel The first column is a timestamp and the other columns are the data needed.and I am trying to get a graph with multiple plots with these data.
attached here are the excel file and a labview file. In the labview file, the top part is an example I got from the forum, an interesting graph I am trying to follow.
The bottow part is my tentative to extract the data from excel into array and try to use it. but I am stuck here. Any help please!
Thank you,
Agyna
Attachments:
graph.vi ‏13 KB
Histo.xlsx ‏53 KB

Hi agyna,
I've saved xls file into csv and then i'm reading into labview and plotting the graph. Please check it this is what you need.
Thanks
uday,
Please Mark the solution as accepted if your problem is solved and help author by clicking on kudoes
Certified LabVIEW Associate Developer (CLAD) Using LV13
Attachments:
graph.vi ‏18 KB

Generate a LabVIEW VI From My SignalExpress Project

I'm using Signal Express to acquire and analyse signal from Tektronix TDS 2012B digital storage oscilloscope.
I've two problems facing now.
1.
I'm not able to plot the BH Loop (Hysteresis Loop) in Signal Express, which is shown correctly in TDS 2012B but it is shown as two seperate channels in Signal Express. How can i get the BH loop in Signal Express.
I've attached the snapshots for the signal from 'TDS 2012B' and 'Signal Express'
2.
Now I've this project saved in my comptuer. I was trying to convert this project to a LabVIEW vi. While converting it shows an error that "Tektronix instrument control steps cannot be generated into LABVIEW code at this time".
What should i do to convert the saved project into a labview code successfully.A snapshot of the 'error' is attached with this message.
Using LabVIEW 8.0, 8.0.1, 8.2
Attachments:
Error.jpg ‏87 KB
TDS 2012B image.jpg ‏96 KB
from Signal express.png ‏7 KB

Hi,
Sorry, I didn't realize you were using SignalExpress 1.2. The ability to view time signals as XY was added in SignalExpress 2.0 which released earlier this year.
I'm including a simple LabVIEW VI which you can run in SignalExpress 1.2 using the "User-Defined Step". In the step, select the VI that I'm including and pass your 2 channels as inputs. The output of the step will be an XY value. You can graph this directly and it will be in XY. It's the equivalent of what SignalExpress 2.0 does natively in the graph.
I hope this helps,
Phil
Attachments:
ConvertToXY.vi ‏38 KB

Controling a LabVIEW VI from C#

Hello,
I'm writing a C# program that calls LabVIEW VI's using the ActiveX automation interface.
Getting started was quite straightforward (Load a VI, set/get simple parameters, run VI, etc...), but I could not figure out how to pass "clusters" from my C# program to LabVIEW...
The help for the "VirtualInstrument.call" method mentions a cluster should be treated as an array of variants - any example available?
I also noticed a "LabVIEWTypes" assembly that seems to have been created to allow manipulation of waveform data types was available- Did anyone experimented with this already?
...Any information would be appreciated!
Regards

I could figure it out ...
In .NET, there are no variants anymore - everything derives from "object" and so we need to create an array of object - each object in this array being a "field" of our cluster.
Let's consider a cluster that contains 3 numeric (double), we would control it from C# in the following manner :
//settings cluster [cluster = array of objects]
object[] myCluster;
//declare settings "cluster"
myCluster = new object[3];
myCluster[0] = new double(); //
myCluster[1] = new double(); //
myCluster[2] = new double(); //
//assign values to settings cluster
myCluster[0] = 3.14; //
myCluster[1] = 1.2; //
myCluster[2] = 2.3; //
//Write value to the LabVIEW cluster
myVI.SetControlValue("<clusterName>", myCluster);
Enjoy...

Calling labVIEW vi from matlab

i want to pass data (modulated sine wave) from matlab into labview,
transmit it (through the NI-DAQ card) into a channel, receive it back
on the input port of the card and pass the data back from labVIEW into
matlab. i built the vi and compiled the corresponding mex function.
when called, the function runs without error but the problem is that i
get back only noisy values and i have also verified with the help of a
CRO that no actual wave is transmitted. i.e., it seems that the labVIEW
vi doesn't actually run (though the LabVIEW window does open). this
after i have selected the "load front panel" option in the vi
properties. i might add that when i created a vi that uses the
"simulate sine signal" tool of labVIEW itself to transmit a sine wave
over the channel (As against using data from matlab, as in the former
case) but receive the data into matlab only (as in the former case),
the VI runs when called from matlab, the CRO shows sine waves being
transmitted and received and the data i receive into matlab is an
attenuated sine wave as expected. any MIT pro who can help me out?
Thanks.

It sounds like the problem is not that the VI isn't running, but rather that the data it is "receiving" from MATLAB is getting messedu up. This conclusion is drawn, of course, from the fact that simulated data can successfully be written and read in LabVIEW and passed to MATLAB using the same methods. The only way to get to the bottom of this dilemma is going to be to do some good, old-fashioned troubleshooting.
Since we believe that the problem lies in MATLAB passing data to LabVIEW, the first thing you can try is putting a pause at the beginning of your LabVIEW code and creating a graph on the VI's front panel to show the data before it is written. If it is jumbled there, then you'll next want to check the data inside of MATLAB before it is passed. If that data is okay, then you've narrowed it down to the actual transfer, and you should then start making sure that you are matching the proper datatypes and formats. Hope this points you in the right direction!
Kind Regards,
E. Sulzer
Applications Engineer
National Instruments

Change TS Labview Server from Labview OI?

I have tried the NI recommended way to select the LabView server programatically from TestStand which works fine e.g.
RunState.Engine.GetAdapterByKeyName("G Flexible VI Adapter").AsLabVIEWAdapter.SetServerInfo(LabVIEWServer_RTEServer, "C:\\Program Files\\National Instruments\\Shared\\LabVIEW Run-Time\\8.6\\lvrt.dll")
But I would like to call the same functionality from a LabView Operator Interface...
After I get the engine reference I can use an Invoke node for GetAdapterByKeyname but I am struggling with the next AsLabVIEWAdapter.SetServerInfo part - I can't see these methods. Any tips/examples how to do this?
Thanks.

Simon,
Thank you for providing CIM1 with this VI! I have made a few improvements to the VI and attached it below. You don't actually have to use the Adapter.AsPropertyObject method at all, you can directly connect the Adapter reference to the Variant to Data VI and cast it to a LabVIEW Adapter.
Also, the logic that was used for determing the type of LabVIEW Server seems incorrect. According to the LabVIEWServerTypes Enumeration Help, the LabVIEWServer_ExecServer enum should be used for the LabVIEW development environment or a LabVIEW executable that registers itself as a LabVIEW ActiveX Automation Server. The LabVIEWServer_RTEServer enum should only be used for the LabVIEW Run-Time Engine. In your code it seemed like you were setting the LabVIEWServer_RTEServer enum for both the LabVIEW Run-Time Engine as well as a LabVIEW executable server. I've modified this portion of the VI as well to behave correctly.
Let me know if you have any questions.
Manooch H.
National Instruments
Attachments:
ConfigureLabVIEWAdapter.vi ‏13 KB

LabView donwconvert from 11.0 to 9.0

Similar Messages

Maybe you are looking for