Archive for the ‘Timing’ Category
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
Speed of En Masse Operations
Zip-zap-zowee and swoosh! Just in case you thought I was kidding in the article on en masse operations, I decided to offer some proof of the speed advantages they can give you. I used the Timing Template vi to measure the time it takes to
An Improved Analog Clock
Sometimes all that digital stuff is just too bland. A bug undocumented feature of the original analog clock was that the markers on the scale were at intervals of 1.25 seconds, a consequence of LabVIEW preferring to use 4 intervals per major tick, when we silly
Delays, delays, delays
Can’t you signals just work together? Usually, in a data acquisition program, all the signals you measure are “live”, meaning they represent the current conditions at the time they are sampled. However, in some cases you might have some signals which are not live, but
An Analog Clock (first version)
Sometimes all that digital stuff is just too bland. If you want to display a time-of-day clock in LabVIEW, it takes three seconds to plop down a TIMESTAMP indicator, and 10 more seconds to enter ADVANCED EDITING mode, and skip the month, day and year,
What Time is it?
When you’re trying to make things in your program work faster, it’s important to remember a simple rule. On any given computer… You cannot make the computer go faster. You can make it do less work. Of course, to take advantage of that rule, you
Contact Info
207-593-8109
Culverson Software
184 Lakeview Drive
Rockland, ME 04841
General questions:
Accounts/billing questions:
