Currently the GPIBtransport is a naive implementation that only does simple reads/writes to a board index and address through linux-gpib.
This works fine for one instrument, but having multiple instruments can/will cause multithreading issues.
To remedy this we should implement a global GPIB interface class that manages addressing and read/write per GPIB interface card/dongle. This will allow use of multiple instruments on one bus. Running multiple instances of ngscopeclient and arbitrarily accessing instruments will remain unsupported.
Currently the GPIBtransport is a naive implementation that only does simple reads/writes to a board index and address through linux-gpib. This works fine for one instrument, but having multiple instruments can/will cause multithreading issues. To remedy this we should implement a global GPIB interface class that manages addressing and read/write per GPIB interface card/dongle. This will allow use of multiple instruments on one bus. Running multiple instances of ngscopeclient and arbitrarily accessing instruments will remain unsupported.