LabWindows/CVI 2013 SP2

I just received the email announcing LabWindows/CVI 2013 SP2 is available for download.
I can't seem to find the release notes that explain the changes anywhere on the NI website.
Anybody know where the release notes are posted?
Thanks,
Kirk

Hello Kirk,
Please refer to the LabWindows/CVI 2013 SP2 Bug Fix Information document for a list of bug fixes included in the release.
Thanks,
Daniel D.
National Instruments
Automated Test Software R&D

Similar Messages

LabWindows/CVI 2013 SP2 stops working when I try to open a file using the project file menu.

I have windows 7 on my system and sometime late last year I starrted getting a Windows dialog telling me that LabWindows/CVI has stopped working when I try to open a file from the project file menu. I also get an error when I run a project debug mode and use a selectFilePopup in the code. The error says, "The program has suspended execution at address 0x75D5025E. No source line information is available." I've tried removing and reinstalling CVI to no avail. Any suggestions?

Constantin,
Thank you for your response. I've attached screnshots showing the version details for kernal32.dll and ntdll.dll. I also looked at the updates to see which might have been installed when the problem started. Unfortunately there are 15-20 updates every month. I didn't take note of when the error started to occur. At first it only affected my ability to open files from within the project (i.e. file->open->Source, etc). Then I went back to modify a project that had a SelectFilePopup and found that that wouldn't work either.
Attachments:
ntdll.dll version.jpg ‏15 KB

CVI 2013 SP2 and PID toolkit

Just a question on NI's Web site documentation:
The announcement of CVI 2013 SP2 mentions that the PID toolkit is now included...
Searching for CVI toolkit, the NI download page mentions a PID toolset 2.1, which, however, is said to work with Windows Vista/XP 32-bit/2000 only.
So before downloading and installing I'd like to know if it will work with Windows 7 and / or 64 bit?
Thanks!
Solved!
Go to Solution.

Hi Wolfgang,
I updated the web download page to reflect the OSs on which the PID toolkit has been tested. PID Toolkit 2.1 (32-bit) is supported on both Windows 7 32- and 64-bit OSs.
Thanks for bringing this to our attention!
Daniel D.
National Instruments
Automated Test Software R&D

Need to install LabWindows/CVI PID Control Toolkit (Part Number 320794A-01)

Hello -
I have a customer with a very old application who needs to upgrade their system to Win7 64-bit. The app references the old PID functions (manual here: http://www.ni.com/pdf/manuals/320794a.pdf) but no matter what I have searched for, I cannot find an installation for that toolkit. I have never had a need to use the current PID toolkit so I am not versed with it, and the difference in the functions do not seem to be a 1 to 1 change. Additionally, the customer is not paying for a code change - just assistance with the upgrade and reinstall. I would greatly appreciate if someone could point me to that download.
If such a download is not in existence any longer, I will need to request some assistance with modifying the source to use the current PID functions. I could attach the pertinent code if need be (there are not a great deal of references).
Thank you.

Hi CVIBri,
The installation files for the LabWindows/CVI PID Control Toolkit 2.1 are located at the URL below. I realize these are only officially compatible with versions of Windows up to Vista, however this is the most recent version of the toolkit that exists. I've also provided a link to the Evaluation License Files. That being said, LabWindows/CVI 2013 SP2 now includes the PID Control Toolkit as part of its Base and Full versions, and it is fully licensed with the same serial number used to activate the LabWindows/CVI development environement. The Readme linked below should provide more information.
PID Control Toolkit: http://www.ni.com/download/labwindowscvi-pid-control-toolset-2.1/1037/en/
PID Control Tookit Evaluation License Files: http://www.ni.com/download/labwindowscvi-pid-control-toolset-2.1/1038/en/
LabWindows/CVI 2013 SP2 Readme: http://www.ni.com/pdf/manuals/374674a.html
Thanks,
Myriam

Error when Building on CVI 2013 XmlReader fails to load

Thsi occurs during a code build under LabWindows CVI 2013 (FDS Version 13.0.2 (278) Windows 7 64 But Enterprise
The builds completes and is functional. However midway through the builds the error windows pops open and returns the following. This is a fairly recent change, I think, as the code (albeit being continuously changed with minor changes) used to build without erro windows. Possibly related to a Windows system update.
Please let me know if there is a known fix.
Error:
Error Details:
MetaToolbox::XmlReader::Load failed. SchemaPath=''
MetaToolbox:chemaValidationErrorHandler::fatalError: Error at line 1:
Invalid document structure
Error:
Error Details:
MetaToolbox::XmlReader::Load failed. SchemaPath=''
MetaToolbox:chemaValidationErrorHandler::fatalError: Error at line 1:
Invalid document structure

Hi;
Can you verify if the following files and folders exist?
C:\ProgramData\National Instruments\MIF\MetaInstaller\settings.xml
C:\ProgramData\National Instruments\MDF
It might be possible that the software needs to be reinstalled. In the following document you can see the instructions on how to repair it:
http://digital.ni.com/public.nsf/allkb/AC6ED75D3D93375686256E8E00245F0D

Return of void functions inconsistency between CVI 2013 and older

Hello,
I have discovered an inconsistency using CVI 2013 (SP2 or not) compared to CVI 2010 and CVI 8.5 (the versions I have).
I have written, by mistake, a code where I'm returning a value for a void function. CVI 2013 does not complain (but should) while other CVI versions complain (and that's OK).
Here is the code:
static void pouet(void)
return;
static void hop(void)
return pouet();
int main(void)
hop();
return 0;
Could this behaviour be fixed for the next CVI update ?
Thanks.
Frédéric Lochon.

Well it's technically not causing wrong behaviour, but may cause less than best performance depending on the compiler code generation as the register usually used for function return values might be assigned some garbage value that never will get used though.
Causing an error is likely a bit strict, issueing a warning would be the prefered behaviour, not generating either a warning or error is a bit lazy. Problematic would be if you could write this without getting an error:
static void pouet(void)
return;
static int hop(void)
return pouet();
int main(void)
hop();
return 0;
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

82351a with labwindows cvi

Hello,
I am trying to use Labwindows CVI 2013 with a GPIB card, Agilent 82351a and it can't talk with a GPIB instrument connected to the GPIB card.
NI-MAX can see the 82351a card but I can't use this card to talk with an instrument.
I installed Labwindows CVI with NI-VISA 5.4, AGILENT IO suite 16.3 with Agilent Visa a secondary VISA.
With NI-MAX, in the options VISA, I enable "Passport for Tulip" and with Agilent Connexion Expert, I tried to enable '"programs Agilent GPIB cards for 488" but it reboots the PC and the option remains not validated.
I wan't to know if this Agilent 82351a card can work with Labwindows CVI 2013.
thanks

http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/82351a-with-labwindows-cvi/m-p/2818356/highli...
Paolo_P
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Travaux Pratiques d'initiation à LabVIEW et à la mesure
Du 2 au 23 octobre, partout en France

CVI 2013 and Windows SDK

Hi,
I just downloaded and installed Labwindows/CVI 2013 full development system on my new computer.
It's a Win7 64 bit computer.
Do I have to do any additional installations to use Windows SDK functions, or is it included in the typical installation?
Thanks,
Kirk
Solved!
Go to Solution.

Unless in 2013 something has changed, normally you must explicitly select the corresponding option in order to have the SDK installed. You must perform the setup again and expand the CVI item in the product tree, next select "Interface to the Win32 API" item: the appropriate libraries and include files will then be installe on your system.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Cvi 2013 sp1 bug?

Hello,
I have defined a structure in the program :
typedef struct
    char name[100];
    char ip_addr[65];
}BATTERY_ALARM_STATE;
static BATTERY_ALARM_STATE gBatteryAlarmState;
void func()
        snprintf(gBatteryAlarmState.ip_addr, sizeof(gBatteryAlarmState.ip_addr), "%s", "127.0.0.1");
       snprintf(gBatteryAlarmState.name, sizeof(gBatteryAlarmState.name), "%s", "123456");
when executing the func(), it always popup the error message: Attempt to write beyond end of string. and the error always be stopped at the second "snprintf". This code run well in the cvi2013, but just have the error in the cvi 2013 sp1.
David

Hi David,
Where do you call func, in your program? I tried putting together a simple application (see snippet that follows), but it doesn't reproduce the behavior you described in LabWindows/CVI 2013 SP1.
// Include files
#include <ansi_c.h>
//====================================================================================================
// Types
typedef struct {
char name[100];
char ip_addr[65];
}BATTERY_ALARM_STATE;
//====================================================================================================
// Static global variables
static BATTERY_ALARM_STATE gBatteryAlarmState;
//====================================================================================================
// Function declarations
void func();
//====================================================================================================
// Global functions
int main ()
func();
return 0;
void func()
snprintf(gBatteryAlarmState.ip_addr, sizeof(gBatteryAlarmState.ip_addr), "%s", "127.0.0.1");
snprintf(gBatteryAlarmState.name, sizeof(gBatteryAlarmState.name), "%s", "123456");
//====================================================================================================
Can you confirm whether this code causes the same error for you?
Thanks,
Daniel D.
National Instruments
Automated Test Software R&D

Breakpoint are not respected on cvi 2013 under w8.1

Dear all,
I am using Labwindows/CVI 2013 on windows 8.1, and I have a strange behavior on breakpoints. Indeed, my program is not stopping on some breakpoints which I have set.
Randomly, the breakpoints are respected, which means that the program stops correctly on these breakpoints. Randomnly also, the breakpoints are not respected, which means that the program do not stop on the setted breakpoints, event that the program runs the instructions where the breakpoints are set.
I use the debug mode, and the instructions were the breakpoints are set are not comments, they are instructions.
I do not have this behavior when I run cvi 2012, under w 7. I do not know if the issue come from w8.1 or cvi2013, or...,
I would like that this issue wil be fixed.
Thank you for any help.
Cheers,

Hi hapiest,
Thank you for posting on this thread.
Can you share a simplified code that reproduces the behaviour and that I could run on my computer without any hardware and the .cws file ?
Also :
- What version of CVI are you using (SP ?)
- Does the berakpoints that are ignored still appread in the breakpoint listing box ?
- If you creates a project from scratch, does it reproduces the issue ?
Best Regards,
Isabelle G.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Été de LabVIEW 2014
12 présentations en ligne, du 30 juin au 18 juillet

CVI 2013 compiler: increment / decrement operator evaluation

I'm looking at pulling an old project forward to CVI 2013, but have hit a challenge, which is documented as follows:
"In assignment, the value of the right operand is evaluated before an array indexing is performed in the left operand. Expressions such as a[i] = i++; will evaluate differently in LabWindows/CVI 2013 when compared with previous versions."
(There is a somewhat related thread here to do with the order that function arguments are evaluated.)
This change in evaluation order is shocking to me. I assume there is some C history behind it, and I'm not going to be able to change that.
So, my question is: What is the easiest way to find all places in my code where this could affect me? I have ~75,000 lines of legacy code. Perhaps some regex magic?
Thanks,
Ian
Solved!
Go to Solution.

You can try to compile your code with sequence point checking. CVI compiler doesnot seems to know that.
But maybe lastest version of clang and/or gcc can help there. Be sure to compile with and without optimization, some warning messages depend on this.
( try -Wsequence-point on cmd line or something like #pragma clang diagnostic warning "-Wsequence-point" in source code)
Better but harder(i think) sollution can be to use some MISRA-C checker, they should detect this but maybe they give you too much warnings about all the unspecified and undefined behaviours.
Some list is on (section analyzers): https://www.securecoding.cert.org/confluence/display/seccode/CERT+C+Coding+Standard
I do not use any of them so i cannot reccomend one.

Visual Studio or LabWindows/CVI?

I have a bit of a dilemma.
I currently own Visual Studio 2010, IMAQ Vision Development Module 2013, and Measurement Studio (not sure of version). I currently do all of my programming in VB.net. Because IMAQ VDM is stuck in .Net framework 3.5 and there will be no further .net development by NI, I need to plan for the future. My applications need run on Win 8, 9, 43, or whatever my company decides to migrate to from Win 7.
My understanding is that the NI modules I currently own will work with LabWindows/CVI. Correct? I also believe I can use them with C++ using the VS IDE. Is this also correct?
Within my applications I do a lot of interfacing with Excel, writing text files, and interfacing to non-NI devices (cameras, DAQs, scanners, etc). I am able to do these things pretty easily using VB.net using vendor-provided SDK's.
Therefore, my question is this...given the investment I have in software already, do I gain anything by migrating to LabWindows/CVI? What do I lose?
I should point out that regardless of the path I choose I will need to bone up on my programming skills in the corresponding language.
Thanks for all your help!

Hello Steverino!
Here are some advantages when using LabWindows/CVI over Visual Studio, which make the product more suitable for various industry-related applications:
You are correct, LabWindows/CVI integrates with the NI platform: NI hardware and software, like TestStand or LabVIEW (e.g. debugging source code from one software to another, seamlessly).
NI hardware and third-party hardware connectivity.
OpenMP support.
CVI integrates with intrument control.
CVI Run-Time benefits from User Protection.
Run-Time checking (e.g. for uninitialized variables).
Scientific User Interface Controls and GUI Editor.
Advanced debugging capabilities:
Remote debugging support from ADE.
Real-Time debugging support from ADE.
Memory leak detection using the LabWindows/CVI Resource Tracking Window.
Just-In-Time debugging.
Deployment: build custom installers and patches that you can ship as stand-alone easy-to-use installers.
LabWindows/CVI libraries: Advanced Analysis, Toolbox, Connectivity (Network Variables, Network Streams, DataSocket), etc.
Support for LabWindows/CVI Toolkits: SQL Toolkit, Vision, PID, RT.
Regards,
- Johannes.

Labwindows CVI Full featured OI fails to start

I've done a deployment installer for Teststand-2013. On one Target PC( Windows 7 64 bit) it works fine. But on another target PC starting the Labwindows/CVI Full featured OI fails to start ( screenshot attached) with an Error -145 when trying to load testexec.uir . Both targets have Windows7 64 bit and Office 2010 installed. How can I find out which Active-X control is missing/damaged on the second PC ?
I've allready found http://digital.ni.com/public.nsf/allkb/9894BE2B832B7FDE86256ECD00041172. But Office is installed and the ActiveX Control Pad is deprecated and incompatible to Windows7 64Bit and no longer available from MS.
Solved!
Go to Solution.
Attachments:
Fehler Teststand.png ‏31 KB

There are no custom commands. It is launching the Operator Interface after the panel with the checkbox, where you decide if you want to activate now. We choose to activate later there. And it also launches the OI when uninstalling.
I'am attaching the .tsd file, we are using. This installer should only include stuff , which is common to all teststations like the OI and Teststand Public. So it doesn't include sequences and other files, which are specific to one teststation.
Attachments:
testand2013.zip ‏25 KB

Entering numeric values with suffixes in Labwindows CVI (e.g 100 kHz instead of 100e3 or 100000 )

is there any practical way of entering numeric values with suffixes in Labwindows CVI in order to prevent user from struggling with '0' es.

In LabVIEW there is another Display Format called "SI Notation" that is exactly what you're looking for.
Maybe you can add a feature request in CVI Idea Exchange Forum and ask NI to add this Display Format in CVI too.
Vix
In claris non fit interpretatio
Using LV 2013 SP1 on Win 7 64bit
Using LV 8.2.1 on WinXP SP3
Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

Software Development Engineer positions at Hysitron, Inc. in Minneapolis (LabWindows CVI exp preferred)

Software Development Engineer
Hysitron, Inc. is a premier scientific instrument manufacturer. Founded in 1992 with headquarters located in Eden Prairie, MN we are committed to promoting nanotechnology by developing advanced transducer and control technology. This leadership has made Hysitron the world leader in nanomechanical test instruments. The TriboIndenter®, TriboScope®, Ubi, and other Hysitron innovations have opened new horizons for scientists interested in investigating and understanding mechanical properties of materials at nano-scale. Hysitron fosters an environment and culture where innovation flourishes, teamwork is encouraged, and superior performance is rewarded.
Hysitron invites applications for multiple software development engineer positions from those aspiring to explore and succeed in the nano world. Hysitron, Inc. is an Equal Opportunity Employer M/F/D/V
Job responsibilities
The software development engineers would be responsible for developing test and measurement software applications for nano-mechanical testing instrumentation. Job deliverables would include:
-          Develop software applications in C based Labwindows CVI for Hysitron Instrumentation
-          Support the development of applications to address challenges in instrument automation and control
-          Test software applications using debugging and simulation tools
-          Perform software releases and software quality assurance activities
-          Participate in the design of new software products
-          Perform maintenance activities for existing products
-          Adapt and deliver on quality software development practices
Minimum qualifications
-          BS in Computer Science/ Computer Engineering/ Equivalent Scientific or engineering discipline
-          Min of 3 yrs experience in Instrumentation software development in an industrial or R&D environment
-          Expert at programming language C, knowledge of C++
-          Working knowledge of various communication protocols, e.g. USB, RS232, IEEE, RS485, TCP/IP, Modbus
-          Knowledge of general software design/documentation processes in test and measurement systems
-          Proficient problem solving skills
-          Strong analytical and technical skills
-          Excellent communication and interpersonal skills
Preferred Qualifications
-          Proficient with LabWindows CVI and XML
-          Working experience with DSP(Code Composer Studio) and/or FPGA level programming
-          Exposure to digital electronics and instrumentation
-          Working experience in Robotics interface programming
-          Experience with Controls/Automation engineering
Application and Information
Qualified candidates should send a letter of application and their resumes to (please include ‘SW Engineer’ in subject line):
Hysitron, Inc.
10025 Valley View Rd
Eden Prairie, MN 55344 USA
Phone: (952) 835-6366
Fax: (952) 835-6166
E-MAIL: [email protected]
Web: www.hysitron.com

This position is still accepting resumes/CVs.

LabWindows/CVI 2013 SP2

Similar Messages

Maybe you are looking for