04-09-2010 02:55 AM
Hi,
I followed the instruction on
http://digital.ni.com/public.nsf/allkb/5CD8196D39880CDF86257450000B7C44
to install the LVRTS 6.0.2 on a Development TS4.2 maschine.
We need this to modificate and maintain Sequencefiles for some TS2.0/LVRTE6.0.2 Production maschines.
(and we dont want to install TS2 and switch with the version selector !!)
4.2 Editing and backward saving to TS 2.0 works well. But Executing not!
It seems that TS4.2 no longer supports the old stuff from LV 6.0.2
Why ??
Or is there a simple workaround ?
Regards
Juergen
04-09-2010 05:17 AM
I dont believe labview 6.X is compatibile with TestStand 4.X or Vista
Also you will have problems with running your TS2 stuff in TS4.x, especially if you have custom step types.
Regards
RayF
04-12-2010 02:12 AM
Hi Ray,
There are just simple SequenceFiles which are using only 3 built in StepTyes (Statement,Action,NumericLimitMeasurement).
I do not want to use the LabView's Editor at all. I only like to use the Run -Time-Engine.
For doing this in TS for the old projects i switch the TS4.2 LabView Adapter configuration from LV-RTE 2009
to TestStandLVRTS
As you see in the attached shoot the correct runtime server will called and executed.
But i think a TS/LV version flag will prohibit me to consume it.
Regards
Juergen
04-20-2010 12:34 AM
04-20-2010 12:51 AM
04-20-2010 01:05 AM
04-20-2010 11:08 AM
Juergen -
As Ray mentioned, TestStand 4.2 does not support LabVIEW 6.x. Unfortunately, unless you mass compile to LabVIEW 7.1.1 or later, you will not be able to call these VIs.
04-21-2010 12:56 AM
Hi Manooch,
Thanks for your answer.
The TS Messagebox pointed that there is no support.
I am really, really disappointed about that. I assumed with the LVRTS you have backward compatibilty.
But not for LV 6, 5(assumed). When i am looking 8 years back when i have started using Teststand on 2.0
There where CVI6, VS6 and LV 5,6. Now in 2010 there is Teststand 4.2 and my old stuff from the beginning in
CVI or VS is running in the latest TS version without !any! modifications. Especally CVI: created with CVI6
i is just running with the lasted CVI runtime engine. Good work! The guys from LV shout visit the few guys at CVI
and take a look how they did backward compatibility.
Now for our maintainance stuff we have the old version selctor and switch back to 2001 to test if modifications
are running.
For me this is one case of not creating my codemodules in LV. Will create my stuff in future as in the past in
VC and CVI, because i have the power of Microsoft and National Instruments AND near 10 years of backward compatibiliy
Regards
Juergen