Skip navigation

Community

Blog Posts

Blog Posts

Items per page
1 2 Previous Next
0

I am pleased to announce that the Measurement Studio development team is currently working on a new deployment feature to help you provide a professional installer experience for your clients. We aim to offer an intuitive tool to configure and customize your Windows software installer and easily include all National Instruments components and drivers with your Measurement Studio application. As a result of this ongoing effort, the yearly Measurement Studio release cycle will be altered and the next version of Measurement Studio will release in 2015.

 

We will welcome Beta participants to explore the tool prior to release, so I encourage you to join the Measurement Studio and .NET Developers Community to receive updates and an invitation to the Beta program.

 

To ensure that our customers can continue to upgrade their Measurement Studio projects to new versions of Visual Studio, we have published a set of instructions on how to Use Measurement Studio 2013 with Microsoft Visual Studio 2013.

 

Measurement Studio Release Cycle

MStudio Release Cycle Roadmap.png

Please do not hesitate to send me your feedback.

 

Thanks and happy programming,

 

Anna Kozminski

Measurement Studio Marketing Manager

 

» Download Measurement Studio 2013

» Submit a feature request to the Idea Exchange

0
0
This feed URL is no longer valid. Visit this page to find the new URL, if you have access: <a href="http://www.facebook.com/profile.php?id=357696587589030">http://www.facebook.com/profile.php?id=357696587589030</a>

Originally posted by Facebook.com at http://www.facebook.com/feeds/syndication_error.php#5bb1329e84a0d7cae566d1161054 2b7c_
0

LVcompatible.silver_small.hor.PNG
We're very proud to announce that Grafcet Designer is now a Silver level Compatible with LabVIEW product and member of the LabVIEW Tools Network ! You can find it here.

 

 

lvtn_vipm.PNG

 

As a part of the LabVIEW Tools Network and can be downloaded through the VI Package Manager (VIPM by JKI Inc.).

1

Hallo Herr Salomon,

 

wir haben eine Frage zu unserem Projekt:

 

Wir senden mit unserem Programm eine UDP Message und erwarten eine Antwort. Wir bekommen dann aber einen Timeout-Fehler (ERR 56), da wir keine Datenpaket erhalten.

 

Liegt der Fehler in unserem Programmcode oder müssen wir für die UDP Kommunikation irgendwelche Einstellungen in LabVIEW vornehmen? Das Internet gibt hierrauf keine hilfreichen Antworten.

 

MfG

Röhm & Genkinger

0

Dear readers,

 

there have been some questions on how to create a Visual Studio project from the source files (.cpp) that are attached to some of the posts on this blog. This makes it possible to modify the code to your preferences.

The post will hopefully act as a tutorial in order to successfully create a project using either OpenCV or PCL functionalities. You can setup the project manually of course, but I prefer using Cmake (open-source). This helps you configure all dependencies and libraries with a couple of mouse clicks. You can get it from here:

 

http://www.cmake.org/

 

After installing Cmake, follow the instructions below:

 

1. create a new folder (I will call it "project folder") and put the source code (.cpp) inside it. Create another folder inside the previously created folder and name it "build".


2. create a file named "CMakeLists.txt", put it in the "project folder" and setup the Cmake variables in the .txt as follows (replacing the bold text with your values):

    

     2a. using OpenCV

         

               cmake_minimum_required(VERSION 2.6)

               project(project name)

               find_package(OpenCV REQUIRED)

               add_executable(name source_file.cpp)

               target_link_libraries(name ${OpenCV_LIBS} )

 

     2b. using PCL

         

               cmake_minimum_required(VERSION 2.6 FATAL_ERROR)

               project(project name)

               find_package(PCL 1.3 REQUIRED)

               include_directories(${PCL_INCLUDE_DIRS})

               link_directories(${PCL_LIBRARY_DIRS})

               add_definitions(${PCL_DEFINITIONS})

               add_executable(name source_file.cpp)

               target_link_libraries (name ${PCL_LIBRARIES})

 

3. open Cmake and add path to source code (...\"project folder"). Add also the path to the "build" folder.

 

4. select "Configure" and specify the generator for the project (I use Visual Studio 2010). Use default native compilers. Click finish.

 

     4a. if OpenCV configuration is giving errors, complaining that OpenCV directory is not found, manually add it. Select "ungrouped entries" and specify the OpenCV dir "...\opencv\build". Click "Configure" again.

 

5. click on "Generate".

 

6. the "build" is now populated with the Cmake output. Open the Visual Studio solution.

 

7. in "Solution Explorer", right click on your project and select "Properties". Under "General" change "Target Extension" to .dll and change "Configuration Type" to "Dynamic Library (.dll)".

 

8. Apply changes and build solution. I suggest using "Release" configuration for optimized performance. Remember you need to do step 7 for the "Release" configuration also.

 

Hope this will be useful to people having troubles with building from source code.

 

Best regards,

K

5

As most regular readers will know my prime interest is software design and specifically why a design becomes complex. Since becoming a CLA I have had quite a lot of my fellow CLAs stipulate how important SMORES is when judging a good design.

 

In the interest of foolishness I going to state now that I don't get it!

 

So the question I throw back is this.

Is SMORES the only tool you use to judge a good design?

 

First I guess I should describe SMORES

 


Scalable

Modular

Optimized

Reusable

Extensible

Simplified

 

I'm going to do my due diligence now and explain each one in turn. Most of this has been stolen from here.

Scalable

For something to be scalable, it must work the same without modification regardless of how much throughput the system has to manage.  In software, scalable software can handle one or many users, one or many channels of data, one or many reports, etc.

Modular

If you use SubVIs you are making modular code, if these modules are designed with some regard to coupling, cohesion and information hiding your code will more pleasant than if you don't.

Optimized

Software, processes, and systems should be reviewed and streamlined to ensure the best possible output has been achieved. 

Reusable

To make something "reusable" refers to the extra investment required to take anything originally designed for a specific purpose and add the input and output definitions and refinements to make the same object attractive for use on another purpose.

Extensible

Extensible refers to the ability to connect new functionality onto an existing system without having to rearchitect whatever you are connecting on to.  A good example of this is a plug-in architecture.

Simplified

Simplified doesn't always mean the object can or should be "simple".  It means that there is value to be had in making the object you are building as simple as possible without sacrificing scalability, extensibility, etc.

 

I have several issues with these as design considerations in my problem domain, I'll tackle the easy ones first...

 

Optimized and Simplified - now these seem a little wishy-washy and hard to measure to my engineering brain, who defines simplified for example. As we have seen from our design discussions here simple for me is not necessarily simple for someone else (more likely the other way round in my experience), so how do we judge it?. Similarly at what point are we happy that a system has been optimized to our satisfaction.

 

Modular - I've whittered on about modular design a lot here and it is kind of an assumption that if you don't use SubVIs you probably shouldn't be worrying about SORES (see what I did there)

 

Scalable - We've had several interesting conversations about this and my position is this, we write configurable software, this gives us a certain amount scalability. I would also add that LabVIEW is a high level language (definitely 4GL), some might even call it a Rapid Application Development environment. Should we really be applying this amount of importance to scalability for a language so high level?

 

Extensible - I think the following quote from an excellent article by avilay sums up a lot of the point I'm trying to make.

“but suppose that tomorrow somebody wants to add X here…”. Be wary of this design principle. Be very wary. Unless “tomorrow” is a real date in the future, and “somebody” is a real person, this design principle can lead you down a deep rabbit hole with nothing but dirt at the bottom.

 

http://avilay.wordpress.com/2012/09/01/what-is-good-software-design/

 

Re-use - I like re-use, really I do. But I suspect a lot of time is spent polishing code for re-use and it gets stuck away and never touched. There is some very interesting and honest work done on re-use that concludes that the payback of planned re-use is not quite what you would expect.

 

Arnoud de Kuijper - Test and Measurement Solutions did an excellent presentation at the European CLA Summit, in it he introduced SMURF

A version is linked here

 

Scalable
Modular

Unique
Reusable
Flexible

 

I prefer this mainly because I love the little blue fellas. Also Flexible is very very important to me and Unique is actually a grown up way of describing what we do. We have a couple of standard templates but quite a lot of what we do is unique from system to system.

 

Now I would like to add a few more to the list.

 

I can't believe Functional and Robust are not on the list. Readable, Debuggable and Maintainable are extremely important design considerations too. Measurable is also an increasingly important design consideration, especially in RT or control systems. As mentioned earlier Configurable as a sub-set of scalable is a very important design criteria for us.

 

Now how do our customers mark our software if they have to allocate points and how does this compare to our own marks?

James Shore writes about good and great software design in an article titled Quality with a Name. From the article:

 

A good software design minimizes the time required to create, modify, and maintain the software while achieving acceptable run-time performance.

 

Also these requirements don't always play nice together, many of the techniques for extensibility seriously affect readability and so it goes on.

 

So am I dismissing SMORES out of hand?

I think SMORES is useful if you are designing APIs and toolkits, I think it is less useful for projects.

So perhaps we need acronyms for each type of use case.

 

Or

 

Perhaps we should not use acronyms blindly.

 

Lots of Love

S.T.E.V.E

0
This feed URL is no longer valid. Visit this page to find the new URL, if you have access: <a href="http://www.facebook.com/profile.php?id=357696587589030">http://www.facebook.com/profile.php?id=357696587589030</a>

Originally posted by Facebook.com at http://www.facebook.com/feeds/syndication_error.php#5bb1329e84a0d7cae566d1161054 2b7c_
0

Optical sensing is an important new technology for strain and temperature measurements in demanding applications, such as harsh environments and high channel count applications. We are excited to announce a pricing promotion for the PXIe-4844 Optical Sensor Interrogator through August 10, 2014, to give engineers and scientists the ability to benefit from this technology.

 

 

ni-osi.jpg

 

Key Benefits:

  • Acquires measurements with 1pm of accuracy (~0.1 °C and ~1.2 µε)
  • Nonconductive, electrically passive, and immune to EMI-induced noise
  • Can transmit data over long distances
  • Ability to daisy chain 80 sensors on a single module

 

>> Learn more about optical sensing.

>> Learn more about the promotional pricing.

0

Queremos felicitar a los nuevos usuarios entrenados en la plataforma LabVIEW 2013, a través de los cursos Core 1 y Core 2, dictados en la semana del 7 de abril, en nuestra oficina de NI Chile.

 

Los alumnos pertenecen a uno de nuestros integradores DTS, además de Armada de Chile y EnerControl.DSC_0707_800_500.jpg

 

Muchas gracias por su participación y buena onda, y acá estamos para seguir apoyándolos en sus proyectos con LabVIEW.

0

The U.S. Department of Energy is counting on wind power to meet 20% of the nation’s power needs by 2030, up from 3% today. This feat will only be possible if the leading academic and industry experts advance technologies needed to develop offshore wind power, and NI is playing a central role in this collaboration.

 

Last November, Clemson University unveiled the world’s largest 15-megawatt Wind Turbine Drivetrain Test facility, intended to create new technologies for the energy market. They selected NI LabVIEW and  NI PXI modular hardware for a majority of measurement types. 

 

clemson1.jpg

 

The facility has expanded to include a grid simulation lab that allows manufacturers to test both the mechanical and electrical characteristics of their machines in a controlled and calibrated environment. It uses LabVIEW and NI Multisim software, as well as NI PXI, NI R Series, NI FlexRIO, and NI CompactRIO hardware.

 

With this new and innovative testing center, companies can test a hardware prototype for any energy resource on a utility scale (up to 15 MW, which is HUGE) and gauge the impact of adding this technology to the actual grid before deploying it. This blows away any other wind turbine test facility in the world!

 

>> Read the full case study.

0
This feed URL is no longer valid. Visit this page to find the new URL, if you have access: <a href="http://www.facebook.com/profile.php?id=357696587589030">http://www.facebook.com/profile.php?id=357696587589030</a>

Originally posted by Facebook.com at http://www.facebook.com/feeds/syndication_error.php#5bb1329e84a0d7cae566d1161054 2b7c_
0
This feed URL is no longer valid. Visit this page to find the new URL, if you have access: <a href="http://www.facebook.com/profile.php?id=357696587589030">http://www.facebook.com/profile.php?id=357696587589030</a>

Originally posted by Facebook.com at http://www.facebook.com/feeds/syndication_error.php#5bb1329e84a0d7cae566d1161054 2b7c_
1

Hello my problem is that. I am able to control only one led and the other one, i am not able to control it.

can somebody help me what is the problem with the VI. My lifa is ok since the first led is working

perfectly fine when i am pressing the on / off button in labview. I will really appreciate to get answer

for this problem of mine.

0
This feed URL is no longer valid. Visit this page to find the new URL, if you have access: <a href="http://www.facebook.com/profile.php?id=357696587589030">http://www.facebook.com/profile.php?id=357696587589030</a>

Originally posted by Facebook.com at http://www.facebook.com/feeds/syndication_error.php#5bb1329e84a0d7cae566d1161054 2b7c_