search

team4909 / 2019-Deep-Space

Team 4909's 2019 Robot Code
MIT License
2 stars 1 forks source link

Design + Implement User Interface #55

Closed roshanr10 closed 5 years ago

roshanr10 commented 5 years ago

We need to design the user interface based upon the following requirements (embedded below, found here)

Driveteam Requests (remedied in subsequent discussion)

Driver Controller

Operator Controller

roshanr10 commented 5 years ago

Here's what we came up in our discussion for dashboard:

Both Driver/Operator Screens:

Main Screen Only (Jeff & Matt):

Operator Screen Only (Jeff):

Test Pane:

roshanr10 commented 5 years ago

Cameras:

I'm currently unsure if we want ahead & floor lines taken care of by the same camera or have a switching functionality... thoughts?

roshanr10 commented 5 years ago

Prior to #77, I think we need to finalize both gamepads for their full functionality control. thoughts? @ashwinc12

ashwinc12 commented 5 years ago

Yes. We should have both gamepads ready for competition in case the smartdashboard stuff doesn't work or if the drivers preferred gamepads instead.

As of right now,

driverGamepad can do the following

manipulatorGamepad can do the following

Not sure where the control for the stilts is going to go if all the joysticks are taken up

roshanr10 commented 5 years ago

Here's what I'm thinking, feel free to add/change:

Driver Gamepad:

Operator Gamepad:

I'm aware the manual control doesn't include buttons for Rocket Cargo placement, but I think it's close enough at that point that we can easily manually maneuver it closer within the small gap, and adding other controls would add unneeded complexity given how this is intended to be a fallback.

That said, an option would be to have a single button, say LB be pressed after choosing the hatch panel setpoint to correct to the cargo setpoint since they all maintain the same offset.

roshanr10 commented 5 years ago

This is also assuming my comments in #56 that the stilts automatically engage to keep the robot level once the elevator begins to lift the robot off the ground and that once LB is pressed, the PID loop is subsequently disabled.

Furthermore, the elevator hatch panel setpoints are intended to set heights and wrist articulation, to clarify.

roshanr10 commented 5 years ago

cleaned up and revived as #83.

derrell commented 5 years ago

Why is this issue closed?

derrell commented 5 years ago

It's hard to understand how this could all be determined entirely by the software team. The software team is not doing the driving or operating... And furthermore, it seems like all of the recommendations of the expert in the field of user interface design have been ignored in the process of coming up with these solutions. It's your choice, of course, but seems a poor decision, to me.

The goal of user interface design is to devise the interface that best accomplishes the goal, appropriately divides the operations between the available operators (in this case, the driver and operator), and importantly, makes it least likely that mistakes will be made. There is a very lot that goes into creating a good user interface. I'd highly recommend that you discuss this with me, or even better, Shelley, and that the driver and operator be extensively involved in determining how it will work the best for them. Remember the mantra: You, the software engineer, are NOT the typical user. It's best not to make assumptions based on your own feelings.

roshanr10 commented 5 years ago

This issue was streamlined in the new issue #83 as per my last comment, all of the content is otherwise identical, but this was becoming immensely difficult to follow.

On Sun, Feb 10, 2019 at 10:06 Derrell Lipman notifications@github.com wrote:

Reopened #55 https://github.com/FRCteam4909/2019-Deep-Space/issues/55.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/FRCteam4909/2019-Deep-Space/issues/55#event-2129251130, or mute the thread https://github.com/notifications/unsubscribe-auth/AEUIR0UXJgS0ptjwbz5u0ke59_KKMIUwks5vMDV6gaJpZM4af15J .

roshanr10 commented 5 years ago

To clarify, this is not the final revision. We just wanted to make it easier to follow along the design process as it documented in #83. That’s been sent out to Matt & Jeff for a preliminary review, this was just to start discussion.

roshanr10 commented 5 years ago

Closing as per earlier discussion, this is valuable information but more difficult to see the overall perspective as in #83