Skip navigation


Blog Posts

Blog Posts

Items per page
1 2 Previous Next

Building Graph Data in The Daily CLAD

Posted by SercoSteveB Mar 27, 2015

Which of the following is a possible result of the data generated by the VI?


NOTE:  Assume all settings left at default.


Graphing 2D Arrays 27_03_2015.png


Graphing 2D Arrays Answers 27_03_2015.png


To Time Stamp in The Daily CLAD

Posted by SercoSteveB Mar 26, 2015

What is Timestamp Out following execution of the VI?


Timestamp Out 26_03_2015.png


a) 00:00:00.000 DD/MM/YYYY

b) 00:00:00.000 00/00/1904

c) 00:00:00.000 01/01/1901

d) 00:00:00.000 01/01/1904


Article from Anita Shekhar, Planet NI Program, National Instruments


"Our experience being an Alliance Partner has helped us provide advanced LabVIEW solutions using NI hardware at a low cost. This has helped us deliver the best customer service possible and has proven to be a great asset for our company."—Erman Ozdemir, Managing Director, ENOVAS



Established in 2012 in Istanbul, Turkey, ENOVAS specializes in signal processing and communications. The company is currently developing signal processing training kits and communication training kits based on NI Educational Laboratory Virtual Instrumentation Suite (NI ELVIS). ENOVAS joined the Planet NI program in 2013 to support the development of the training kits that are based on NI ELVIS. ENOVAS also uses LabVIEW and works with local academic institutions, so the company also joined the NI Alliance Partner Network. Since then, Feras Moualla, the field service engineer manager from NI Arabia, has worked closely with ENOVAS on several academic opportunities and provided training credits to improve the company’s LabVIEW expertise. The success of ENOVAS is due to Feras’ vision, leadership, and hard work. In 2014, an engineer from ENOVAS became a Certified LabVIEW Developer and successfully renewed the Alliance Partner membership. Since then, the company has helped grow NI’s business, especially with sales to universities contributing more than $1 million USD in revenue.

Over the past four years, NI has supported more than 500 small-to-medium enterprises (SMEs) by making NI tools and training affordable to start-ups and small companies through the Planet NI program. The goal is for these SMEs to become a part of the Alliance Partner Network and build a lasting, mutually beneficial business relationship. ENOVAS is a perfect example of making progress toward that goal.

In collaboration with the Alliance Partner team and the software team, the Planet NI program started the on boarding process in 2013. New small companies in developing countries enter the Planet NI program, and after local sales teams identify them as potential alliance partners, they start a nurturing process and ultimately become a part of our global Alliance Partner Network.

“On boarding SMEs into the Alliance Partner Network has been a great way to expand NI partnerships in strategic areas around the globe,” said Tony Vento, NI vice president of systems assurance and alliance partners. “We are happy to have companies like ENOVAS as a part of the NI family.”


Learn more about Planet NI.



将来、リハビリ療法が成功する確率を高めるため、National University of Singaporeの技術者は仰臥位歩行リハビリ装置を開発し、


CompactRIO LabVIEWを使用して、技術者は装置の歩行サイクルを制御し、患者の下肢を動かします。

Supine Gait Rehabilitation Device_SA.jpg










毎年、世界の原子力発電所から10,000 mもの高レベル放射性廃棄物が生成されます。



Nuclear Waste Containers.jpg




LabVIEW FPGAモジュールがFPGAのプログラムに使用されました。






Jawaharlal Nehru港はインドのコンテナ全体の65%を超える量を処理しています。

この港とムンバイのPanvelハイウェイを結ぶ橋がなければ、トレーラーや他のコンテナ車両は22 kmも遠回りをしなければなりません。

そこで、Sardar Patel College of Engineeringと21st SHMのコンサルタントは構造健全性監視のソリューションを開発し、



Bridge rehabilitation.jpg





また、NI Report Generation Toolkitを使用して、すべての測定値のデータレポートを作成しました。







Hi, everyone!


I am pleased to inform you that the LabWindows/CVI 2015 Beta Program is now open for new registration requests. As a beta program member you will be among the first to use the next LabWindows/CVI release, providing you the opportunity to give NI feedback and to test your existing projects against the latest LabWindows/CVI features.


If you are interested in participating in the program, we encourage you to request participation by visiting and choosing to register for the LabWindows/CVI 2015 beta from the drop-down menu. All previous beta users must re-register for the LabWindows/CVI Beta to ensure we have up-to-date information.


We look forward to hearing from you!


Warm regards,


How big of a number can we put in an I32? A double? What happens when we try to cram a bigger number into a data space that can’t hold it? We explore these questions today, as well as look as designing applications with these concepts in mind. Next time we’ll talk about numeric coercion and conversion.

Want to meet us? Come to a regional course!

And keep up with us here:!/sixclear

(start transcription)

Here at VI High, Sixclear’s LabVIEW training video blog, we believe in the power of YouTube to enact meaningful social change as well as teach technology. Now, on our videos we have almost as many views as PSY, but he did beat us to the punch in breaking YouTube by reaching 2,147,483,647 views, and as we can see, he surpassed that. There was a kerfuffle lately about reaching that number. So, why is it significant?

Let’s pop into LabVIEW and put down a numeric, and I’m going to change this representation to I32. When I hover over it, the Context Help tells me its range. This number looks a little familiar. That was the limit to the maximum number of views a YouTube video could receive because the data type holding it couldn’t hold anymore. Let’s expand this and we’ll put in a big number, like 5G for billion, and as we can see, it doesn’t allow me to go any higher than this number. If I increment, no luck. I can go down but not beyond that number. For instructive purposes, I’ll make a copy of this, and change its representation to an I8. My Context Help tells me that I can now take -128 to 127. So, I’ll put 125 in here and I’ll increase this, but of course we can’t go beyond that because LabVIEW is preventing us from putting a greater value into the numeric than it can hold. But what if I go and programmatically add a value to it? Say I take 127 and add 5 to it. Run it, I get -124. Now, that’s some fuzzy math. What’s happening here? The value is actually rolling over kind of like the digits in a gas gauge when your gas prices aren’t at historic lows. Since we added 5 to this, the next digit would’ve been -128, then -127, -126, -125, and then, finally, -124. So, clearly this could be dangerous if we start adding, subtracting or multiplying numbers beyond the range that they can contain.

So, let’s learn about data types in general. As we saw, if I go and put down a new numeric control, LabVIEW makes it a double, DBL. What does that mean? Our Context Help tells us that we have around 15 digits of precision. It doesn’t give us that exact range that it gave us with integers because this is a floating point value. So, I could have 134265 or 1.34265. So, really it’s the number of digits that’s more important, and with doubles we get about 15. As we also see, that’s 64 bits or 8 bytes of memory, and if we’re in the LabVIEW environment, then that will take 8 bytes of virtual or volatile memory. If I store it to disk, it takes 8 bytes of storage. If I go and grab an integer constant from the block diagram, LabVIEW makes it an I32, possibly inspired by PSY, and that’s fairly typical for most integers, and these two numeric representations are fairly typical. In most cases in LabVIEW, if we have a fractional value, it’s a double. If we have an integer, it’s an I32, though some functions and VIs in LabVIEW may take different data types, like a U32. For instance, our last episodes on timing showed the Wait function and the milliseconds to wait is a U32. So, obviously, with any of these numerics we created, we just right-click, go to Representation, and choose the numeric representation, which dictates how much memory is used and the format: U32s always being positive; I32s being positive and negative; these across the top being fractional values, in other words not whole numbers; across the bottom, complex values, a real value and its imaginary counterpart, in other words, complex conjugates.

Now, why is this information valuable? Well, let’s say I’m in the design phase of a new application, one that tests air quality, and I’m prototyping my front panel because that’s a good idea to do, and here is my very simple user interface. I’ll have the number of test runs, the pressure at which I’m collecting data, and then the value of CO2 in parts per million with an array holding those data values and a display holding the same. Now, in this design phase, I could go through each individual control on my front panel and consider what could go in there. For instance, I know the number of runs will always be between maybe 0 and 10. So, therefore, I could say: well, I should just choose that to be a U8 because that’s the smallest data type that can hold that value, and I also think it’ll always be positive so no need making it an I8. I look at my pressure, and I know I don’t need any great precision to hold my pressure so I make it a single. Now, the CO2 value itself is the thing I’m most interested in so I keep that as a double in order to keep greater precision. Now, that was simple enough for this very simple application. It took a little bit of time for me to think about these things, record them, and then design my application moving forward based on those data representations. But what about the future?

What if I want to scale this up, if I want to replicate it on another test stand? What happens? Let’s say this code is working well for six months, and a coworker says, “Hey, that’s a great code. Can I go and take it on this new test bench we’re building where I’m measuring NOx instead of CO2, and I want to change pressure to temperature, and I’ll do a different number of runs?” Well, I need to go through this same analysis on that new test stand. The question is: what do I really gain from that? In this case, these are a couple of scalars, so I’ve gained at most a few bytes while this code is running. So, I gain a few bytes but I’ve lost some time in my re-evaluation, and there’s some danger. What if I’m changing pressure to temperature and I want it to be much more precise? We’ve seen what happens if you try to cram values into memory space that’s not big enough to hold it. In an unrelated example, my girlfriend used to ask me about the future a lot, especially when I moved to downtown Austin to a smaller condo that wouldn’t accommodate any extra data, and now she’s just a memory. You see how everything comes back to LabVIEW?

So, plan for the future. What do I mean? If you’re on a modern computer, that is, with enough memory and processor juice to handle your applications, then you can just default to LabVIEW’s defaults for numeric representation: that is, doubles for fractional values and I32s for integers. That’s kind of a no-brainer for scalars, in other words, single data values, not arrays. However, with an array, that’s a bit trickier. How big is this array going to get. Is this a huge data set? Maybe in the millions? In that case, the size of the data representation definitely makes a difference, and that could spin up to MBs or even GBs of extra memory which would cause your code to lag or even crash. Now, note that this discussion applies to coding on a Windows machine or a Mac or Linux if you’re using that, but not on something like an embedded device or a microcontroller, where memory considerations are far different because you’re working with much less available memory.

Good chat. In the next episode, we’re going to discuss what happens when we want to change data values. When LabVIEW changes it, which is coercion or when we change it, which is conversion. If you like this stuff, check out our full course at We also deliver it in person. You can meet me. I’m really not that bad. We have regional courses all over the place. For instance, I’ll be in Minneapolis in April 2015. I’m excited to go to Minneapolis. Maybe I’ll see you there.

(end transcription)

Originally posted at


テスト/計測の分野において、これまでプロセッサのクロックレートを上げることでテスト時間を短縮し、コストを削減してきました。確かに数多くの企業、特に半導体やコンシューマエ レクトロニクスを扱う企業は、テストハードウェアを制御するPCをアップグレードすることで、その恩恵にあずかってきましたが、クロックレートだけに依存した処理能力の向上には限界が見え始めています。

クロックレートが高くなると、プロセッサの放熱と電力効率の問題が伴います。そこで、この10年、コンピュータ業界では、CPUの処理能力を向上させるために、クロックレートを高くするのではなく、複数の並列処理要素、つまりコアを組み込むことに焦点を絞ってきました。ムーアの法則は、チップ上の トランジスタ数が2年で約2倍に増えるというものですが、CPUベンダは、このトランジスタ数の増加という考え方をコア数の増加へと発展させました。現在、デュアルコアプロセッサおよびクアッドコアプロセッサは、デスクトップ、モバイ ル、およびウルトラモバイルのコンピュータセグメントにおいて一般的になっており、サーバの場合は通常10個以上のコアが搭載されます。サーバクラスのプロセッサでよく見られますが、コア数が10を超えると、そのプロセッサは「メニ―コア」となります。


テスト対象を広げながら、テストにかかる時間を短縮するというプレッシャーに打ち勝つために、テスト/計測アプリケーションは新しいプロセッサアーキテクチャを活用しつつ さらなる前進を遂げる必要があります。



「The Core Of The Matterマルチコアからメニーコアプロセッサへの進化」 (ファイル名:ato2015_manycore.pdf)



ナショナルインスツルメンツは、テスト/計測業界における最新の技術や手法に関する教育界や産業界における研究結果、NIが行ったユーザコミュニティや顧客調査の結果、ビ ジネスインテリジェンスや顧客諮問委員会の報告などに基づき、主要な技術トレンドを「Automated Test Outlook」としてまとめています。詳しくは、以下よりダウンロードください。

  >> Automated Test Outlook 2015 (英語)をダウンロード


If Numeric Value in = -1, what is Boolean Array Out following execution of the VI?



Numeric to Boolean Array 24_03_2015.png


Numeric to Boolean Array Answers 24_03_2015.png

Shelley Gretlein

Wir lieben sie oder wir hassen sie, aber Benutzeroberflächen, welche die sichtbare Hülle von Programmcode, Konfiguration, Hardware und Datenanalyse darstellen, definieren unsere Erfahrungen und beeinflussen unsere Produktivität. Die Geschichte der grafischen Benutzeroberfläche ist bemerkenswert. Vom erfolglosen, doch einflussreichen Xerox Star im Jahr 1981 bis zum Macintosh von 1984 und Windows 3.0 haben wir Fenster mit mehreren Registerkarten, „Schreibtischmetaphern“ mit Papier, Ordnern, Uhren und Papierkörben gesehen. Der Konkurrenzkampf der Browser hat uns Dashboards beschert und seit Windows 8 gibt es die Live-Kacheln. Diese Geschichte weist den Weg für künftige grafische Benutzeroberflächen.


Benutzeroberflächen für Wissenschaft und Technik unterscheiden sich seit jeher von Verbraucher- oder Architekturdesigns. Für NI sind grafische Benutzeroberflächen eine wesentliche Grundlage für den Erfolg der virtuellen Instrumente, weil sie herkömmliche Stand-alone-Messgeräte nachbilden. Das Konzept der virtuellen Instrumente übertrumpfte traditionelle Test- und Messsoftware, deren Entwickler vor lauter Eifer, immer mehr Funktionen zu liefern, das grundlegende Design der Benutzeroberfläche aus den Augen verloren.

LabWindows/CVI ist ein Beispiel für eine auf Messtechnik spezialisierte grafische Benutzeroberfläche, denn sie bildet herkömmliche Stand-alone-Messgeräte nach.


Heute befinden wir uns in einer Übergangsphase, in der das Design einer Benutzeroberfläche nicht nur einen Wettbewerbsvorteil, sondern sogar eine unverzichtbare Anforderung darstellt. Moderne Anwender sind stark von aktueller Unterhaltungselektronik beeinflusst und verlangen deshalb nach Lösungen, die nicht nur alle nötigen Funktionen mitbringen, sondern auch noch möglichst intuitiv zu bedienen sind.


Deshalb sollten alle grafischen Benutzeroberflächen die folgenden Eigenschaften aufweisen:

  1. (Echt) Grafisch: Unintuitive, textbasierte Benutzeroberflächen gehören der Vergangenheit an.
  2. Anpassbare Skins: Benutzeroberflächen sollten nicht nur anwenderspezifisch anpassbar, sondern mit Themen, Skins und dokumentierten Erweiterungsmöglichkeiten ausgestattet sein.
  3. Modern: Ein klares, minimalistisches Design (bei Benutzeroberflächen ist weniger meist mehr) lenkt die Aufmerksamkeit auf die Daten und Informationen anstatt auf die Bedienung.
  4. Design: Layout, Farbe, Schriftart und Sättigung spielen eine wichtige Rolle und sollten deshalb keinesfalls vernachlässigt werden.


Um diese Erwartungen zu erfüllen, investieren Hersteller (einschließlich NI) in die Interaktion, die Bedienfreundlichkeit und in Designer für Benutzeroberflächen.. Ich denke, in Zukunft werden bei Benutzeroberflächen weitere Trends auf uns zukommen:

  • Klares Design: Vor ein paar Jahren begannen die meisten Designexperten damit, einen minimalistischen Designansatz für eine bessere Bedienbarkeit zu propagieren, mit freien Flächen, klaren Linien und hellen Farben.
  • Mobiles Design: Dabei entstehen unter Berücksichtigung von High-End-Grafikleistung einfachere Oberflächen und Zweidimensionalität (siehe Redesign von Metro und Gmail in 2012).
  • 3D-Design: Angeführt von der Spiele- und Multimediaindustrie ermöglichen uns direkte 3D- und OpenGL-Technologien eine positive Erfahrung auf leistungsstarken Plattformen mit 3D-Darstellung, Schattierungs- und Transparenzeffekten (AIGLX für Red Hat Fedora, Quartz Extreme für Mac OS X und Aero für Vista).
  • Virtuelle Realität: Head-up-Displays sind inzwischen ausgereifter und nicht mehr nur Piloten zugänglich. Die VR ist seit der PriusAirbus Smart Factory im Jahr 2013 immer häufiger anzutreffen.


Das Design ist auch künftig das wichtigste Element, das stets berücksichtigt werden muss, denn Designtrends werden und müssen sich weiterentwickeln. Ihre Gewinnspanne und die Beliebtheit Ihres Produkts werden von der Bedienfreundlichkeit definiert und diese hängt zuallererst von der Benutzeroberfläche ab.


Noch nicht überzeugt? Das Marktforschungsunternehmen Forrester Research hat herausgefunden, dass die „Konzentration auf die Bedienfreundlichkeit die Zahlbereitschaft von Anwendern um 14,4 % steigert, die Bereitschaft, zu einer anderen Marke zu wechseln, um 15,8 % senkt und die Wahrscheinlichkeit, Ihr Produkt weiterzuempfehlen, um 16,6 % erhöht.“


Was denken Sie? Teilen Sie uns Ihre Meinung in einem Kommentar mit oder lernen Sie im Forum UI Interest Group Tipps und Tricks von LabVIEW-Entwicklern.


Shelley Gretlein


Shelley Gretlein ist selbsterklärter Software-Nerd und Roboterfreak. Als Director of Software Marketing bei NI wirbt sie auf Keynote-Bühnen von Anwenderforen genauso wie in Gesprächen im Fahrstuhl unermüdlich für LabVIEW. Folgen Sie ihr auf Twitter unter @LadyLabVIEW.


If Numeric Value In = -1, what is Boolean Array Out following execution of the VI?


Numeric to Boolean Array 19_03_2015.png


Numeric to Boolean Array Answers 19_03_2015.png


i opened LIFA_BASE.ino on Arduino 1.6.0 but it didnt compile and message occured !!


Arduino: 1.6.0 (Windows 7), Board: "Arduino Uno"



C:\Program Files (x86)\Arduino\libraries\RobotIRremote\src\IRremoteTools.cpp:5:16: error: 'TKD2' was not declared in this scope

int RECV_PIN = TKD2; // the pin the IR receiver is connected to


Error compiling.



  This report would have more information with

  "Show verbose output during compilation"

  enabled in File > Preferences.


what should i do ??


USRP as fast a/d? in NI USRP2

Posted by Timbo_Sauce Mar 20, 2015

I need to set up my USRP as a fast A/D.   I am not interested in demodulating signals.  I just want to read raw signal at 10KHz to 10MHz rate.  I need some guidance.  For instance, will I need to reprogram the FPGA?  Are there examples that I could follow?