Subject: Raspberry Pi and NI 6009
In-Reply-To: <656364F6F6C85D42A64355D5A899D4AB2887E6AD12@AU2EML2K702.corp.resmed.org>
References: <mailman.1.1355520987.6049.info-labview-infolabview.org@lists.infolabview.org>
<656364F6F6C85D42A64355D5A899D4AB2887E6AD12@AU2EML2K702.corp.resmed.org>
Message-ID: <17048866-E6DC-4B4D-B986-D6861170533F@magnet.fsu.edu>

On Dec 16, 2012, at 21:58, Vito Ignazzi <Vito.Ignazzi at resmed.com.au> wrote:
> My question to the community are:
>
> 1) Could the fixed C code have been written on the iPad and therefore remove the Raspberry Pi?

Tricky since the NIDAQmxBase or some portion would have to be ported to the iPad. Not clear if the iPad development environment allows such driver code to be installed. The iPad is unfortunately locked down fairly tight.

> 2) Would it be useful if the fixed C code source was released so that we could tailor it to our application?
YES!

> 3) What is the data communication channel between the Raspberry Pi and the iPad?
Adam's email seemed to imply that it is web services over a wireless connection.

> 4) How much better would this be if LabVIEW code could be written to target Raspberry Pi or iPad?
Is this a philosophical question of "better" or a market survey? Not to be flip here, but the question is about running LV code in a small processor or embedded environment. The question is what environments should NI support and to what extent. Then it is a question of market and profit.

-sth