Ignore:
Timestamp:
08/13/12 09:45:44 (12 years ago)
Author:
tbretz
Message:
It is not necessary to check the rate control only for the timeout of the FADs. Before starting the trigger we have to wait until the state of the rate control is GlobalThresholdSet
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/FACT++/src/mcp.cc

    r14244 r14350  
    329329
    330330            Message("Starting Rate Control");
     331            // State of RC is not reported back fast enough!
    331332            Dim::SendCommandNB("RATE_CONTROL/CALIBRATE");
    332333
     
    348349            if (fDimFTM.state() == FTM::State::kConfigured &&
    349350                fDimFAD.state() != FAD::State::kConfigured &&
    350                 fDimRC.state()  >=  RateControl::State::kSettingGlobalThreshold &&
     351                /*fDimRC.state()  >  RateControl::State::kSettingGlobalThreshold &&*/
    351352                fFadTimeout+boost::posix_time::seconds(15)<Time() &&
    352353                count(fFadNeedsReset.begin(), fFadNeedsReset.end(), true)>0)
     
    359360            if (fDimFTM.state() != FTM::State::kConfigured ||
    360361                fDimFAD.state() != FAD::State::kConfigured ||
    361                 fDimRC.state()  <  RateControl::State::kSettingGlobalThreshold)
     362                fDimRC.state()  <= RateControl::State::kSettingGlobalThreshold)
    362363                return MCP::State::kConfiguring3;
    363364
Note: See TracChangeset for help on using the changeset viewer.