Jump to content

Bare minimum Requirement For LabVIEW Application to Run on Linux


Recommended Posts

Hello All,

 

I am developing the application for Linux using LabVIEW For Linux under openSUSE 12.1 & 11.4 versions.

My application would be a stand alone application running on the system.

 

What I want to achieve is :-

        a). An application which would serve the tasks defined by user and will do that tasks continuously. Here this system with LabVIEW application will be acting as the Server.

        b). Another application which would act as user interface to client for configuring the tasks & this tasks will be sent to Server System as mentioned in point no. a. Here the LabVIEW application will be acting as User Interface Client.

 

Now my Questions are:-

 1. What is the bare minimum requirement by the LabVIEW application from the Linux OS to run the LabVIEW application without interface or X window in Linux or the LaBVIEW application in the console format in Linux.

 

  2. What is the bare minimum requirement by the LabVIEW application from Linux OS to run the LabVIEW application with LabVIEW GUI interface.

 

In above both system is not considered as for development, considered as only for deployment point of view. Development System will be different.

 

Please give your valuable suggestions or help or guidance if anyone has done this before.

 

Thanks & Regards.

Nilesh

 

Link to post
Share on other sites

I have no LabVIEW + Linux experience so keep that in mind.  But your questions seems to open ended.  What if I asked:

 

 

What is the minimum system requirements for a program to run in Windows?

 

The problem with this question is it depends on what the program does.  If I write a hello world program, that should run (if it has compatibility) on any Windows version.  If I wrote some new high end first person shooter then that program may have other system requirements for the program.

 

Similarly you can ask what are the system requirements to run a hello world program, and I would say any processor Pentium 1 or newer with and 32MB of RAM (maybe less).  But if you are writing a program with more processing needs the requirements will be higher.  No one can say what the requirements are until the program is complete.

Link to post
Share on other sites

I would try killing x to see whatit does. LabVIEW still doesn't have a concept of a console only app even on Linux. Best case it still runs without issue but I wonder whether it will throw an issue. In terms of sw requirements, as a few people have said you need the runtime engine. I am not aware of any dependency listings beyond the 3 distros NI officially support. That said I have found it to run without issue on manjaro so there's nothing too specific.

Link to post
Share on other sites
Hello All,

 

I am developing the application for Linux using LabVIEW For Linux under openSUSE 12.1 & 11.4 versions.

My application would be a stand alone application running on the system.

 

What I want to achieve is :-

        a). An application which would serve the tasks defined by user and will do that tasks continuously. Here this system with LabVIEW application will be acting as the Server.

        b). Another application which would act as user interface to client for configuring the tasks & this tasks will be sent to Server System as mentioned in point no. a. Here the LabVIEW application will be acting as User Interface Client.

 

Now my Questions are:-

 1. What is the bare minimum requirement by the LabVIEW application from the Linux OS to run the LabVIEW application without interface or X window in Linux or the LaBVIEW application in the console format in Linux.

 

  2. What is the bare minimum requirement by the LabVIEW application from Linux OS to run the LabVIEW application with LabVIEW GUI interface.

 

In above both system is not considered as for development, considered as only for deployment point of view. Development System will be different.

 

Please give your valuable suggestions or help or guidance if anyone has done this before.

 

Thanks & Regards.

Nilesh

Here i am considering the standard x86 based standard PC with latest intel Atom Processor with HDD + 2GB RAM etc..

Here i want to achieve is best processing so i want to chop down the Linux OS. All will be data processing with this application and send to and fro data over TCP/IP.

Link to post
Share on other sites

If processing is the concern then the main issue is going to be background processes. The good news is I wouldn't expect much dependency here. I still don't know if it will run without X but going for a minimal window manager will be a good start. Then removing any continuous running processes in the background (use top to see what is running). I don't imagine there are many/any that are required.


EDIT: Just tested, definitely need X running.

Link to post
Share on other sites

You can build a Shared Library in LabVIEW for Linux with the "Embedded" runtime (in the Advanced page of the build spec properties check the box that says "Use embedded version of run-time engine"). When you do this your shared library will link against a LabVIEW runtime engine without GUI support, which means it does not require X windows. We don't support building executables this way, but you can build a shared library and then load it into a simple shell executable written in another language. This may be a useful way to write your server.

 

As for system requirements in general, our website documents that information: http://sine.ni.com/nips/cds/view/p/lang/en/nid/2541 (see the "overview" tab).

Link to post
Share on other sites
  • 1 year later...

Right, but my previous post explained how you can create a LabVIEW application on Linux that does not have a dependency on X11 at all. That method is officially supported, and it was designed for exactly this use case. It is what we (NI) recommend doing.

Link to post
Share on other sites

Right, but my previous post explained how you can create a LabVIEW application on Linux that does not have a dependency on X11 at all. That method is officially supported, and it was designed for exactly this use case. It is what we (NI) recommend doing.

Oooooh. LabVIEW streaming server on NAS? :book:

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By PaulL
      Out of the box text in the icon editor looks awful. (See attached image, which is better looking than most.)
      (Yes, even with small fonts: https://forums.ni.com/t5/Linux-Users/Labview-Icons-under-GNOME/gpm-p/3379530.)
      Details:
      LabVIEW 2016 64-bit, CentOS 7 Linux OS
       
      We have tried many things to get this to work, to no avail. 
      Does anyone have a solution?

    • By szewczak
      I wanted to cross post metux's discovery here asap, and have a separate discussion.
      Metux's original post:
      The recent Linux driver package introduces a CRITICAL security vulnerability:
       
      http://www.ni.com/download/ni-linux-device-drivers-2018/7664/en/
       
      It adds additional yum/zypper repos, but explicitly disabling package signing and using unencrypted HTTP transport. That way, it's pretty trivial to completely takeover the affected systems, by injecting malicious packages.
       
       
      DO NOT INSTALL THIS BROKEN SOFTWARE - IT IS DANGEROUS !
       
      CERT and BSI are already notified.
       
       
       
       
       
    • By ensegre
      More out of curiosity than of hope: has anybody any idea why SVs are almost unsupported on linux? By almost I mean that controls and indicators cannot be bound to shared variables, and that shared variables cannot be programmatically created and looked up. I know that SVs hosted on windows can be accessed in linux LV using datasocket nodes, but that is all it gets. And it has been said that datasocket is despicable. What are the missing pieces that make SV windows-only?
      I didn't find much in the canonical places, so I posted a dumb zero-kudos attracting idea.
    • By Zyl
      Hi everybody,
      Currently working on VeriStand custom devices, I'm facing a 'huge' problem when debugging the code I make for the Linux RT Target. The console is not availbale on such targets, and I do not want to fall back to the serial port and Hyperterminal-like programs (damn we are in the 21st century !! )...
      Several years ago (2014 if I remember well) I posted an request on the Idea Exchange forum on NI's website to get back the console on Linux targets. NI agreed with the idea and it is 'in development' since then. Seems to be so hard to do that it takes years to have this simple feature back to life.
      On my side I developped a web-based console : HTML page displaying strings received through a WebSocket link. Pretty easy and fast, but the integration effort (start server, close server, handle push requests, ...)must be done for each single code I create for such targets.
      Do you have any good tricks to debug your code running on a Linux target ?
    • By fennectp
      Hi all,
       
      I've got a customer that wants to zip/unzip files on their cRIO-9035, so I had them playing with the OpenG Zip tools to see if it would fit their needs. Although they've found that they can zip files on their cRIO just fine, they find that they get disconnected from their RT target and the shell shows the following error message:
      LabVIEW caught a fatal signal 15.0 - Recieved SIGSEGV Reason: address not mapped to object Attempt to reference address: 0x0x10000000 stdin: is not a tty  
      The zip file they're testing with includes two simple .txt files with short strings in them ("booya" and "booya2"). This file unzips just fine on the host PC with the "ZLIB Extract All Files To Dir" VI, but when copied over to the cRIO and unzipped via the same VI, it only unzips the first text file and the resulting file doesn't have any text in it.
      I've attached a copy of the project and the zip file I used to reproduce this behavior using a cRIO-9033 that I had on hand. (The only thing I can't provide is the cRIO >_<)
      Could anybody tell me what I'm doing wrong? Any suggestions as to what other workarounds I could take to zip/unzip files on a LinuxRT target would also be very much appreciated!
       
      Regards,

      Tamon
      Unzip on cRIO-9033.zip
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.