| ||Format||Pages||Price|| |
|16||$60.00||  ADD TO CART|
|Hardcopy (shipping and handling)||16||$60.00||  ADD TO CART|
Significance and Use
5.1 The significance of the information to be recorded in a test report allows for A-UGV performance to be contextualized with A-UGV configuration.
5.2 Limitations of the practice are that not all A-UGVs have the same capabilities or configuration parameters. For example, for capabilities, a vehicle that remaps during navigation versus another vehicle that uses a static map may behave differently in repeated runs of an obstacle avoidance test. For configuration, a vehicle that remaps during navigation may have varying times that obstacles remain in the map for test recreation.
5.3 The environment map used by the A-UGV, developed through localization including any landmarks, shall be saved as used on the A-UGV and should be saved and provided as a human-readable layout on or off the A-UGV (see showing a sample layout drawing).
5.4 The main A-UGV hardware parameters shall be recorded as follows:
5.4.1 Make and Model
5.4.2 Part Number
5.4.3 Serial Number
5.4.4 Hardware Revision number (if any)
5.4.5 Number of drive/steer wheels
5.4.6 Steering type
5.4.7 Type: for example, Fork, Tugger, Unit Load, Cart
5.5 The main A-UGV software parameters shall be recorded as follows:
5.5.1 All applicable software and firmware versions.
5.5.2 Velocity – translation and rotation, minimum/maximum.
5.5.3 Acceleration – translation and rotation, minimum/maximum.
5.5.4 Stand-off distances – safety sensor thresholds, obstacle avoidance thresholds.
5.6 The context for the test shall be recorded by providing detailed answers to the following questions:
5.6.1 When are the various software configurations used during the test? For example, two software versions may be required as follows: Use configuration A for straight aisles and configuration B for turns.
5.6.2 What other hardware and software parameters/settings are required to recreate the A-UGV behavior (that is, attached debug, settings, or other files)?
5.6.3 What is the A-UGV layout that is saved and used on the vehicle and, if possible, saved and provided as a human-readable version?
5.6.4 Are there constraints that the requestor has placed on the A-UGV? Examples may include the following:
22.214.171.124 generic test environment: for example, outdoors or indoors, day or night, defined or undefined test areas?
126.96.36.199 velocity and acceleration that are below the maximum capability?
188.8.131.52 clearances between the A-UGV and an obstacle during obstacle avoidance maneuvering?
184.108.40.206 negative obstacle measurement capability enabled?
220.127.116.11 choose its own path or is required to use a preferred path?
5.7 Higher-level categories of A-UGV capabilities shall be recorded as follows:
5.7.1 Localization method: for example, natural features, reflective markers, tape on ground, matrix barcodes/visual fiducial system, lights in ceiling.
5.7.2 Safety-rated equipment: for example, scanning lasers and their make and model numbers; other functions of safety sensors.
5.7.3 Other sensors used: for example, cameras, including their make and model numbers, and image processing software used for path planning.
5.7.4 Added equipment for A-UGV testing: for example, cameras, including their make and model numbers, and image processing software used for capturing docking performance.
1.1 This practice describes a means to record the A-UGV configuration when testing. The practice provides a method for recording A-UGV hardware and software control parameters and describes high-level capabilities, such as used for A-UGV safety and navigation.
1.2 This practice: contextualizes the A-UGV configuration during a test, including the identification and adjustment of main configuration parameters; provides the proper context for test results; provides a basis for comparison of the test circumstances across different vehicles or tests, or both; and allows a test to be recreated.
1.3 The values stated in SI units are to be regarded as the standard. The values given in parentheses are not precise mathematical conversions to imperial units. They are close approximate equivalents for the purpose of specifying A-UGV characteristics while maintaining repeatability and reproducibility of the test method results. These values given in parentheses are provided for information only and are not considered standard.
1.4 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety, health, and environmental practices and determine the applicability of regulatory limitations prior to use.
1.5 This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.
2. Referenced Documents (purchase separately) The documents listed below are referenced within the subject standard but are not provided as part of the standard.
F3200 Terminology for Driverless Automatic Guided Industrial Vehicles
ICS Number Code 43.020 (Road vehicles in general); 43.040.15 (Car informatics. On board computer systems)
|Link to Active (This link will always route to the current Active version of the standard.)|
ASTM F3327-18, Standard Practice for Recording the A-UGV Test Configuration, ASTM International, West Conshohocken, PA, 2018, www.astm.orgBack to Top