07-06-2006 10:22 AM
07-06-2006 10:44 AM
07-06-2006 11:20 AM
07-06-2006 11:35 AM
That looks like a completely different problem to me. Is the instrument on and is the VISA Resource Name correct?
I also just noticed something strange in your 'no event' state. The array of strings that gets indexed into the Insert Queue Element is missing all of the values except for element 0 and that's a wrong value. Your front panel buttons won't work.
07-06-2006 11:52 AM
Yes, all the instruments are 'on' and the VISA resource name is correct. (still overwrites the instrument setting)
A couple of questions...
1. Does the order of the array element decide the element number? (I guess '0' should be 'load config' and '1' is 'set config'??)
2. Is it possible to selectively execute certain case structure for testing purpose?
07-06-2006 12:01 PM
1. Yes. The order of the elements in the string array should match with the order of the Boolean array you create.
2. If your string array is correct and you return to the 'No event' state every time, then yes, you can debug individual states. That means, though, that you can't modify the queue in any of the states. So, for example in the 'load instrument settings' state, you would have to remove the Insert Queue function temporarily or put a case statement around it so that you can disable it when you want.
07-06-2006 01:34 PM
So, if I want to just test on 'load instrument settings' and 'save config' states, I need to return to 'No event' state after 'save config' (?)
What do I have to do for those elements in the string array in case if they are not used?
I am not sure what actually causes instrument to reset even after manually changing setting values...
07-06-2006 02:09 PM - edited 07-06-2006 02:09 PM
Your No Event state should look like this:
The only thing that would case an instrument to reset is if you are issuing the reset command.
Message Edited by Dennis Knutson on 07-06-2006 01:10 PM
07-06-2006 04:07 PM
07-06-2006 04:47 PM