Skip to content

Commit 696cd1a

Browse files
committed
add notes on custom bob screen
1 parent f09b8a9 commit 696cd1a

File tree

2 files changed

+13
-0
lines changed

2 files changed

+13
-0
lines changed

docs/images/custom_bob.png

396 KB
Loading

docs/tutorials/dev_container2.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,19 @@ ec up -d
5656

5757
Phoebus will be launched and attempt to load the bob file called **opi/ioc/index.bob**. The **opi** folder is a place where the author of this generic IOC could place some screens. The subfolder **ioc** is not committed to git and is where the IOC instance will place its autogenerated engineering screens. The autogenerated screens always include and index.bob which is the entry point to all other autogenerated screens.
5858

59+
## /workspaces in Phoebus Container
60+
61+
Just like the developer container itself, the Phoebus container mounts the folder above **ioc-adsimdetector** into the container as **/workspaces**. This means you can access bob files from peer projects.
62+
63+
The autogenerated engineering screens currently show the image array as a list of integers. But we already had a nice screen for displaying an overview of the PVs, including an image widget for the image array. That screen was made for the same IOC instance we are currently running inside of the developer container.
64+
65+
To access the screen, chose `File -> Open` in phoebus and navigate to **/workspaces/t01-services/opi/demo-simdet.bob** file. This will open the screen in phoebus and allow you to view the sample image.
66+
67+
:::figure
68+
![Phoebus Screen](../images/custom_bob.png)
69+
Example overview screen for bl01t-ea-cam-01
70+
:::
71+
5972
## Using Host Machine Tools
6073

6174
If you have EPICS tools installed on the host machine then those can now also be used.

0 commit comments

Comments
 (0)