I’ve seen something similar mentioned but not exactly this.
What I think would be nice would be to have a small LCD screen integrated into the joystick so that its easy to see the robots status.
maybe something like a smaller version of the current LCD screen, and it would probably have to sit where the current vex logo goes…
For the programmer probably give it a similar interface to the current LCD screen and have it controlled from the robot, i.e. the joystick just passively displays information sent from the robot, maybe just keeps an eye out for certain packets or something.
The idea of getting an LCD screen for the joystick has been around for a while, and I’ve personally seen it suggested many times. However, one must remember that that would take up more bandwidth on vexNet, creating an even less stable and slower robot connection. As far as I’m can think of, that is the big problem with creating such an add-on for the joystick
You are correct, driving a display would have a negligible effect on WiFI usage. When the ROBOTC debugger is running and receiving information through VEXnet, it uses far more bandwidth than a display would. I don’t think there’s a minimum packet size for a 802.11 frame like the 64 byte ethernet minimum but a few extra bytes per packet for display would have no real impact.
This is clearly on the technology road map as suggested here: https://vexforum.com/t/lcd-cable-to-joystick/21796/1
I don’t think bandwidth is the issue, rather a master firmware update and which connection to use on the handset, the most likely would be the programming to allow for a second joystick and competition connections.
If you read the post from JVN, it has been discussed as an add on to the controller (i.e. those mysterious screws on top have a purpose) I think it would be a great option that would enable drivers to receive more information from the robot.