09-13-2005 09:10 AM
09-13-2005 11:44 AM
09-13-2005 02:54 PM
09-13-2005 03:27 PM
09-13-2005 03:48 PM
09-14-2005 08:17 AM
09-14-2005 05:15 PM
09-15-2005 08:05 AM
09-17-2005 05:06 PM
09-19-2005 08:20 AM
I've worked in production environments for over 25 years and have often worked with microwave.
Listen, all I'm saying is that using a numerical control ability to coerce and limit a range is not the most elegant. Incorporating some simple range checking is not all that difficult and provides all the benefits of restricting what values are passed to an instrument and providing feedback to the user at the same time. Error checking means that no incorrect commands are sent. It does not mean write the command and return an error. When you set the error Boolean true in the error cluster, no write or read is possible.
If a production program is passing incorrect values to an instrument, then there's a major problem with the production program and the test is invalid. If my program has such a bug, I want it to stop. How else are you going to fix it?
I thought we were talking about generic drivers. Imho, anything else belongs in the higher level application program.