Custom Hardware with LabVIEW

Hi all,
We have a custom made DAQ card (ISA one). We are using "C language" to communicate with this card . Now we want to use LabVIEW for the same purpose. Is there any protocols we have to follow to do this? or any additional steps we have to take for this? Please guide us.
I am new to this thing. So please bare with me.
Thnaking you.
Vishal Shah

That would depend on how you access the card. You can use the LabVIEW "Inport" and "Outport" VIs to talk directly to a card (if you know what the I/O base address is). It may be better to build a C .DLL and the LabVIEW "Call Library" VI. Use what works best for your system and card.
Rob

Similar Messages

Integrating custom PCIe hardware with LabView

Hi, I am new to LabView so appologize if question is in the wrong place.
I have a custom PCIe acquisition card that I want to use in LabView environment to postprocess some data. So far the board has been used successfully with its windows drivers and VS.NET software. What is the process for setting up a device like that in LabView? Can LabView use the COM object windows driver just like a Visual Studio project would? If yes, is there a document that explains how this is done?
I have worked with NI's own instruments where the driver is provided and seamlessly integrates into the LabView, but I am a bit lost with this custom non NI board.
Thank you.

Thanks. I tried searching that site for examples... but this is a board that our company has developed (software defined radio) and I am certain no one has written any drivers for it yet. Thats the problem statement that I am trying to research. What would it take to make the board we designed compatible with LabView. Since this is a Software defined radio platform, LabView offers some useful functions that can be used to postprocess and analyze data captured by our card.
Ideal goal is to have LabView module capture data from PCIe buffer allowing for further processing (filtering, FFT, demodulation, etc...). I would appreciate if you can direct me to some examples or literature on this topic.
Thanks,
Anton

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

Can I target the STM32 Primer2 hardware with LabVIEW for ARM

The STM32 Primer2 hardware looks very cool. Can LabVIEW for Arm target this hardware? From looking at the list of ARM devices supported by LabVIEW, this would appears to be a Tier 2 device (ARM Cortex-M3) with no support for TCP/IP or IO.
Can anyone tell me the feasibility or effort required to get TCP/IP, IO, and maybe even display support for this device?
Message Edited by Jim Kring on 09-11-2009 10:46 AM

Have you ever said something you wish you could take back after having time to reflect upon it? Another forum I like, http://newsbusters.org lets the author edit his posts for a short time. Maybe NI could to that and I would not be pulling out my foot so often.
Well, perhaps I was a bit more "colorful" than I meant to be. Frustration does that to me sometimes. Still the idea of a strong rope covered with disgusting risks does get the point across magnificently. I just wish I had saved it for something more suitable.
Let me think back to some of the problems I've had in which I've lost hours trying to figure out...
1. Can't use the Wait ms function. It halts the program. Express wait works fine. It was sprinkled throughout which made it hard to isolate.
2. Some sub VIs don't run unless they are checked as inline code. I don't yet understand why.
3. At the beginning of my main vi there was a small cluster in which I filled the data from an SD card file. I used a constant of the cluster on the input of the Bundle function, but because my program and variable sizes were near the max I changed a number of variable representations to save memory. ...But I didn't replace the constant. The program started exhibiting really strange behaviors. I couldn't even get a simple state machine to run. I was reduced to commenting out (disable structure) sections to find the problem before noticing the coercion dot on the input to the bundle (The dot against the red string color doesn't stand out very strongly which is why I missed it). Apparently it overwrote memory since the older cluster was significantly larger than the new.
4. Spent a lot of time trying to get the SD card to work with SPI functions. Even though I read that 2009 supported SD card file services I didn't intuitively understand how to wire up since the Open/Create/Replace function has a ref num output which actually connects to the file(use dialog) input of the read and write functions.
5. Had a problem with breakpoints and probes not working. That apparently was caused by item #3.
6. Typo bug in the Arm_irq.c file LM3Sxxxx_GPIOCAHandlerP to LM3Sxxxx_GPIOCHandlerP
Some of these are of the rope variety. A few are actual bugs. All probably could have been solved in moments had I a local guru. Anyway, I've spent hours and my hands hurt. I hope to have this little project working on the LM3s8962 today and after some hardware changes will port it over to the Primer2... Hopefully...
This forum has been a real help... especially your quick responses.
regards to all,
David

Custom hardware connectivity

I Have this below mentioned hardware Embedded PC
Analog Modules (TEWS 865-10) Analog Modules are connected to Embedded PC through backplane connectors. This TEWS module don’t have any labview drivers but this hardware is running fine on C++.
There will be some way that I can access this hardware through OPC server. I have also viewed a webcast at NI website which says that access your custom hardware through Labview. So How I can access my modules Inputs and outputs in Labview.

Hi Arrowminds and All,
Good Morning and I hope your well today.
Arrowminds has contacted NIUK Support regarding his issues.
Here is a summary of the support so far,
Looking at the TEWS website, Installing the
Device Driver allows you to interface with the device in any environment -
including LabVIEW. Here is a link to the section of the device driver
manual I am talking about,
http://www.tews.com/products/SW-Manuals/TIP/TIP501-SW-65,property=PdfFile.pdf
In Section 3 - Device Driver Programming, the article explains that the,
"The standard file and device (I/O) functions (CreateFile, CloseHandle, and
DeviceIoControl) provide
the basic interface for opening and closing a device handle and for
performing device I/O control
operations.
All of these standard Win32 functions are described in detail in the
Windows Platform SDK
Documentation (Windows base services / Hardware / Device Input and Output).
For details refer to the Win32 Programmers Reference of your used
programming tools (C++, Visual
Basic etc.)
This sort of information on the type of dll and the function prototypes is
what you require for your device. If the device isn't on the website
anymore you need to contact TEWS and ask them for the information. Ask for
the Device Driver and Documentation to allow you to use the Device DLLs.
Then using LabVIEW you can use these DLLs. Below are some resources to help
you and explain how to do this.
Using Existing C Code or a DLL in LabVIEW
http://decibel.ni.com/content/docs/DOC-1690
Calling External APIs
http://zone.ni.com/reference/en-XX/help/371361E-01/lvexcodeconcepts/calling_external_apis/
How Do I Call a Dynamic Link Library (DLL) from LabVIEW?
http://digital.ni.com/public.nsf/allkb/DCB90714981A1F148625731E00797C33
Thanks,
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!

Problems with labview 7.1

hi all,
i had posted this question before but no one replied so i am posting it as a new message.
i am using labview 7.1 and wanna use fp-1000 and fp-tc-120(2 of them) to measure 16 temperature values from t-type thermocouples.
i connected the fieldpoint hardware with labview through RS-232 and also installed fieldpoint 5.01(with support for labview 7.1) in my system. but MAX does not detect the device. why is this happening. i checked the port settings and they are fine.
if the following info helps then i must mention that a pci-gpib card and a scxi daq system is also attached to my pc. i also made sure that the addresses are different for each one of the hardware devices.
something more, previously i was using labview 8.2 on which the device was working fine. but i had to migrate from one pc to another on which there is labview 7.1 and i cannot install labview 8.2 on this system. so please let me know what to do?

Hello Kuna,
Looks like your other forum post was replied to. In order to maintain the efficiency and organization of NI Discussion Forums, please refrain from creating duplicate posts in the future.
Cheers,
Emilie | Applications Engineering

Labview freeze when accessing a custom menu with data on the clipboard

This one has got me stumped: When selecting a custom menu item with data on the clipboard the GUI freezes. Freezes are longer for more data and longer for older versions of Labview. I wrote the test code, attached, but the example "Menu Selection Demo.vi" shows the same behavior.
Running Labview 2011 here are some freeze delays for my laptop (a bit slower machine) with various amounts of text data on the clipboard:
Clipboard size        Delay
1.3MB                   2.1 sec
2.6MB                   4.9 sec
3.8MB                   17.2 sec
14MB                    253.3 sec
The delay appears to be non-linear. A doubling of the clipboard data size more than doubles the delay and a tripling of the clipboard data size produces a delay of almost 10X! Things are also much, much worse on my ancient version 8.2.1 (over a 40 second freeze for 1.3MB and it goes up from there).
Note that the freeze also occurs on programs with a custom menu when exiting. This would seem to suggest it might have something to do with the timeout, but why timeout should vary with clipboard size and not with the value wired to it makes this feel even more like a bug in the custom menu functionality.
This seems to be related to known issues in Labview 2011 #39604 49UBP4LE (http://www.ni.com/white-paper/13168/en#39604_by_Date) that was first reported in version 8.2.1. This known issue relates to Labview freezing when large amounts of data are copied from Labview to the clipboard. No fix has been implemented since this was originally reported in 2007.
This freeze also occurs when shortcuts to menu items (such as Ctrl + L) are used when large amounts of data are on the clip board.
Thus far this has been 100% repeatable and I have not been able to find a way around it. I also haven't found anything else similar on the forums or on the web. It appears to be a GUI freeze with Labview still running in the background, which is also odd.
My work-arounds at this point are either to not use the clipboard (bad), programatically clear the clipboard several times each second (worse) or remove all custom menu functionality and replace those functions with onscreen controls. So, for now, I'm removing custom menu items because my users need the clipboard and I can't have massive delays making my data acquisition code look crashed.
Any ideas would be helpful. This one has me scratching my head...
Attachments:
Menu_Clipboard_Lv2011.vi ‏17 KB

Well, doing Microsoft Word, Excel and what else on a computer that is used to run an important production test, is a very bad idea. There is no way that you can guarantee, that one of these applications is not causing some interruption to the currently running time critical task. Word and Excel and just about any other computer application can crash, lock up the computer or eat your breakfast while you are doing seemingly harmless things.
The issue with the clipboard in LabVIEW is indeed a problem that exists for a long time and I hope they fix it sometime, but the fact remains, that you should NEVER use a computer for other tasks while you run a test or other manufacturing related application on it, when a failure of that application can cost you more than a few pennies.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

For Experts: Why does LabView cause System reboot while accessing hardware with driver?

Hello NI Developers!
I use LabView 7.1 under Windows XP
I have a programm console application which accesses through Jungo Windriver PCI-E board.
This program works fine - and performs DMA data transfer between PC and Board's memory.
In order to implement this console application work together with LabView I did following:
1) Added this function inside the source:
_declspec(dllexport) void LVMainFunction(uInt32 *IntValue);
_declspec(dllexport) void LVMainFunction(uInt32 *IntValue)
    AllocConsole();                   //Open new console window
   SetConsoleTitle(L"Debug Window"); //Set a title for console window
    freopen("CONOUT$","a+",stdout); //redirec standard output stream to current window so
                                    // so we are able to see "printf" outputs
   freopen("CONIN$","a+",stdin);    //redirec standard input stream to current window so
                                    // so we are able pass inputs from keyboard
   main();                          //Call applications main function which does all the work
2) Compiled this new source as DLL library
3) Call LVMainFunction(...) function from LabView using Call Library Node
In the result: Executing VI - opens new console window, shows debug outputs and receives keyboard inputs.
It works fine till the last function, which perform DMA data transfer - and reboots PC.
1) Why does this happen?
2) I understand that opening console from Call Library Node, attaches together this console window and running VI. So If I close one of them - both windows closes.
   So does LabView have somekind of restrictions of accessing Hardware's functions?
I can read Board's resource information and view size of memory on board, interrupt functions and other information about device, but when I try to reach
DMA my system reboots. And I understand that this should be some kind of LabView problem, cause I tried different implementations, even without use of
console window - and the result is the same.
3) Should I split the program in to two separate processes and perform data exchange using Sockets or Pipes techology?
Thank you in advance!
ACiDUser
Message Edited by ACiDuser on 11-13-2008 09:37 AM

Hello!
At LAST!!!
I solved this problem!
From the beginning I was following National Instruments manual on how to build DLL with external IDE:
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/building_library_project/
Set the Struct member alignment control to 1 Byte.
Now this option caused my PC to reboot!
So could someone explain why this happened? and If it is a bad tip, so it's better to remove from manual. Then other people will not have such problems as I did
- wasting 2 monthes of time determining the problem.
I changed it to Set the Struct member alignment control to DEFAULT.
and now everything works fine.
Regards
Message Edited by ACiDuser on 11-13-2008 11:14 AM

Where can I found hardware to get analog signal from VCR and work with labview and then sample this signal in very high frequency?

I am trying to build a Digital Video Recorder using Labview. The problem is that I found that Labview sample the signal in the order of milisecond. I wanted it to be in the order of microseconds. Also I am looking for a cheap Hardware solution if it is possible

Your question does not make a lot of sense to me, so I will just point out a few things.
1. The PCI-1411 works well with VCR signals. It has a BNC connector as well as a S-Video connector. The price is under $1000, so it is fairly reasonable. The amount of time you save getting it to work with LabVIEW is worth any extra cost.
2. The PCI-1411 is sampling three colors at 30 frames per second, with an image resolution of 640x480. This is the best resolution you are likely to get from a VCR signal. The sampling rate for each byte in the image is about 28 MB/sec. This is in the microsecond range that you are looking for, I think. If you are only interested in the raw signal instead of the image, you could look at the high speed digitizing boards NI sell
s that acquire at higher rates.
If this information isn't really what you were looking for, perhaps you could clarify your question.
Bruce
Bruce Ammons
Ammons Engineering

Im looking evaulation hardware to get trained in interfacing with labview. kindly suggest

Im looking for any Hardware (NI or third party Hardware) in which i can get trained with interfacing with hardware with different communication techniques like Can, I2c, as well 232 and 485.. and Few DAQ interface... So kindly let me know any such hardware from any vendor is available.. Kindly suggest.

The best place to start would probably be the NI LabVIEW Basics 1 & 2 courses. They cover some of these concepts. You can find out more at http://www.ni.com/training. Other wise if you search the knowledge base on the NI Developer Zone you can find tutorials for lots of hardware bus interfaces, like this one on the CAN bus.
Jason
Wire Warrior
Behold the power of LabVIEW as my army of Roomba minions streaks across the floor!

Looking for hardware programmable with labview

We are pretty new to labview. We plan on switching to labview for many of our control systems we develope and will utilize panel PC's. We still have many applications that we use a traditional plc and these do not require a GUI of any sort. We would still like to find a solution to switch completely over to labview but I am having a hard time finding a low cost hardware solution to run a labview program. Does anyone have any good ideas? Thanks in advance
Solved!
Go to Solution.

Trinity32244 wrote:
... In all reality I think it is a long shot to find any hardware that labview can run on to replace a $80 plc but figured I would ask in the forum. As for the I/O needed it varies for each job so I would most likely have to find a remote I/O solution that is customizable to connect to the controller. We are proficient in ladder logic as well but it would just be nice for us to all be able to program with one language instead of both labview and ladder. Thanks for any suggestions
I don't think you will find a hardware device that you can target LabVIEW with for $80, but maybe you should think about Arduino. There is a LabVIEW library for interfacing, and there are various 'shields' that you can customize for your I/O...
https://decibel.ni.com/content/groups/labview-interface-for-arduino
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

Interfacing Beckhoff EK1100 with LabVIEW without using any other hardware

Hello All,
I'm new to Beckhoff & I have EK1100 with EL2809 & EL3054. I want to interface with EK1100 with LabVIEW with PXI or cRio or any other hardware.
Is there anyone who can explain how?
I'm using the following sofwares & drivers.
LabVIEW2012
EtherCAT Acquisition Driver
EtherCAT Acquisition Library for LabVIEW
TwinCAT ADS Library v3.0.3
Please suggest at the earliest.
Regards'
Love Diwan |+91-9810013576

cross post
Jesse Dennis
Design Engineer
Erdos Miller

Error, in Getting started with Labview. Chapter 3, part 4.

Hi.
Still struggling on, trying to find the time to work through the "Getting Started with LabVIEW" document.
Only 19 days left to go, and I'm still only in chapter 3!...
Right. In the "Saving Data When Prompted by a User" exersise, part 4...
4.   Right-click the Signals input of the Write To Measurement File
      Express VI and select Insert Input/Output from the shortcut menu to
      insert the Comment input.
Problem is, that option is greyed out, so not available!...
I did what the instructions said, I right clicked on the "Signals" input, and it doesnt do what it says on the tin!
Any pointers?   Please don't mention search the help, I've crashed the entire LV environment 3 times now, trying to search for something in there. It's OK if it finds someting, but it seems to bomb at times, when there is some ambiguity when searching.
Also, I won't be able to do anyting with any replies for a day or two, as I have to go up country to a customer, and mess about with hot oil, high volts, and lots of RF. It never ends.   (I've still got the day job to do, while trying to fight my way through this "evaluation". 30 days of "Use" would be better, than 30 calendar days for some of us.)
Regards.
Dave Baxter.
Technical Manager: AR-UK Ltd.
AR United Kingdom
OK... Who let the smoke out?

Hi Dennis, and everyone else..
That is not how it looks when first dropped on the BD. On my machine, it is partialy expanded by default, after you clear the Configure dialog that pops up ocupying most of the screen.
Again, if it makes a difference to the way the Right Click shortcut menu works, it should be documented in the Getting Started document, especialy as it seems to be a critical point.
OK, explain this...
I've just rubbed out the save to file VI, cleaned up the broken wires etc, and then planted a new one on the BD. Once I cleared the Configure dialog that covers up most of the screen before you see it the first time, the VI was partialy expanded. I forget the exact list, but "Signals" was not at the top.
I did *EXACTLY* the same again, deleted it, cleaned up, and then planted a fresh new one. That DID appear that time with nothing but the "Signals" item showing, and two down caretts below that, indicating more items.
So......
Why the different behaviour each time, on the same BD, in the same session. Some underlying working data not being correctly initialised when invoked? Of course, that never happens, right? ('C' programmes eh?)
Trying some more, it seems the behaviour loosley depends on just how close to the edge of the While loop grey border you place it.   Odd.   I have a 1280x800 screen to play with, and a 1280x1024 second screen I use for the Getting Started document. That is the absolute maximum I can have, due to hardware limits.
I also find, that if you fully expand the "Write to Measurement File" VI block, then fully collapse it, then expand it again, all the items in that list have changed places! Why?
I had noticed earlier that there is no uniformity in the layout of even the items common to many if not all VI blocks (error in, and error out to name but two) Sometimes one is above the other, sometimes the other way round, sometimes they are not even ajacent to each other. Has that been done as a source of minor ammusement or something?
Talking to another colegue here, who just wandered in to see how I was getting on with this. Seems he also has tried the introductory entry into LV (V8.something) in the past. But he too, found too many things that behaved differently from one time to another, so abandoned it as a lost cause, then decided to learn how to use Visual Basic with NI-GPIB IO instead.   Not without issues either he said, but at least it all behaves exactly the same, each and every time.
End of the day now...
Regards.
Dave B.
OK... Who let the smoke out?

Electrical Engineer with LabVIEW Experience, Windsor, CO - Start Immediately

National Analytics, Inc. is looking for a talented and motivated Electrical Engineer with a proven electronic hardware design and development background to complement our team of system integration experts. Experience with RF and DC power supplies or high power, high voltage inverters is highly desirable.
Located in beautiful Northern Colorado, National Analytics has become a mainstay in remote monitoring & control, systems integration and engineering solutions. Our services include software engineering, hardware engineering, mechanical and electrical design, contract manufacturing & test, project management and training. Some of our recent customer markets include:
* Government
* Aerospace
* Nuclear, Fossil & Wind Power
* Environmental Remote Monitoring
* Defense
* Medical
* Oil & Gas
* Manufacturing
Eligible candidates must be hard working, eager to learn, and able to adjust to rapidly changing project demands. We provide a fast-paced, fun work environment that promotes personal growth with challenging opportunities.
Requirements:
1. BSEE
2. Proven electronic hardware design and development experience
3. 3 years minimum LabVIEW programming experience required.
4. Experience in analog and digital circuit design, schematic capture, board level PCB layout, design, and validation
5. Embedded microcontroller programming
6. FPGA programming
7. Experience in design and development of automated test equipment for products with analog, digital, and embedded software content
8. Ability to operate a variety of test equipment (oscilloscope, function generator, spectrum analyzer, etc.)
9. Altium or similar electronics design package
10. Demonstrated proficiency with LabVIEW
11. Ability to solve complex technical problems independently
12. Good verbal and written communication skills
13. Ability to work in fast paced, high-pressure environment
Please include professional references and salary expectations.
Due to government contracting requirements, only US Citizens will be considered.
Learn more about us at http://www.nationalanalytics.com
No phone calls please.

Hi Dan,
I am the manager for the Customer Education department for NI Canada. We are looking for Engineers with extensive LabVIEW/LabWindows experienced to become certified as Professional Instructors of our courses. We are currently looking for someone experienced developing Real-Time applications, TestStand and CVI.
We do not offer a full-time position, rather are Contract work.
If you are interested and have the experience, feel free to contact me for further details.
Thanks,
Berenice Tostado
National Instruments Canada
Customer Education Manager

Electrical Engineer with LabVIEW Experience - Needed Immediately - Windsor, CO

National Analytics, Inc. is looking for a talented and motivated Electrical Engineer with a proven electronic hardware design and development background to complement our team of system integration experts. Experience with RF and DC power supplies or high power, high voltage inverters is highly desirable.
Located in beautiful Northern Colorado, National Analytics has become a mainstay in remote monitoring & control, systems integration and engineering solutions. Our services include software engineering, hardware engineering, mechanical and electrical design, contract manufacturing & test, project management and training. Some of our recent customer markets include:
* Government
* Aerospace
* Nuclear, Fossil & Wind Power
* Environmental Remote Monitoring
* Defense
* Medical
* Oil & Gas
* Manufacturing
Eligible candidates must be hard working, eager to learn, and able to adjust to rapidly changing project demands. We provide a fast-paced, fun work environment that promotes personal growth with challenging opportunities.
Requirements:
BSEE
Proven electronic hardware design and development experience
Experience in analog and digital circuit design, schematic capture, board level PCB layout, design, and validation
Embedded microcontroller programming
FPGA programming
Experience in design and development of automated test equipment for products with analog, digital, and embedded software content
Ability to operate a variety of test equipment (oscilloscope, function generator, spectrum analyzer, etc.)
Altium or similar electronics design package
Demonstrated proficiency with LabVIEW
Ability to solve complex technical problems independently
Good verbal and written communication skills
Ability to work in fast paced, high-pressure environment
Please submit your resume via email to [email protected] . Please include professional references and salary expectations.
Due to government contracting requirements, only US Citizens will be considered.
Learn more about us at http://www.nationalanalytics.com
No phone calls please.

Hi
I completed my M.S in electronics engineering and working with GE in INDIA since June 2005. I have total 20 months of experience with LabVIEW and have the follwoing skills.
Intermediate-to-advanced knowledge of LabVIEW.
Familiarity with data acquisition concepts and hardware.
Ability to troubleshoot electrical and electronic systems at the module and equipment level.
Discipline and organization with respect to software maintenance and version management.
Ability to work both alone and with colleagues to solve problems and to weigh the merits of differing approaches
you can reach me at [email protected]
Thanks & Regards
Anil Punnam

Custom Hardware with LabVIEW

Similar Messages

Maybe you are looking for