Attempt to build ubuntu container/w:
- network tools such as ping
- opentap
- tui
- keysight libraries
- x11 libraries to support running gui apps over xterm
- On the host (i.e. your laptop/desktop), perform these steps...
- Clone the project from github/the repo, change to the research directory of the project.
cd vte/research/tuiresearch - If it is not in the directory (i.e., not part of the repo since it's a big file and we don't always include it in the repo), you'll have to go out and download the KS library independently, namely
iolibrariessuite-installer_20_0_26913_1.runand copy it to the project directory. - Likewise, if it is not in the directory, you'll have to go out and download the latest OpenTap package independently, namely
OpenTap.9.16.2+f3c96b9f.Linux.TapPackage - Run:
./build.sh - If, during the build, you see the error message similar to
This device is not connected to the network -- aborting the installation., which is from the keysight library installation, stop the build, then make sure you are not connected to any LQ/TMC VPN, and then restart your host's (laptop/desktop's) docker engine, then re-run the build script). This error was especially an issue when running the build script on a Mac and each time a restart of the docker engine seemed to fix it. - You'll have an ubuntu container with openTap, tui, keysight libs, and x11 libs.
- Run:
docker images | grep ot - You should see your new image,
otin the list of docker images - Run:
./run.sh - Your image will start up as a container, optionally Run:
docker ps, you should see the ot container - To log in to the container, Run:
docker exec -it ot bash - You should now be logged into the ubuntu container
- Optionally, try to ping the instrument:
ping 192.168.26.49(that is an example IP only) - To run TUI, run:
tap tui - To run the TP_SIGGEN_IDN.xml test plan, open it up in TUI and hit the Run Test Plan
- Alternatively, within TUI, you can create a new instrument/w the correct VISA address
- Also within TUI, you can create a new SCPI test step to execute just the *IDN? command
- Finally, within TUI, run the test plan
- Exit TUI and you'll be back in the cmd line of the container
- To test out xterm capability with your host you can run:
xclock. An xclock gui should appear if you have set up your xterm/x11 properly on your host. If it does not work, then you can check the run.sh command of this project for hints on how to get it running, but this is beyond the scope of this project. - If the xclock app worked, you can optionally run the ConEx application. Run: `/opt/keysight/iolibs/ui/connection-expert/ConnectionExpert.
- To exit the container, Run:
exit - You're now back at the host ~ ~ ~