Change version of LabVIEW RT

i've installed LV Real time version 9.0 in a PXI8108 controller in a PXI1000B chassis. i need to down rev it to 8.6. in the Measure snd Automation explorer, when i do add/remove software, select labVIEW Real-Time 9.0, the Available versions on the host only lists 9.0.\
i have a desktop on the same network also running LV Real time 9.0. when i select that one, i get a choice of 8.6 and 9.0 in the drop down for available versions on the host.
any ideas?

There should not be any dependency issues with installing LabVIEW 8.6. I have attached a link for installing LabVIEW RT using a USB stick. Give that a try and post back if you run into any problems.
Using Desktop PCs as RT Targets with the Real-Time Module
http://www.ni.com/pdf/manuals/371857f.pdf
Nick Keel
Applications Engineering
National Instruments
Nick Keel
Product Manager - NI VeriStand and Model Interface Toolkit
National Instruments

Similar Messages

Could there be independent VI paths for different versions of LabVIEW?

Hello,
When jumping between different versions of LabVIEW (6.1, 7.1, 8.5) it is annoying that the current path for one becomes the current path for the other.
If I am working with LV 7.1 in a folder dedicated to 7.1 VI's, and then open LV 8.5, I don't want 8.5 to go to that 7.1 folder by default. Alternately. if I was working in LV 8.5, closed it out, and then I click on a 7.1 VI, I don't want it to open in LV 8.5.
I've tried changing the path options in each version of LabVIEW, but that doesn't seem to help. Is there any way of isolating these folder paths from one another? One of our newer LV guys accidently opened some 7.1 code in 8.5.1 and then saved it. Luckily, I had archived code to return to, but it could have been a disaster.
Thanks for any ideas,
McSynth

You're actually asking two different questions.
The first question has to do with which version of LabVIEW gets launched when you double-click a file. This is an operating system thing. The one that gets launched is the last one that got used. (Your first question will be: can this be changed? Answer: Change the operating system. Or, play around with the registry each time you quit out LabVIEW.)
The second question has to do with search paths. These are independent. However, a VI will contain information about its subVIs in terms of where to find them. This is not a function of LabVIEW, as it is a function of the VI. Thus, it will make no difference which version of LabVIEW you use to open the VI. You can, if you wish, modify the search paths that LabVIEW uses to find VIs for each version of LabVIEW from the Tools->Options menu. However, this will not eliminate the problem, and your best bet is to keep those backups frequent.

Identifying and Converting from an older version of LabVIEW

I have an old .vi program that I am trying to access and run now. I don't know what version of LabView it was written in but I do know it came off of a Windows 95 computer.
Any Suggestions?
Will Huntley
Solved!
Go to Solution.

You said "trying to". Does that mean you've been unsuccessful? On what OS are you trying to run it?
When you open an old VI in a newer version of LabVIEW, if the VI isn't too old, then it will open. If you close the VI you'll get a dialog asking you to save it. The "explain changes" will tell you the version of LabVIEW used to write the VI.
If you cannot open the VI because it's too old, and your LabVIEW is too new (e.g., opening a LabVIEW 5.x VI with LV2011), then you can post a request in the Version Conversion board. If the code is really old (e.g., LabVIEW 3.x or earlier), chances are you will not be able to get it upconverted since versions that old require a special toolkit from NI that is not publicly available.
EDIT: Duplicate answer. Was creating my response while Dennis posted his.

Is there a way to programmatically tell what version of LabVIEW a VI is compiled in?

Is there a way to tell programmatically what version of LabVIEW a VI is compiled in?
LabVIEW seems to know. If you click on "List Unsaved Changes", it (sometimes?) tells you the version of LabVIEW that the VI is already saved under (i.e., 8.0 instead of 8.0.1). So if LabVIEW knows, maybe they've provided a way for us lower-echelon folks (i.e., customers) to know too, eh?
Is there a way to get this from, say, VI Properties (i.e., Property Node gets passed a ref to a VI & I select the right property name)? I couldn't find any property name that has "version" or anything like that, but maybe what I'm looking for is using terms that are so different than what I'm expecting that I just can't tell.
Or by some other method? (I gvimmed a few .vi files, and see some stuff that looks like I *could* get the version by parsing/searching the file itself, but parsing the binary might give pretty unreliable results.)

Just dro a proerty node on the diagram and select property: "Application...Version number" and display the resulting string output.
Message Edited by altenbach on 07-02-2006 11:33 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
version.png ‏9 KB

Is it possible to open a VI using an older version of LabVIEW, and if so how?

As stated in the title. I have installed all the run-times from lv6 to lv8.6, but cannot open any VIs that have been compiled in a more recent version of LabVIEW. We run (on different computers) lv5, lv6.1, and lv8.5. Upgrading some of the older machines is not possible since they cannot handle the required OS.
Is there any way to open a VI created/compiled in a higher version of LabVIEW? This is proving to be a major sticking point with us and our ability to transfer VIs between computers.
James
Never say "Oops." Always say "Ah, interesting!"

Hi James,
I was able to use VI server to invoke LV 6.1 VI's using LV 7.0 without issue.
After discovering this and mentioning it in a post somewhere, Rolf Kalbermatter indicated that was expected. and I should not be suprised.
So....
Vi Server may help you.
James Mamakos wrote:
Is there a separate place for me to post VIs to be converted? What's a ballpark figure for the maximum file size i could put on to be converted?
Do you know if the LabVIEW developers can/will create a way to overcome this problem rather than having to convert a VI through all the intermediate versions?
To the best of knowledge NO.
For each versino of LV there isw code included that runs behind the scenes when you open a VI from an earleir version which replaces old functions with the new versions. This is called Mutation code. To accomplish its task it has to know everything that changed between version X and Y. Since it is possible to baby step the versions up and the number of user that jump multiple major versions is small, I don't think any effort will go into that work.
THe largest attachment I have managed to upload was 3 or 4 Meg.
Just trying to help,
Ben
Message Edited by Ben on 04-28-2009 08:58 AM
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

"VI has error of type 1002288.The full development version of LabVIEW is required to fix the errors"

Hi,
I had created an executable in LabVIEW 8.6 on a windows XP 32 bit PC. The application uses some Vision VIs. The executable runs in most of the PCs except one. the PC is a windows 7 64bit. Initially i got the error "Labview Load error code 3: could not load front panel". I fixed this by changing the source file settings in the application builder. Now i am getting the error "VI has error of type 1002288.The full development version of LabVIEW is required to fix the errors" and the exe shows a broken run button.
But if i build the exe in the same PC i get no errors and it works fine. Moreover i have tested this exe in a different PC with the same configuration, it works there. I have tried reinstalling labview in the PC the problem still persists.
Solved!
Go to Solution.

Hi Rajshekar.
> Which version of LabVIEW are you using on PC with Win7 64bit? would like to check if there are any issues with LV2009 32bit on 64bit OS..
- The version of Labview on the win7 64bit PC is also lv8.6 full development system.
> Do you get the same error on the other PC with same config(Win7) when running the .exe generated using LV 8.6 on WinXP 32bit? just to make sure the problem is with OS or LV..
- the same problem occured at one more PC with the same configuration. but when i tested in an another PC of the same config it worked i am not able to isolate and decide that the error is based on one particular PC config.
I have listed the environments in which application ran and how the application was put in to the PC.
I would also like you to know that i have created an installer for the exe. I am also using NI vision in my application and this is the error "An error occured loading VI 'IMAQ GetImagePixelPtr'. LabVIEW load error code 3: could not load front panel"....and rest is what i said in my previous post
1. Use the installer to install the application.
2. just copy the exe created in LV 8.6 into a PC that already has LV development system installed in it
3. The PCs might either be a blank one with no history of LV installed in them
4. The PCs might have diffrent versions of LV development systems installed in them (8.2,8.5,8.6,2009)
All PCs that have LV development system(s) installed in them, was able to run the application except the one with win7 64, where i have tried uninstalling all NI software and use only the installer to install, install LV 8.6 full development system and try runnning the exe, nothing works.
Thanks

Event structures in older versions of labview?

Can anyone tell me how to create a workaround for a 'value change' event structure in an older version of labview? I have a student version of LabVIEW 6i and need to create a queued buffer from each value change. Thank you.

James.Morris wrote:
Ah, you're only one release away from the event structure. That's too bad.
You're going to have to implement a Polling loop that continuously checks the user inputs. Make sure you add a Wait function to the loop (~100ms) because that will act as your chance for the user to make changes. You can use shift register(s) to keep the previous loop's values and compare to get a bunch of Value Change booleans. If you want a specific case for the specific events, then you can group all of your Value Changes in to an array and act upon the ones that are True via a Case Structure.
The Event Structure only pulls a single event per loop and has a queue of events to handle for following loops. You might encounter multiple value changes in a single loop if the user clicks fast enough, or you trigger value changes. To avoid losing the trailing events, you should probably have a For loop within the Polling loop that handles all True values. Either that, or have a consumer loop that handles all of your events.
James, I swear I'm not picking on you today
You can set the maximum number of events alowed in the event queue per event in the edit event dialog box. Check box and int fields in the lower right side.
6.i didn't have a "Value (Signaling)" property- (a subject of some CLAD exam questions not that you suggested it)
Student editions could not use 6.i events. From 7.0 or 7.1 through 2011 Student Edition could use but not edit event structures. 2012 and on Event Structures are available in "All Versions" of LabVIEW- at the time. I haven't looked into the newer license options.
On to licensing options. (Not a lawyer! consult your Legal Dept!)
If you are not doing work towards earning a educational certificate you should not be using Student Edition. And, in some cases (Like working on a student project with commercial investment) not even then!
The Home Edition is also a new option. It is intended to enable fast "Proof of Concept" development or development for your sole non-comercial use.
LabVIEW Full and Professional are for comercial use and have a "Home Use License Agreement" clause attached. If your company owns a LabVIEW License you CAN install a copy on a "Home PC" for the limited use of aiding your employer (who paid for the license) such things would arguably enclude "Training"
NI is not totally opposed to negotiating "Exceptional" agreements for mutually beneficial reasons. Youl'd better bring a justification better than "I can't afford it" Go find some investors and buy a license in that case. And Yes, until the moderators take this down, I did at one time have a LabVIEW license for exclusively engaging the LabVIEW Community (Forums and NI Sponsored events use only- LAVA was not encluded) I'm not sure if such a deal could be negotiated in the future. In Fact, The Home Edition would have been less costly.

Upgrading to latest versions of labview development software, drivers, engines

What is the best way to upgrade to a newer version of labview and drivers, but still maintain support for projects created and deployed with older software, drivers and deployment engines? If I have to make changes to an existing project and then deploy them to a controller or create an exe application, I seem to always have some issues when I have to update drives and deployment engines. Problem is I would really like to ulilize the newest software and drivers but the conversion of projects created in older version seems to be such a hassle. Any suggestions on the best way to do this would be helpful. I can offer more details if needed.

The most sure way I have found is to dedicate a PC to the LV version. I have a PC for 6.1, and one for 7.0/7.1. I do
develop with 7.1 and 8.2.1 on my laptop, but the 7.1 is only straight LV, no drivers to speak of.
Some pertinent threads:
http://forums.ni.com/ni/board/message?board.id=170&message.id=288055#M288055
http://forums.ni.com/ni/board/message?board.id=170&message.id=248018#M248018
Matt

Will hardware drivers work with the run-time engine or only a full version of Labview?

Hello.
I'm trying to get a quatech I/O card to work. The instructions with the drivers we were given state "you must have labview installed before installing these drivers".
A program I wrote on my machine works fine with those drivers and does toggle outputs on the card, but when I build it into an executable on our test unit (doesn't have a full version of Labview, just the Run-Time engine) the card doesn't work.
We installed the run-time engine on the unit, then the drivers.
I guess my question is: Do most drivers work with both the full version of Labview and the run-time engine? Or do I need to somehow 'convert' these drivers to work with the run-time engine?
Th
anks for your help!
Dave Neumann
[email protected]

Dave:
I can't determine which dll is required but if there are more than one that
shipped with the quatech I/O card try to placing one dll at a time in the
same directory as the exe so that you can determine which one is the
required one. If that doesn't do it then it may need more than jsut one of
the dlls so placing all that came with the quatech I/O card s/w driver
package in the same directory as the exe should do the trick.
Best of luck.
-Tom
"Neumannium" wrote in message
news:[email protected]..
> Tom,
>
> Thanks for your reply. One of the problems I'm having is figuring out
> which .dll I would need to include (I'm not a software guy).
>
> Would the .dll your speaking of be different th
an the one which is
> installed with the drivers? I'm looking at a .dll that is installed
> when you install the labview drivers for this card, but the run-time
> engine still doesn't want to get the card to work. (The file installed
> when I install the drivers is called 'daqlv32.dll' and I don't know
> how to find any other .dll's I might need)
>
> Actually, it appears the card 'is' being seen by the run-time engine,
> but I'm getting impulses rather than distinct changes of state.
>
> Anyway, thanks for the help.
>
> Dave Neumann
> [email protected]

I recieve the following error when running an executable ("This VI is not Executable. The full development version of Labview is required to fix the errors"

I recieve the following error when trying to build and run a labview executable. I am able to build the executable but when trying to run the executable, a pop up window comes up asking the user to select a dll. (please see screen shot attached). Once the DLL is selected, I get the error that This VI is not Executable. The full development version of Labview is required to fix the errors. (please see screen shot attached). I have also attached a snapshot of the project window.
I have the professional development system
I can run the main VI
all the required DLL's are in the dependencies section of the project window.
I am trying to find the root cause of this error but to no avail. can anyone give me a clue to what i am missing here. Any suggestions on where i should look to find the problem ?
Thanks in advance to all labview users for your help
Attachments:
project window.PNG ‏36 KB

other PNG
Attachments:
Broken Arrow on EXE.PNG ‏179 KB

Multiple versions of labview on 1 computer

Hello,
I have just purchased LV 8.2 and am about to install it on my computer. The old version of LV I currently have on my computer is 7.1. Can I run both versions on the same computer or is it beneficial to take off LV 7.1 first before installing the new 8.2. Any opinions?
Azazal
Azazel
Pentium 4, 3.6GHz, 2 GB Ram, Labview 8.5, Windows XP, PXI-5122, PCI-6259, PCI-6115

Azazal,
You can certainly run both versions on the same computer. I have 6.1, 7.1, 8.0, and 8.20 installed on this machine and I regularly have more than one version open at the same time.
However, Paulo is very correct by saying that toolkits typically only install for one version of LabVIEW and that you need to be careful not to open your VIs in the wrong version of LabVIEW. If you were to open and save a LabVIEW 7.1 VI in 8.20 you would be unable to open it again in 7.1.
Matt, great links - I'm going to repeat that first one here in clickable form:
Installing Toolkits for Use with Multiple Versions of LabVIEW
Regards,
Simon H
Applications Engineer
National Instruments
http://www.ni.com/support

How to delete an active change version of a PO?

Hi all mates,
question: given a PO number, assuming that the active version is a change one and the previous version has been ordered (I don't know if this is the proper word: I mean "transferred to the backend" (R/3))... is there a simple way, e.g, a FM, to delete the last version of a PO, so that this goes definitely lost and the previous version is restored and set to active?
As usual, thanks in advance
Matteo
EDIT:
after reading a bit, I'd like to add further details:
- what I call a "change version" is actually a new version of the purchase order which is in status "HELD";
- 'transferred to the backend' -> the current version of the purchase order is in status "ORDERED".
Then, if i click on the "version" tab in SRM, i can see that an order modified after distribution has a previous version (status "ORDERED") and a current version (in status "HELD").
I'd like to know if there's a way to delete the current active version and restore the previous, ORDERED version. The question arises because I'm creating a report that makes an update of a Purchase order, but to do so the order must be in status 'ORDERED' so if an HELD version is active I should "rollback" to the previous one... or alternatively, I must manage overwriting the HELD version currently active ( I wasted a lot of time but I wasn't able to do it ).
Edited by: Matteo Montalto on Apr 8, 2009 12:45 PM

Hi, I have the same problem. Can you tell me the solution that you have find ??

PDO Layer Error while approving a changed version of PO

Hi,
We are in SRM7.0 , EC Scenario , ECC 6.0
In SAP SRM system am experiencing a workflow issue , second level approver is not able to approve/receive the workitem of a changed PO. Moment we try to open the PO (changed version) and navigate to Approval tab, the approval flow is missing and showing the error as
PDO Layer Error
An Exception has occured
Every time we must restart the workflow due to which the approval needs to be done again from 1st approver.
We have raised an OSS Message and following is the response from SAP
" The second approver does not get an workitem because the workflow got the status error. The cause of this error is your BADI implementation
ZCL_SRMWF_AGENT_PO_BUYER method /SAPSRM/IF_EX_WF_RESP_RESOLVER~GET_AREA_TO_ITEM_MAP. This method returns an initial table LT_AREA_TO_ITEM_MAP.
Run method CREATE_DECISION_SETS (/SAPSRM/CL_WF_PROCESS_MGR_SBWF) with
parameter IV_PROCESS_GUID = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx "
When i executed this method CREATE_DECISION_SETS (/SAPSRM/CL_WF_PROCESS_MGR_SBWF) with
parameter IV_PROCESS_GUID = Changed version PO GUID , i got the following error
Exception CX_BO_ABORT triggered
Termination triggered in '' - Rollback required
Can anyone please help !!
Thanks & Regards,
Venkat

Hi ,
can you please share your Badi code?
Saravanan

Can NI-PSP be used to communicate between machines developed with different versions of LabVIEW?

Hi all,
A customer has a large PC application developed with LabVIEW 2010 SP1.
They would like to add extend their system with a cRIO-9075. According to this document (ftp://ftp.ni.com/pub/devzone/tut/crio_software_versions.htm ), the minimum supported version of LabVIEW (with Scan Engine support) is LV 2011.
To minimize risks, it is preferred that we don't upgrade LabVIEW for the main application, which is atively being used in production.
I was thinking of developing the cRIO software in a newer version of LabVIEW (say, LV 2013 SP1), and using shared variables only to communicate between the PC and the cRIO.
Is this a viable option? Does it matter if the PC and the cRIO have different versions of the LV runtime?

It shouldn't matter, but then with shared variables you can never know for sure -- there are so many things that can make them break.
You might be money ahead to write the comm using TCP/IP. You know that will work.
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

Buffer Table Not Up To Date Short Dump When Publishing Change Version of Bid Invitation

Hi experts,
We are running SRM 5.5 with Support Level 16.
We have a bid invitation for which a user is trying to publish a Change Version. This bid contains two bid outlines, with one line item in each bid outline:
ITEM 1: HIER (Bid Outline)
ITEM 2: Line Item
ITEM 3: HIER (Bid Outline)
ITEM 4: Line Item
However, upon clicking on the Check or Publish button, the system throws a CX_BBP_PD_ABORT exception short dump. The reason for the exception given in ST22 is "Buffer table not up to date".
Due to organisational system security restrictions, I am unable to copy-paste the dump from ST22, so I will be typing out some of the details here.
Transaction: BBP_BID_INV
Program: SAPLBBP_PDH
Screen: SAPLBBP_BID_INV_1000
Termination occurred in the ABAP program "SAPLBBP_PDH" - in "BBP_PD_ABORT". The main program was "SAPLBBP_BID_INV".
In the source code you have the termination point in line 73.
Active Calls/Events
(formatted below as "No: Type: Name")
24: Function: BBP_PD_ABORT
23: Form: ABORT
22: Form: ITMADM_UPDATE
21: Form: ITMADM_MAINTAIN_SINGLE
20: Form: ITEM_F_CHECK_FROM_WTAB
19: Form: ITEMLIST_F_CHECK
18: Function: BBP_ITEMLIST_CHECK
17: Form: PROCDOC_DB_CHECK
16: Form: PROCDOC_CHECK
15: Function: BBP_PROCDOC_CHECK
14: Form: SSIS_DOCUMENT_CHECK_COMPLETE
13: Form: STATUS_SET_AND_INTERNAL_SAVE
12: Form: PROCDOC_UPDATE
11: Function: BBP_PROCDOC_UPDATE
10: Form: CHANGE_VERSION_UPDATES_ACTIVE
9: Function: BBP_PDCV_UPDATE_ACTIVE
8: Form: PROCDOC_CHECK
7: Function: BBP_PROCDOC_CHECK
6: Function: BBP_PD_BID_CHECK
5: Form: FCODE_DOCUMENT_CHECK
4: Form: FCODE
3: Function: BBP_BID_PROCESS
2: Form: PROCESS
1: Module (PAI): PROCESS
The ABORT subroutine is being called in Step 22 (ITMADM_UPDATE), at the following line:
* parent guids have to be identical ...
if gt_itmadm-parent <> w_itmadm-parent.
perform abort.
endif.
Upon tracing the variable values in the ST22 dump, it appears the program terminates when processing line 3 (i.e. the second Bid Outline). It appears that the first Bid Outline processes fine.
In the iteration for Line 3, the dump provides that gt_itmadm-parent contains the GUID to the Change Version document header, whereas w_itmadm-parent contains the GUID to the original Bid Invitation document header, resulting in a mismatch and subsequently program termination.
We have tried to replicate this bid invitation in our Development environment, but when executing, both gt_itmadm-parent and w_itmadm-parent contain GUIDs to the Change Version document header, hence the program does not abort.
Any suggestions would be greatly appreciated.
Thanks!
Best regards,
Kwong How

Hi Janu,
For Note 1561750, I have looked at the Correction Details and observed that it makes changes to an IF-ELSE block, but will result in the same path of code execution as before. I.e., the Note changes the code from "IF a THEN b, ELSE c" to just "c", but according to my code trace, we are already executing the "ELSE c" block in its current state.
We will look further into Note 1877600. The unfortunate situation here is that since we are unable to replicate this issue in our Development/QA environment, and the Note description does not explicitly fit the situation we are facing, we need to be very sure that the Note can address the issue before bringing it into Production.
Otherwise, we will raise a message as suggested.
Thank you so much for your help!
Best regards,
Kwong How

Change version of LabVIEW RT

Similar Messages

Maybe you are looking for