Code Comments

Programming Forum and web based access to our favorite programming groups.
For Programmers: Free Programming Magazines
Registration is free! Edit your profileCalendarFind other membersFrequently Asked QuestionsSearch -> 
Post New Thread











Thread
Author

Re: Handling Instrument Error States
See creating user defined error codes in the help for labview.

Report this thread to moderator Post Follow-up to this message
Old Post
jhoskins
04-23-04 06:38 PM


Re: Handling Instrument Error States
Imho, checking of instrument errors belongs in the recomended Prefix
Error Query VI (where prefix is the instrument model). You should get
the latest copy of the templates, guidelines, etc. from <A
href="http://www.ni.com/devzone/idnet/development.htm">here</A>. Do
not put any range checking in the driver VIs themselves. The
instrument itself should be able to determine if a value is out of
range and the driver should be calling the error query function. You
limit the driver by using LabVIEW for things likerange checking. As an
example, say you've a power supplu model A with a max current of 5
amps. Someone tries to program it for 6 amps and the instrument should
put a message in it's error queue that is read and the programmer
fixes his program. Now, model B of the same supply is released and it
has a max current of 7 amps. If you had limited the current range in
your driver, the driver would not be useable for the new model supply.

If you follow the guidelines, you'll have a much better chance that
your instrument driver will be accepted by NI if that's your ultimate
goal.

Report this thread to moderator Post Follow-up to this message
Old Post
Dennis Knutson
04-23-04 08:40 PM


Re: Handling Instrument Error States
Imho, checking of instrument errors belongs in the recomended Prefix
Error Query VI (where prefix is the instrument model). You should get
the latest copy of the templates, guidelines, etc. from <A
href="http://www.ni.com/devzone/idnet/development.htm">here</A>. Do
not put any range checking in the driver VIs themselves. The
instrument itself should be able to determine if a value is out of
range and the driver should be calling the error query function. You
limit the driver by using LabVIEW for things likerange checking. As an
example, say you've a power supplu model A with a max current of 5
amps. Someone tries to program it for 6 amps and the instrument should
put a message in it's error queue that is read and the programmer
fixes his program. Now, model B of the same supply is released and it
has a max current of 7 amps. If you had limited the current range in
your driver, the driver would not be useable for the new model supply.

If you follow the guidelines, you'll have a much better chance that
your instrument driver will be accepted by NI if that's your ultimate
goal.

Report this thread to moderator Post Follow-up to this message
Old Post
Dennis Knutson
04-23-04 08:40 PM


Sponsored Links




Last Thread Next Thread Next
Search this forum -> 
Post New Thread

LabVIEW archive

Show a Printable Version Send to friend Email This Page to Someone! subscribe to this thread Receive updates to this thread
Computer Consultants
Programming Jobs
Visual Basic Controls
SQL Server Programming
Webservices
Java Security
Visual Studio
C# Programming
Visual J++
Software engineering
Open source Software
Perl Programming
PHP Programming
ASP Programming
ASP .NET Programming
Visual Basic Programming
Windows Scripting Host
Java Programming
Java Help
Java Beans
VBScript
Cobol
MAC Applications
Unix Programming
Forum Jump:
All times are GMT. The time now is 02:27 PM.

 

Programming forum archive

Copyrights CodeComments.com 2004 - 2006

Powered by vBulletin Copyright 2000-2006 Jelsoft Enterprises Limited.