Raspberry Pi and NI 6009

From Vito.Ignazzi at resmed.com.au Mon Dec 17 16:40:50 2012
From: Vito.Ignazzi at resmed.com.au (Vito Ignazzi)
Date: Tue, 18 Dec 2012 11:40:50 +1100

Subject: Raspberry Pi and NI 6009
In-Reply-To: <mailman.1.1355780387.31539.info-labview-infolabview.org@lists.infolabview.org>
References: <mailman.1.1355780387.31539.info-labview-infolabview.org@lists.infolabview.org>
Message-ID: <656364F6F6C85D42A64355D5A899D4AB2887E6AEB9@AU2EML2K702.corp.resmed.org>

Thanks everyone for helping me understand the Low Cost USB DAQ Driver for use with Raspberry Pi (https://decibel.ni.com/content/docs/DOC-25806 ).

So, my original thought was that the setup may be:

NI6009 --> Raspberry Pi [running fixed C code] --> iPad [running Data Dashboard]

And I was thinking, what a convoluted way of getting data from an NI6009. Well it appears that the real setup is:

NI6009 --> Raspberry Pi [running fixed C code] --> WiFi Port --> iPad [running Data Dashboard]

Which makes it even more convoluted and crazier!!!

As Justin commented, a better arrangement is:

NI6009 --> Laptop [running LabVIEW]

Simple and powerful. And if you want to view things on an iPad, just use TeamViewer (thanks Justin).

So, in the end, my conclusion is that the Low Cost USB DAQ Driver for use with Raspberry Pi is a crazy way of getting data from a NI6009.

Regards,
Vito

-----Original Message-----
From: info-labview-bounces at lists.infolabview.org [mailto:info-labview-bounces at lists.infolabview.org] On Behalf Of info-labview-request at lists.infolabview.org
Sent: Tuesday, 18 December 2012 8:40 AM
To: info-labview at lists.infolabview.org
Subject: Info-labview Digest, Vol 12, Issue 10

Send Info-labview mailing list submissions to
info-labview at lists.infolabview.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.infolabview.org/listinfo.cgi/info-labview-infolabview.org

or, via email, send a message with subject or body 'help' to
info-labview-request at lists.infolabview.org

You can reach the person managing the list at
info-labview-owner at lists.infolabview.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Info-labview digest..."

Today's Topics:

1. Re: Raspberry Pi and NI 6009 (Vito Ignazzi)
2. Re: Raspberry Pi and NI 6009 (Vito Ignazzi)
3. Re: Raspberry Pi and NI 6009 (Justin Gruenberg)
4. Weekly Reminder - Please Read (info-labview-owner at infolabview.org)
5. Re: Raspberry Pi and NI 6009 (Scott Hannahs)
6. Re: 2 VIs access 1 DAQ card? (William Gilbert)

----------------------------------------------------------------------

Message: 1
Date: Mon, 17 Dec 2012 13:58:53 +1100

From: Vito Ignazzi Vito.Ignazzi at resmed.com.au
To: "info-labview at lists.infolabview.org"
<info-labview at lists.infolabview.org>
Subject: Re: Raspberry Pi and NI 6009
Message-ID:
<656364F6F6C85D42A64355D5A899D4AB2887E6AD12 at AU2EML2K702.corp.resmed.org>

Content-Type: text/plain; charset="us-ascii"

Hi all,

I'd like to go back to square one on this topic. It's a topic that covers LabVIEW, microcontrollers, iPads, connectivity and data acquisition - all the interesting stuff. However, there appears to be some confusion - at least on my part.

The "product" found at https://decibel.ni.com/content/docs/DOC-25806 , I believe, looks like:

NI6009 --> Raspberry Pi [running fixed C code] --> iPad [running Data Dashboard]

Wouldn't the following give the same or better "product":

NI6009 --> iPad [running fixed C code]

One less box to worry about and the same end result?

I'm assuming that the Raspberry Pi connects to the iPad using USB. The only other option appears to be WiFi since the iPad does not have wired Ethernet on it's 30-pin connector. However, this option requires yet another piece of hardware for the Raspberry Pi.

My question to the community are:

1) Could the fixed C code have been written on the iPad and therefore remove the Raspberry Pi?
2) Would it be useful if the fixed C code source was released so that we could tailor it to our application?
3) What is the data communication channel between the Raspberry Pi and the iPad?
4) How much better would this be if LabVIEW code could be written to target Raspberry Pi or iPad?

I eagerly await the day that LabVIEW goes beyond the confines of the desktop. So many exciting targets such as Arduino Due, Raspberry Pi, Stellaris Launchpad, Android devices, iPhone, iPad and many more. LabVIEW would be great as a programming environment for these platforms. I'd be happy with just a couple of these being able to be programmed using LabVIEW! (We know it's possible since the Lego NXT and some old microcontroller boards (LM3S8962 and Kiel MCB2300) can be programmed in LabVIEW.)

Regards,
Vito

Warning: Copyright ResMed. Where the contents of this email and/or attachment includes materials prepared by ResMed, the use of those
materials is subject exclusively to the conditions of engagement between ResMed and the intended recipient.

This communication is confidential and may contain legally privileged information.
By the use of email over the Internet or other communication systems, ResMed is not waiving either confidentiality of, or legal
privilege in the content of the email and of any attachments.
If the recipient of this message is not the intended addressee, please call ResMed immediately on +61 2 8884 1000 Sydney, Australia.

------------------------------

Message: 2
Date: Mon, 17 Dec 2012 14:01:05 +1100

From: Adam Kemp adam.kemp at ni.com
To: Info-LabVIEW <info-labview at lists.infolabview.org>
Subject: Re: Raspberry Pi and NI 6009
Message-ID:
<OF7A076563.BA78990B-ON86257AD4.005E737A-86257AD4.005EA74A at ni.com>
Content-Type: text/plain; charset="US-ASCII"

I don't actually know much about the Raspberry Pi example other than how
it connects to Data Dashboard (one of the products I actually work on). I
suggest you comment on the ni.com article about it (
https://decibel.ni.com/content/docs/DOC-25806) to get answers to your
questions.
--
Adam Kemp
adam.kemp at ni.com
(512) 683-6058

Warning: Copyright ResMed. Where the contents of this email and/or attachment includes materials prepared by ResMed, the use of those
materials is subject exclusively to the conditions of engagement between ResMed and the intended recipient.

This communication is confidential and may contain legally privileged information.
By the use of email over the Internet or other communication systems, ResMed is not waiving either confidentiality of, or legal
privilege in the content of the email and of any attachments.
If the recipient of this message is not the intended addressee, please call ResMed immediately on +61 2 8884 1000 Sydney, Australia.

------------------------------

Message: 3
Date: Sun, 16 Dec 2012 22:34:59 -0500

From: Justin Gruenberg justin.gruenberg at gmail.com
To: Info-LabVIEW <info-labview at lists.infolabview.org>
Subject: Re: Raspberry Pi and NI 6009
Message-ID:
<CAKnGzMER251_0P7LDyEnN-wnPTXYMV3iTsOpvUsLL2L1JMw1Eg at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

On Sun, Dec 16, 2012 at 9:58 PM, Vito Ignazzi <Vito.Ignazzi at resmed.com.au>wrote:

> 1) Could the fixed C code have been written on the iPad and therefore
> remove the Raspberry Pi?
>

As Adam Kemp said, not without modifying the 6009. You can't connect
arbitrary USB devices to the iPad and make them work -- this is Apple's
intent. Even if you could, I think the use cases are somewhat limited.
What would you be able to accomplish that you couldn't with a
ultraportable laptop and any of NI's USB DAQ products? You gain a slick
interface and lose the flexibility of a PC.

I think the iPad works out great as a way to monitor testing remotely --
something that the NI Data Dashboard does. I use my iPad to monitor
LabVIEW applications running on test stands through TeamViewer.

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

Yes. I can imagine the kind of hackery that went into putting the
application together; I assume it's something NI doesn't want to support as
an example application. What would be really awesome would be if NI made
DAQmx available on more linux architectures, and it had the same support as
the Windows version. It'd be awesome if all the vendors I deal with did
this. I can dream.

> 3) What is the data communication channel between the Raspberry Pi and the
> iPad?
>

It appears like wifi. Hook the RPi to your network (wired ethernet or with
a wifi dongle), iPad connects wirelessly.

> 4) How much better would this be if LabVIEW code could be written to
> target Raspberry Pi or iPad?
>

It would be really awesome. Although, in the case of LabVIEW code for the
RPi, I think it'd be better if it could generate Linux binaries for
multiple platforms. I think that's more likely.

Having native LabVIEW executables run on the iPad is very unlikely, as in
the terms for the App store you can't distribute apps that run arbitrary
code. This is one of the reasons there isn't Java for the iPad.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://info-labview.org/attachments/20121216/a8a7c932/attachment.htm>

------------------------------

Message: 4
Date: Mon, 17 Dec 2012 02:00:01 -0800 (PST)

From: info-labview-owner at infolabview.org
To: info-labview at infolabview.org
Subject: Weekly Reminder - Please Read
Message-ID: <20121217100001.8B7C284011 at capricornus.dreamhost.com>

This is the weekly admin reminder for readers of the Info-LabVIEW mailing list and mail digest.
(Last Updated March 19, 2012)

For subscription, archive searching, etc.
<http://infolabview.org>
To manage your subscription please go to:
<http://lists.infolabview.org/listinfo.cgi/info-labview-infolabview.org>

First, if your email address changes, you will not be able to post to the list from your new address. This is the most common problem with not being able to post. Go to the info-labview web page and unsubscribe your old address and add the new one.

To post to the list, mail to <info-labview at infolabview.org> with the following restrictions:

1. Long messages will be bounced by the list software. Please do not quote long messages in their entirety or include copies of an entire digest! See <http://infolabview.org/infolabview/netiquette.html#quoting>.

2. All messages with attachments will be bounced (or the attachments scrubbed off).

3. The list software will attempt to remove HTML formatting. Please avoid such formatting if possible (such formatting may make your message too large).

4. The list will only allow you to post if the message is "From" the same email address as you subscribed. (you have no idea how much spam this blocks!). This is probably why your message is blocked.

5. Do NOT request return notification receipts of email messages. Such messages are extremely annoying and you probably don't want thousands of notifications. All such messages should be blocked. See <http://infolabview.org/infolabview/netiquette.html#notification>.

6. DO NOT send subscription and deletion requests to <info-labview at infolabview.org>. If you do so, your request may be forwarded to each of the readers of the list. Aside from their disinterest in such matters, it wastes lots of net bandwidth.

7. DO NOT send messages to the list asking if it is working. It probably is. There may be other internet connectivity problems or misconfigured DNS and mail servers. If you really must know Paull Sullivan and Uwe Frenz each set up (interlinked) web pages publishing our recent experience with the Info-LabVIEW list (which is the same server as the Igor list) as indicators of the state of the list: <http://www.getemed.net/lvis/LVInfoStat.html> and <http://www.SULLutions.com/LabVIEW/Info-LabVIEW.html>. There is another indicator of the server status. Check <http://lists.infolabview.org/private.cgi/info-labview-infolabview.org/>, and peruse the archives by date. Checking any or all of those pages can give you a good handle on whether the silence is global or local and whether it is due to lack of traffic or technical difficulties.

SUBSCRIPTION requests should be mailed to <info-labview-subscribe at infolabview.org>. This being a double opt-in list, you will need to reply to a confirmation message.

LIST REMOVAL REQUESTS, should be addressed to <info-labview-unsubscribe at infolabview.org>, not to info-labview, or my personal account.

List mail sent to the admin address will be summarily deleted, as I do not have the time to return it to you for proper posting.

If your mail bounces for awhile due to mailbox full, domain registration issues, or other problems, your account will be disabled and eventually deleted. When you get your email straightened out, re-subscribe or change your subscription back to individual messages if you wish.

To make mail easier to sort for the readers of this list, in those cases where your query is machine-specific, I'd like to ask you to try to identify your postings by adding [M], [W], or [L] to the beginning of your Subject: line for Mac, Windows, or linux, respectively. If your question is of a more general nature, don't worry about this. Since LabVIEW is cross platform this is not an indication of which platform you happen to be using. Note: Some people automatically filter messages for platforms considered uninteresting.

Note gmail users: you may get a warning that the mail from a gmail address is not actually from the sender's address. More info at http://mail.google.com/support/bin/answer.py?hl=en&ctx=mail&answer=185812

PLEASE NOTE! This is a user list, run by and for LabVIEW users. If you have a commercially available item to announce, please make the announcement brief. It should be no more than a pointer to an email address, WWW site or phone number people may use to get full details. Posting full text of a product announcement to this list is Very Bad Form.

A list of archives of VIs can be found at <http://www.info-labview.org/resources.html#ftp>

-
Dr. Scott Hannahs, National High Magnetic Field Lab
Info-LabVIEW List Maintainer <mailto:info-labview-owner at infolabview.org>
<http://infolabview.org>

Subscribe: <mailto:info-labview-join at infolabview.org>
Unsubscribe: <mailto:info-labview-leave at infolabview.org>

------------------------------

Message: 5
Date: Mon, 17 Dec 2012 08:26:27 -0500

From: Scott Hannahs sth at magnet.fsu.edu
To: Info-LabVIEW <info-labview at lists.infolabview.org>
Subject: Re: Raspberry Pi and NI 6009
Message-ID: <17048866-E6DC-4B4D-B986-D6861170533F at magnet.fsu.edu>
Content-Type: text/plain; charset=us-ascii

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

------------------------------

Message: 6
Date: Mon, 17 Dec 2012 14:13:29 -0600

From: William Gilbert fotoelectron at gmail.com
To: Info-LabVIEW <info-labview at lists.infolabview.org>
Subject: Re: 2 VIs access 1 DAQ card?
Message-ID:
<CADYC0OPcRFs-Rc8aVTVd8RP4kLW7MAHZ3tR0PEDM3FGvpQpKAg at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi Jim,
Due to thread confusion, not sure if someone already pointed this out.
You probably need to make one vi, maybe we could call it a servlet,
to read all the data from the AI, and separate it into two queues or
buffer vi's that are then read by the client vi's. Can't be much help
with wizards or assistants, since I've never used them. Suspect they
only work for uncomplicated jobs. Also just noticed you asked the
question a month ago. Oh well, did the typing already, hope it helps.
--
Bill Gilbert, EM Tech
Univ of MN Physics
Phone 612 624 4870
Fax 612 624 457

On Fri, Nov 16, 2012 at 3:58 PM, Neville Dholoo <ndholoo at yahoo.com> wrote:
> Jim,
>
> DAQ Express VI's, or DAQ Assistant or Wizard etc. all use underlying calls to DAQmx VI's. As Nathan mentioned, you can't have two tasks accessing the same hardware resource (i.e. the analog channels). So it won't work, whatever method you choose to use.
>
> The reason for this is there is only one timing engine per channel group. I am assuming you are using hardware timing?
>
> Sample them all at the higher rate, and then downsample a group of that to your lower sampling rate.
>
> It might be possible using software timing (obviously not as repeatable as hardware timing).
>
> Two separate loops with the same task ID, reading all channels at different loop rates. Sorry I don't have any desktop hardware to confirm this.
>
>
> Neville Dholoo
> Advanced Measurements Inc.
> Calgary AB
> Canada
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://info-labview.org/attachments/20121116/1412e73c/attachment.htm>
> _______________________________________________
> Info-labview mailing list
> Info-labview at lists.infolabview.org
> http://lists.infolabview.org/listinfo.cgi/info-labview-infolabview.org

------------------------------

_______________________________________________
Info-labview mailing list
Info-labview at lists.infolabview.org
http://lists.infolabview.org/listinfo.cgi/info-labview-infolabview.org

End of Info-labview Digest, Vol 12, Issue 10
********************************************

Warning: Copyright ResMed. Where the contents of this email and/or attachment includes materials prepared by ResMed, the use of those
materials is subject exclusively to the conditions of engagement between ResMed and the intended recipient.

This communication is confidential and may contain legally privileged information.
By the use of email over the Internet or other communication systems, ResMed is not waiving either confidentiality of, or legal
privilege in the content of the email and of any attachments.
If the recipient of this message is not the intended addressee, please call ResMed immediately on +61 2 8884 1000 Sydney, Australia.