Set-up and measurement sequence

When loader / spectrumloader is loaded, it looks at the instrument parameter sent to it and begins loading the modules in that string. Each module is responsible to register itself in the instrument registry after it has initialised itself and are ready to be used. The instrument registry keeps track of the instrument movieclip, the instrument module movieclip and a xml tag used to identify the instrument. Currently only one instrument is allowed per module.

After all the modules are loaded the client is ready to be used. The user sets up its experiment and performs the experiment (Presses the "Perform experiment" button).

Before any measurements can be performed the client must authorise itself against the server. This is done automatically (by the CSession), when you do your first measurement. The cookie parameter given by the webserver are sent in a special authorisation request to the server. The server verifies that the ip and the cookie matches the one given by the webserver.

Now all the settings are gathered from each instrument registered in the registry. Each instrument must implement the IInstrument interface (source:trunk/ which forces the instrument to be able to handle reading and writing request / response xml and save data respectively. Currently only the breadboard handles save data.

The gathered settings are transmitted to the server in a measurement request, which are transported to the server where the measurement is done. The result is transported back, and each instrument must now read its response data (part of the IInstrument interface). Each instrument must keep the settings and what is displayed in sync. This means that data returned from the server has to be displayed as the imitated instrument would.

Last modified 9 years ago Last modified on Dec 5, 2008, 4:52:28 PM