Archive for the ‘LabVIEW’ Category

 

Monster Panel V

7
History requires a chart, right?       Wrong. In Part I, recall from the requirements that we want : — A chart, showing the history of 1-4 channels.  The history can be the last 30 seconds, or the last 30 hours, or various lengths in

more

Monster Panel IV

0
51 wires?  No – use a cable. In Part III, we talked about how to take 3672 copies of a 300-channel list and cut the memory requirements down to size. The price we pay for that savings is a bit more work on our part.  But it’s a

more

Monster Panel III

2
Re-think the easy ways you have used forever. In Part I, I gave the rough outline of the task: how to manage over 12000 controls/indicators on one panel. In Part II, we started whittling the task down to size, using sub panels and reentrancy.  

more

Monster Panel II

0
Figuring out what you do NOT have to do. In Part I, I gave the rough outline of the task: How to manage over 12000 controls/indicators on one panel. The first thing to realize is that the beginner’s reaction (“holy crowdation Batman, that’s impossible”) is

more

Monster Panel I

0
Handling thousands of controls is easier than you think. LabVIEW programmers progress from the excitement of the new paradigm to just using it as a tool.  We’ve all produced some “spaghetti” code, and we’ve all had to look at somebody else’s flavor of spaghetti and

more

Needle in the Haystack

2
Finding the best answer is not always straightforward. Scientists are not programmers. Repeat that after me: scientists are not programmers. It’s not their fault; it’s just a lack of proper training.  If you are implementing some algorithm given you by a scientist, it’s important to

more

Beware Simplicity

2
Simpler ≠ faster : you still have to know what happens “under the hood”. If you read the post about en masse operations, you might remember that I pointed out that you should know what is happening behind the scenes. Here is a particular case

more

Terminator 2: the Sequel

2
Make sure that quitting time is followed by happy hour. As mentioned earlier, a compiled LabVIEW application behaves similarly to the development system when terminating.  Namely, it leaves the main window on the screen, waiting for you to close it.  That’s handy in the DevSys,

more

Virtual Devices

0
When you don’t have the DAQ hardware you need… Any version of NI-DAQ and the Measurement and Automation Explorer (MAX) released recently has provisions for “simulated” devices.  You choose which devices you want, and then NI-DAQ will pretend those devices are actually installed on your

more

Writing Non-Fragile Code

4
Oooops…. who broke it? “Fragile” code is code that breaks in one place because of changes you make in some other place. It’s most aggravating when you’re due to ship a new version tomorrow and you need to make one last tweak at 11:30 PM,

more

    Affiliations

    • TI Alliance

    Calendar

    September 2017
    M T W T F S S
    « Sep    
     123
    45678910
    11121314151617
    18192021222324
    252627282930  

Testimonial  Contact Info

207-790-0949

1-877-676-8175 (toll-free)

Fax: 1-815-572-8269

General questions:

Sales@Culverson.com

Accounts/billing questions:

Accounts@Culverson.com


Logo