SAE AS 5393-2002 Health and Usage Monitoring System Blade Tracker Interface Specification《健康和使用监控系统的叶片跟踪器接口规范》.pdf

1、AEROSPACE STANDARDAS5393Issued 2002-12Health and Usage Monitoring System,Blade Tracker Interface SpecificationTABLE OF CONTENTS1. SCOPE .31.1 Classifications31.2 Specification Terminology32. APPLICABLE DOCUMENTS42.1 SAE Publications .43. DEFINITIONS.44. POWER/BLADE TRACKER INTERFACE45. INDEXING SENS

2、OR/BLADE TRACKER INTERFACE46. HUMS PROCESSOR/BLADE TRACKER INTERFACE.56.1 Send rotor Track Data66.2 Send rotor Balance data 76.3 Send Average Rotor Track Data96.4 Send Average Rotor Balance Data96.5 Send Average Rotor Track Data With Statistics 106.6 Send Average Rotor Balance Data With Statistics 1

3、16.7 Set Auto Lighting mode .126.8 Force Night Mode 126.9 Force Day Mode 126.10 Clean Lens.126.11 Number of Blades12Reaffirmed 2009-1SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report i

4、s entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising therefrom, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE

5、 invites your written comments and suggestions. Copyright 2009 SAE International All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the pr

6、ior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: 724-776-4970 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.orgSAE values your input. To provide feedbackon this Technical Report, please visit http:

7、/www.sae.org/technical/standards/AS5393SAE AS5393 - 2 -TABLE OF CONTENTS (Continued)6.12 Number of Revolutions to Acquire .136.13 Reference Angle 146.14 Rotor Diameter.156.15 Mean Blade Chord.156.16 rotor Blade Radius .166.17 Tracker “r“ Position 176.18 Tracker “ Position176.19 Tracker “z“ Position1

8、86.20 Tracker Pointing Angle.196.21 Number of Harmonics196.22 Minimum Rotor Speed .206.23 Maximum Rotor Speed 216.24 Minimum Coning Angle216.25 Maximum Coning Angle.226.26 Blade Tracker Errors237. ACCELEROMETER/BLADE TRACKER INTERFACE .238. DATA TYPES 238.1 Floating Point.238.2 Integer239. NOTES249.

9、1 Background24SAE AS5393 - 3 -1. SCOPE:Blade trackers measure: (a) rotor blade height and (b) lead-lag for use in a Rotor Track and Balance (RT&B) function in a Health and Usage Monitoring System (HUMS). HUMS is a generic term for a system used to measure, monitor, process, and store information rel

10、ating to the functioning and usage of an aircrafts on-board primary systems, including the engine(s).1.1 Classifications:This specification establishes the interface requirements for blade trackers for use in a helicopter Health and Usage Monitoring System. The main purpose of this document is to st

11、andardize the electrical and data interfaces between the blade tracker and the aircraft. We expect that a successful standardization effort will reduce the cost of HUMS blade trackers, reduce HUMS sensor inventories and increase interchangeability among HUMS sensors and systems. This blade tracker u

12、tilizes the SAE AS5394 - HUMS Advanced Multipoint Interface Specification. Sensor characteristics have been specified where they are fixed or limited by the sensing application. The blade tracker may have up to four electrical interfaces with the aircraft: electrical power, rotational system indexin

13、g sensor (SAE AS5392), accelerometer (SAE AS5391) (optional), and HUMS processor as illustrated in Figure 1.FIGURE 1 - Blade Tracker Electrical Interfaces1.2 Specification Terminology:The terms “shall” and “should” within this specification observe the following rules:a. The word “shall” expresses a

14、 mandatory requirement of the Specification.b. The word “should” expresses a recommendation or advice on implementing the specification or actions expected of users of the system.SAE AS5393 - 4 -2. APPLICABLE DOCUMENTS:The following publications form a part of this document to the extent specified h

15、erein. The latest issue of SAE publications shall aply. The applicable issue of other publications shall be the issue in effect on the date of the purchase order. In the event of conflict between the text of this document and references cited herein, the text of this document takes precedence. Nothi

16、ng in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.2.1 SAE Publications:Available from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.AS5391 Health and Usage Monitoring System Accelerometer Interface SpecificationAS5392 Heal

17、th and Usage Monitoring System Rotational System Indexing Sensor Interface SpecificationAS5394 Health and Usage Monitoring System Advanced Multipoint Interface Specification3. DEFINITIONS:ACCELERATION - The time rate of change of velocity usually expressed in ft/s/s, m/s/s, or Gs in gravity units (g

18、).ACCELEROMETER - A sensor with an output that varies directly proportionally to the acceleration aspect of motion.“g” - Standard unit of acceleration equal to one earth” gravity at mean sea level one “g” equals 32.17 ft/s2or 9.807 m/s2.SENSOR - A measurement device that transforms one form of energ

19、y into another. Also referred to as transducer or pick up4. POWER/BLADE TRACKER INTERFACE:The blade tracker shall use 28 V DC power, 30 watts, maximum. The blade tracker shall be designed to work under the power quality specification used for the particular aircraft for which it is installed.5. INDE

20、XING SENSOR/BLADE TRACKER INTERFACE:In order to match blade track and lag to a specific blade, the blade tracker needs input from an indexing sensor. The blade tracker shall accept an indexing sensor signal from a “self powered indexing sensor” as specified in the “SAE AS5392 - HUMS Rotational Syste

21、m Indexing Sensor Interface Specification.“SAE AS5393 - 5 -6. HUMS PROCESSOR/BLADE TRACKER INTERFACE:This interface shall meet the requirements of the “SAE AS5394 - HUMS Advanced Multipoint Interface Specification.” The HUMS processor and blade tracker will have a Master/Sub Master relationship as d

22、efined in the aforementioned specification, so as to allow the blade tracker to possibly control other digital sensors in the future. All the blade tracker commands shall be sent in the standard message format as specified in the multipoint interface specification. Only the data part of the message

23、will be specified in this document. The remainder of the message shall conform to the standard message format specified in the “SAE AS5394 - HUMS Advanced Multipoint Interface Specification.” The blade tracker shall always respond to the “Send Rotor Track Data“ command. All other commands, defined i

24、n the table below, are optional:TABLE 1 - Blade Tracker Command SetSAE AS5393 - 6 -6.1 Send Rotor Track Data:The “Send Rotor Track Data“ command is used to communicate per revolution blade track data.6.1.1 Command Message: The command message will have the following data blocks:FIGURE 26.1.1.1 Numbe

25、r of Revolutions: This will contain the number of revolutions over which the command shall be performed. Valid values for the “Number of Revolutions” block are 0 to 255. If “Number of Revolutions“ equals “0“, the default number of revolutions specified in the “Number of Revolutions To Acquire“ comma

26、nd will be used.6.1.2 Response: The blade tracker shall respond to the “Send Rotor Track Data“ command with the following data blocks:FIGURE 3SAE AS5393 - 7 -6.1.2.1 Initiating Command: This is an echo of the command number sent to the blade tracker and will be used by the interface electronics to i

27、nsure that the return message is properly interpreted.6.1.2.2 Revolution Being Returned: This is the revolution number during which the data in this message was collected. This signal can have any value between 1 and the value of the “Total Revolutions“ block. Zero is not a valid value for the “Revo

28、lution Being Returned“ block in response to the “Send Rotor Track Data“ command. The “Revolution Being Returned“ block is equal to the “Total Revolutions“ block when the final message is being sent.6.1.2.3 Total Revolutions: This block reports the total number of revolutions for which data will be c

29、ollected. Valid values for the “Total Revolutions“ block are 1 to 255.6.1.2.4 Number of Blades: The number of blades on the particular rotor shaft is included in this message so that the structure of the return message can be properly interpreted. Valid values for the “Number of Blades” block are 1

30、to 255.6.1.2.5 Average Absolute Track: The average absolute track is defined in 9.1.1.6.1.2.6 Relative Track: Relative track is defined in 9.1.1.6.1.2.7 Average Absolute Lag: Average absolute lag is defined in 9.1.2. Average absolute lag is given in millimeters and referenced to the blade tip.6.1.2.

31、8 Relative Lag: Relative lag is defined in 9.1.2.6.2 Send Rotor Balance Data:The Send Rotor Balance Data command is used to communicate per revolution balance data.6.2.1 Command Message: The command message will have the following data blocks:FIGURE 46.2.1.1 Number of Revolutions: This will contain

32、the number of revolutions over which the command shall be performed. Valid values for the “Number of Revolutions” block is 0 to 255. If “Number of Revolutions“ equals “0“, the default number of revolutions specified in the “Number of Revolutions To Acquire“ command will be used.SAE AS5393 - 8 -6.2.2

33、 Response: The blade tracker shall respond to the “Send Rotor Balance Data“ with the following data blocks:FIGURE 56.2.2.1 Initiating Command: This is an echo of the command number sent to the blade tracker and will be used by the interface electronics to insure that the return message is properly i

34、nterpreted.6.2.2.2 Revolution Being Returned: This is the revolution number during which the data in this message was collected. This signal can have any value between 1 and the value of the “Total Revolutions“ Block. Zero is not a valid value for the “Revolution Being Returned“ Block in response to

35、 the “Send Rotor Track Data“ command. The “Revolution Being Returned“ Block is equal to the “Total Revolutions“ Block when the final message is being sent.6.2.2.3 Total Revolutions: This block reports the total number of revolutions for which data will be collected. Valid values for the “Total Revol

36、utions“ block are 1 to 255.6.2.2.4 Accelerometers: The number of Accelerometers being monitored.6.2.2.5 Accelerometer ID/Address: The accelerometer identification number or address (in the case of digital accelerometers) for the accelerometer being monitored.SAE AS5393 - 9 -6.2.2.6 Acceleration, Amp

37、litude: Fourier amplitude data: The number of blocks of amplitude data is equal to the number of harmonics collected which is specified in the “Number of Harmonics“ configuration command.6.2.2.7 Acceleration, Phase: Fourier phase data: The number of blocks of phase data is equal to the number of har

38、monics collected which is specified in the “Number of Harmonics“ configuration command. Fourier phase data is represented by qn in the trigonometric Fourier series expansion given below. The “Number of Harmonics” is represented by the variable “n”.(Eq. 1)6.3 Send Average Rotor Track Data:The “Send A

39、verage Rotor Track Data“ command is used to communicate track data averaged over many revolutions. Only one set of data is returned by this command.6.3.1 Command Message: The command message will have the following data blocks:FIGURE 66.3.1.1 Number of Revolutions: This will contain the number of re

40、volutions over which the track shall be averaged. Valid values for the “Number of Revolutions” block are 0 to 255. If “Number of Revolutions“ equals “0“, the default number of revolutions specified in the “Number of Revolutions To Acquire“ command will be used.6.3.2 Response: The format of the respo

41、nse to the “Send Average Rotor Track Data“ command shall follow that of 6.1.2 with the “Revolution Being Returned“ set to “0“, indicating an average data collection.6.4 Send Average Rotor Balance Data:The “Send Average Rotor Balance Data“ command is used to communicate balance data averaged over man

42、y revolutions. Only one set of data is returned by this command.ft() Ann0t n()cosn0=SAE AS5393 - 10 -6.4.1 Command Message: The command message will have the following data blocks:FIGURE 76.4.2 Response: The format of the response to the “Send Average Rotor Balance Data“ command shall follow that of

43、 6.2.2 with the “Revolution Being Returned“ set to “0“, indicating an average data collection.6.5 Send Average Rotor Track Data With Statistics:The “Send Average Rotor Track Data With Statistics“ command is used to communicate track data, averaged over many revolutions, along with standard deviation

44、 data. Only one set of data is returned by this command.6.5.1 Command Message: The command message will have the following data blocks:FIGURE 86.5.2 Response: The format of the response to the “Send Average Rotor Track Data With Statistics“ command shall follow that of 6.3.2 followed by the standard

45、 deviation data. The format for the standard deviation data is shown below.SAE AS5393 - 11 -FIGURE 96.6 Send Average Rotor Balance Data With Statistics:The “Send Average Rotor Balance Data With Statistics“ command is used to communicate balance data, averaged over many revolutions, along with standa

46、rd deviation data. Only the standard deviation of the Fourier amplitudes is returned by this command.6.6.1 Command Message: The command message will have the following data blocks:FIGURE 106.6.2 Response: The format of the response to the “Send Average Rotor Balance Data With Statistics“ command sha

47、ll follow that of 6.4.2 followed by the standard deviation data. The format for the standard deviation data is shown below.FIGURE 11SAE AS5393 - 12 -6.7 Set Auto Lighting Mode:The “Set Auto Lighting Mode“ command is used to put the blade tracker in its auto lighting mode. When in this mode, the blad

48、e tracker determines and enters day or night mode based on the ambient lighting conditions.6.7.1 Command Message: This command message contains no data.6.7.2 Response: The blade tracker will respond to the “Set Auto Lighting Mode“ command with an error message as defined in the “SAE AS5394 - HUMS Ad

49、vanced Multipoint Interface Specification.”6.8 Force Active Mode:The “Force Active Mode“ command is used to put the blade tracker in its active operation mode.6.8.1 Command Message: This command message contains no data.6.8.2 Response: The blade tracker will respond to the “Force Active Mode“ command with an error message as defined in the “SAE AS5394 - HUMS Advanced Multipoint Interface Specification.”6.9 Force Passive Mode:The “Force Passive Mode“ command is used to put the blade tracker in its passive operation mode.6.9.1 Co