Lantz is an automation and instrumentation toolkit with a clean, well-designed and consistent interface. It provides a core of commonly used functionalities for building applications that communicate with scientific instruments allowing rapid application prototyping, development and testing. Lantz benefits from Python’s extensive library flexibility as a glue language to wrap existing drivers and DLLs.
(Is this a pull request?) Although I don't know if this something that can or should be fixed, when closing/disconnecting normally from a multimeter (specifically a Keithley 2100 DMM), i.e. not due to an error, the instrument is left in remote mode; when I rerun the script without manually placing the DMM back in "local" mode, it errors "-410 Query INTERRUPTED". If I manually return it to local made (by pressing a button on the front panel), repeated script executions work just the same. Is there a way to check if the instrument requires returning to local mode, and if so, sending the command before shutting everything down? If it can't be checked, is there an easy boolean that would be settable to enable this?
(Is this a pull request?) Although I don't know if this something that can or should be fixed, when closing/disconnecting normally from a multimeter (specifically a Keithley 2100 DMM), i.e. not due to an error, the instrument is left in remote mode; when I rerun the script without manually placing the DMM back in "local" mode, it errors "-410 Query INTERRUPTED". If I manually return it to local made (by pressing a button on the front panel), repeated script executions work just the same. Is there a way to check if the instrument requires returning to local mode, and if so, sending the command before shutting everything down? If it can't be checked, is there an easy boolean that would be settable to enable this?
Thanks!