The Device Permissions Bits

The real motor, pseudo motor, and operation definition entries in the database.dat file each have two lines for restricting the use of the device. The two lines each have the same bits, but apply to different types of groups of users. The first line applies to the Blu-Ice user that have 'Staff' permissions. The second line applies to the Blu-Ice clients that do not have 'Staff' permissions.

There are two lines permission entry for each device will look like this:

Line x: passiveOk remoteOk localOk inHutchOk closedHutchOk
Line x+1:passiveOk remoteOk localOk inHutchOk closedHutchOk

1. The passiveOk parameter can be 0 or 1. A '0' indicates that the Blu-Ice client requesting the move must be 'Active' before DCSS forwards the request to the reponsible DHS. A '1' in this field would allow DCSS to forward the motor move request to the reponsible DHS even if the requesting Blu-Ice is not 'Active'.

2. The remoteOk parameter can be 0 or 1. A '0' indicates that with the hutch door open, the Blu-Ice client must be either running on a 'LOCAL' or 'HUTCH' console before DCSS will forward the move request to the responsible DHS. A '1' in this field would allow the move request to be forwarded to the DHS regardless of where the Blu-Ice client is running, even with the hutch door open.

3. The localOk parameter can be 0 or 1. A '0' indicates that with the hutch door open, the Blu-Ice client must be running on a 'HUTCH' console before DCSS will forward the move request to the responsible DHS. A '1' in this field would allow the move request to be forwarded to the DHS if the requesting Blu-Ice client is running on a 'LOCAL' machine, even with the hutch door open.

4. The closedHutchOk parameter can be 0 or 1. A '0' indicates that the hutch door must be open before the request to move the motor is forwarded to the responsible DHS. A '1' in this field indicates that the motor move may be moved with the hutch door closed.

Figure 1 shows the possible combinations of permission bits and the expected behaviour of the device depending on whether or not the client is 'REMOTE', 'LOCAL', or in the 'HUTCH', and whether or not the hutch door is closed or open.

Figure 1: Device Permissions