Planning to develop a compact portable Data acquisition system.The idea is to use a Single Board Computer and PC 104 cards.The PC 104 vendor confirmed that LabVIEW drivers are available for Windows XP OS.Thats fine.Now I would like to know if I can use the LabVIEW that I have used on PC on the Single Board Computer as well.Please suggest.
Nothing with the answers I got there.In fact they were very useful.
Thats a good point let me make it clear.The focus on that post was primarily on the interfacing of the PC104 cards for LabVIEW.
This post was made to make a note of the process,if any of using LabVIEW on a Single Board Computer - This was mentioned in the former post but isnt detailed.
So,Now,I would like to know the available options for using LabVIEW on a SBC.
- Can I load the Developer Suite onto it?
- Should I develop application on a PC and use an executable on SBC?
- What is the practise and what are the issues likely to be faced during the process of application porting/development?
I guess there are people around here who worked/working on similar projects.So,it would great if details of what and how they have done can be shared.
Hope this explains.
I am working on a project using PC to control/communicate with Single Board Computer.
First, I could ping each other with both connected to a route.
Second, failed telnet section. What I try to do is build a command line interface. Eventually, could use for others.
Do you recommend to install labview to the SBC? The SBC I used is VPX based.
Any tips or examples?
This post was made to make a note of the process,if any of using LabVIEW on a Single Board Computer - This was mentioned in the former post but isnt detailed. So,Now,I would like to know the available options for using LabVIEW on a SBC.
What do you mean by "LabVIEW for SBC"? Are you talking about software development (where you actually run LabVIEW, create VIs, and run them in Development Mode) or about running an application that you developed (on a PC) in LabVIEW?
It is certainly possible to do the latter (NI, for example, has a number of Single Board RIO systems that can run "headless" applications developed in LabVIEW). My guess is that NI would be the best source for such SBC, as a considerable amount of effort needs to go into creating a Run Time Environment that complements the LabVIEW Development environment, and they would be the ones best suited to do this. Have you contacted NI?
Guys, you are replying to a 5 years old post. There are lots of "zombee" posts recently:
edit: the OP was active last time in 2013...
This post was made to make a note of the process,if any of using LabVIEW on a Single Board Computer (potential spam link removed)- This was mentioned in the former post but isnt detailed. So,Now,I would like to know the available options for using LabVIEW on a SBC.
I am assuming that this is a serious question and not just some ploy to showcase a website for advertising purposes.
Yes, it is an old thread with obsolete information, but got revived by a link to some single board computers. You can interact with any singleboard computer using LabVIEW, if it can run a service that understand certain commands, e.g. via ethernet or such. This might be of limited usefulness.
Yes, there are e.g. sbRIO single-board computer from NI. They run NI linux and run LabVIEW RT, but are sold only in bulk. The eval kit is one way to get a single one. While it comes with an extended (90 day) evaluation license, ultimately you need LabVIEW, LabVIEW RT and LabVIEW FPGA to continue, which can be expensive. There is also MyRIO.
Recently, it also became possible to deploy LabVIEW executables that run natively on a selection of single board computers, such as rasperry PI and beaglebone Black. (noncommercial use only).
Unfortunately, if you look at ealltech's total posts (at least until the mods pull many of them down), many seem to have some 'casual' mention to this Shenzhen... SBC company either from Alex or someone else seamingly affiliated with the company, and best case are only loosely related to the orignal post. Sorry this poster has successfully wasted our collective time.