Sometimes MaiTai reports laser off when it is not. Acq then does not start

[raacampbell]

Running laser.isPoweredOn always resets it. So we run this before testing for power on state; 864aec9

[raacampbell]

In theory this means the acquisition can proceed but the laser will still appear to have a problem and users will be confused. So need a better system. e.g. have the maitai class run the method if it sees modelocking but no power. I don't recall exactly what the GUI reports when it does this.

[raacampbell]

This is getting annoying. It has stopped acquisitions starting a couple of times now. BT.checkIfAcquisitionIsPossible is running obj.laser.isPoweredOn

    %If a laser is connected, check it is ready
    if obj.isLaserConnected
        obj.laser.isPoweredOn %Sometimes laser claims it is off when it is not. This seems to reset it.
        [isReady,msgLaser]=obj.laser.isReady;
        if ~isReady
            msg = sprintf('%s%d) The laser is not ready: %s\n', msg, msgNumber, msgLaser);
            msgNumber=msgNumber+1;
        end
    end

[raacampbell]

I am confused how to handle this rare problem. I have added a check in the GUI that will force a re-read of the laser on state if the laser is reported as being mode-locked but also powered off (as this is not possible): 561e504

Briefly, in the laser GUI we now do:

        function updateLaserOnElements(obj,~,~)
            % If the laser is reported as being off but is also reported as being
            % mode-locked, then double-check whether or not it is on. Sometimes we
            % have had a laser report it is off when really it is on. Maybe this check
            % will suppress the problem.
            if obj.model.laser.isLaserOn==false && obj.model.laser.isModeLocked==true
                obj.model.laser.isPoweredOn; % forces update of obj.model.laser.isLaserOn
            end