Display Arduino analog input using LabVIEW

Posted on Tuesday, June 13th, 2017 in how-to by DP


Zx Lee shared detailed instructions of how to display the Arduino measurements using LabVIEW:

To get started, I will explain what is actually going on in Arduino. In this project, I am using an Arduino Nano to acquire signals and send the data to PC. As mentioned earlier, two analog input channels (A0 & A1) will be used to measure input signals. To ensure an accurate measurement is performed at fixed sample rate, the Arduino is configured to wait the predefined interval before taking a measurement and send to PC serially. The concept used is similar to the BlinkWithoutDelay example in Arduino. The benefit of using this method is that there is a while loop that always checks if it has crossed the desired interval. If it is reached, it will take the measurement, else it will skip and you can make it to work on other task.

More details at his blog here.

This entry was posted on Tuesday, June 13th, 2017 at 11:59 pm and is filed under how-to. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.

One Response to “Display Arduino analog input using LabVIEW”

  1. Max says:

    The tutorial on creating a Labview display may well be of use to some, but I can’t help finding it thoroughly hilarious how the article goes to great length explaining how the Arduino code involved is not using blocking Delay() calls but periodically checks the passage of time instead so it can do something else between samples, only to, ummm, not do absolutely anything else between samples – a version using Delay() would have been literally exactly equivalent.

    If anything, it would have been worthwhile to point out that this approach prevents drifting of your sampling moments (more specifically ties it to the precision of your independently running hardware timer) instead of simply ignoring all the code being executed between your Delay(desired_but_less_than_the_actual_sampling_interval_you_get) calls – but the advantage currently claimed is not actually taken advantage of…

Leave a Reply

Notify me of followup comments via e-mail. You can also subscribe without commenting.

Recent Comments

  • Pekka Akselin: This is ridiculous!? :-) We are back at 256(!) byte EPROMs that needed multiple, a handful, of voltages to run! :-(
  • KH: Let's try a back-of-envelope calc balancing energies. From MCP1700 datasheet, there are graphs for a 200mA load step. Estimate the energy shortfall as 12uJ. Say...
  • Daniel: It's been a week and my comment is still awaiting moderation. Apparently the CIA doesn't want their involvement known?
  • KH: Agree, so okay, I guess he must have learned from somewhere. 100nF and 1000uF is so far apart, that was jarring; it's more magic incantation...
  • Max: I have a suspicion the hefty electrolytic cap might be some sort of cargo cult carry-over from other RF-based projects - for instance, I've seen...