Update Web app startup

arrell_c 2025-03-31 17:23:13 +02:00
parent 77b2c985e3
commit 2d120a8fdf

@ -84,6 +84,50 @@ When a **Setup** button is pressed for a spectrometer, the following process tak
- A **status message** below each button confirms whether the update was **successful** or if an **error occurred**. - A **status message** below each button confirms whether the update was **successful** or if an **error occurred**.
--- ---
## Trigger Settings Restoration
The updated process now includes restoring trigger settings alongside hardware settings. The trigger configuration is stored using minimal information to keep the configuration file human readable while allowing full PV names to be reconstructed later. This configuration contains:
- **server:** The trigger server name (e.g., `SGE-CPCW-73-EVR0`).
- **pulser:** The pulser number that is used to form most trigger PVs.
- **values:** A sub-dictionary with keys that are the EPICS PV suffixes:
- `Evt-Trig0-SP`
- `Evt-Set0-SP`
- `Evt-Reset0-SP`
- `Delay-SP`
- `Width-SP`
- `SetReset-Sel.SCAN` (always updated on Pul4)
- **SW_PULSID_SRC:** The software pulser ID value (from `<camera_name>:SW_PULSID_SRC`).
For example, if the trigger configuration for `SARFE10-PSSS059` is:
```json
"trigger_configuration": {
"server": "SGE-CPCW-73-EVR0",
"pulser": 5,
"values": {
"Evt-Trig0-SP": 0.5,
"Evt-Set0-SP": 1.2,
"Evt-Reset0-SP": 0.8,
"Delay-SP": 100,
"Width-SP": 50,
"SetReset-Sel.SCAN": "Periodic"
},
"SW_PULSID_SRC": 3
}
```
Then the system reconstructs and writes to the EPICS PVs as follows:
- `SGE-CPCW-73-EVR0:Pul5-Evt-Trig0-SP` → 0.5
- `SGE-CPCW-73-EVR0:Pul5-Evt-Set0-SP` → 1.2
- `SGE-CPCW-73-EVR0:Pul5-Evt-Reset0-SP` → 0.8
- `SGE-CPCW-73-EVR0:Pul5-Delay-SP` → 100
- `SGE-CPCW-73-EVR0:Pul5-Width-SP` → 50
- `SGE-CPCW-73-EVR0:Pul4-SetReset-Sel.SCAN` → "Periodic"
And the software pulse ID offset fix is updated by writing the value `3` to `SARFE10-PSSS059:SW_PULSID_SRC`.
### When should these buttons be used? ### When should these buttons be used?