That would be a nice feature. I've also got a misbehaving instrument. When it gets an *IDN? query, it locks up even though it is a supported command. This is not a fault in MAX, it is a fault in the instrument and it sounds like the HP instrument has some problem. No instrument should lock up if it gets an invalid query.
With this misbehaving instrument, I wish I could avoid running a scan for instruments but it's really not possible in my case. When an instrument is returned from cal, the first thing the technician does is a scan for instrument to verify that the instrument is set up correctly. We had to create a special procedure for this system to have him reset the goofy instrument after doing the scan. Having a setting in MAX to skip certain addresses would have made things a lot easier.
