Bottomline: I can’t seem to hit a visa instrument/w TUI in a container because it cannot find the KS IO libraries (which are installed). Screen shot below summarizes the issue.
Hopefully this is my last issue with running the TUI in a container. When I am able to create a SCPI instrument and test step in the TUI, when the step is executed, an error is displayed that implies that the KS libraries are not being found. A screen capture showing the error message during execution is shown below. Here is a summary of the situation/environment:
- This is running in a docker that can ping the instrument
- If I run the docker with a pure python pyvisa and pyvisa-py backend (without the KS backend), I can run the *IDN? scpi command ok. (I have a special one-off container that loads up python, pyvisa, and pyvisa-py). I can also run an external browser to the instrument’s OEM web page from my host (laptop) and run the scpi command that way too, so I know the network is set up correctly.
- It’s difficult to get an SCPI instrument created in the TUI due to it locking up when trying to create a new instrument (I posted a different thread about that issue), but once in a while I can manage to get the instrument created and a subsequent SCPI test step created ok. I can then execute that test plan, but that is when the following error shows up. (see screen shot below)
- If I run another one-off docker with python, pyvisa, and the KS libraries, the python script that tries to run the SCPI command will fail, again with an error similar to that in the TUI: that the visa backend cannot be found (sorry I don’t have the exact error message that the python script displays)
- If I manage to get TUI to create an instrument and test step and save off the resulting /opt/tap/Settings/Bench/Default files, and then re-use those files in another newly created docker container (created with the same Dockerfile), then TUI doesn’t come up: it just locks up at a blank screen.