Labview 12.0 to Labview 11.0..1f2

I got this message when I tried to run:
Labview: File version is later than the current labview version.
an error occurred loading VI 'save_v2.vi'. Labview load error code 9: VI version (12.0) is newer than Labview version (11.0.1f2).
Thanks a lot,

thank you so much for your quick response. code works well.

Similar Messages

LabVIEW Class crash - ntdll.dll access violation

Hi,
When I close my LV11SP1f2 I always get a warning.
It didn't bother me until a vi I wrote that uses a class with nothing out of the ordinary started crashing my LV.
The crash says that: "DAbort 0x37C03D in MemoryManager.cpp"
I sent the log files to the local support and they saw that the common issue between my logs is an access violation in ntdll.dll.
Any operation that uses the property nodes of that crazy class fails, sometimes with a crash and sometimes with a error that sends me to a bundle by name in the autocreated property node.
I rewrote the project with the class and there is no error.
Sending the crashing project to another computer gave no error.
Before I go on and investigate windbg to search for a conflicting app and finally formatting my entire computer could some1 help? Please...
I attached several logs for example.
Thanks in advance,
GoofyWires.
Attachments:
92c82e7b-fa2a-43af-b2be-a6650c031681.zip ‏2485 KB
daa462b5-9395-4e3f-8894-05a3bdb3d159.zip ‏65 KB
ea2c40ef-056d-41ed-a4c5-9cf4bc6666fc.zip ‏494 KB

I did a clean format and reinstalled LabVIEW 11.0.1f2 without adding many of the add-ons from VIPM and without installing the rest of my shortwave, yet, the crash is still here!
I was able to reproduce it on my pc:
1. I have a class that contains two children of another class which each contain another class with a class inside it.
2. I accessed the classed through property nodes.
3. I then went on and deleted a private data from the first class control, deleted its property nodes and added a new private data to that class control and added the property nodes for it.
4. I updated the vi that used the classes to stop using the deprecated property node and start working with the new one.
5. I did a "save all" and run the vi. All OK!
6. I closed LabVIEW and reopened the project and run the vi which is not broken! LabVIEW crashes!!!
I guess the complexity of the class is not the issue and it can be reproduced in a much simpler way.
Yet, since I bet the scenario caused you to raise an eye brow I'll give an example as an analogy:
File Handler class contains ASCII Read class and ASCII Write class which inherit from class ASCII.
Class ASCII parent contains class Headers while class Header contains class Data.
Thus, class ASCII Handler will use class ASCII Read/Write to give a high level simple interface while during the read/write the inner ASCII Read, for example, will add to the Header class in it the read data which will in turn be added to the array in the private data of class Data.
I'll try and reproduce it on a different pc and send the local NI support the code and way to reproduce.
I see two possibilities:
1. Something is wrong with my new Dell PC.
2. LabVIEW doesn't handle and propagate correctly changes in a class to all the vis that use it. Maybe changing the array size in a class overrides some memory since the class can't change its size.
Please let me know if this rings a bell.
Update: I coundn't reproduce the crash on my pc with a simpler case. There is something missing...
I'll try to replroduce with the complex class on a different pc and if it crashes I'll simply send my original code.

Problem with different Labview platform

Maybe this issue must be address to NI.
I have this library calling a register DLL. The purpose of the library is to convert a type of movie file from hard drive(*.mcf type) to image stream then to show and eventualy to save it.
The DLL is designed by NAC camera designer, which is a high speed camera. The code is based on properties, methodes and events from DLL.
Code works well in Labview 8.6.1, in Labview 11.0.1, Labview 12.0f3. Unfortunately code does not work in Labview 11.0.1f2 which happens to be the one I am developing my applications.
I will post the code developed by NI Japan (camera also is designed in Japan) and the mcf file as well as the DLL which must be registered.
The code is compiled in 8.6.1.
Register first the dll then open the NAC MCFF Control_E.vi.
Brows the mcf file
Press Open button
Slide the frames one by one for showing the images content of the mcf.
If you want to open under other labview then 8.6.1 then copy the folder and run a mass compile under that version then open the same top vi.
Please, show me what is different for different versions of labview then in my version does not work.
Than you,
Virginia
Solved!
Go to Solution.

Just because it doesn't crash does not mean automatically that everything is alright. You just might be unlucky that the memory corruption does not happen in a vital part of the LabVIEW memory.
Now, when loading your LLB in LabVIEW on my machine, the first indication that something is wrong would be the error message that C:\Windows\System32\gdi32.dll could not be found. And indeed this is a system DLL that should never be referenced by the full path but simply by the DLL name alone. So change the Library Name or Path in the CLN inside the nac_NI_BitmapRead.vi to just "gdi32.dll" (without quotes). And when you are at it, change the first parameter to be a pointer sized integer too, since this IS a pointer.
Now look in the configuration dialog in the Function tab a bit further down and notice that the Calling convention is set to C. 99% of all Windows userspace APIs are really stdcall under Win32 and fastcall under Win64. A "bug" in LabVIEW versions before 2009 attempted to automatically fix wrong calling conventions from C to stdcall, based on certain naming attributes of the actually exported function in the DLL (and no, LabVIEW does not show those decorated names but the human readable name). The problem with this fix was that it did not allow for calling (admittingly seldom but nevertheless possible configurations) of DLL functions that happen to follow this naming scheme but were explicitedly declared cdecl by the programmer.
Try it and tell us if that will help.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

IMAQ-dx acquires at half the expected framerate

I have a USB 2.0 camera that I am using with IMAQ-dx. I currently have the video mode set to 640x480 MJPG 30.00 fps. However, whenever I attempt to use the grab function I get frames returned at about 15 fps, with spikes between about 10 and 19 fps. I have tried using both NI-MAX and property nodes to set the framerate to 30 fps, but while I can set it that way, the camera still acquires images at 15 fps.
Additional information:
I have a second USB camera that I sometimes use at the same time as a first camera. When both cameras are using the grab function, the framerate is the same as when just one camera is (15 fps).
The camera acts the same in both labview 13.0.1f2 and labview 14.0f1. \
I have attached a simple program that I'm using for diagnostic purposes.
Attachments:
camera properties.vi ‏20 KB

How is your exposure on your cameras and lighting situation?

TestStand Building Express VI menu error 42

Trying to refresh/build express VI menu in TestStand 31 using LabVIEW 7.1.1f2. Get error code 42 (generic error). Any suggestions?
Have tried to delete "ExpressMenu7.1.1" in ..\TestStand 3.1\Cfg - same error

Hi
I've found a solution: Only if default menu is selected in LabVIEW, TS is capable to update the express menu.
Best regards
Vagn
Attachments:
TestStandBuildingExpressVImenuError.JPG ‏124 KB

Digital - Finite Output.vi

LabVIEW初心者で、サンプルプログラム Digital - Finite Output.vi についてお聞きします。
環境
　- LabVIEW 13.0.1f2 (32bit)
　- PXIe-6363
　- ライン＝PXI 1Slot3/port0/line7
- サンプルクロックソース＝OnboardClock
　- サンプルレート＝1000 （デフォルト値）
　- トリガなし
質問
　サンプルの、
　フロントパネルで、「書き込むデータ」欄に配列があります。
　ブロックダイアグラムで、DAQmx Write.viにつながっている配列です。
　この配列はどのような意味があるのか教えてください。
状況
　配列には8個の値（1,2,4,8,16,32,64,128）があり、
　128以外の数値を変更しても、出力信号に変化がみられません。（オシロで観測）
　一方、128の数値を127以下にするとパルス列は出力されなくなり、
　128～255の間だけパルス列が出力されます。
　数値の意味についてヘルプ等探しましたがわかりませんでした。
添付図
　FrontPanel.png　サンプルのフロントパネル
　8番目の値＝128（デフォルト）　デフォルトのまま実行したときの波形
　8番目の値＝127（値を変更）　8番目の値だけを127に変更したときの波形
以上、よろしくお願いします。
解決済！
解決策の投稿を見る。
添付:
FrontPanel.png ‏76 KB
8番目の値＝128（デフォルト）.png ‏13 KB
8番目の値＝127（値を変更）.png ‏10 KB

お聞きされたいのは、LabVIEWの配列制御器に関することなのですね。
左側のBOXには、配列の指標番号を指定して、どの要素を表示させるかを決めます。
例えば、要素が1, 2, 4, 8, 16, 32, 64, 128の配列がある場合、左側のBOXに7を指定すると、指標7 (最初の要素は指標0なので、前から8番目の要素を指す) の128が、配列制御器の一番上に表示されます。
そのため、左側のBOXの値を変更しても、配列制御器に表示させる要素を変更しているだけで、配列データそのものは変化しません。
詳しい内容はヘルプを確認してください。
配列やクラスタでデータをグループ化する - LabVIEW 2013ヘルプ - National Instruments
http://zone.ni.com/reference/ja-XX/help/371361K-0112/lvconcepts/grouping_data_with/
なお、DAQmx読み取り VIに、要素が1, 2, 4, 8, 16, 32, 64, 128の配列が入力されて、かつ、DAQmxタイミング VIのサンプル数に、例えば100が指定されている場合、VIを実行すると、1, 2, 4, 8, 16, 32, 64, 128, 1, 2, 4, … といった形で、出力するサンプルが100に至るまで繰り返し出力がなされます。
[例1] でP0.7が正論理となるのは128というサンプルが出力される際で、[例2] でP0.6が正論理となるのは64というサンプルが出力された際なのではないかと考えられます。

Is there a way to detect a bad http client handle before it locks up LabVIEW?

The attached VI demonstrates a simple way to hang LabVIEW such that the only way to recover full use of it is to kill the LabVIEW process. LabVIEW version is 11.0.1f2 and this problem will occur in both WinXP and Win7.
Is there a way to detect when an HTTP Client Handle refnum is stale and should not be used?
Is this a known bug?
Attachments:
Hang after Bad HTTP Client Handle.vi ‏15 KB

Have you tried the bad reference comparator?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Ran updates, LabVIEW & MAX will no longer recognize my cDAQ?

As stated, I ran updates yesterday through NI Update Service... it suggested SP1, and a couple of others. Ran them, and today my computer doesn't see my cDAQ (9174).
Running...
Win7 Pro 64bit
LabVIEW Professional Ver. 12.0.1f2 (32-bit)
MAX Ver. 5.4.0f0
Tried to run my VI I was working on day before... obviously, if it's not seeing the cDAQ then it can't get data... ran MAX and it still shows up on the list, but doesn't' register as being hooked up. I tried powering it down and back up, rebooted computer, restarted LabVIEW, unhooked the unit from the hub it's normally hooked to and retried everything above with it plugged directly into my laptop.... nada.
I'm at a bit of a loss here. Anyone have any suggestions? I'm going to take the laptop over to my other systems and see if it recognizes any of them.
Thanks!
Chad

Kyle,
Yes, I have taken the hub out of the equation. Correct, I have plugged this laptop into my other control pannels that are running cDAQ's and they are not recognized either.
Other computers question... I have two laptops that I use in lab, the one currently in question (call it laptop1) was working fine until I ran the suggested updates on it... SP1, and some others and that brings us to where we are now. My other laptop (laptop2) was working fine until I started running the suggested updates on it, and now it's doing the same thing.
FYI, I have a support ticket open with NI, (Ref#-7383377).... Leah, has had me uninstall the DAQmx drivers and install the newer drivers... still no recognition in MAX and now my computer doesn't chime when I plug in the unit directly.
Nor does the cDAQ show up in the device manager anywhere.
Tried something....
I have a spare cDAQ that hasn't been used yet.. I plugged it in and it seem to recognize it until I ran MAX and it doesn't show up in there either. It did chime when I plugged it in, and it told me it was installing drivers.... Seemed to work for a second, but now it's telling me that it's an "Unknown Device" under the Universal Serial Buss controllers.
Still no joy in the device manager with my original cDAQ. I plugged in the spare, it did it's thing... I unplugged it, and plugged the original back in, I got a chime, but no recognition... after that, no more chimes and doesn't show up in the Device Mngr at all.
Other ideas?
Thanks!
Chad

Slow LabView 2013

Hi
I have Labview 2013 Professional Dev Sys SP1 ver 13.0.1f2 (32-Bit) and it is slow when I develop any aplication.
For example, if I have a tab control and I change to another tab, it takes about 2 seconds to change tab after I click it.
If i wire a new line, it takes 2 seconds to appear that line in block diagram, and so on.
I have a new computer Dell Optiplex 7010, i7 Processor 3.40Ghz, 64-Bit, 4Gb RAM, WIndows 7 enterprice SP1
If i run Windows task manager it shows 17% CPU usage and 2.14 GB Memory.
If I run for example, excel 2013 it does not seems slow.
Do you have any suggestions ?
Regards
Solved!
Go to Solution.

EDGAR_PLATRONICS wrote:
Hi Yamaeda:
I am not sure about mass compile. You mean rewrite code ? Or create exe file and test?
A this moment I have checked with only one Vi but it is very large. Many sub VIs and code.
Actually it worked correctly in labview 8.5 but i converted to LV 2013.
I will research about transparent borders overlapping.
Hi Altenbach:
17% is overall. 3 cores are high % than others.
The problem is at edit mode and also when I run program.
Yes I have many front panel indicators, but I do not think they have tons of data but I will double check.
When I open my VI in labview it shows 118 MB memory when running and 124MB at edit mode
By the way, last week when by mistake I moved a part of code to some centimeters below, block diagram was frozen and was been updated to new position but line by line until complete full screen. I took about 5 minutes to work normally.
I am using 2 monitors in my PC. One to display LV panel and one for LV code.
I meant Tools -> Advanced -> Mass compile and recompile your upgraded code. In the same manner a ctrl+run array will force recompile your program. It can help. Else you're down to e.g. using VI analyzer tool to find the culprit, it might be some VI that's corrupted and needs to be moved to a new VI.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

XYGraph Cursor legend bug instantly crashes LabView 2012

Hi!
I am just facing a very annoying bug.
Please find my example VI attached, I would like to know wheather you can confirm the bug? Run the VI if you wish to see some curve (actually the bug appears even if you do not put any data on the graph, if you do, just the same) and after that try to click on the cursor legend vertical scrollbar to scroll up or down to see the cursor names.
It instantly crashes my LabView 2012 Full version: 12.0.1f2 (32-bit). This XYGraph always crashes LabView... I cannot go on with my project, now I will just try to bypass the error, I will try to delete the cursors, and add them again...
Anyhow, very strange and annoying behaviour...
Anyone could repeat the same bug?
Thanks for support!
Solved!
Go to Solution.
Attachments:
XYGraph_bug_test1.vi ‏149 KB

hello,
please find attached my example VI, where I would like to programmatically set the label position of a cursor. Why my code does create at every run a new cursor with the same name?
thanks!
Attachments:
cursor_offset_label_via_propertynode.vi ‏12 KB

How to update NIDAQmx driver in Labview RT?

Dear members,
I have a problem to make my NI PCI 6289 card working in Labview RT.
Namely when I run the self test appears an error number -88716.
The screenshot says that the NIDAQmx drivers on the host and on the target are different.
It suggests to update the driver to correct the error.
Now I have checked. On the host I have the NIDAQmx8.5.1f2 driver on the RT target the NIDAQmx8.5.1.
The question I want to ask is. How can I update the driver on the RT target to the other version?
Since I have installed the RT system just yesterday I can't imagine that I have done some updates on the host which are not done on the target.
Someone has an idea how to override the error?
Thanks
Principiant
Solved!
Go to Solution.

The NI support solved my problem here is the link with the solution.
http://digital.ni.com/public.nsf/allkb/A47734CC1E03922186257435004D0C49?OpenDocument
In the download page, just download the first link NIDAQmx 8.7.1 not the runtimes at the end of the page.
Thanks for the help .
Bye
Principiant

Open and close multisim contact with LabVIEW

Can I open and close multisim contact with labview and read the receptor estatus (p.e. lamp)?
Thanks.
Attachments:
Dibujo.JPG ‏13 KB

Hi Guddan,
I created a RFC having a query which is taking a long time to execute. So i want to close RFC connection with portals which is via java connector(JCO) before that query and open the connction again after that query.
I guess i will need to understand your requirement a little more in detail, as i understand you have an RFC which has a query within to fetch some data and is taking a long time to do so. In the meantime you don't want to keep the connection open?
My question would be, Is the role of this RFC to only execute the query and fetch the data or does it do something else?
If it does other things and these are independent of the query execution, then you can span a parallel call within the RFC to execute the query and in the meantime the RFC does the other things (or vice versa) hence reducing the overall time taken.
If the sole purpose of this RFC is to execute the query, then you will not be able(i mean to say there is no simple and direct way of doing this) to close the connection after the Query is started and re-establish the connection after its execution, for a simple reason that - how will you know if the query has completed it's execution, so that you can establish the connection back.
Alternate solutions, make this a two way asynchronous call, 1) You invoke the RFC asynchronously and close the connection, the RFC in turn will execute the query and transfer the data to JCO via another RFC call.
If this needs to be a synchronous call, then you will need to optimize the query to its best.
Regards,
Chen

LabView Exe Application file not launch Excel application for report generation

Dear All,
I created one LabVIEW application file for report generation (using Excel Template).
While I run the program in programming mode it works well and create the report file in the specified path.
After creation of the application file(exe), it gives the correct path of where the excel template is placed. The same path is given to New Report.vi, but it gives the error 'File Not Found'.
Tell me, is any other configuration required for generating Excel reports? (During exe application mode)
Give me the solution.
Thank You
Jegan.

Hello,
Most likely you are encountering a problem of stripping and/or building paths. Probably the easiest thing to do is put a couple indicators on your front panel for the path or paths you care about, build your exe, and make sure you are really using the path you'd like. If you always put the report at some deterministic place relative to the exe (that is, even it the exe is moved, it will go with the exe and remain in the same relative path location, then you can use the Current VIs Path funtion found in the ... File I/O -> File Constants palette as a start path (where you will want to strip at least the exe name off of course).
I think this will bring some clarity to the issue!
Best Regards,
JLS
Best,
JLS
Sixclear

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

Why do I get "The exception Privileged instruction (0xc0000096) occured in the application" error message when exiting LabVIEW 6.1?

I have created a vi that uses the LV-GPIB and database connectivity vis. The program runs fine and it ends execution by running the "Close Database Connection.vi".
After closing out my front panel windows and exiting LabVIEW 6.1, I get an error dialog box that reads the message "The exception Privileged instruction (0xc0000096) occured in the application". What does this error mean and how do I resolve it?
Thanks,
Taf

Hi Taf,
Given the broad scope of your application, it may be best to try and isolate the problem down by taking out parts of your application and simplifying it down as much as possible until you can get a consistent version that throws this exception. I would first try to take out either the GPIB or database connectivity portions of the application to narrow down our problem. This error generally occurs when accessing DLLs and external applications, so I wouldn't be surprised if it's the GPIB or database. Let's try to see exactly which one it is and then we can dig deeper into that part of the code. Thanks for your cooperation!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

Labview 12.0 to Labview 11.0..1f2

Similar Messages

Maybe you are looking for