Help with Labview for Linux applicatio​n - datalog to XML format

Hi,
I am working on an application that makes use of a PDA for instrument control and data acquisition, and all our code has been written with the use Labview PDA 8.2. The instrument data is returned wirelessly to a remote server, and one of the specifications we set early in the project was the data would be returned in XML format in line with Labview's inbuilt XML schema.
Unfortunately, this XML funtion is not available on Labview PDA! We have made a change to return the data in Labview's 'Datalog' format, and then we now intend to run an additional application on the server to convert this information to XML before passing the data to our customer's software.
We have successfully done this with Labview for windows, but our customer's server is Linux based.
Is anyone aware of someone (or a company) who would be able to take our existing 'datalog-to-XML' vi and compile it for Linux? The program is really simple, and I would hope that all the functionality we use is supported in Labview for Linux.
Thanks,
Mark

Hi Mark
LabVIEW VIs that are developed in a Windows environment can be used in a Linux version of LabVIEW. As long as the VIs have not got Windows specific features such as ActiveX or Windows dll call you can run the VI in Linux. Also there maybe some specific drivers that are not supported under the Linux environment (see link). The VI will simply be recompiled in Linux. The Linux user must have a copy of the Linux LabVIEW Development System installed though.
http://digital.ni.com/public.nsf/websearch/35D2B5E​483A001A18625716B005BE464?OpenDocument
Kindest Regards
YatinM
NIUK & Ireland

Similar Messages

  • How to interface greek fonts (iso-8859-7) with labview for linux 8.5.1

    I am trying to interface an Labview Linux application with greek fonts ,how i can achieve this out ? I want to use iso-8859-7 icharset. I am using a gentoo distro. Can anyone help me  ?
    thanks....
    Ελευθερία σημαίνει ότι μαθαίνεις να έχεις απαιτήσεις μόνο από τον εαυτό σου, όχι από τη ζωή ή τους άλλους

    Hi Sak1s,
    Are you looking to create labels and captions with Greek fonts?  You may be interested in the LabVIEW Help topic on Localizing VIs. 
    Jennifer R.
    National Instruments
    Applications Engineer

  • Arial font substitution for (LabVIEW for) Linux

    Hello,
    as LabVIEW was not capable of keeping the font size and spacing constant when running a VI under different Windows versions, screen resolutions etc, I have never used the "application", "system" and "dialog" font options in LabVIEW but have fixed all fonts to Arial 14 pt. This worked wonderful on all Windows systems - without that unnerving problem that control lables overwrite each other and things like that (what always happened when using LabVIEWs "application" font option).
    Now, when running the same VIs under LabVIEW for Linux, the font looks terrible, as there is no Arial font in Linux. Does somebody know an easy way to solve this problem without setting all fonts to "application font" in LabVIEW? For instance, any "ini file type" setting in Linux telling the operating system which font to use when Arial is not present, or any free font substitution that we could add to our installer routine that the operating system would use automatically instead of Arial?
    Best regards,
    Gabs

    Unfortunately, your problem is a version of a generic problem faced by GUI programmers of all types - how do you handle varying system fonts?  There are various solutions, based on who your customers are.  You are using one of the easy ones that works well until you start doing cross-platform development.  The main options are, in order or increasing complexity:
    Lock the font to a specific font and size.  This works well if your customers are limited to a single platform and are not visually impaired (do not want to use large fonts).
    Use system fonts and allow extra space.  This is a compromise that only works in most cases.  Use about 50% extra for small strings and 10% - 20% for larger strings.  This also gives you extra space for localization, should you need it.  Visually impaired customers will run into space issues, because large fonts can be 2X or more larger than the default, system fonts.  Note that the different Windows variants have different font sizes as well.  Windows Vista increased default font sizes, especially for some Asian languages, such as Japanese.
    Query the font size on entry into a GUI VI and rescale everything appropriately.  This is hard, since it must be done for every VI with a GUI.  Some system dialogs do not handle large fonts well, so you will probably end up replacing them with your own versions to get good appearance.  You could probably write a system to handle this sort of scaling, but to my knowledge, no one has (please prove me wrong ).  I have always used custom code when needed.
    No one really does this well.  Change your system font on a Windows OS to large fonts and note all the problems you run into.  I would recommend option 2, unless you have a lot of extra time.  Your customers will love you if you pull off option 3.
    More tips to help.
    Do your development on the platform with the largest system fonts.  If this is not possible, change the LabVIEW system fonts of your development system to match the largest size you support.  I usually develop using 13pt Verdana, since it is one of the largest of the variable spaced fonts.
    Check your work by using large fonts in Windows.  If it looks good there, it will probably be OK for most uses.
    Good luck!
    This account is no longer active. Contact ShadesOfGray for current posts and information.

  • LABVIEW FOR LINUX

    Hello,
    Presently i am a user of labVIEW 7.1 and 8.2.1 windows version.
    and also working on following hardware.
    SCXI-1001 12 chassis,
    SCXI-1125,SCXI-1124,SCXI-1160,SCXI-1162,PXI-1001,PXI-6251,PXI-6602,USB
    1600,USB 6602,PXI-1044,PXI-6133,PXI-8187,PXI-9257.
    since i am facing the problem of virus and sudden restarting of system,I am planning to switch over to linux version of linux.
    what is ur comment on my deceision?
    which version of linux OS will support all above mentioned products.
    what are the other advantages i can get from LINUX version?.
    Wil i get full programming help as available in windows?
    Can we easily learn the programming by reding the help?

    Hello chandhuu,
    Most of your hardware will be supported except for the USB devices.  The readme file for DAQmx 8.0 for Linux lists which devices are supported and by which Linux OS.
    The LabVIEW 8.5 readme file for Linux would also be helpful, along with this KnowledgeBase article, which lists which Linux OS versions support National Instruments software and drivers.  You will find that programming in LabVIEW for Linux is basically the same as in Windows, so you shouldn't have any trouble switching over if you are familiar with Linux and with LabVIEW.  Personally, I am not too familiar with Linux so I feel much more comfortable with LabVIEW for Windows.  What about just having a dedicated Windows PC that you can take off the network and use with LabVIEW so that you don't have to worry about viruses?
    Regards,
    Clint M
    National Instruments

  • LabVIEW for Linux licensing

    Hello all,
    I have LV6i for Linux installed on a Slackware distribution. I would
    like to know why there is no serial number associated with the LV
    installation. Usually when you install on Windows machine the
    installatin will prompt you for a serial number. This is not the case
    with LV for Linux. Entering a serial number is never mentioned.
    The reason why I ask is because I'm a little confused on how this could
    be dealt with during an audit, which I've never experienced. If I have
    LV for Linux installed on several machines how would an NI auditor
    determine that I have excess licenses? Not that I plan on doing this
    .... unless it's legal with the Linux installation. This certainly isn't
    implied in the license agreement but perhaps the
    re's an exception with
    Linux.
    I'm trying to find yet another good reason for my employer to move to LV
    for Linux.
    Thanks,
    Kevin

    > I have LV6i for Linux installed on a Slackware distribution. I would
    > like to know why there is no serial number associated with the LV
    > installation. Usually when you install on Windows machine the
    > installatin will prompt you for a serial number. This is not the case
    > with LV for Linux. Entering a serial number is never mentioned.
    I am not a lawyer and I am not claiming to be an authority on our
    licensing agreements. As someone else suggested, you should consult your NI
    salesperson (or your own attorney) if you're unsure.
    The licensing for LV for Linux is the same as for our other versions,
    which is per seat. To run LabVIEW on five different computers, you need to
    buy five licenses.
    The reason the LabVIEWs for UNIX don't ask for a ser
    ial number is
    practical. Typically in the UNIX world, LabVIEW is installed by an
    administrator who is different from the end user. We never bothered to
    create a tool for the administrator to enter the serial number, and we can't
    count on the end user having write access to the LabVIEW directory to store
    the serial number. If this becomes an issue (e.g., your auditor won't let
    you use LV for Linux because of this), we can try to address it.
    I hope this helps.
    Brian

  • LabView for Linux - Ready?

    I am setting up a research lab and would like to use linux for all my
    computing needs. I was wondering how peoples experiences with LabView on
    Linux have been? I would be using it to control instruments via GPIB
    and to take data using DAQs. Is it stable and reliable, or is it too
    early in its development to make the switch from LabView on windows? How
    is NI's LabView support? Thanks for the help.
    G. M. Steeves
    California NanoSystems Institute
    U. C. Santa Barbara

    Geoffrey,
    The LabVIEW for Linux FAQ page has many of the answers you are looking for.
    LabVIEW for Linux is very equivalent to the Windows versions with the exception of ActiveX and NI-DAQ. Data Acquisition is supported on Linux through the Comedi. This is a third party, open souce driver that supports many of National Instruments' DAQ boards. Also, the only toolset available for Linux at this time is the Internet Toolkit. For more information go here.
    Support is done at the same level as for Windows and can be done through all of the same ways.
    Randy Hoskin
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

  • 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!

  • 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

  • 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

  • Is there a way to use Labview for Linux for IBM AIX 5.1.

    I think any application built for linux can run on the AIX 5.1 if the application is recompiled on the AIX 5.1. So theoretically NI can just recompile there Linux version of Labview on the AIX 5.1 and it will work. Is there a possibility that NI will port Labview for AIX 5.1.

    I think that the use of LabVIEW for linux is platform independent as far as hardware. I believe that as long as you are running a compatible GUI (I believe XWindows and KPT??? are two that are recommended - check ni.com/linux for more information. So, for your purposes, as long as you can install the proper GUI, and then LabVIEW for Linux, you can then run, code, compile, and deploy applications on the AIX 5.1.
    I am personally VERY interested in knowing about your success (or failure, should that unlikelyhood occur) on Linux. If you browse the topics, there is actually one on non-windows useage of LabVIEW. I am currently setting up my first Linux machine at my home office, and am very curious to know how other people do with this 'adventure into unc
    harted territory'. The only documented useage I have seen is in Gary Johnson's newest edition of Power Programming.
    Good luck, and please keep us posted. I sense that I am the only LabVIEW for Linux fan besides yourself. But please feel free to post to this thread, and to the topic.

  • VXI support under LabVIEW for Linux

    A potential client contacted me regarding a small project using VXI hardware under Linux. I'm considering using LabVIEW for Linux but I'm not too clear on NI's VXI driver support and whether they have a VI library for the particular hardware. I contacted NI tech support over the phone but they didn't have any answers. BTW, I've used LV with PCI and ISA DAQ boards under Windows and Linux but I've never used VXI.
    Here is the hardware in question:
    PCI/VXI-MXI-2(8026) - PCI to VXI bridge
    VXI-AO-48XDC - 48 channel analog output board
    VXI-MIO-64XE-10 - multifunction DAQ board
    Anyone know what's involved in building a LV app for this system under Linux, i.e. what's NI's HW driver and LabVIEW support?
    -kevin

    Kevin,
    National Instruments has NI-VXI for Linux. The driver provides support for the PCI/VXI-MXI-2(8026), and VXI embedded Controllers. The NI-VXI driver also provides the programming API that will allow you to communicate with the VXI boards in your system.
    You can find a KnowledgeBase that shows what versions of Linux are currently supported by NI-VXI here.
    If you have never used VXI before I should note that it is different from using a PCI DAQ card. You might want to read this here which will explain a little about VXI.
    The LabVIEW for Linux system requirements can be found here. I should note that LabVIEW will work on the 2.6 kernel, however since you are looking at NI-VXI you will need to use the 2.4 kernel anyway.
    Hopefully this answers your question, but if you have any further questions feel free to ask!
    Shawn B.
    National Instruments
    Use NI products on Linux? Come join the NI Linux Users Community

  • What LabVIEW for Linux based on ?

    Whar is the way LabVIEW 7 for Linux communicate with
    DAQ boards ?
    Is it the same as on Windows ?
    Can I write application on 'C/C++', that use only low level library that LabVIEW based on ?
    It this possible on Windows with Visual C?
    With LabWindows it is possible.
    More precisely, I may use only NI-DAQ library and do
    nothing with IDE of LabWindows.
    But if I right, neither LabWindows nor NI-DAQ/NI-DAQmx is't for Linux.
    I have some experience with LabWindows/CVI, but nothing
    with LabVIEW.
    What is principal difference between them in low level communication with DAQ boards ?
    Thanks.
    Andrey

    AndreyCherepenko wrote:
    > Whar is the way LabVIEW 7 for Linux communicate with
    > DAQ boards ?
    > Is it the same as on Windows ?
    No! LabVIEW for Linux does not come with any DAQ libraries. There are
    basically two options at this time:
    You can download the NI Measurement Hardware DDK from NI and the
    according LabVIEW VI libraries or you can use Comedi.
    > Can I write application on 'C/C++', that use only low level library
    > that LabVIEW based on ?
    The NI Measurement Hardware DDK (and Comedi) is a C based interface with
    precompiled binary libraries which you can use from your C/C++
    application. The NI provided VI libraries allow access of that API from
    within LabVIEW.
    > It this possible on Windows with Visual C?
    The NI Measurement Hardware DDK is also available for Windows in which
    case it consists of a number of DLLs, header files and examples. They
    are callable from any C application. But this DDK is in principle a low
    level API which often requires you to go down to register level directly.
    You can also call NI-DAQ (the API LabVIEW uses on the Windows platform)
    from your C compiler, Visual C or whatever, but that API is not
    available on non Windows platforms (oh well there was an old version for
    MacOS and Sun Solaris but that is I don't know how many years old).
    > With LabWindows it is possible.
    > More precisely, I may use only NI-DAQ library and do
    > nothing with IDE of LabWindows.
    LabWindows just provides FrontPanels to the NI-DAQ libraries. It is not
    a LabWindows implementation of NI-DAQ but instead it accesses exactly
    the same libraries LabVIEW does or your own C application would.
    > But if I right, neither LabWindows nor NI-DAQ/NI-DAQmx is't for Linux.
    No! They aren't and except hopefully for a limited DAQmx library
    probably never will be.
    > I have some experience with LabWindows/CVI, but nothing
    > with LabVIEW.
    > What is principal difference between them in low level communication
    > with DAQ boards ?
    LabVIEW is a graphical programming environment whereas LabWindows CVI
    uses C programming. The difference between LabWindows and a standard C
    compiler is the standard built in support for many libraries used in
    Test & Measurement, Data Acquisition etc, the extensive library of
    graphical user interface components and the FrontPanels provided for all
    the library functions. Nothing you couldn't do with a normal C compiler
    nowadays, but they are very tightly integrated in CVI and generally
    working together well.
    As an experienced LabWindows CVI user it may be better to stay in that
    environment than starting to use LabVIEW. LabVIEW is similar in what you
    can do, a lot more comfortable for the casual programmer, but on the
    other hand also a little patronizing in more advanced features. As much
    as it is comfortable to generally not have to worry about memory
    allocation and code frameworks before you even can start to implement
    your first algorithme, it can get in the way when you try to do high
    performance operations as you not only don't have to worry about memory
    allocation but you have in fact limited and only indirect influence in
    how memory is allocated.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Calling DLL on LabVIEW for Linux

    I have a vi that calls a dll made with Visual C++ on windows enviroment. What are the steps for calling this same dll on Linux ? Do we need to generate another dll?

    In article <[email protected]>, Labviewguru wrote:
    > First, I don't know if LabVIEW for Linux can even call a DLL. I
    > suspect that since this technology (as obsolete as it is, at least for
    > an operating system - thank you Windows) has been adopted by Linux,
    > that you can. I don't have my linux workstation on at the moment, but
    > if you need to know, I can check.
    >
    > As for the DLL itself, I suspect you will have MAJOR problems getting
    > it to work right in Linux, and that you will almost definitely have to
    > rebuild it with a Linux native compiler. It sounds like you have the
    > source code, so it should be a matter of just porting it over, and
    > stripping out all of the platform dependent calls a
    nd substituting all
    > of the necessary function calls.
    >
    > Good luck, and please keep us up to date on your progress. Not many
    > of us use Linux, and any and all information on the matter is gold.
    In linuxland isn't a dll called a shared library? You'd basically have to
    get the source for the dll and beat on it until it turns into a shared lib
    (better still, see if you can get an already built linux library). Actually
    hooking into the library from within LV should work the same in either world.
    NI, by the way, has app notes on this subject. I haven't gotten around to
    reading any of them yet, though.
    That's my story and I'm sticking with it.

  • LabVIEW for Linux support on VXI hardware

    A potential client contacted me regarding a small project using VXI hardware under Linux. I'm considering using LabVIEW for Linux but I'm not too clear on NI's VXI driver support and whether they have a VI library for the particular hardware. I contacted NI tech support over the phone but they didn't have any answers. BTW, I've used LV with PCI and ISA DAQ boards under Windows and Linux but I've never used VXI.
    Here is the hardware in question:
    PCI/VXI-MXI-2(8026) - PCI to VXI bridge
    VXI-AO-48XDC - 48 channel analog output board
    VXI-MIO-64XE-10 - multifunction DAQ board
    Anyone know what's involved in building a LV app for this system under Linux, i.e. what's NI's HW driver and LabVIEW support?
    I've purchased LV 7.1 FDS for Linux for other projects. Do I have to buy anything else? I found this link on the NI site:
    http://sine.ni.com/apps/we/nioc.vp?cid=10603〈=US
    -kevin
    PS: Sorry for the repost. I accidentally posted this to the LabVIEW forum.

    Kevin,
    You will need NI-VXI/VISA for Linux part number 778131-01. Which can be found on the link you provided. The forums seemed to have removed the "〈" from the link so it is a good idea to preview your post Hopefully you have read my reply to your other post but we can continue it here if you have further questions.
    Shawn B.
    National Instruments
    Use NI products on Linux? Come join the NI Linux Users Community

  • Labview for Linux Trial

    Does anybody know why there is no a trial version of Labview for Linux?
    I think it would be welcome by many...
    Marco

    I don't know why there is no trial version of LabVIEW for Linux but if you want to try one on trial, then you can contact the local sales engineer of your area and maybe he/she can help you out. To get information on the engineer, just contact your local NI office.
    Adnan Zafar
    Certified LabVIEW Architect
    Coleman Technologies

Maybe you are looking for