25.07.2014 Views

pdf download - Software and Computer Technology - TU Delft

pdf download - Software and Computer Technology - TU Delft

pdf download - Software and Computer Technology - TU Delft

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Diagnosing the Beam Propeller Movement<br />

of the Frontal St<strong>and</strong><br />

5.2 Scope of the Target System<br />

part in the row Info that enumerates all kinds of parameters. These parameters all say something<br />

about the state of the system.<br />

The scope of the target system depends on considerations, that are specific for PMS, this particular<br />

subsystem, <strong>and</strong> motives of the modeler. Not all components that could cause a failure of the<br />

beam propeller movement are included in the target system. The architecture of the system that contains<br />

components that are considered is described in Appendix B.1. The considerations to decide if<br />

components are included or excluded in the target system are as follows. For all known components<br />

the following questions are asked:<br />

1. Could a PMS service engineer replace this component with a healthy one? In other words, is<br />

the component a FRU?<br />

2. Does the malfunctioning of this components causes an error 11 message to be logged?<br />

3. Could an expert think of any (hypothetically) produced error 11 log data, of which any conclusions<br />

about the component’s state could be derived?<br />

4. Does including the component lead to superfluous complexity of the model?<br />

5. Is the component part of a control loop?<br />

If, for a certain component, all answers on these questions are positive, the component is included<br />

in the scope of the target system. The last consideration is special to this specific subsystem. The<br />

beam propeller movement is implemented by means of three nested control loops, respectively a<br />

position loop, speed loop, <strong>and</strong> current loop. These three control loops play an important role, <strong>and</strong><br />

therefore this question is of importance (see Section 5.3).<br />

Table 5.2 shows the components that are excluded (see Appendix B.1 for the place of a component<br />

within the architecture). The discussed fault diagnosis only addresses the components that are<br />

Component<br />

Failing Consideration<br />

All components that propagate or influence (the cloud in Figure 5.2) the requests 2<br />

speed signal until it enters the backpanel control unit.<br />

backpanel control unit 3<br />

LUC 3<br />

Power Supply 4<br />

Table 5.2: Components that are excluded from the target system.<br />

part of the subsystem Geometry. All components of other subsystems that might lead to a failure<br />

of the beam propeller movement do not cause an error 11 message to be logged. The backpanel<br />

control unit <strong>and</strong> the LUC are not included. The reason for this is that in the current technical setup<br />

it is impossible to differentiate if faults are activated by the backpanel control unit, LUC or its<br />

corresponding LUC_Extension. Because the LUC_Extension has, by far, the highest a priori failure<br />

probability, it has been chosen to include this component in the target system. The power supply<br />

is not included, because adding it leads to superfluous complexity of the model. Note that the fault<br />

diagnosis process proposed below could be extended to enable the diagnosis of these, currently,<br />

omitted FRUs as well.<br />

Table 5.3 names the set of components that are within the scope of the diagnostic process. Each<br />

of them has been given an a priori component failure. These values only determine the order of<br />

53

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!