Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
optimization
dschless
Member
08-02-2004 10:39 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I am kind of new at programming and I was wondering if anyone had ideas on how to optimize my code.
Download All
Virus scan in progress. Please wait to download attachments.
MikeG
NI Employee (retired)
08-09-2004 06:17 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Thank you for contacting National Instruments.
Though our tech support department generally doesn�t look over code for the purpose of general commenting or debugging, I surveyed your code and I can suggest a couple of things.
The first is a programming practice that has wide applicability for many DAQ applications. The practice is to create a separate thread for data acquisition. This way, your data acquisition, which really is the time critical piece of the code has precedence over the user interface updates, which are almost always less important from a timing standpoint. Full details on creating new threads in CVI can be found at the following link:
http://zone.ni.com/devzone/conceptd.nsf/webmain/2DF76D8073AA2A8C86256D2C005586D2?opendocument
As an
other general tip, and I don�t think this is necessarily an issue here, make sure that you are updating your front panel values only as frequently as necessary. For instance, if a value isn�t going to change between updates, you may want to skip the call to update the user interface with that value until it actually does change. There is always a little overhead associated with changing the UI display, so it is something to keep in mind.
The first suggestion is the major one, of course. Hope this helps!
Regards,
Mike G.
National Instruments Support
Though our tech support department generally doesn�t look over code for the purpose of general commenting or debugging, I surveyed your code and I can suggest a couple of things.
The first is a programming practice that has wide applicability for many DAQ applications. The practice is to create a separate thread for data acquisition. This way, your data acquisition, which really is the time critical piece of the code has precedence over the user interface updates, which are almost always less important from a timing standpoint. Full details on creating new threads in CVI can be found at the following link:
http://zone.ni.com/devzone/conceptd.nsf/webmain/2DF76D8073AA2A8C86256D2C005586D2?opendocument
As an
other general tip, and I don�t think this is necessarily an issue here, make sure that you are updating your front panel values only as frequently as necessary. For instance, if a value isn�t going to change between updates, you may want to skip the call to update the user interface with that value until it actually does change. There is always a little overhead associated with changing the UI display, so it is something to keep in mind.
The first suggestion is the major one, of course. Hope this helps!
Regards,
Mike G.
National Instruments Support
