[!CAUTION] This section is incomplete.

This will explain how the User Controls are implemented.

Core Functionality

Use RFID reader for checking if a User is authorized. Then, allow User to turn on the tool and manage use with just a few physical buttons. All while tracking tool use in the background. The hardware is all here on this wing, but it relies heavily on fully developed firmware and servers to achieve the goals set out above.

Simple Use Explanation

The steps below are only for the most-common use case of an implemented wing-combo as an abstracted 'box' that controls User's access to a tool. There are lots of details and alternate paths these steps can branch into, but what is here is the idealized operation. More detail about alternate paths are described further down the page.

1. User swipes their ID card on the RFID reader.
2. The wing-combo responds with yes/no to authorization request, in the form of LED, buzzer and possible relay activation.
   • The relay and larger green indicator lamp will come on if a User is authorized, and they may proceed through the following steps.
3. Authorized Users press the green button within a short time window, and my use the attached tool.
   • The tool will 'timeout' if the green button is not pressed in time (usually ~ 1 minute after card swipe).
4. The wing-combo will automatically track the current drawn by the tool, to ensure that it is still in an ongoing session with a User.
5. The User finishes using the tool and presses the red button. This cuts power to the tool, and the wing-combo resets itself for the next session.

Detailed Tool Control Breakdown

Tool Control is primarily the purview of firmware and the server. However, the broad strokes are shown here. Some things, like the firmware logical diagram, are very dependent on the software involved. Other items, like the function of the buttons or the relays, are hard-wired and you can be reasonably sure that they will always operate in the same manner. Either way, some of this has been included here for the primary use case; as it will add more clarity than confusion.

Function of Controls by item

These are all the end-user exposed items, for those who will see this device as mostly just a magical black-box.

• RFID Reader
  • Observe the UUID on an RFID card, and start an authorization request
• Red/Green LED indicator
  • Feedback for authorization request: showing if request is accepted, denied, or errored
• Large green indicator light (important indicator, not control)
  • Indicate SR-latch is active: tool is 'enabled' or currently powered, in a session
• Buzzer
  • Audio feedback for authorization request: sounding off it request is accepter, denied, or errored
• Bypass Key 🔑
  • A physical key that can place the tool into 'enabled' state without authorization requests or server
• Green Button
  • Once the tool is in 'enabled' state, button can turn on the contactor and thus the tool
• Red Button
  • Once the tool has been turned on, can turn off the tool/ end user session
  • This is the ideal way that a user would turn off the tool/ end a session
• Emergency Stop [E-Stop] number 1
  • Once the tool has been turned on, can turn off the tool/ end user session
  • If left on, this can block tool operation from starting again
  • meant to be a quick-stop for all power, in emergency situations
• Emergency Stop [E-Stop] number 2
  • Once the tool has been turned on, can turn off the tool/ end user session
  • If left on, this can block tool operation from starting again
  • meant to be a quick-stop for all power, in emergency situations