Configure(): Difference between revisions
Jump to navigation
Jump to search
(Added Sequencer procedure Navbox) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
The function 'configure' is called whenever a module gets active, i.e. it becomes part of an active branch. It is not called again if the branch changes, but the modules is remains active. | The function 'configure' is called whenever a module gets active, i.e. it becomes part of an active branch. It is not called again if the branch changes, but the modules is remains active. | ||
In 'configure' the entire configuration as specified by the user in the module should be sent to the instrument. It is important that the configuration is not sent in [[initialize]] because it might change later again, for example if a second module connects to the same instrument in another branch where a completely new configuration is needed. | In 'configure' the entire configuration as specified by the user in the module should be sent to the instrument. It is important that the configuration is not sent in [[initialize()]] because it might change later again, for example if a second module connects to the same instrument in another branch where a completely new configuration is needed. | ||
{{Sequencer_procedure}} | {{Sequencer_procedure}} | ||
Latest revision as of 13:50, 2 May 2024
The function 'configure' is called whenever a module gets active, i.e. it becomes part of an active branch. It is not called again if the branch changes, but the modules is remains active.
In 'configure' the entire configuration as specified by the user in the module should be sent to the instrument. It is important that the configuration is not sent in initialize() because it might change later again, for example if a second module connects to the same instrument in another branch where a completely new configuration is needed.