DOOCS server for synchronizing laser oscillators to optical and RF reference signals.
see here... (links)?
Version 1.17.00, released on
- OXC-ODL motor selection and configuration
a) Property ///OXC_MOTOR_ADDRESS_ACTIVE.RD replaced by ///OXC_ODL.ADDRESS_CONFIG.WR
b) Property ///OXC_MOTOR_ADDRESS_CONFIG.WR replaced by ///OXC_ODL.ADDRESS_ACTIVE.RD
Change logic of ODL address creation.
Before 1.17.00 ///OXC_MOTOR_ADDRESS_ACTIVE.RD was used only to store address of OXC-ODL motor and used only in jddd panels
In version 1.17.00 user can use 2 configurations:
a) OXC-ODL motor is controlled by external server.
Then ///OXC_ODL.ADDRESS_CONFIG.WR contains address of external motor.
Address CANNOT point to the instance of the server which holds the property.
External server MUST be available during start of the laser lock server.
Example entry: FLASH.SYNC/LASER.LOCK.EXP/FLASH2.THZSTR.OSC/FMC0.MD22.1.
In this mode ///OXC_ODL.ADDRESS_ACTIVE.RD will contain the same value as ///OXC_ODL.ADDRESS_CONFIG.WR
b) OXC-ODL motor is controlled by laser lock server instance which is using it.
In this case ///OXC_ODL.ADDRESS_CONFIG.WR is NOT created.
Enabling this mode and selection which MD22 motor instance is used is done by entries in "appCsa.config" config file located server folder.
To enable the mode following entry must be found in "appCsa.config"
26A.L1; OXC_ODL.MD22_SLOT; 0; UINT
Allowed values are 0 and 1. It defines FMC slot of MD22 used to drive OXC-ODL.
Server will stop during startup if misconfiguration is detected.
If case mode b) is enabled (entry is present), second entry can be introduced into config file.
26A.L1; OXC_ODL.MD22_ID; 0; UINT
Value defines which motor on given MD22 card is used.
If entry not present or value is different than 0 or 1, the default value 0 is applied.
In this mode ///OXC_ODL.ADDRESS_ACTIVE.RD contains properties prefix of used motor. Examples: "FMC0.MD22.0." or "FMC1.MD22.1."
Version 1.16.00, released on