Hardware for LabVIEW Realtime (ETS)

Hello NG,
right now we are using two NI-Devices (PCI 5122 and PCI 6251) in an
Intel based PC with Windows XP as the operating system.
We would like to switch to a Realtime-System (ETS) using our PCI-devices
again in an Intel based PC. As I read (and as we also had to realise)the
hardware requirements are quite strict and it is very hard to figure out
if some hardware will work in advance.
So, does anyone have experience with setting up a realtime system (ETS)
on a standard PC? Moreover, can anybody give some advice which hardware
(manufacturer and product-id) will work?
Thanks in advance
Oliver

Actually I read all of those documents. First we tried to set up a
realtime system using RTX (realtime extension for windows), trying to
get our hardware to work in a realtime environment on top of windows.
It was really hard to get at least something to work, where something
means running labview without hardware on one of the several PCs we
tested. But we didn't get access to any of our NI-devices, where at
least the 6251 should have worked referring to the specs.
So, after calling the NI support they suggested using ETS on a separate
machine instead of using RTX. We then downloaded the programm to check
several PC for ETS capability. But all we tried got stuck somewhere in
the testing procedure (they are probably too new and maybe ETS is not a
friend of AMD )
So now, we are going to buy a PC for ETS, but after what we experienced
with RTX and also with ETS so far, we feel that it could be hard to get
the right PC or PC components. Because of this I'm looking for advice
regarding hardware (manufacturer, partnumber etc.).

Similar Messages

Suggest Embedded PC for Labview realtime

All,
It appears that I am not going to be able to use a cFP/cRIO for my applications am going to need to migrate (Back) to an embedded PC.
Previously I have been using windows xp embedded with a labview .exe which has been diabolical to be polite, windows is not a nice embedded environment.
I am investigating the use of NI LabVIEW Real-Time Deployment License for Desktop PCs and would like to see if anyone has any recommendations.
My application uses Comms (485/422) to interface with it's world, so built in comm ports are preferred.
Speed needs to be >800 mhz 0-50 degrees c.
Advantech have a range that may be suitable but I am interested to see if anyone has actualy successfuly done it before heading down a dead end path.
Problems tend to be drivers for ethernet or plug in cards
Thanks
iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT

Hi Timmar,
Thanks for the detailed post. As you already stated, whenever converting a PC to a LabVIEW Real-Time ETS PC, the biggest thing to watch out for will be compatibility of Ethernet chipsets and processors. Since you don't have the Advantech embedded PC yet, you can check for hardware compatibility by referencing this Knowledge Base article: http://www.ni.com/white-paper/8239/en
If you do get your hands on any of the embedded PC or if you have a really awesome friend at Advantech, you can run a test program through a USB utility which can test out the hardware compatibility for you: http://digital.ni.com/public.nsf/allkb/9209361E17708D548625744A007FF353
With these two documents, you can get started on building your own LabVIEW RT PC.
Aldo A
Applications Engineer
National Instruments

How do I set up LabView RealTime ETS on a desktop computer?

I have been trying to set up the LabVIEW Real-Time 8.0 OS on a desktop computer. I have read the the "Requirements for a Desktop PC as a LabVIEW Real-Time target and followed the instruction in the installation manual "Using Desktop PCs as RT Targets with the LabVIEW Real-Time Module".
The problem I have run into is that there is a built in Network card on the motherboard (Intel Pentium 4 processor ) and the boot program is unable to recognize the Intel Pro/100S Network card I have added (PCI slot 1). The error message is: "Unable to configure primary network device". I can not figure out what settings I have to change in the BIOS to get the thing working (BIOS version EV91510A.86A.0444)
I have done the following:
- Formatted the drive as FAT32 & used the Desktop PC Format Harddrive Disk
- Set the Serial Harddrive ATA/IDE Configuration to legacy
- Disabled Legacy USB Support
- Disabled onboard & legacy FP Audio
any help would be appreciated

I have tried turing off the built in NIC from the BIOS setup but I could not get it to work. I disabled the Onboard LAN but this did not seem to do anything. I am not sure what I have to change in the BIOS setup in order to make the PCI network card the primary network device.

Using Labview realtime module in RTAI

hello everyone,
i want to use Labview realtime module in RTAI for real time applications beacuse of it's free source and very good performance. is it possible to do this work?
if it is, can anyone introduce some same case study or something similar to this?
Solved!
Go to Solution.

amirsaman wrote:
hello everyone,
i want to use Labview realtime module in RTAI for real time applications beacuse of it's free source and very good performance. is it possible to do this work?
if it is, can anyone introduce some same case study or something similar to this?
I don't think that is possible for anyone outside NI. LabVIEW realtime supports at this time only Windows as development host and as target only National Instruments hardware with specifcally targeted OSes or the Pharlap ETS system on x86 systems with a somewhat specific hardware configuration. Using RTAI as target OS for LabVIEW realtime applications would require first some modifications to the LabVIEW realtime plugin to support this new platform.
Also none of the LabVIEW realtime files created for either the NI platforms running VxWorks or Pharlap OS, or the Pharlap ETS system woud be possible to get deployed to a RTAI system, as they are not compatible. You would in the first place have to port the whole slew of shared libraries that make up the realtime LabVIEW runtime system on one of these targets to your RTAI system which is basically a completely new LabVIEW target platform that you can only create with quite a bit of effort from the LabVIEW source code. It's not really impossible for NI as most of the LabVIEW code is written quite platform independently but it would be a combination of the compile settings for current LabVIEW realtime, with settings to produce LabVIEW VxWorks realtime targets with some extra Linux settings. Yet it would be by far not trivial and some of the parts are actually hardware specific drivers which have to be ported too, and limit the possibility of what RTAI hardware could be used even further. In short not something that would make any commercial sense to NI as they would have to invest a lot of resources without any possibility to sell extra hardware.
And hell is freezing up before NI releases LabVIEW source code in any form that would give non-NI employees access to it!
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Job Opening for Labview Test engineer and Senior Labview Test engineer in Honeywell Automation India Limited,Pune

Job Openings at Honeywell Automation India Ltd., Pune
Honeywell Automation India Ltd, Pune is currently looking Senior and Junior Labview Test Engineers.
Position -Permanent
Job Location: Pune,India.
Job description is as follows:
For Senior Labview Test engineer Position: (4-6 years)
Primary Skills:
• Should be an expert in NI Labview.
• Should be familiar with various NI toolkits and add-on modules like NI LabVIEW Report generation toolkit, LabVIEW RealTime/FPGA toolkit etc
• Experience on hardware test automation using NI and third party hardware
• Candidate should have knowledge on various protocols such as RS-232, GPIB, MODBUS, Ethernet,Devicenet, Profibus using NI LabVIEW.
• Should have functional test development experience using various NI hardware modules (PCI, PXI, cDAQ, cRIO etc)
• Ability to work independently with our clients for gathering requirements, preparing various test plans, coding & testing, Installation & support
• Candidate should have good communication skills, presentation skills and interpersonal skills.
• Knowledge of analog and digital electronics that includes schematic reading and understanding
• Knowledge on Database, driver development, communication protocols
Niche Skills:
• Knowledge of Project Development Life Cycle
• Experience in NI Teststand/ LabWindows
• Good Communication Skills
• Requires cross-functional engagement with Operations, Engineering, and Manufacturing.
• Project deployment at client site
• CLD (certified labview developer)
Added Advantage:
• Ready valid passport / VISA will be a plus point.
• Candidate need to travel abroad depending on project requirements.
• Shorter joining period.
• Ready to relocate to Pune
For Junior Labview Test engineer Position: (2-4 years)
Primary Skills:
• Candidate should have worked in NI LabVIEW for atleast 2-4 Years.
• Should be familiar with various NI toolkits and add-on modules like NI LabVIEW Report generation toolkit, LabVIEW Database toolkit,etc..
• Should have functional test development experience using various NI hardware modules (PCI, PXI, cDAQ, cRIO etc)
• Candidate should have good communication skills, presentation skills and interpersonal skills.
• Knowledge of analog and digital electronics that includes schematic reading and understanding
• Knowledge on Database, driver development, communication protocols
Niche Skills:
• Requires cross-functional engagement with Operations, Engineering, and Manufacturing.
• Project deployment at client site
• CLAD (certified Labview associate developer)
Added Advantage:
• Ready valid passport / VISA will be a plus point.
• Candidate need to travel abroad depending on project requirements.
• Shorter joining period.
• Ready to relocate toPune,India
Please Forward your updated profile to [email protected]

Dear Sir,
With reference to the website of your company I came to know that there always are the vacancies for the suitable candidates and hence I wish to apply for the same.Currently working in hydraulic environment I am approaching you through this application with great enthusiasm, that I have scope and chance to show my ability and contribute my efforts in well direction. I am enclosing here with my complete Curriculum Vitae .
I am currently working with M/s Minar Hydrosystems PVT. LTD. in Nagpur which is one of the largest manufacturers of hydraulic/pneumatic cylinders, jacks etc. I am In charge for quality department having complete knowledge of instruments with level II in non destructive and automated non destructive techniques. Also handling SAP module in current company with effective administration.
If you need further information regarding my candidature please do write/call me.
Thanks & Regards
Rushikesh P. Deogade
Nagpur, India
Ph.:- +91 9923858523
Attachments:
B.E. Mechanical with 3 years exp as a QC Incharge.doc ‏25 KB

Using dll in labview realtime

Hi to all,
I would like to know the best way how to open a file DLL in labview.
I created this dll with matlab, real time-workshop, nidll.tlc
after that I have to use these dll in a real time VI, for using that into a cRIO,does it exist a tutorial in order to explain the procedure?
thank you

No it is not! As it uses Cygwin to port the Gnu Unix tools so they can run under Windows. Cygwin is a great tool but had always a hard time to run on newer Windows versions than what was released at the time a particular Cygwin version was created.
The VxWorks versions that NI used for their realtime controllers is very old. There is no hope that someone would go through the trouble of trying to backport the Cygwin bugfixes since that time to this Gnu toolchain, nor has VxWorks any interest in creating a new Gnu toolchain based on modern Cygwin and Gnu tools for older VxWorks versions.
NI has moved since away from using VxWorks. In fact the only reason they went with VxWorks, was because Pharlap ETS was not compatible with the PPC CPU and at that time the choice in powerful x86 compatible CPUs for embedded applications was VERY small or actually non-existent.
As you can see Open source observes similar rules as commercial software. Don't spend much time in trying to make old stuff work on new versions. In fact commercial software usually makes a lot more effort to be portable across different versions. In Open Source the general tenor is, I want feature X, that requires GCC Y, which will only work with glibc x.z.v. Don't spend time in trying to make any of these work with older versions too, or update older applications to work with newer OSes etc. If you want Windows 7 or 8 you have to have Cygwin 1.7.something and that will usually require GCC 4.something and a myriad of other dependencies. The gnu toolchain for VxWorks 6.3 which is used on the NI controllers since LabVIEW 8.5 uses GCC 3.4.4.
Considering that LabVIEW 8.5 was released in 2008 and the VxWorks tools to create the OS for the controllers obviously even quite some time before that, but Windows 7 RTM was only in July 2009, there is not much you can complain about the fact that those tools do not run on Windows 7 or 8.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Reg: vacancy for LabVIEW developer in Bangalore, Chennai and Delhi with (1-6) years experience

Recruitment Process for LABVIEW: Tele Interview in case of outstation candidates. Bangalore candidates will have to first come for a Written Test (Technical + Analytical), 1-2 rounds of direct technical interview.
Degree/Branches: B.E / B.Tech in Electronics / EEE / E&C / E& Instrumentation .
ROLES AND RESPONSIBILTIES OF ASSOCIATE ENGINEER-SEG:
Development
1. Responsible for developing software for the project/module allotted to you with smooth coordination and smooth handing over of the work executed by one to another member in case of change of projects.
2. Expected to work on multiple projects, project dead line, adhere to coding guidelines and update your progress on the project on a weekly basis to your immediate supervisor.
3. Developing the software strictly as per the requirement specification, design and Bug free.
4. Responsible for building a trouble-free system to the satisfaction of the customer.
Installation
1. Responsible for installation of hardware and software at customer site for coordinating with the vendor and Manager – Sourcing to see that works done by the vendor is as per requirement specification
Customer Support
1. Responsible for providing support to the customer on the system supplied by the Captronic Systems in the past as well as present.
2. Attends to the support case within 48hrs(local) / 96hrs(outstation ) / 96hrs(out of warranty) of reporting and collecting the Support Closure Report from the customer and submit it to the SBU-HEAD
3. Informs Support executive with Support Status, Action Taken and Support Closed On
Training
1. Responsible for providing training to customer on the systems supplied by Captronic Systems.
2. Responsible for in-house training to newly recruited engineers.
Testing
1. Responsible for testing code developed by you, by another developer and testing entire system at the customer site.
2. Responsible for testing hardware supplied by Captronic System and log the test report on the hardware test register.
Sales Support
1. Expected to travel with sales team to provide support to sales-team in proposal making at short notice and perform flawless pre-sales system and requirement study.
General
1. Expected to take part in technical sessions and keep yourself abreast with the recent product released and technical advancement made
2. Expected to become domain expert is at least one field and to constantly improve coding style and knowledge.
Quality
Responsible for implementing the project methodology and quality policy of the company for all activities under your purview
Interested candidates may forward your resumes witheir current CTC and notice period to [email protected] . Salary is never the Constraint.

SANDU SUNITHA
D/o.S. Venkateshwarlu,
H.No:11/57, Kothapeta,
Maruthi Nagar,Dhone,
Kurnool (Dt.),
Andhra Pradesh.
E-Mail:[email protected]
Mobile : 91-9963586292/08884822259
Date: 09/ 05/ 2013
Respected Sir/Madam,
I have done my masters in Control Systems Engineering in Electrical
branch from Malla Reddy College of Engineering. I am a well organized
person, with good knowledge about the subject, able to do
multitasking, able to work within a team and have excellent
communication skills. As a good Engineer and excellent team player I
can handle the responsibilities and challenges of the post of an good
engineer to its fullest.
I have worked for 6 Months as Project Trainee in CSR INDIA PVT LTD. My
responsibilities in that institute include Testing, Reporting and
Debugging, Updating the bugs as a trainee fresher. I was a part of the
team that designed MERCURY TESTING TOOL, world's Best Automation tool
today. I tested the model and executed the changes.And i had worked as
Project Engineer in FUSION ELECTRONICS on Wonder ware SCADA. Presently
working as Project Scientist in NAL (National Aerospace Laborateries)
under Research and Development of IVHM(INTEGRATED VEHICLE HEALTH
MANAGEMENT) Project on MATLAB/SIMULINK ,Labview ,Wireless Sensor
Networks,WatchDog and Testing.
Here is the list of the documents enclosed with this cover letter.
1. Resume
I hope that you find these of worth. I assure you that if selected; I
will not let you down and would prove to be an asset for your reputed
industry.
Sincerely yours,
SANDU SUNITHA
Attachments:
SANDU_SUNITHA(29_Apr_2013).doc ‏176 KB

Looking for LabVIEW Developer with 2-3 years of experience for Mumbai based Company

Software Plantation, Mumbai is currently looking for LabVIEW Developer who can contribute to the development of automated test, data acquisition, and control systems using National Instruments LabVIEW.
This position is located at Lokhandwala, Andheri West, Mumbai.
Requirements:
Applicant must meet the following criteria:
2+ years of LabVIEW experience.
Should be from Engineering background.
Knowledge of various communication protocols like RS-232, Modbus, USB, etc.
Knowledge of NI DAQ hardware boards.
Automated test, measurement, data acquisition, and/or control experience.
Good at documentation.
Knowledge of Software Development Cycle
Must be able to meet objectives as directed.
Ability to effectively work independently.
Ability to contribute and work in a team environment.
Ability to adapt to changing requirements, rapidly absorb new concepts, and apply them effectively.
Good communication skills.
CLAD certified developer will be preferred. Knowledge of C/C++, Linux is an added advantage.
If your background and qualifications match this position, please send your resume via email with subject line as: 'LabVIEW Developer Application'.
E-Mail: [email protected]
Note: Please do not post your resume on the job forum. Mail it to the above mentioned email ID.

Kindly send me your resumes on [email protected]

Hi, can someone help me how can i connected my multimeter to my pc with rs232, because my computer can´t recognize the device, i mean the multimeter, is a multimeter keithley serie 2400, and i already downloaded all the drivers for labview even the VISA

hi, can someone help me how can i connected my multimeter to my pc with rs232, because my computer can´t recognize the device, i mean the multimeter, is a multimeter keithley serie 2400, and i already downloaded all the drivers for labview even the VISA

Marco,
Here are some suggestions:
1) Check the manual the Keithley manual to see how to configure the RS-232.
    On some models you need set Factory defaults to USER and turn on the RS-232.
    Also there may be a setting for SCPI which you want on (probably on by default).
2) On your PC - open Device Manager. See if a COM port exists and is functional.
     You must get this working before continuing.
      You can set the COM port parameters by right clicking and selecting Properties.
     (On some PCs the onboard ports can be disabled in the BIOS)
3) If step two was OK, open MAX (Measurement and Automation eXplorer).
    On the left side, click on Devices and Hardware.
    Click on Serial and Parallel.
    Go to the COM port you found in Device Manager.
    Open a VISA Test Panel.
    Now I don't have one I can look at right now, so this is general idea:
   Configure the COM port to match the Keithley settings (should be OK if step 2 worked)
   Go to the (I think) Input Output tab (you want to send a command)
   The command string input should already have a *IDN? entered, if not, type it in.
   Click on the Query button to send the command and check the response.
   If you get an ID string back (Company name, Model, FW Version ...) then it works.
   (Disregard an error saying it did not get enough charcters back.)
I hope this helps,
steve
Help the forum when you get help. Click the "Solution?" icon on the reply that answers your
question. Give "Kudos" to replies that help.

Job openning for Labview developer with fiber optical experience

job openning for Labview developer with fiber optical experience

I am a Test Engineer with 10 years LabVIEW experience, as well as TestStand, VB6, C, Assembly language, programming
also experienced with electronics/hardware, and a talented problem solver
I worked for CIENA Corporation writing automatic testing software for their fiber optic products (DWDM)
Available due to plant closing
please contact me at [email protected]
thank you

M Series code for Labview

I am using the PXI-6230 on Linux. I downloaded the MHDDK for NI-Visa, and the code uses C, along with some examples that are in C. There are some good examples, but I need working code that will work in Labview. Are there some examples that people have for the PXI-6230? Or is there some way I can use the C code for Labview? Any help is appreciated.
Thanks,
Thomas Pham

Hi Thomas,
The DDK is a set of reference examples for writing a device driver from scratch. Since most write-it-yourselfers expect to be running in an uncommon environment (where LabVIEW cannot run) or need to undergo some kind of final validation or peer review (where not everyone may have LabVIEW available), a text-based implementation provides them a faster "see how it works" starting point for those purposes.
When programming for the 6230 from LabVIEW, you have a few options available.
You can use the existing C++ chip objects in the DDK but manipulate them into a shared library (a .so) so that you can call the Library Function Node in LabVIEW [1].
You can use the register I/O palette [2] in VISA and transcribe the C++ chip objects into LabVIEW.
Expand the DAQmx Base driver [3] to make the extra RLP calls for the 623x (explained below).
All three are somewhat challenging, and you will also need some additional information about the specifics of programming for the 623x sub-family. Since they have isolated IO, some of the registers are re-purposed for enabling and disabling the isolators. There are several threads in this forum [4] about the 623x-specific calls that need to be made.
If you choose to exapand the DAQmx Base driver, you will find that a bug in the code will make the system think your 6230 is a 6222 [5]. In addition the 623x-specific RLP calls, you'll need to correct and differentiate the 6230 from the other M Series boards.
[1] Call Library Function Node -- LabVIEW Help
http://zone.ni.com/reference/en-XX/help/371361G-01/glang/call_library_function/
[2] Register Access Functions -- VISA Help
http://zone.ni.com/reference/en-XX/help/371361G-01/lvinstio/high_level_reg_acc_func/
[3] DAQmx Base 3.4 for Linux
http://joule.ni.com/nidu/cds/view/p/id/2128/lang/en
[4] 623x RLP Considerations
http://forums.ni.com/t5/forums/searchpage/tab/message?location=Node%3A90&q=623x#message-list
[5] DAQmx Base 3.4 incorrectly attaches to the 6230
http://decibel.ni.com/content/message/20827#20827
Joe Friedchicken
NI VirtualBench Application Software
Get with your fellow hardware users :: [ NI's VirtualBench User Group ]
Get with your fellow OS users :: [ NI's Linux User Group ] [ NI's OS X User Group ]
Get with your fellow developers :: [ NI's DAQmx Base User Group ] [ NI's DDK User Group ]
Senior Software Engineer :: Multifunction Instruments Applications Group
Software Engineer :: Measurements RLP Group (until Mar 2014)
Applications Engineer :: High Speed Product Group (until Sep 2008)

Has anyone ever written a driver for LabVIEW for Omega CN9500 process contollers w/Modbus protocol over RS485?

Omega has a protocol manual to facilitate this on their web site

Jay,
Most folks use an OPC Server, such as Lookout Protocol Drivers (sold under package "IA OPC Servers") to communicate with devices using the Modbus protocol from LabVIEW. The KnowledgeBase below describes this method in detail.
Drivers for Communicating to PLCs, RTUs, and Other Industrial Hardware"
As for direct Modbus protocol VIs for LabVIEW - I have never personally used them, but I have seen many Developer Exchange posts in the past where folks have used and recommended them. Simply search this developer exchange for "modbus AND labview" and numberous discussion threads on this topic will be returned.
Regards,
Greg
Caesar
Applications Engineer
National Instruments

Using Keyboard or Mouse in LabView RealTime

Hi,
I would like to know whether keyboard or mouse can be used as input in LabView RealTime. If yes, can anyone explain me how to get the input coming from the keyboard or mouse?
Thanks

Hi e_Rik,
Could you explain what you are trying to do a little further? Currently the only real-time targets that can have a keyboard or mouse plugged into them is a PXI chassis or a desktop ETS system.
The following links also touch on the subject as well.
http://forums.ni.com/ni/board/message?board.id=170&message.id=147602&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=170&message.id=149424&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=180&message.id=27461&requireLogin=False
I double checked and currently there are no keyboard or mouse VIs that work on real-time targets. You may be able to get around this by finding a serial keyboard and mouse and using VISA calls. Hope that helps clarify, and have a good day.
Brian K.

Interfacing of hardware with labview

can u pls tell me the steps for interfacing a hardware wiht labview........ i mean to say the detailed descrpition....... for ex: interfacing keithley sourcemeter with labview....... pls do give me a detailed steps of interfacing

Start by downloading the LabVIEW driver, which is available in http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=7117
You should also make sure that the VISA driver is installed. It should have been part of your LabVIEW installation.
Or a shortcut location from the Keithley website is here:
http://www.keithley.com/support/data?asset=51950
Message Edited by Ray.R on 04-11-2010 05:42 PM

NATIONAL INSTRUMENTS LABVIEW REALTIME V6.1, NI-488.2 V2.01, CNC CADCAM

IAR, NATIONAL INSTRUMENTS LABVIEW REALTIME V6.1, NI-488.2 V2.01, CNC CADCAM
IAR,
Microwave Design Office 2002, Cadence, OrCAD, Protel, FPGA, VHDL,
Natinst, Xilinx, Siemens Simatic, Labview, metrowerks codewarrior8
[2CDs],
other 20 gigabytes/week software for pc and mac
send email for catalogue

Hello,
Which driver have you on your computer ? You can see them in MAX >> Software. Which is version of ni-visa, ni-488.2 ?
What kind of protocol do you want to use : gpib, serial, parallel ?
What ahhpens in AMX when you test your communication ?
What are error code and error string ?
Regards,
Isabelle
Ingénieur d'applications
National Instruments France

Hardware for LabVIEW Realtime (ETS)

Similar Messages

Maybe you are looking for