SCC with different LabVIEW versions

Hi. I have many different projects, and some of them are in older versions of LabVIEW. I was wondering if there is support and what kind of support there is for older versions in the SCC tools of LabVIEW 6.1

We don't offer any cross versions tools for the source code control because VIs are generally saved in the LabVIEW version in which they were edited. If you want to use SCC with a project in an older version of LabVIEW, we recommend checking the files out of the master directory into the local, opening the VIs from the old local with LabVIEW 6.1, saving, and putting the VIs in a new project with the 6.1 SCC. This way you leave the old master directory intact for backup purposes.
Jeremy Braden
National Instruments

Similar Messages

Vi server compatibility with different Labview version

I have to PC => one with Labview 5.1 and the other with labview 6.0
Is it possible to launch through vi server application a vi on the PC 1.
The server applicationis written in labview 6.0 and the client application with labview 5.1

LV 6.0 through LV 7.1 should be OK.
Before 5.1 and 8.0 and up, I can not speak to.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Setup Central Contract Management SRM 7.01 with differing release versions

Hello experts,
OSS note 1268821 explains how to configure the central contract management between a SRM 7.0 and an ERP 6.04. So far so good, but how should it be handled if there are differing release versions such as ERP 6.04 and ERP 6.03? I guess that a technical split (xml services/ ALE distribution) is necessary?
Assuming that there are some backends with differing release versions and in some cases with differing master data (not supported by central master data client) would you always go via PI? Independent of release version, technology and master data.
Could you give some further detailed informations how to configure such a scenario? What has to be done to transfer existing contracts from an ERP 6.04 into SRM CM component (migration concept)?
Thanks!!!
KR Thorsten

Hi Thorsten
The minimal ECC version is 6.0 EHP4, Central Contracts require certain business functions in ECC to be activated and as these are included within ECC EHP4 you won't have these available in lower version. Therefore you won't be able to operate central contracts in such an ECC system.
You would either have to go with patching these systems or go with GOA's for these systems.
Operating central contracts via PI or SOA i believe provide almost similar functionality. SOA however requires an SRM EHP1 system and ECC EHP5 back-end to operate whilst central contracts configured via PI can be operated onwards from an SRM 7.0 and EHP4 system.
I can't help you on your migration issue, maybe someone else can.
Kind regards,
Tim

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

Live Migration with Different CPU versions on the hosts, win 2012R2 Datacenter

Hello
This question have been asked in different forums but when I read the the thread's I feel that I get mixed answers.
And most answers are dating from 2012 (Win 2008R2), I don't know if they are still correct in win 2012R2.
So now I ask the question myself and hope to get at clear answer :)
We are in the process of installing a new Hyper-V cluster using Win srv 2012 R2 Datacenter as OS.
I'm planning to re-use some of the "old" servers from our current Hyper-V 2008 R2 cluster, removing it from the cluster and do a clean installation of 2012R2 Datacenter.
But I will need to buy two new servers to manage this (with a new version of CPU, same brand (AMD))
Old server: AMD Opteron(tm) Processor 6172 (12 Cores)
New server:
AMD Opteron™ 6344 (12-core)
Now my question:
Will Live Migration work between these servers in my new cluster without me doing any special settings in hyper-v or in the VM or what do I need to do to get this to work?
/Anders

Hi,
It is important that all the hardware supporting Windows Server 2012 Failover Clusters be certified to work with Windows Server 2012.
In a cluster where all the nodes of the cluster are exactly the same, hardware migration is fairly straightforward. There are no concerns about differences in hardware, and
especially no concerns about different capabilities of the CPUs.
More information:
When to Use Processor Compatibility Mode to Migrate Virtual Machines
http://technet.microsoft.com/en-us/magazine/gg299590.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

CK24 - mark and release with different costing version

Hi,
We are currently using standard costing variant PPC1 and costing version 1 to mark and release the standard costs. However when we try to recost the material cost due to price changes, system does not allow to mark & release revised standard cost if we try to mark & release on same day. pls note standard cost estimate is already released for the month. And we do not want to delete existing standard cost estimate. Instead we want to explore other options. We are using 4.7.
My questions are :
a) Can recost using costing version 2? CK11N allows to save the costing result. However in CK24 Marking allowance, system does not allow to change Costing Version. is there any config option to change this.
b) If we cannot use different cost version, can we update material cost with same costing variant (PPC1) and costing version (1) in this case. However when we tried to do recost with same costing variant & verison on same day, system gives an error 'Material AAAA in plant MMM has a released cost estimate.'
Any inputs on above issue highly appreciated.
thanks
Sunil

Hi,
While, you can use any of the Costing versions to mark & release Standard cost estimate, you can release Cost estimate only once in a fiscal period. If you want to release correct prices, then you have delete existing released cost estimates using CKR1 transaction and then re-run CK40N to release.
Hope this helps.

Shared Listener with different oracle versions

Hi,
I have configured the following shared listener for two databases running with different versions.
I have started the O02TXN3-9i along with the shared listener and then listener was started with 9i version and then I brought up the O01TXN3 -10g.
Please let me know whether I can connect to the 10g database O01TXN3 remotely with shared listener.
Note: Please find listener and oratab files below.
Your early response is much appreciated.
Database O01TXN3 with 10g
Database O02TXN3 with 9i
==== Listener.ora File ======
TNS_DTXN03 =
(ADDRESS_LIST =
(ADDRESS=
(PROTOCOL=IPC)
(KEY= O01TXN3.world)
(ADDRESS=
(PROTOCOL=IPC)
(KEY= O01TXN3)
(ADDRESS=
(PROTOCOL=IPC)
(KEY= O02TXN3.world)
(ADDRESS=
(PROTOCOL=IPC)
(KEY= O02TXN3)
(ADDRESS =
(COMMUNITY = tcpcom)
(PROTOCOL = TCP)
(Host = dtxn03)
(Port = 1525)
STARTUP_WAIT_TIME_TNS_DTXN03 = 0
CONNECT_TIMEOUT_TNS_DTXN03 = 10
LOG_DIRECTORY_TNS_DTXN03 =/dtxn03/txn/oracle/admin
TRACE_LEVEL_TNS_DTXN03 = OFF
SID_LIST_TNS_DTXN03 =
(SID_LIST =
(SID_DESC =
(SID_NAME = O01TXN3)
(ORACLE_HOME = /dtxn03/txn/oracle/10.2.0-64)
(SID_DESC =
(SID_NAME = O02TXN3)
(ORACLE_HOME = /dtxn03/txn/oracle/9.2.0-64)
# Added to get rid of the "inbound connection timed out (ORA-3136)"
INBOUND_CONNECT_TIMEOUT_TNS_DTXN03 = 180
==
Oratab:
#LISTENER:/dtxn03/txn/oracle/9.2.0-64
O01TXN3:/dtxn03/txn/oracle/10.2.0-64:Y
O02TXN3:/dtxn03/txn/oracle/9.2.0-64:Y

As a general rule, only one listener is required for a machine as long as all database versions are currently supported. (In other words one listener for Oracle7 and Oracle11g will not work.)
As a general rule, an old listener MAY not be able to handle the features of the newer database (such as transferring blobs was a limitation in Oracle8). Therefore use the newest listener to handle all the databases.
As a general rule, listeners can be considered independent of databases in a sense similar as ASM. Therefore it's not a bad idea to have a separate ORACLE_HOME specifically to install the listener. This is especially useful if you have multiple databases with differing service level agreements,
I'd want to see
1) the output of lsnrctl status
2) any console session stuff and copy/paste to be surrounded by preview tages as described in the FAQ (http://www.oracle.com/technology/forums/faq.html#q14)

Access two EAS with different Essbase versions and different java versions from the same p.c.

Hi,
I need to regularly access Essbase 11.1.2.2. and Essbase 11.1.2.3 EAS from the same client machine.
They are on, and must be on, different versions of java, is there a way to have both versions of java installed but each using the correct version and without the two java versions causing any kind of problems?
thanks,
Robert.

Hi Robert... I assume this is web-launched?
I spent a day or so trying understand the intricacies of the JNLP protocol and create shortcuts that will invoke web-launched EAS with the appropriate version of Java. I can get one version of EAS to use the 1.6 Java Web Launcher, and the other version of EAS to use the 1.7 Java Web Launcher - but both Web Launchers eventually invoke the same version of Java! There are switches in the JNLP syntax that seem like they should allow you choose the actual Java version that gets invoked, but I just could not make it work.
You can use the Java Control Panel (in Control Panel) to enable and disable the relevant versions before launching EAS.
If you find otherwise I would love to know (or if you find out how to control which versions are enabled or disabled via command-line script).

Device type file compatability with different SAP versions

Hi All,
         I need to know whether there is any difference in Device type file (.PRI) for different SAP versions [ SAP 4.6b , 4.6c, 4.7, mySAP ERP 2005.,]
         Is there any change in .pri file required when upgrading/degrading SAP versions?
        Pls let me know abt this. very urgent..

i tried the following code on a WAS 7.00 SP14 and it works as expected.
create object cached_response type cl_http_response exporting
add_c_msg = 1.
    cached_response->set_data( file_content ).
    cached_response->set_header_field( name =
if_http_header_fields=>content_type
                                       value = file_mime_type ).
    cached_response->set_status( code = 200 reason = 'OK' ).
    cached_response->server_cache_expire_rel( expires_rel = 180 ).
    call function 'GUID_CREATE'
      importing
        ev_guid_32 = guid.
    concatenate runtime->application_url '/' guid into display_url.
    cl_http_server=>server_cache_upload( url      = display_url
                                         response = cached_response ).
call method runtime->server->response->redirect( url = display_url ).
navigation->response_complete( ).

Still confused with different ABAP versions

Hi folks,
does anybody have an idea where I could possibly find a comparisson of the different ABAP versions (ABAP runtime environments) in order to find out the changes especially coming from 4.6C to the next versions SAP WAS 7.0.
Especially in ABAP Objects I expect some changes. Could anybody post a good source on that?
Thanks for your help
bye
Torsten

Not sure where to find that stuff but here is a little rundown.
One thing about classes, is that there is now the Friends tab where you can define a friends relationship to other classes
There has been quite a lot of changes to the ABAP runtime including the inclusion of a full web server and the ICF(Internet Communications Framework) This allows for such things like Web Services, BSP(Business Server Pages) and Web Dynpro.
Other things that are new are Shared Memory Objects, Persistent Objects, ABAP Units, Adobe Interactive Forms, the New Debugger, and the new ABAP Editor.
This is just to name a few.
Regards,
Rich Heilman

Costing on Internal Orders with different plan versions

Hi,
Is it possible to carry out Costing on Internal Orders using different plan versions?
I would like to carry out more than one costing on Internal Order so that I could compare different versions. Maybe there are other parameters (other than plan versions) which can be used for executing different parallel costing.
Best wishes,
Karol

Hi Karol,
In Release 3.0, the following new planning functions are available in order planning:
<b>Copy plan versions</b>
In Release 3.0, you can plan order costs for internal orders in different versions. In contrast to earlier releases, you can now
1. change versions
2. copy versions
3. Here you can select :
the planned values to be copied: annual or total values
whether the planned values in the target version are to be retained or overwritten compare versions using the information system
Planned values are not revaluated in the target version (for example, when you change the value date).
Overhead and settlements are not copied and, if required, must be repeated in the target version
Regards,
Hemachandra K S
<b>Please, donot forget to mark the answer as Helpful, Very Helpful or Problem solved.</b>

Matchcode problem with different GUI versions

We have upgraded most users to SAP GUI for Windows 640 Final Release. After this upgrade we have encountered an error in the matchcode lookups that the last character in most fields is being dropped so that when the lookup is performed it has an incomplete field for inquiry. Example:; in Sales Office we put in SO20, but when it uses this it drops the last character and performs the lookup with SO2 only.
However, SAP Frontend for Windows 620 Final release, the GUI prior to updating machines does not have the matchcode problem and works correctly.
I hope I have explained this adequately, any help is appreciated.

Hi,
I have this problem during the upgrade, I could not exactly figure it out what will be problem, but i upgrade my SAPGui frontend to 7.10 patch level 3, after that the problem found solved.
SAPGui 7.10 have backward compatiability, so it will work fine with 6.40 version
a®

Catalyst 2960s Stacking with different IOS versions

Hello Forum Team;
When adding a new switch with older ios version to an existing stack (flexstack) does the new switch will be able to join the stack?
Thanks in advanced!

Hi,
In a stack/flexstack all the switches should have exact same IOS version, otherwise there will be a version mismatch on the stack and the new switch will not be able to join the stack.
The following Document contains more info:
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps6406/white_paper_c11-578928.html
Thanks
Ankur
"Please rate the post if found useful"

Multiple License for different Labview version

A coworker is trying to tell me that he read somewhere on the NI forums or knowledge base that with a multiple license it is possible to use
the maximum number of licenses on EACH version of Labview. That is, if there are 5 licenses available that there could be 5 copies of 8.5 and 5 copies of 9.0, etc. available for concurrent use. That seems pretty unlikely to me. Can someone clarify?

Hi Over_Nyquest,
If you have a single license then the different license types are the different options you have for using the software. So, you could use your single license as a "Computer-Based License" and only activate it on one computer for multiple people to have access to. The other option you have is to use it as a "Named-User License" and install it on 3 computers in different locations for your use. For instance, you could install it on your personal PC/laptop, your office computer, and your labroom computer. This is designed for your use only and will allow you to use LabVIEW at different locations during the day.
-Jake B.

Report Generation - Build an exe from a PC with different Office Version

Hi,
I want to build an exe from a VI that uses Report Generation Toolkit. The application has to be deployed on several PCs that use Office 2000. During development phase I installed on my PC, Office 2000 and everything was ok. After I was done with it, I reinstalled Office 2007. So, the Report Generation Toolkit from my PC is for Office 2000 (it was installed when I had Office 2000 on my PC).
These days I had to fix some bugs from my application, I made a new exe but the part that generates Word reports (using RGT) is not working anymore - I received that error with -35...9935 (or something like this).
I tried to search for the problem and I found it: with exactly the same VI's (_Word Dynamic VIs.vi - for Office 2000) the invoke nodes from a PC with Office 2007 and a PC Office 2000 look different. For example in Word_Open_Document.vi, the invoke node Document is different for a PC with Office 2000 + RGT for 2000 and a PC with Office 2007 + RGT for Office 2000 (no mistake).
So, I've tried to copy the VI's from a PC with Office 2000 + RGT 2000 to my PC but I cannot build it because I get the error: There are some errors in _Word Dynamic VIs.vi (the invoke nodes do not fit).
Finally my question is: How can I build the exe on my PC: Office 2007 but with RGT for Office 2000??
Thanks,
Paul
Solved!
Go to Solution.

Hi,
Thank you for your advice. Can you please tell me what you want to say with the wrapper vi? I don't really understand what you mean.
By the way, I solved the problem. I discovered that the Invoke Nodes are updated based on the Object Library for the ActiveX control (in this case the MS Office). The data types are store in the msword9.olb (version 9 - for office 2000 in Office folder) and msword.olb (version 12 - for office 2007 also in Office folder). I tried to register the msword9.olb (using the regsvr32.exe) but it doesn't work for olb files - I need the ocx or dll. But, if I replace the msword.olb from Office 2007 with msword9.olb from Office 2000 everything work.
Ok, steps that have to be done:
1. Install the RGT for Office 2000 on the PC
2. DO NOT Change anything in _Word_Dynamic VIs.vi. When Office 2007 is installed the VI arrow should be broken (error in VI)
3. Copy the msword9.olb from a system with Office 2000 (or your version) and copy it to your system with Office 2007 with the new name msword.olb. DO NOT FORGET to make a backup of the original MS Office 2007 file and to restore it at the end.
4. After the new msword.olb is there, the _Word_Dynamic VIs.vi should have no error
5. Build your exe application
6. Restore the old msword.olb
7. ENJOY your life !
I hope this is useful also for somebody else.
Paulie

SCC with different LabVIEW versions

Similar Messages

Maybe you are looking for