Any problems with labview runtime v 7.1 on one host interacting with lvrte 6.1 on another host?

Using OPC, UDP ant TCP on the host running lv 7.1 runtime, communicating with a second host running lvrte 6.1. Both hosts communicating with cpfp 2020 and using similar IAK files. Need to know if there are any known problems with this scenario. I cannot convert st this time, the legacy 6.1 side.

Hello,
Thank you for contcting National Instruments.
I am not sure I understand your question. The LabVIEW Run Time Engine (LV RTE)is used when you will be running an executable on a target. If you want to run executables on your cFP-2020 that were built in LV 6.1 and 7.1, you will need to make sure that LV RTE 6.1 and 7.1 are installed on the cFP 2020.
If you wish to run VIs (not executables) targeted to your cFP-2020, you can use LabVIEW Real-Time 6.1 or 7.1, but not both.
Let me know if you have further questions.
Sean C.
Applications Engineer
National Instruments

Similar Messages

Communicate with LabVIEW RunTime Application

Hi all.
I have an application created in LabVIEW, and I built an executable file from it (Let's call it App1.exe).
While App1 is running it sometimes generates an exception and is aborted. The problem is that the Run-Time APP1.exe GUI remains open (Which is undesirable). I need a way to close it somehow. I realized that the only way to close it is from another application (Let's call it App2).This solution can be realized in 2 different ways:
1) App2 communicates with App1 and closes it if App1 is not alive. The problem is that sometimes App1 is simply working slowly because of system problems and I might shut it down even though It's still running
2) To somehow obtain from the Run-Time engine what's the state of App1. I think that this way is preferable but i don't know how to communicate with the Run Time Engine.
I'll appreciate any suggestions (Preferably with some kind of example code)
Thanks, Nadav
P.S. I'm using LabVIEW 8.2.1.

What do you mean that it is "causing an exception"? Typically, an exception is a pretty serious failure that would kill the runtime engine too (thus closing all windows associated with it). What sort of error is stopping your application, but not the runtime engine executing it? It sounds like you possible have an internal error state that you haven't handled adequately. Part of the handling for a non-recoverable error should be orchestrating an orderly shut down of the application.
For what it's worth, if the runtime engine is still alive you can connect to it using VI Server and ask the execution state of the top-level VI. If it comes back "Idle" your code has stopped.
Mike...
Message Edited by mikeporter on 05-21-2007 12:43 AM
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

LabView TestStand interoperability with LabView runtime adapter

I would like to get some background information on how the interoperability of LabView and TestStand works.
We are using LabView steps mainly for some minor tasks in TestStand projects.
We do not use the regular deployment way as proposed by NI, but simply use one or more VI folders from which we reference LabView steps.
Deployment is done by copying the whole TestStand/LabView folder structure to the target machine.
We use the LabView runtime adapter within on our deployed systems.
We never mix LabView versions within one project.
Now, we frequently face the situation that the exact same project structure on two different machines has problems with the LabView steps.
So one changed VI runs on one target machine while the other after copy deployment is broken. Due to the same project structure and the virtual drives the paths must be the same.
A mass compile usually solves the situation.
So this is mystery number 1.
Today, I had the same problem, however I did not mass compile the full VI folder but simply some folders which I assumed had changed.
One VI which was referenced by TestStand was not mass compiled and was declared as broken by TestStand.
All I did was opening the broken VI in LabView Development System and nothing was obviously changed by LabView.
I closed the VI and pressed the Reload VI button on the TestStand step and the VI was working again, however the sequence file now had changed somehow (* at file name).
Another phenomenon:
An existing project on a machine was running with a certain user.
After switching the user, the VI steps of the project were suddenly broken.
My questions?
1) Why do VIs which run in the development system flawlessly become broken in the runtime?
2) Does the runtime use different search paths than the development system?
3) What kind of information does the mass compilation produce and where is it stored.
4) What kind of information does TestStand store along with the VI?
5) Is there a way to diagnose the problem with the runtime adapter ? With the runtime adapter I cannot open the VI to see what is the problem and in the developer mode it works.

First, to clarify a few points:
1) It is not necessary to use a workspace for TestStand deployments. You can specify a directory of source files for a TestStand deployment.
2) TestStand licensing should not be affecting this issue in any way. TestStand licenses do not have any impact on LabVIEW VI execution in TestStand.
Thorsten,
The issues you are describing are likely being caused by the LabVIEW VIs needing to be recompiled. The runtime engine is not able to recompile VIs, but the LabVIEW Dev System can, so this explains why you are able to execute again after opening the VIs in LabVIEW Dev. it also explains why a mass compile fixes the issue.
There are a variety of reasons why this could be happening. One scenario that could cause this to happen is that you make a change in one VI, but the change causes a second VI to need to be recompiled. This could cause a problem if you redeploy only the VI that you changed, because it will not be able to work properly unless the second VI is recompiled, which cannot be done by the LabVIEW RTE alone. This can happen because the LabVIEW compiler will optimize certain operations in the compiled code depending on where data is used--for example, the compiler will try to avoid allocating a copy of an array if it does not need to be accessed by multiple pieces of code at the same time. As you can imagine, this type of optimization might be appropriate for one version of your code, but might not be appropriate if a subVI changes such that it needs access to the array in parallel with the rest of the code.
The specific example I mentioned is called the Inplaceness Algorithm, and is described along with much more information about the LabVIEW compiler in this whitepaper. This might help explain the reasons a LabVIEW VI would need to be recompiled.
One potential solution to your problem that would allow you to keep your current deployment method would be to use packed project libraries (PPLs). You could have multiple PPLs for different parts of your code that you want to be able to update individually, which would allow you to make small changes to your codebase without having to deploy the entire set of code at once. A PPL is a self-contained set of compiled code that does not change, which should avoid the recompile issue from occurring.

Is there any problems using LabView 5.1.1 on Win2K?

I am currently upgrading the company's system from Win NT 4.0 to Win2K and I am wondering if there is any problems in upgrading LabView to Windows 2000?

No infact i'm running LV5.1.1 and LabVIEW 6.0.2 on the Win2k system.
A Rafiq
National Instruments
http://www.ni.com/support

Is there a VI availible that will allow one to interact with an analog signal

Hello all,
I am new to the sight and look forward to participating. I have a project that I’m working on and I would like to ask for your thoughts and direction if you’re willing. I have a few weeks left before completing an electronics program degree and Labview is one of the classes. The project I have chosen is to illustrate the differences between a micro controlled system and Labview controlled environment. I will be acquiring a signal through a ultra sonic distance sensor. The analog signal will be produced after which acquired through a SCB – 68 connector block and converted using the pci-mio-16E. The sensor operates at 40 kHz emitting a 5v pulse (burst) then falling to gnd for a short period followed by a 5v rise and staying high for a period of time waiting for the return of the frequency. This time period represents 3 inches to 27 ft in distance. I would like to interact with this signal through the distance period (portion) and output a string displaying a numeric value of the distance on the front panel obtained from an array built from different periods of the signal. I am not clear on what Labview function offers this type of control. I am hopeful in utilizing a vi or some type of trigger that allows me to build an array produced by some math functions. Any help would be appreciated.
Thank you, dhitch

First thank you for your response, I will have an opportunity to make a capture tomorrow in class. I believe I have run across the waveform measurement VI in my searches and am sure it’s a very good choice. The trigger VI you suggest, going by the name, should be my ticket. Would you imagine a delay or decreasing time after the capture, allowing the trigger VI time to respond to an output configuration be required?
If I remember correctly the sampling rate capabilities are 500K samples/ second with 12 bits of resolution and as I say that it seems some of the capabilities rely on the processing speed of the computer. I guess I will kick the tires tomorrow hey. There are 2 class periods remaining to finish our projects @ 2 hrs / class and my anxiety is a bit high. Wish me luck and thank you so much.
dhitch

I am having much trouble with the new reminders in IOS7 and how it interacts with Outlook Exchange. Many features lost in the new version.

When I downloaded IOS7, I found that the reminders/task app and how it interacts with Outlook Exchange is much more difficult to use. Some of the issues that I am having are...
1. Trying to edit my task on my phone is not possible, if the notes are lengthy. When you click on the text to edit data near the top, it will scroll to the bottom and not allow you to edit the text because you cant see it.
2. Now all of my task are in one long list. I can not move from day to day like we could in previous version IOS6
3. When I do edit a short task reminder and click done, it crashes and completly goes away. It does save the edit though
4. You can only add task at the bottom of each days reminders. This is very inconvient and much more difficult than IOS6
5. There is a major delay or latency when interacting inside of reminders in this version. Much more than IOS6. It is very unstable and quirky.
I have never seen Apple take a step back with a product until now. I am a huge Apple fan and always will be, so I am hoping they make enhancements to fix these issue. It is a big time prodcutivity killer.
Thanks for any and all help you can give.
Troy Meachum

Some power supplies or designed so that if there is a short or overload they shut them selfs off and some will not turn back on. Some have a relay that will click back on and work, some you have to cycle the power switch. Those that won't come back on will have to be replaced. I'm not saying that yours is that type as I have no way of telling. But if you have a friend who will loan you a good power supply you might try it. As someone else said just turning off the power will not darn all the power from some motherboards. To test this turn off your power supply than turn on the computer with the start botton. Mine will flash the lights and fans will start to spin than die. So every time you turn off computer to work on it. After turning off PSU hit the start botton to drian any power left in it before working on it. Also do this after unplugging it just to make sure.

Is iPad compatible with adapter from iPhone or just the one it came with?

Is the ipad compatible with the little power adapter that came with the iphone or should it just be used with the one that it came with the ipad. WIll other adapters do the battery damage? thanks

You can charge the iPad with the iPhone's power adapter, but charging will take longer than when using the power adapter that shipped with the iPad. You can also charge the iPhone with the iPad's power adaptor.
Copied from this link.
http://www.apple.com/batteries/ipad.html
The quickest way to charge your iPad is with the included 10W USB Power Adapter. *iPad will also charge, although more slowly, when attached to a computer with a high-power USB port (many recent Mac computers) _or with an iPhone Power Adapter_.* When attached to a computer via a standard USB port (most PCs or older Mac computers) iPad will charge, but only when it's in sleep mode. Make sure your computer is on while charging iPad via USB. If iPad is connected to a computer that’s turned off or is in sleep or standby mode, the iPad battery will continue to drain.

Computer with labview runtime engine (v8.2) cannot find sub-VI NI_AALBase.lvlib:Mean.vi. What do I have to do?

I am trying to run an exectutable on a computer that has the labview v8.2 runtime engine. The error I am getting is: Cannot find sub-VI NI_AALBase.lvlib:Mean.vi. What is the easiest solution?

the matrix,
I would try reinstalling the LabVIEW 8.2 Run-Time Engine. You may also want to try creating a very simple project in your development environment that has a VI with just the Mean.vi, try building an executable and then running it on the machine that just has the 8.2 RTE.
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me

"Incorrect function" error on PostUIMessageEx in Labview with Labview runtime

Hi,
I have a TestStand GUI developped in C#. Now, TestStand has some Labview modules that needs to send UIMessages to the GUI (It is too deep in Labview code to bring it back to TestStand to send the UIMessage).
When I am using the Labview Full development version 8.6.1, everything is fine, I can see my messages. Now, when I switch to Labview run-time 8.6.1, the invoke node PostUIMessageEx gives me an error: Incorrect Function (error 1).
I have been trying rebooting PC/TestStand/Labview without success. Is there anything I am missing?
Thanks
Alex
Solved!
Go to Solution.

Hi Manooch_H,
Changing to synchronous did not change anything. In fact, being asynchronous was a previous test, and I forgot to change it...
I have been trying few experiments, and here are the results:
1) I decided to change strategy. The Labview code would change a global variable. And in my PostStep callback, when I see that my global variable is deifferent from "", and send it to the GUI using a UIMessage, and I put it back to "". I know, I know, it is not optimal. But this way, the UIMessage is from TestStand to c#, and not from Labview to c# using teststand api... But, I ran into a similar problem using the SetValString in Labview to change my global variable.
2) What I do, is that I keep my Engine reference in a functional global. I have been trying to use either IEngine or Engine (TestStand.Engine.1) from the NI TestStand API 4.1.1 Version 1.0.
3) When I call my VI directly without using my Engine reference kept in the functional global, it is working. But I noticed that if I call this VI 3 times in a row, the Engine reference is different each time. It does mean that the Engine reference I am keeping in my functional global would be no more valid! So when I am using my functional global, it is not working...
There is something I don't do right. Is there a way to give Labview an Engine reference that would be valid throughout my execution? Or do I need to give back the updated reference each time I want to use the Engine in Labview?
Thanks
Alex

If I'm installing a PC-6221 board to work with Labview 7, do I need to get anything else with it if my connector I have right now is 50 pins to go with my old PC-1200 board?

What other specific things would I need?
Thanks

Hey,
Thanks for the reply. Before I buy the PC-6221 board, a new cable, and a new to go along with it, I was just wondering if there was a way for me to use 50 pins from my PC-1200 board. I have three laying around, so I was wondering if there was a way to use them to make a 68-pin one. This is probably not likely, but any suggestions would be great. Thanks again for the reply, and you understood what I was trying to ask.
Take it easy,
Ryan

Install MAX with only LabVIEW runtime engine

Hi,
I want to know if it is possible to install MAX from the Device Driver CD, when only LabVIEW RunTime engine is installed. There is no full installation of LabVIEW on that PC. That's MAX 3.1.1.3004 with LabVIEW RunTime Engine 7.1.
Patrick.

Dear Patrick,
The device driver CD usually does not have a single installation of MAX, but you can install MAX by installing most of the other drivers such as NI-DAQ, NI-488.2, NI-Serial, etc. MAX does not require LabVIEW, so you can have MAX and LabVIEW Run-Time without LabVIEW. Have a great day!
Sincerely,
Marni S.

If i connect with led to recharge battery there is any problem in the iphone 5

if i connect with led to recharge battery there is any problem in the iphone 5

No idea what you mean by "connect with led".

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

Hi Leo22,
Does this error occur if you use any of the example programs that come shipped with LabVIEW? I would try opening one of the examples that write data to Word and see if those give you an error. Also, have you tried just putting down a New Report.VI and change the report type to Word? If this simple vi (that's all you need to open Word) breaks, I would check to see if there are any instances of Word still open. Check the task manager to see if any word processes are still open. There should not be a problem accessing Word 2003 from LabVIEW 7.0. If neither of these solutions work, please give some more detail about your application and we can research further. Thanks!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

Will our existing drivers work with LabVIEW 8.x?

We have drivers for some of our DAQ products that were developed in LabVIEW 6 or 7.
Is there any reason these drivers would not work with the latest versions of LabVIEW?
We ask because there seem to be some customers in Europe who believe our drivers do not work with LabVIEW 8.5, but we know there are users with LabVIEW 8.0 and 8.1 using the drivers without problems.
Any thoughts or suggestions, or are there any known issues with older drivers in LabVIEW 8.5?
Regards,
Roger Hammerquist

Hi Roger,
In general, the latest versions of LabVIEW will work with older
versions of the DAQ drivers. However, it is certainly possible that some of
the older drivers could have some conflicts.
How “old” are the driver versions that your customers are
using? Specifically, what version of the
driver does your customer report seeing the errors with? Is the
customer using the same operating system that the original program was written
for? Is the customer seeing problems
upgrading the VIs from LabVIEW 6 or 7 to LabVIEW 8.5?
The suggestion to work with someone to try it out is excellent.
Posting the specific driver versions
seeing the conflict, might also shed some light on the issue.
Jared T.

Control multi dynamixel AX-12 with LabView

I need help controlling 2nd Dynamixel AX-12 from LabView based on "Dynamixel Sync Write Example" code.
We used one USB2 dynamixel to control one dynamixel ax-12 from Labview. It worked well.
Recently I added another ax-12. The two ax-12 are in series. USB2dynamixel is set to TTL. The Labview code generated dual control front panal automatically. Controlling one unit is good. But controlling the 2nd ax-12 is a problem:
The ID seems incorrect according to USB2dynamixel chart: the unit next to the USB should be #0, the one in series with #0 should be #1 and so on. On my setup, I couldn't find a correct ID associated with the unit next to the USB. The one in series with it is #1. Only #1 responds correctly to front panel control.
When click "run" 1st time ax-12 #1 will rotate according to set positions. click "run" again, the other ax-12 will rotate according to #1's set positions, not its own positions. The other unit's ID can be set any number, and results are the same.
Has anyone used the same LabView code to control more than one ax-12 with USB2Dynamixel? Anything I have missed? Appreciate your inputs.
Attachments:
front.PNG ‏53 KB
block.PNG ‏38 KB

Thanks, Drew
You are correct that the code is from NI example less while loop. I did repeated runs, results are the same as two single runs.
I just traced the executions and recorded header and checksum parameters for ID #1 and #2 for debugging. I placed two sets of positions to separate ID#1 and ID #2:
         Control      Dial      Position      Manual pos
ID#1      0           off         60              160
ID#2      1           on        100             200
There is only one set of header and checksum value being passed in the program. That might explain only one set of position (ID#1) was set, the other one (ID#2) was ignored.
Does that make sense?
Anne
Attachments:
111026 dynamixel.pdf ‏198 KB

Any problems with labview runtime v 7.1 on one host interacting with lvrte 6.1 on another host?

Similar Messages

Maybe you are looking for