Motion Group - Slide Rooms 6.14
Tue, 2020-02-25 18:00 — Martin Perlot
From the Motion Group,
Edits and test profiles for Slides.
| Attachment | Size |
|---|---|
| 6.14 Slide Rooms.docx | 36.21 KB |
| 6.14 Slide Rooms_Rev2.docx | 24.84 KB |
Proposed
Proposed Edit
------------------
New Profile: Slide Control Panel. (This would apply to devices that are intended to control a slide room.)
Test.
Datum: Stop Command
Test: After motion has commenced, the user removes his finger (or analogous input device) from the button or control.
Required Response: A Stop command is broadcast within 100ms. No subsequent Motion commands are allowed.
Test:
Datum: Motion Command
Test: The user places his finger (or analogous input device) on the button or control and maintains the input for a period of time.
Required Response: A series of Motion commands is broadcast with a message gap between 50ms and 100ms.
--------------
Justification
Safe operation requires a compatibility test for the control panel as well as the slide room. Note that code requires that the user input be analogous to a non-latching switch.
Proposed
Proposed Edits
-----------------------
1. Create two new Generic Alarms.
Alarm Instance 1. Slide Activity Started.
Alarm Instance 2. Slide Stowed.
2. Edits to Slide Room Base Profile
Add to Command Test, Required Response, "Respond with Generic Alarm, Instance 1. Alarm should not be sent again unless no activity is noted for ten seconds.
Add new test. Stop Response. Test: A Stop command is sent. Required Response: as above. Required Behavior: The controller must respond within 50ms.
Add new test. Command Timeout. Test: A series of motion commands is sent at 100ms intervals. Required Response: Slide Status is broadcast with each command, and at the termination of motion. Required Behavior: The slide moves continuously in the indicated direction. After the last message is broadcast, motion terminates within 250ms.
-------------------------
Justification
The new alarms are valuable for forensic purposes - establishing after the fact, for example, whether unexpected motion was due to an RV-C command or a physical glitch in the slide.
There was discussion in the Lead Group meetings regarding whether it was appropriate for the Working Group to establish timing parameters for devices such as the slide. In general it is not the place of the RV-C committee to establish performance levels for products, but here the specification does not concern inherent product performance (we do not specify the speed of the slide or how quickly it physically responds). The profile here tests only how the slide interacts with the control panel or other UI device - without specifying a requirement for message frequency, it would be impossible to ensure the smooth operation of the slide.