Leaderboard

Hello everybody. I just wanted to show LabVIEW running on an Asus Vivotab 8 tablet. The tablet was purchased in a good deal for $139 (now gone), but can be purchased from Microsoft for $149. It runs the Intel Atom Z3745 "Bay Trail" quad-core cpu, has 2GB of ram (most other value tablets only have 1GB ram), and 32GB of flash, plus a micro SD slot and USB OTG. The unit I purchased came loaded with Win 8.1, but I believe the units being sold by MS come with Win 10 preloaded. I downloaded the LabVIEW 2014 SP1 runtime engine directly to the tablet and installed it with no issues. I then updated the tablet to Windows 10. I used my Win 7 pro laptop to create a simple application that throws some white noise into a waveform graph and compiled it to an executable. I transferred the application to the Vivotab 8 using a micro SD card, and ran the app directly from the SD card. It runs LabVIEW runtime like a champ. Very fast loading (although it is a simple app) and fast screen updates, virtually no difference from my laptop. So if you want a great tablet that will run LabVIEW for around $150, this puppy will do it. Shouldn't there be a forum category devoted to LabVIEW on tablet & phones? There is a PDA category, but that seems a bit dated.

Also I think I remember reading the performance of this is better. More generally, is this something that could be Xnoded? I don't personally have the skills for it, but it seems like its a pretty straightforward adapt-to-type deal.

I think it's polymorphic. Try wiring a string to the path input.

The only improvement I can suggest is to use the VI Name instead of VI Path. If you're attempting to use this on a VI that hasn't been saved yet, obviously the path will return not a path. The VI Name works because the VI is already in memory, it has to be because it is a dependency of the calling VI when you put down the static VI reference.

An SQLite database consists of a single standalone file, which your application can place anywhere it wants. No need to install a server. (That's why it's called "Lite") There's even the option of an in-memory SQLite database (which exists in RAM only, not on disk -- the user will never know that SQLite was involved)

Perfect use-case (on the surface) for a relational database.