LabVIEW Virtual User Group: Power Programming with LabVIEW Datalogging and Supervisory Control (DSC) (CLD)
Take advantage of the tools available in LabVIEW Datalogging and Supervisory Control (DSC) Module to take your LabVIEW programming to the next level. Learn about the Model-View-Control architecture for LabVIEW and how to effectively use shared variables through static and dynamic addressing and other such heuristics. Optimize your VIs by eliminating polling logic by adding event structure support for shared variables.
What does CLD mean?
CLD stands for Certified LabVIEW Developer. National Instruments certifications are industry-recognized credentials that distinguish expertise in using NI products for developing measurement and automation solutions. Find out more about the National Instruments Certification Program.
View Now (watch)
49 minute(s) webcast
Reader Comments | Submit a commentDSC Module
I am very disappointed with this module. If a user has to write all the programs on his own, then why not start from a scratch - why buy this DSC module. For instance, you do not need to write program in Windows if you want to create a new folder - its just a matter of right clicking the mouse and select create new folder. However, in DSC, you have to do each and every programming even for creating menus, plotting, event handlings etc. I would suggest process engineers to look for other process software if they are doing HMI and SCADA application - where you just need to create user interface and define variables for your application and integrate them together with the interface that come with the main software. Then you do not have to worry about programming event handling, plotting, developing menus and so on. This will save lots of time. In this video, they have said there are help files associated with the example that ship with this module. I am not sure if that is true. I just tried to use one of the examples - boiler trends, could not find any help files - and I just defined two shared variables rather than using their variables to see if it works. All the code looks the same but its already two days I have been trying to debug. If I have to spend days to deploy examples for my application, then whats the use. Then, if I contact their support, they take another 2 -3 days to solve the problem. For one simple problem, if you have to allocate a week then I am not sure how you can develop application containing 10000 variables programmatically in labVIEW DSC and Labview. Of course if you have 10 years then you can do it. I would rate this product as incomplete and give a poor rating.
- Rupen Panday, REM/NETL. email@example.com - Jan 25, 2011