Difference between LabVIEW RTE and TS LabVIEW RTE

Ok, this may be an easy one but still I would to have it clear. What is the difference between using LabVIEW RTE and TS LabVIEW Runtime Server to run LabVIEW modules/steps in PC's with TestStand Deployment licences???
Thank you,

Hi,
The TestStand LabVIEW Adapter can run VIs
using any of the following LabVIEW environments, or servers: the LabVIEW
development system, the LabVIEW Run-Time Engine, or a LabVIEW executable built
with an ActiveX server enabled. The Teststand LabVIEW run-time server
(TestStandLVRTS) is a version of the third option written way back at a time before the LabVIEW run-time engine is what it is now.
The only reason you would possibly want to use the TestStandLVRTS is when you
have VIs written with versions of LabVIEW older
than 6.1.
Have a great day,
Ecleamus Ricks, Jr.
National Instruments
Applications Engineer

Similar Messages

What's the difference between 6.x and 7.x of labview?

What's the difference between 6.x and 7.x of labview?

Hello,
I recommend you to read the "Labview upgrade notes" for LV 7.0. This gives you a short but fast overview of the new features of LV 7.0:
http://digital.ni.com/manuals.nsf/webAdvsearch/E8D86CD680B0753D86256D2C005D8EA0?OpenDocument&vid=niwc&node=132100_US
Of course you can download an evaluation version of LV 7.0 to test it yourself:
http://www.ni.com/labview/
Regards,
Luca
Regards,
Luca

What are the main differences between Signal Express and Labview?

National Instruments provides a matrix so one can quickly compare the
various versions of Labview but no comparison of Signal Express with
Labview. Hence how does Signal Express compare with Labview? What
are some of the things one can do with Labview one can't do with
Signal Express?
Howard

hrh1818 wrote: Which version of Labview are you referring to? I don't consider the graphical version of Labview to be a full featured programming language. LabWindows/CVI is by a long shot a lot closer to being a full featured programming language than the graphical version of Labview.
Howard,
You clearly don't know what you are talking about. There is no "graphical version" of LabVIEW, there is just LabVIEW. Click on the article "Is LabVIEW a general purpose programming language?" written by the Jeff K. for some easy reading from a few years ago. It is all still true (except that object oriented features and recursion have been added in recent versions).
One of the main points at this years NI-week was the discussion of how processor development is switching more and more to multicore designs to improve performance because a simple boost in clock frequency is becoming more difficult. Linear, text based code is not well suited to take advantage of multticore design, while the dataflow based LabVIEW programming language automatically scales well to multiple processor cores, without any need to rewrite older code. I would say that only LabVIEW is futureproof in this respect. LabVIEW programmers are not wimps that are simply too stupid to write text based code. LabVIEW is not a toy language for people that don't want to learn a "real" programming language.
LabVIEW is arguably the best programming language in terms of getting things done! I've never felt limited with LabVIEW and my programs often don't even have anything to do with data acquisition or instrument control. The difference between text based code vs. LabVIEW is like "DOS vs. Windows", "Radio vs. HD television". "Trilobyte vs. Homo sapiens" (sorry Putnam ). Text based code is monochrome, archaic and outdated and its linearity imposes unecessary constraints on the programmer that can only be (partially) overcome by wasting even more time throwing even more code at it.
Sure, a seasoned text based programmer will initially have problems adapting to LabVIEW, just because you would need to adapt to and embrace the power of dataflow and not try to make a literal translation of the text code to LabVIEW, retaining old habits. If you get stuck, come back and ask here in the forum.
You were looking for object oriented features and failed. All you need to do is a quick site search. All the information is out there. Just because you cannot find it in the first five sentences of the glossy brochure does not mean it does not exist. Maybe you want to read one of the application notes such as:
LabVIEW Object-Oriented Programming: The Decisions Behind the Design
In general, you should avoid judgement until you have all information. Your opinions seem quite biased and superficial and not really based on hard facts.
Initially you asked about the difference between signal express and LabVIEW.
hrh1818 wrote:
> What kind of measurments do you want to do and what kind of requirements do you have?
> You can also see for yourself and download evaluation version of both.
No thanks, there has to be a better way to get an answer to my
question than get involved in a two month study project.
If you would answer the first question quoted above, we could certainly help you with the decision. Isn't that the main purpose of this thread?
You can also contact your local LabVIEW Field Engineer to go over your requirements and help you make a decision. They usually know their stuff!
Message Edited by altenbach on 09-02-2007 11:51 PM
LabVIEW Champion . Do more with less code and in less time .

What is difference between local variable and property node ?

What is difference between local variable and property node ?
" 一天到晚游泳的鱼"
[email protected]
我的个人网站：LabVIEW——北方客栈 http://www.labview365.com
欢迎加入《LabVIEW编程思想》组——http://decibel.ni.com/content/groups/thinking-in-labview

To make things clear, here are two small examples that show how nasty locals and value properties can be to the naive programmer.
- Open the diagram of the race condition.vi before running it and try to predict what will be the values of the two counters after the third run.
- Use the Compare Locals Properties and Wires.vi to find out how slow locals and value properties can be (times 1000+).
This being demonstrated, I must add that I use globals and value properties quite often, because they are often very convenient
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...
Attachments:
Race condition.vi ‏9 KB
Compare Locals Properties and Wires.vi ‏18 KB

Difference between open loop and closed loop mode when finding the index on a stepper motor axis.

I have a test system which uses a PXI-7352 motion controller with a MID-7602 stepper motor drive to position a 200 step/revolution stepper motor with an attached 1000 line encoder. The MID-7602 is configured for 64 microsteps per step, giving 12,800 microsteps and 4000 encoder counts per revolution. The system is controlled using LabView 7.1 and NI-Motion 6.13. To home the motor, I've defined a sequence in MAX which first finds the reverse limit switch and then moves forward to the encoder index pulse.
When finding its reference in open loop mode, the system its reference at the same microstep each time. When findings its reference in closed loop mode, the system finds its reference somewhere within about a 20 microstep wide range.
I hope somebody out there with more experience with this controller can describe the difference between finding the encoder index in open loop mode and finding the encoder index in closed loop mode.
Thanks,
Mark Moss

Hello Mark,
I suspect that the behavior you are experiencing has today
with the resolution difference between your encoder and your
microstepping. Let me illustrate with an
example:
Example Setup
Stepper
Motor
NI
Motion Controller
10
steps per encoder pulse (Every 10 steps the controller gets an encoder
pulse, therefore positions 0-9 all appear to be 0 to the controller)
The
system has a maximum of 3 pull in moves set
Open Loop Scenario
The
system is commanded to go to position 9.
The
controller sends out 9 pulses.
The
motor moves to position 9.
Closed Loop Scenario
The
system is commanded to go to position 9.
The
controller sends out 9 pulses.
The
motor moves to position 9.
The
controller checks its position and sees that it is still at position 0
because it has not received an encoder pulse.
Because
the controller thinks it is still at position 0, it sends another 9 pulses
as its first pull in move.
The
motor moves to position 18.
The
controller checks its position and sees that it is at position 10 because
it has only received one encoder pulse.
Because
the controller thinks it is still at position 10, it sends1 reverse pulse
as its second pull in move.
The
motor moves to position 17.
The
controller checks its position and sees that it is at position 10 because
it has only received one encoder pulse.
Because
the controller thinks it is still at position 10, it sends and additional
single reverse pulse as its third pull in move.
The
motor moves to its final position of 16.
I believe something similar is happening with your
application as it looks for the index pulse.
Because the controller does not compensate for what it perceives as
position error in open loop mode, the motor always goes to the same commanded
position. In closed loop mode, the motor
is bouncing around inside the single index encoder pulse trying to find a
certain position.
There are several recommendations I can make towards
correcting this behavior. These
recommendations are in order of effectiveness:
Setup
your system so that there are more encoder counts per revolution than
steps per revolution.
Turn
off pull-in moves by setting them to 0 in MAX.
Use an
open loop configuration.
Play
around with the pull in window in MAX.
Regards,
Luke H

Difference between Low level and Normal IMAQ ?

There are two options in IMAQ palette a low level and a normal one. Both have the same function names and the same icons the only difference being the balck and white icon of low level functions and colored icons of the normal functions. What is the difference between these two and what is the need of making a low level palette of functions ?
Regards
Asad Tirmizi
Design Engineer
Institute of Avionics and Aeronautics
" Its never too late to be, what u want to be"
Using LabVIEW 8.2

Low level imaq functions gives you relatively more function to control the hardware. Buffer functions is one which is not there on the high level palatte

Troubleshooting hints - differences between development environment and release environment

Hello,
I am using LabVIEW 8.6 for an application involving stepper motors. We are using 2 Velmex stepper motor systems to run PIR targets for a manufacturing test. The problem I am having is that the program runs fine in the states where it was developed but hangs approximately every 10th run when running in the manufacturing environment in China. Since I am on the EAst coast there is the 12 hour time delay, and I am planning on doing a live support call to find out what is going on. The person who installed the code made some modifications, but I am not aware of the differences. He also may send his code here and see how it runs.
The assumption I am making (based on past experiences from here in the States) is that the stepper motor interface is hanging. since I can't recreate the problem here I can't troubleshoot it.
With a past prooject I was working I did some code on one machine, and when I ran it on a different machine the order of execution for items in a sequence was different between the machines. Has anyone run into this before? Unfortunately for the task at hand the stepper motor has to run at the same time that analog data on multiple channels are being acquired.
Any suggestions?
Mike
Mike

Thanks for the reply. I did think about putting in a producer-consumer. It turns out that there was a problem with the computer it was being run on. The computer was changed and the problem got better, although it did not go away. The stepper motor was done through a com port talking to another hardware / software solution. The tasks are truly independent and pass no data between them. However, the other task being run involves collecting analog data and updating on a chart (and in one instance stimulating an analog output), and when the stepper motor starts the analog data collection is not updated on the chart. I figure this could be because the charts are a memory hog. No data is lost, and it is running, so I figure if it's not broke don't fix it. It now occasionally locks up. I can run it here for 100 times with zero lock ups, and the last report I got was it ran 30 times in china before locking up. I may have to start examining differences between their machine and my machine.
Now as to the configuration management. It needs to be clarified a wee bit. I'm doing the initial code development / updating, and then we hand off to china, which can make code tweaks as needed. They also have 3 lines running this program, and one of the items I did was to load the differences between lines from configiration files (INI files), and that I got working well. We have fixture variables, items that vary between lines, and configuration items, which are I/O lines and what not. The digital I/O and analog I/O referenced MAX tasks, and that worked well. There are also a com port call for the stepper motor, and in another program an RF power meter, which had to be referenced from an INI file. I will reccomend that they do their code development on one machine and create executables to store on the production lines. We have been bouncing code back and forth from the team members from the states that are currently in china doing the install.
Mike
Mike

What is the difference between buffered acquisition and non buffered acquisition?

What is the difference between buffered acquisition and non buffered acquisition? How will I decide whether I want buffered acquisition or non buffered acquisition?

I will also add that with non buffered acquisition you have to use software timing. Windows is not a real time OS, so the the timing is not accurate. But if you use buffered acquisition the timing will be controlled with an accurate internal clock on the Daq unit. I think non buffered acquisition should be avoided in most cases.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

What is the difference between VI Template and vi that is reenterant?

What is the difference between VI Template and vi that is reenterant?
From what little info I can find about them, they seem to basically do the same thing....
What are the difference?
What are the pros and cons of each?
Thanks alot for the help.....

Tarek316 wrote:
I inherited an app that uses .vit for the purpose of having multipe separate instances.
Thanks,
OK, here's what happens when you call a VI Template using Call by Reference or using Invoke and Property Nodes.
Since the VI you are calling is a template, LabVIEW creates a new instance of that VI by creating a copy of it and giving a new name. Notice in the title bar of the instantiated VI the VI name is the same as the template VI plus a number. This is the same thing you see when you open a template from the "New..." menu. So if you call the template VI 3 times, you'd end up with 5 newly instantiated VIs named, "VI Name 1.vi", "VI Name 2.vi" and "VI Name 3.vi". This is how you end up with multiple instances.
Reentrancy only works on subVIs when they are used as a normal subVI in a top level application. Using Call by Reference or Invoke and Property Nodes to open and run a reentrant VI results in the VI only being opened once because LabVIEW will not automatically give it a new name. The new name is only generated when calling templates. Since LabVIEW can only a have a single instance of VI name in memory at a time, you'll not end up with multiple instances.
Not sure if I can help with the know issue on OSX. If it's specific to using the Call by Reference function, you could try calling the templates using Invoke and Property nodes.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

Searching and Matching - Difference between 'Match Pattern' and 'Match Geometric Pattern'?

I was wondering if someone can explain to me the difference between 'Match Pattern' and 'Match Geometric Pattern' VIs? I'm really not sure which best to use for my application. I'm trying to search/match small spherical particles in a grey video in order to track their speed (I'm doing this after subtracting two subsequent frames to get rid of background motion artifacts).
Which should I use?
Thank you!
Solved!
Go to Solution.

Hi TKassis,
1.You may find from this link for the difference between these two,
Pattern Match : http://zone.ni.com/reference/en-XX/help/370281P-01/imaqvision/imaq_match_pattern_3/
Geometric Match : http://zone.ni.com/reference/en-XX/help/370281P-01/imaqvision/imaq_match_geometric_pattern/.
2. I always prefer match pattern because of its execution speed, and incase of geometric pattern match it took lot of time to match your result. You may find in the attached figure for same image with these two algorithm execution time.
Sasi.
Certified LabVIEW Associate Developer
If you can DREAM it, You can DO it - Walt Disney

Are there any functional differences between the trial and the paid version?

Are there any functional differences between the trial and the paid version for Labview 2009? Thank you.
Solved!
Go to Solution.

This outlines the limitations of the eval version of Labview: Limitations of the LabVIEW Evaluation Version
Cheers,
Misha

What is difference between sy-tabix and sy-index.

SAP Seniors,
Can you please let me know what is difference between sy-index and sy-tabix.
I read the SAP help, it is confusing for me. it looks like both are same from help. please help me.
Thank you
Anitha.

HI,
Here is a brief description of difference between SY_TABIX and SY_INDEX and using them with several conditions.
SY-TABIX
Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
SEARCH <itab> FOR sets SY-TABIX to the index of the table line in which the search string is found.
SY-INDEX
In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
Hope this helps.
Thank you,
Pavan.

Difference between sy-tabix and sy-index?

tell me about sy-tabix and sy-index?what is the difference between sy-tabix and sy-index?
Moderator Message: Please search before posting. Read the [Forum Rules Of Engagement |https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement] for further details.
Edited by: Suhas Saha on Jun 18, 2011 5:33 PM

HI,
Here is a brief description of difference between SY_TABIX and SY_INDEX and using them with several conditions.
SY-TABIX
Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.
LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
SEARCH <itab> FOR sets SY-TABIX to the index of the table line in which the search string is found.
SY-INDEX
In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.
Hope this helps.
Thank you,
Pavan.

What is difference between sy-index and sy-tabix and where both are using ?

what is difference between sy-index and sy-tabix and where both are using ?

hi nagaraju
sy-tabix is in Internal table, current line index. So it can only be used while looping at the internal table.
sy-index is in Loops, number of current pass. This you can use in other loop statements also (like do-enddo loop, while-endwhile)
SY-INDEX is a counter for following loops: do...enddo, while..endwhile
SY-TABIX is a counter for LOOP...ENDLOOP, READ TABLE...
Here is an example from which you can understand the difference between sy-tabix and sy-index.
Itab is an internal table with the following data in it.
id Name
198 XYZ
475 ABC
545 PQR.
loop at itab where id > 300.
write :/ itab-id, itab-name , sy-tabix, sy-index.
endloop.
My output will be :
475 ABC 2 1
545 PQR 3 2
Sy-tabix is the index of the record in internal table.
sy-index gives the no of times of loop passes.
So, for the first record in the output (475 ABC), 2 is the index of the record in internal table and as it is first time loop pass occured, sy-index value is 1.
Regards,
navjot
award points

The difference between chapter markers and dvd studio pro markers

Does anyone know what is the difference between chapter markers and dvd studio pro markers? I can not find anywhere on Google. Also in the tutorials I have seen, suggesting DVD Studio Pro markers, but it did not mention the chapter markers.
Thanks,

"Adding Chapter and Compression Markers to Your Sequence
Once you have your edited sequence or program finished, you can add markers to the sequence for use on DVD. Markers are reference points you can place within clips or sequences that identify specific frames. There are two kinds of markers you can add that directly relate to authoring a DVD—chapter markers and compression markers.
• Chapter markers allow DVD authoring applications to create a navigable chapter list for your exported QuickTime movie. Chapter markers force MPEG keyframes (known as I-frames) at their location, since the DVD specification requires an I-frame at each chapter point.
• Compression markers identify areas of abrupt change and include two types: those that are automatically inserted by Final Cut Pro at all edit points, and those you manually place in the clip or sequence. Like chapter markers, compression markers force I-frames at their location, although in this case it is for better quality encoding, and they are not used to create a chapter list.
Note: When you export a QuickTime movie, you have an option to export various kinds of markers, including compression, chapter, or DVD Studio Pro markers. *When you choose to export DVD Studio Pro markers, Final Cut Pro actually exports chapter markers and all compression markers.* This includes compression markers you set manually, as well as ones created automatically by Final Cut Pro at edit and transition points."
From the Final Cut Pro User Manual.
So, JS was right the first time

Difference between LabVIEW RTE and TS LabVIEW RTE

Similar Messages

Maybe you are looking for