RE: FW: [rtl] Labview
I will forward this to the news group as well I hope you don't mind. I think there may be others out there wondering the same thing. National Instruments has ported LabView to Linux. This was done primarily due to prodding from the Linux Lab Project and a few individuals like myself. Once National Instruments felt there was enough business base out there they ported it over. You can find out more about it at the National Instruments we site. http://www.ni.com/linux/ I am currently running Red Had 5.1 but I am going to upgrade soon. I am also running RT-Linux 1.1 Again I am going to upgrade soon. I am currently running on a Pentium 450 and of course I plan on upgrading soon. Has anyone tried any of the 1 GHz machines yet? > -- > From: [EMAIL PROTECTED][SMTP:[EMAIL PROTECTED]] > Sent: Thursday, May 11, 2000 3:56 PM > To: Basham, Richard R > Subject: Re: FW: [rtl] Labview > > > > Richard; > > You'll pardon me if I don't understand, sometimes the obvious eludes me > > Are you running a Linux version of LabView? > > How do you get LabView to run under or alongside Linux? > > I understand LabView to be a WinTel (i.e. Windows/Intel) type product. > > What does your configuration look like, & what operating system(s) are you > running? > > Thanks and regards, > > Raymond C. Minich > Producibility Engineer > Dresser Piping Specialties > Dresser Equipment Group > Bradford, Pennsylvania > > -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
Re: FW: [rtl] Labview
On Thu, May 11, 2000 at 09:19:33AM -0700, Dan Samber wrote: > > I have a naive question: > How does Labview benefit from RTLinux? Alledgedly, the people at National > Instruments > have arranged things (via special drivers or some other mechanism) so > that there > are no ugly things like gaps in data acquisition etc. > > Can someone clear things up for me? > A good data acquisition board these days have hardware fifos that allow them to sample at full speed (>100 kS/s) without dropping samples. That being said, the operating system does have to guarantee _some_ maximum interrupt latency, in this case, at about 10 ms. Windows can handle this until you walk away and get a cup of coffee. I've never seen this failure under Linux (with my limited set of computers.) PCI cards using DMA allow you to increase this latency indefinitely, assuming you have enough RAM, and also assuming you have access to the driver source code... =) However, simple acquisition isn't very useful if your needs are more complicated than streaming input and output. Very quickly, it becomes necessary to record and generate synchronization events, accurate timestamps, etc. These things can be done trivially using an RTOS, but cannot be done accurately using LabView or any other user-space tool. Using RTLinux is essentially like using NI's plug-in real-time 486 boards, except that you can use existing ISA/PCI-based hardware. dave... -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
RE: FW: [rtl] Labview
The huge advantage you get with RT-Linux is that you can make a LabView program that has real time properties. There is more to real time software than eliminating gaps in data acquisition or data acquisition in general. Yes, they have made special hardware to capture buffers of data to eliminate the gaps. However, the software can not make real time decisions based on the data that was captured. RT-Linux allows you to provide: real time data acquisition, real time decisions based on that data, and real time control signals out to the physical world. LabView by itself does not allow real time processing. With RT-Linux you can have several different real time processes working together and still maintain their real time properties. In LabView there are some priority settings that can be assigned to separate threads but none of them are real time. As other threads get higher priorities some threads suffer from a loss in performance. National Instruments does have a special board with a DSP to provide some real time control. From what I have seen so far it is limited to general purpose stepper and DC motor (pulse width modulation) controls. > -- > From: Dan Samber[SMTP:[EMAIL PROTECTED]] > Sent: Thursday, May 11, 2000 11:19 AM > To: Basham, Richard R; '[EMAIL PROTECTED]' > Subject: Re: FW: [rtl] Labview > > > I have a naive question: > How does Labview benefit from RTLinux? Alledgedly, the people at National > Instruments > have arranged things (via special drivers or some other mechanism) so > that there > are no ugly things like gaps in data acquisition etc. > > Can someone clear things up for me? > > Thanks, > > Dan > > > At 04:09 PM 5/10/00 -0700, Basham, Richard R wrote: > > > I have been using LabView with RT-Linux for over a year now. It has > > worked out quite well. > > > > > > I use the LabView to deal with the mundane user interface and non time > > dependant things such as file access. I have displays that present near > > real time information from the real time processes for the operator to > > view. I also provide button commands that control some of the execution > > of the real time processes. > > > > > > I use a shared library of small routines to pass the data back and > > forth between LabView and RT-Linux. These routines access both shared > > memory and the RT-fifos. > > > > > > I used the initial execution of the LabView program to install the real > > time modules and I also had LabView remove the modules in an orderly > > fashion when the program was terminated. This was important because some > > of the users of the project did not want to be bothered with the low > > level details required to make it work. They just wanted to be able to > > use it and they really wanted to have a single point of entry and exit. > > > > > > The largest benefit that I got from using these two products together > > was that I was able to produce the graphical user interface quickly. It > > is easy to change the interface when new requirements arrived. > > > > > > I will admit that I have had about 40 hours of training in > > LabView. However, it was about a year before starting the > > project. Furthermore, this was the first project in which I used LabView > > since the training. > > > > > > I was hoping to put together a little write up on how I interfaced the > > two products with each other and send it to the news group. I wanted to > > include code examples etc. However, every time I think I have some time > > to do that I get a couple more jobs piled on. If this is of interest to > > other people I may be able boost the priority. > > > > > > > > > Richard Basham > > > Control Systems Group > > > Environmental & Material Test Laboratories > > > Boeing Defense & Space > > > Seattle, Washington > > > > > > > > > > > > -- > > > From: [EMAIL PROTECTED][SMTP:[EMAIL PROTECTED]]> > > > Sent: Wednesday, May 10, 2000 1:12 PM > > > To: [EMAIL PROTECTED] > > > Subject: [rtl] Labview > > > > > > > > > If you are interested in Labview on RTLinux, please send me a note. > > > Tell me if you are currently using Labview, and, if you > > > can, why you want RTLinux/Labivew or a similar product. > > > Other comments on Labview and RTLinux gladly accepted. > > > > > > > > > > > > -- > > > ---
Re: FW: [rtl] Labview
I have a naive question: How does Labview benefit from RTLinux? Alledgedly, the people at National Instruments have arranged things (via special drivers or some other mechanism) so that there are no ugly things like gaps in data acquisition etc. Can someone clear things up for me? Thanks, Dan At 04:09 PM 5/10/00 -0700, Basham, Richard R wrote: > > I have been using LabView with RT-Linux for over a year now. It has > worked out quite well. > > > > I use the LabView to deal with the mundane user interface and non time > dependant things such as file access. I have displays that present near > real time information from the real time processes for the operator to > view. I also provide button commands that control some of the execution > of the real time processes. > > > > I use a shared library of small routines to pass the data back and > forth between LabView and RT-Linux. These routines access both shared > memory and the RT-fifos. > > > > I used the initial execution of the LabView program to install the real > time modules and I also had LabView remove the modules in an orderly > fashion when the program was terminated. This was important because some > of the users of the project did not want to be bothered with the low > level details required to make it work. They just wanted to be able to > use it and they really wanted to have a single point of entry and exit. > > > > The largest benefit that I got from using these two products together > was that I was able to produce the graphical user interface quickly. It > is easy to change the interface when new requirements arrived. > > > > I will admit that I have had about 40 hours of training in > LabView. However, it was about a year before starting the > project. Furthermore, this was the first project in which I used LabView > since the training. > > > > I was hoping to put together a little write up on how I interfaced the > two products with each other and send it to the news group. I wanted to > include code examples etc. However, every time I think I have some time > to do that I get a couple more jobs piled on. If this is of interest to > other people I may be able boost the priority. > > > > > > Richard Basham > > Control Systems Group > > Environmental & Material Test Laboratories > > Boeing Defense & Space > > Seattle, Washington > > > > > > > > -- > > From: [EMAIL PROTECTED][SMTP:[EMAIL PROTECTED]] > > Sent: Wednesday, May 10, 2000 1:12 PM > > To: [EMAIL PROTECTED] > > Subject: [rtl] Labview > > > > > > If you are interested in Labview on RTLinux, please send me a note. > > Tell me if you are currently using Labview, and, if you > > can, why you want RTLinux/Labivew or a similar product. > > Other comments on Labview and RTLinux gladly accepted. > > > > > > > > -- > > - > > Victor Yodaiken > > FSMLabs: www.fsmlabs.com www.rtlinux.com > > FSMLabs is a servicemark and a service of > > VJY Associates L.L.C, New Mexico. > > > > -- [rtl] --- > > To unsubscribe: > > echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR > > echo "unsubscribe rtl " | mail [EMAIL PROTECTED] > > --- > > For more information on Real-Time Linux see: > > http://www.rtlinux.org/rtlinux/ > > > > >-- [rtl] --- >To unsubscribe: >echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR >echo "unsubscribe rtl " | mail [EMAIL PROTECTED] >--- >For more information on Real-Time Linux see: >http://www.rtlinux.org/rtlinux/ -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
FW: [rtl] Labview
> I have been using LabView with RT-Linux for over a year now. It has worked out >quite well. > > I use the LabView to deal with the mundane user interface and non time dependant >things such as file access. I have displays that present near real time information >from the real time processes for the operator to view. I also provide button >commands that control some of the execution of the real time processes. > > I use a shared library of small routines to pass the data back and forth between >LabView and RT-Linux. These routines access both shared memory and the RT-fifos. > > I used the initial execution of the LabView program to install the real time modules >and I also had LabView remove the modules in an orderly fashion when the program was >terminated. This was important because some of the users of the project did not want >to be bothered with the low level details required to make it work. They just wanted >to be able to use it and they really wanted to have a single point of entry and exit. > > The largest benefit that I got from using these two products together was that I was >able to produce the graphical user interface quickly. It is easy to change the >interface when new requirements arrived. > > I will admit that I have had about 40 hours of training in LabView. However, it >was about a year before starting the project. Furthermore, this was the first >project in which I used LabView since the training. > > I was hoping to put together a little write up on how I interfaced the two products >with each other and send it to the news group. I wanted to include code examples >etc. However, every time I think I have some time to do that I get a couple more >jobs piled on. If this is of interest to other people I may be able boost the >priority. > > > Richard Basham > Control Systems Group > Environmental & Material Test Laboratories > Boeing Defense & Space > Seattle, Washington > > > > -- > From: [EMAIL PROTECTED][SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, May 10, 2000 1:12 PM > To: [EMAIL PROTECTED] > Subject: [rtl] Labview > > > If you are interested in Labview on RTLinux, please send me a note. > Tell me if you are currently using Labview, and, if you > can, why you want RTLinux/Labivew or a similar product. > Other comments on Labview and RTLinux gladly accepted. > > > > -- > - > Victor Yodaiken > FSMLabs: www.fsmlabs.com www.rtlinux.com > FSMLabs is a servicemark and a service of > VJY Associates L.L.C, New Mexico. > > -- [rtl] --- > To unsubscribe: > echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR > echo "unsubscribe rtl " | mail [EMAIL PROTECTED] > --- > For more information on Real-Time Linux see: > http://www.rtlinux.org/rtlinux/ > > -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl " | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
