analisi di qaulche rip atraverso i dump della master

/local/aolog/current/ADAPTIVE-SECONDARY_00001347938197_20120918_031637.log

durante un CL a 36 modi

i modi 10,13 e 28 tendono a divergere

/local/aolog/current/ADAPTIVE-SECONDARY_00001347947524_20120918_055204.log

durante un autogain

idx (temporale) cosa accade
993 tutto ok
994 slope sparata, forze ok
995 slope ok, forze saturate
996 tutto ok
se mi ricordo bene la slope skazzata viene passata alla diagnostica, ma non viene applicata, ma al passo dopo c'e' la slope precedente per tenere pulita la delay-line

pero' non mi torna la corrente curraverage. Da investigare accuratamente.

Per evitare i rip dagli eventi spuri, abbiamo aumentato il CAF nella fast da 0 a 2.

/local/aolog/current/ADAPTIVE-SECONDARY_00001347957116_20120918_083156.log: skip+rip mentre era semplicemente a loop chiuso

fastdiagn.L        |WAR|    419469|2012-09-18 08:31:56.630250|     FUNCTWARNING > FunctWarning CHFFPURECURRENT-0005 -0.428089
fastdiagn.L        |WAR|    419470|2012-09-18 08:31:56.643099|     FUNCTWARNING > FunctWarning CHFFPURECURRENT-0005 -0.436926
fastdiagn.L        |WAR|    419471|2012-09-18 08:31:56.658167|     FUNCTWARNING > FunctWarning CHFFPURECURRENT-0005 -0.468383
fastdiagn.L        |ERR|    419472|2012-09-18 08:31:56.667525| FUNCTEMERGENCYST > CHCURRAVERAGE-0019 = -0.8  [Funct.cpp:94]
fastdiagn.L        |INF|    419473|2012-09-18 08:31:56.667570|      ADAM-MODBUS > AdamModbus: disabling coils...

sembra proprio un overcurrent

  • max_abs_force.png: x=loop cycles y=max(abs(actuator forces)). Red=skipped frames. after a couple of skipped frames the loop continued correctly. The last skipframes are a consegunce of a previous event, possibli an overcurrent.
    max_abs_force.png

  • piston_force_zoom.png: to see it an overcurrent appened look at the piston current (=average(forces)). To be checked if overcarrent threshold is 53.5mN per actuator
    piston_force_zoom.png

  • piston_force.png: full history of piston force: the rip event happened at the maximum of pushing force. To be check it that corresponds to the overcurrent threshold. who is driving this force? wind? piston on the commands?
    piston_force.png

  • position_piston_nm.png: The mirror move in piston (80nm PtV in this sample) who is driving that? to be check if there is a piston command in the commands from the reconstructor
    position_piston_nm.png

-- ArmandoRiccardi - 18 Sep 2012
Topic revision: r2 - 19 Sep 2012, ArmandoRiccardi
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback