hard-coded ZFC Equipment paths. #1

Open
opened 2026-08-11 11:44:36 +02:00 by krieger_j · 2 comments
Owner

The /Equipment/ZFC odb path is hardcoded in multiple places in this frontend. However, that path was renamed to /Equipment/Zero_field_compens on VMS.
It is likely that this causes the frontend to fail.

odbstat = db_get_value(hDB,0,"/Equipment/ZFC/Settings/Devices/IN/DD/Automatic (0,1)",

The /Equipment/ZFC odb path is hardcoded in multiple places in this frontend. However, that path was renamed to /Equipment/Zero_field_compens on VMS. It is likely that this causes the frontend to fail. https://gitea.psi.ch/lin-midas-drivers/expmag/src/commit/b7b388216370214333d2ac7bd17b46d4e2c70d5b/device/expmag.cxx#L3876
Author
Owner

@wall_e As a hotfix, I think I can just replace the corresponding ZFC paths with the new VMS variant. However, since this frontend is also used on GPS and GPD, this might create issues, when the previous ZFC device is renamed to something else there.
Should I go ahead with that anyway, for now? Or aim for something more configurable?

@wall_e As a hotfix, I think I can just replace the corresponding ZFC paths with the new VMS variant. However, since this frontend is also used on GPS and GPD, this might create issues, when the previous ZFC device is renamed to something else there. Should I go ahead with that anyway, for now? Or aim for something more configurable?
Owner

Go ahead for now. It is better that it can be tested with hardware at one of the instruments. We can worry about making it more generic when the beam is back on :D

Go ahead for now. It is better that it can be tested with hardware at one of the instruments. We can worry about making it more generic when the beam is back on :D
krieger_j referenced this issue from a commit 2026-08-11 13:32:30 +02:00
Sign in to join this conversation.
No labels
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lin-midas-drivers/expmag#1