Menu

Possible hazard on STOP

Support
2020-01-28
2020-05-04
  • Mike Barwise

    Mike Barwise - 2020-01-28

    We have been alerted to a possible, although remote, hazard when the STOP statement or the stop selection of the PAUSE statement is invoked. It may also occur if a script auto-aborts due to time out of a query command for which the T flag is set.

    Regardless of the order in which instruments are opened within your script, under these conditions they close in an arbitrary sequence defined by the Java method currently used for close.

    If both power supplies and signal sources are being controlled, AND if power supply disengage strings include (optional) turn off sequences, under the conditions stated it is possible that power may be disconnected from a circuit under test before signals are turned off. Some sensitive circuits or devices may be damaged by this.

    We are addressing this hazard in an update to be released shortly. In the meantime we recommend that power supply definitions should not include optional turn off command strings in their disengage strings. Power as set in your script should remain on after the script terminates for any reason.

     
  • Mike Barwise

    Mike Barwise - 2020-05-04

    Good news!
    The instrument close sequence issue on STOP has been fixed in Skippity V1.11, available now.

     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB