At 20:23:32 JST, ETMY was tripped suddenly and went to PAY_TRIPPED. At this moment, H3_RMS value seems to jump third time (fig.1), and surpassed the thereshold of WD at last (fig.2). After that, the H3 signal in view of K1:VIS-ETMY_IM_OSEMINF_H3_OUT16 seems to be strange compared with other sensors' outputs (fig.3). Fig.4 is the same signals 17 days before in PAY_FLOAT. Current, H3 seems not to observe ETMY motion for some reason.

I'm not sure how to deal with it, so I leave it tonight.