LabVIEW for PC 104?

For Data acquisition and some minor processing with a PC 104 system,I plan to use LabVIEW.Is it possible to load the LabVIEW application to the Single Board Computer and execute the program like we do on a Desktop/Laptop.If yes,Any specific version or module of LabVIEW to be used or can a exe done with the laptop with LabVIEW Developer Suite works good.Please suggest.

if you have an API for the pc104 daq cards yes. A simple DLL should be enough then and you can implement your own DAQ drivers.
A quick search on Goolge shows that EagleDAQ has 104 boards and provides LabVIEW functions to interact.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Similar Messages

  • LabVIEW for Linux and hardware registers

    Hi all,
    I'm considering using LabVIEW for Linux in an upcoming project based around
    PC/104. As the only way to communicate to the PC/104 module inputs is via
    hardware addressing, I need to know whether it is possible to directly
    address hardware in LabVIEW for Linux. If not can you suggest a way of doing
    this? Also does LabVIEW for Linux and say RedHat make for a more stable
    system than LabVIEW for Windows and Windows 2000/XP?
    Thanks in advance.
    Regards,
    Shane Broadbent
    - remove the 'nospam' to reply by e-mail

    Hi Shane.
    I know that you can address hardware in Labview for Linux: I do it with an NI6071e,k 6602 and 6503. I don't know specifically about the PC/104, but I imagine it can also be done.
    Generally you can talk to the hardware registers using code interface nodes (CINs) in Labview. In the CIN you just use a 'write()' command. I don't think there's anything more to it than that. Creating the CINs is no trouble at all.
    Don't know about stability of Labview with Linux compared to windows, all though others tell me stability is pretty much the same.
    hope this helps and good luck!

  • I am trying to integrate simulink model (.mdl) file with SIT of Labview for RCP and HIL purpose. I am using Labview 8.6, Simulink 6.6 with RTW 6.6 and RTW embedded coder 4.6 ,Visual C Express 2008 and Visual C++ Express 2008.

    I am trying to integrate simulink model (.mdl) file with SIT of Labview for RCP and HIL purpose. I am using Labview 8.6, Simulink 6.6 with RTW 6.6 and RTW embedded coder 4.6 ,Visual C Express 2008 and Visual C++ Express 2008. I have selected system target file as nidll.tlc,make command as make_rtw and template nidll_vs.tmf. When I try to generate .dll file I get the following error.
    Attachments:
    SITProblem.JPG ‏101 KB

    Hi,
    No . I could not solve the issue. Presently we are using microautobox (from Dspace)for doing the RCP.
    Himadri 

  • LabVIEW for ARM 2009 Read from text file bug

    Hello,
    If you use the read from text file vi for reading text files from a sdcard there is a bug when you select the option "read lines"
    you cannot select how many lines you want to read, it always reads the whole file, which cause a memory fault if you read big files!
    I fixed this in the code (but the software doesn't recognize a EOF anymore..) in CCGByteStreamFileSupport.c
    at row 709 the memory is allocated but it tries to allocate to much (since u only want to read lines).
    looking at the codes it looks like it supposed to allocated 256 for a string:
    Boolean bReadEntireLine = (linemode && (cnt == 0)); 
    if(bReadEntireLine && !cnt) {
      cnt = BUFINCR;    //BUFINCR=256
    but cnt is never false since if you select read lines this is the size of the file!
    the variable linemode is also the size of the file.. STRANGE!
    my solution:
    Boolean bReadEntireLine = (linemode && (cnt > 0));  // ==
     if(bReadEntireLine) {    //if(bReadEntireLine && !cnt) {
      cnt = BUFINCR;
    and now the read line option does work, and reads one line until he sees CR or LF or if the count of 256 is done.
    maybe the code is good but the data link of the vi's to the variables may be not, (cnt and linemode are the size of the file!)
    count should be the number of lines, like chars in char mode.
    linemode should be 0 or 1.
    Hope someone can fix this in the new version!
    greets,
    Wouter
    Wouter.
    "LabVIEW for ARM guru and bug destroyer"

    I have another solution, the EOF works with this one.
    the cnt is the bytes that are not read yet, so the first time it tries to read (and allocate 4 MB).
    you only want to say that if it's in line mode and cnt > 256 (BUFINCR) cnt = BUFINCR
    the next time cnt is the value of the bytes that are not read yet, so the old value minus the line (until CR LF) or if cnt (256) is reached.
    with this solution the program does not try to allocate the whole file but for the max of 256.
    in CCGByteStreamFileSupprt.c row 705
     if(linemode && (cnt>BUFINCR)){
       cnt = BUFINCR;
    don't use the count input when using the vi in line mode. count does not make sense, cnt will be the total file size. also the output will be an array.
    linemode seems to be the value of the file size but I checked this and it is just 0 or 1, so this is good
    update: damn it doesn't work!
    Wouter.
    "LabVIEW for ARM guru and bug destroyer"

  • Font Smoothing in LabView for Linux

    Hello,
    I was wondering if anyone has been able to get their fonts in LabView for Linux to be either smoothed using Gnomes subpixel smoother for LCDs, or any other type of anti-aliasing. I currently can use truetype fonts in LabView, and for the most part they do look pretty decent.. btu they are not smoothed at all. Every single application I have loaded has smooth fonts other than LabView. Please let me know if anyone has managed to get this working... and if so, how.
    I am currently using Gentoo with all of my packages updated less than a month ago, with LabView 8.2
    Thanks for any info!

    Unfortunately, we do not support fonts on your operating system. Hopefully another customer is more familiar with this.
    Message Edited by Support on 10-04-2007 01:33 PM
    Charlie M. CLD

  • How do you add a third party sensor to LabVIEW for Lego Mindstorms​?

    I recently purchased an IR Sensor from Mindsensors (DIST-Nx-Long-v3) which I need for a SLAM (Simultaneous Localization and Mapping Application) that I am developing using the LabVIEW for Lego Mindstorms software.  I installed the Mindsonsors IR Sensor, and it works under NXT-G and RobotC, but am having trouble finding a way to get LabVIEW for Lego Mindstorms to install the sensor.
    The Mindsensors website gives the following instructions for installing the IR Sensor:
    1.Unzip the folder mindsensors.com LVEE
    2.Open a blank vi in LVEE
    3.On the Block Diagram Go to Tools->Advanced->Edit Palette Set...
    Unfortunately, on the Block Diagram of the LabVIEW for Lego Mindstorms, there is no "Advanced->Edict Palette Set" under Tools.
    As an alternative, I consulted the documentation that came with LabVIEW for Lego Mindstorms.  The Schematic Editor of LabVIEW for Lego Mindstorms lists several sensors, i.e. the Lego Mindstorms sensors and several Hi-Teach (HT) sensors, but there are no procedures listed in the documentation for adding other third party sensors to the Functions Palette.
    So, how does one go about adding a third party sensor to LabVIEW for Lego Mindstorms?

    Hi Ethan,
    As you can see from my Word document, I am a little light on the proper terminology.  That's because LVLM comes with inadequate documentation.
    I have already followed your recommended protocol for installing a 3rd party sensor (in fact, its the protocol recommended by Mindsensors) with the application set in the Remote Mode (.lvrbt), and it does create a sub-palette with all the Mindsensors functions on it.  But when I drag the Mindsensors icon to the Block Diagram and select "Distance Sensor," the Distance Sensor (an IR sensor) doesn't work (even though the Mindsensor's Distance Sensor does work with NXT-G, RobotC and LVLM under other circumstances (see below)).
    If I repeat the above process with the application set in the Direct Mode (.vi), I also get the sub-palette with all the Mindsensors functions on it.  When I drag the Mindsensors icon to the Block Diagram and select "Distance Sensor," the Distance Sensor does work.
    What I need for my mapping application is for the Distance Sensor to work in the Remote Mode.  I called NI tech support and the first engineer told me to simple drag the Mindsensors Functions (.vi) onto the Block Diagram.  I did this, but when I selected the Distance Sensor, the icon appeared, but the sensor did not work.  Since I have no idea what's under the hood of the vi or a function, I assumed that simply dragging the vi/function onto the desktop didn't install the vi/function properly.  I went back to the Applications Engineer, and he confessed that he did not understand the LVLM product.
    My frustration is being punted to new people, none of whom so far (other than you, of course) understand LVLM.

  • Can't control color sensor in LabView for Mindstorms

    Hello!  New here.
    I'm trying to bone up on LabView via "LabView for Lego Mindstorms" for a possible job in the near future and I've run into a problem early on.
    I'm programming my Lego brick in LabView to simply turn on the color sensor which is easy enough:  I build a while loop and inside that I have a color sensor block connected to a text block which displays light intensity from the sensor in text on the brick.  I compile and run and the sensor turns on and I can read the constantly updating intensity on the brick.  That part works fine.  Now I'd like to control the light sensor (which doubles as a light source with color LEDs) on the LV front panel.  The book I'm using (LabView for Lego Minstorms) says I need to right click the sensor block on the "generate light" input and choose "Create-->Control" from the resulting menu.  A Boolean pushbutton should appear connected to the sensor block in the Block Panel and a push button should appear in the Front Panel.  That's not what happens.  Two things are different here.
    1) I have no "generate light" port to right click on.  This is probably due to using a more up to date version of Mindstorms than the book uses.  That's a book/Mindstorms issue that probably can't be solved here but hopefully solving the next issue will make this one irrelevant.
    2) I right click and create the control, but instead of creating a Boolean push button as the book predicts, it creates a "BrickReference.lvclass" icon.  It connects okay with the light sensor and a corresponding block is created in the Front Panel but it is a paper weight as far as I can tell.  I can't do anything with it.  There is no button to push, no slider, knob, radio button etc. and I can't seem to change it into anything that works in any way.  I delete it and create a no kidding Boolean push button from the library but it won't connect to the light sensor and so I can't compile.  So now I'm a bit stuck.
    I've looked for "Brick Reference" on line in the context of LabView class and have found little or nothing that tells me about its definition or how I can use it to control the light sensor via the Front Panel.  The help section with the software isn't much help either and yet I'm sure there must be a way to control a simple Lego light sensor from the Front Panel for debugging and other purposes.
    If you know what I'm doing wrong or if you know an end run around this issue that will enable me to control a Mindstorms brick from the Front Panel in this way, please let me know.
    Thanks!
    Solved!
    Go to Solution.

    Try posting in the Lego forum.
    http://forums.ni.com/t5/LabVIEW-for-LEGO-MINDSTORMS-and/bd-p/460

  • LabView for ARM - MCB2300 Audio

    Hi, and thanks for reading!
      My name is Chuck and I'm an undergrad ME student taking a mechatronics course. We were asked to create a proximity alarm with the MCB2300 and an IR proximity sensor. I have the entire program running correctly, but this lab has brought up a couple questions about how to better implement audio with the LabView for ARM processors.
      I understand how interrupts work, and I've seen a couple examples online of using an interrupt with a timed loop, but I believe the current version of LabView (2010) doesn't support that feature any more. I had a couple questions about how to get a feature similar to this to work with LV 2010.
      I was thinking I could have the proximity trigger enable an interrupt that I could use to generate higher quality audio than I am already making with a While - Timer loop. However, I'm not sure how to make an increment in the interrupt VI without using some form of a loop. The solution I'm thinking of at the moment is to make a For loop run once and to have an incrementing integer separate from the loop iteration (which would only go from 0 to 1) that stores its most recent value in the shift register.
      My other question is about playing a sound file through the MCB2300. I wrote a VI that reads a .wav file and writes each sample as the output needed to drive a speaker, but that decompression turns a 10KB .wav file into a 300KB text file. I also don't have a way to really load the text file onto the board. Is there any reasonable way to go about this? I found an example online that processes audio data using the MicroVision software, but I don't want to learn a new language to implement this.
      Sorry for such a long post, I just had a couple questions and was looking for some feedback. Any help would be greatly appreciated.
    Thanks so much!

    charlestrep91 wrote:
    Hi everyone,
    I just got my Labview for ARM cortex M3 evaluation kit and I can't download a simple program to the target. I'm using the Keil ULink 2 programmer and I get this error when compiling/downloading:
    [4:23:16 PM] Status: Error
    SWD Communication Failure
    Error: Flash Download failed  -  Target DLL has been cancelled
    Detail: [UVSC_PRJ_FLASH_DOWNLOAD, MSG: 0X100A, STATUS: Ex.] (1) 
    Status: FLASH download error.
    I have read about this error and NI simply refers to Ulink2 user's guide which has this description for this error:
    Serial Wire Debug communication is corrupted. The target SWD interface is not working properly. Mainly caused by the target: debug block not powered or clocked properly. Avoid Deep-Sleep modes while debugging. Lower the Max Clock frequency in the ULINK USB-JTAG/SWD Adapter section.
    I have tried to "Lower the Max Clock frequency in the ULINK USB-JTAG/SWD Adapter section" but it didn't resolve the problem.
    I have also tried to download the program using the usb port on the dev board but instead I get this error:
    [4:51:22 PM] Status: ErrorUnexpected error occurred.
    [Source: Target is in debug mode
    Detail: [UVSC_PRJ_ADD_GROUP, MSG: 0x1002, 
    STATUS: 0xA] Code: 10]
    What am I supposed to do with that?? I'm wondering if the dev board is defective. And this was supposed to be plug and play...
    Any help is greatly appreciated!
    I'll ask the obvious question, are you intending to use SWD or just download through the JTAG.  Check your settings.  I have not used the ARM with LV, but can you download anything using the Keil software?  Give that a try.  That may tell us where the problem lies.  Try to duplicate your settings in LV from the Keil sw.
    Reese, (former CLAD, future CLD)
    Some people call me the Space Cowboy!
    Some call me the gangster of love.
    Some people call me MoReese!
    ...I'm right here baby, right here, right here, right here at home

  • In LabVIEW for Linux, cannot link to a shared library file (.so).

    Hello all,
    I'm having trouble using the Call Library Function Node within LabVIEW for Linux (using Ubuntu).  I can configure my Node correctly, and it sees the available function within it with all the proper parameters, but when I close the Call Library Function dialog box it does a quick search and asks me to Find the Shared Library Named "mySharedLibraryName."  If I select it again, it merely repeats this over and over until I cancel.  Has anyone seen this before or know what is causing this?  The .so file was compiled using gcc++ - is there anything specific that should have been included (does it need a header file)?  Could some missing file be causing this?
    Thanks,
    Jason

    The elf shared library format is a supported feature of all Linux distributions since about Linux 1.0 or earlier. So it is not really an issue that Ubuntu wouldn't support shared libraries as used by the LabVIEW Call Library Node. Since the Call Library Node seems to be able to see the exported functions during selection of the function it also doesn't seem to be a problem with proper export of the symbols.
    This leaves over some dependencies of the shared library on some other shared libraries including C runtime libraries. Was the shared library compiled on the system you try to use it? If not you may have an incompatibility of the C runtime library version used on the system that was used to compile the shared library and your Ubuntu system you try to load it.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • 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 

  • I seek exemple of codes in labview for programming a robot

    Hello,
    I have a project and i seek codes programming in labview for move an lego mindstorm.  It's for have an idea on how use labviex for move or turn the robot
    Thanks 

    Have you tried the vi's contained in the NXT Toolkit?  It has most of the NXT-G blocks, including Move and Motor.

  • Where can I get a trial version of LabView for Unix

    I'm using a Solaris v2.61 at work and I'm trying to gain remote accsesss to a TDS 3032 Tektronix o-scope. Where can I get a trial version of LabView for Unix?

    At least for LV 7.
    You may get NI to give you a LV 6 version for Solaris or Linux. Send an e-mail to sales and see what they say.
    http://sine.ni.com/apps/we/nicc.call_me?p_action=c​ountry&p_lang_id=US
    2006 Ultimate LabVIEW G-eek.

  • Troubleshooting labview for motion control

    I use labview for establishing a 1-d straight line movement for a small dc-motor, i have a PCI-7430 controller and UMI_7774, but after i wrote the code on labview, an error appear,contains the following: error 70006 occured at load velocity(the sub vi called load velocity), and then the message show the possible reasons for this as follows: an invalid axis or other resource ID
    Attachments:
    1-d motion.doc ‏87 KB

    Ni-motion in labview,
    I see that this issue is already being
    discussed in a different thread.  In the future, if you have two similar
    questions, please keep them within the same thread so that we can answer them
    in a concise manner.  Thanks.
    Best regards,
    Vu D

  • Is there a Labview for Linux

    Dear friends,
    I just know that there is a Labview for Linux. I have a Labview for
    Window. I dont the Labview for Linux is free. Can anyone tell me how
    much it should be? Does it have an educational discount?
    Thanks
    Tony Cheng (EE Dept. of City University of Hong Kong)
    email :[email protected]

    There is a LabVIEW of Linux. The NI online catalogue has the pricing info
    etc and you can find it at: www.ni.com/catalog, for LabVIEW for Linux I was
    taken to this page:: http://sine.ni.com/apps/we/nioc.vp?pc=bymn〈=US&cid=1382&p_0=Linux&x=26&y=10
    Cheers,
    Kamran
    Cheng Lee Lung wrote:
    >Dear friends,>>I just know that there is a Labview for Linux. I have a Labview
    for>Window. I dont the Labview for Linux is free. Can anyone tell me how>much
    it should be? Does it have an educational discount?>Thanks>>Tony Cheng (EE
    Dept. of City University of Hong Kong)>email :[email protected]>>

  • How can I configure labview for communication with Modbus I/O?

    i read a article about configureing Labview for communication with modbus I/O in NI developer zone, but it was written for Labview 6, how can I configure it with labview 7. it seems there are some difference. Thanks!

    In both LabVIEW 6 and 7, you connect to modbus using Lookout Protocol Drivers (LPD) and then communicate to LPD using the tag engine of LabVIEW DSC or through DataSocket.

Maybe you are looking for