So I just broke my arm, so I was wanting to create a type of input device for my arm with spare vex material. I have my own limit switches (non-vex) that are small and can be used. However I have a couple of thoughts to make this work:
With the use of limit switches that are non-vex, will anything unexpected arise? I doubt so.
I could get a specialized board (Arduino, iPac, and something that started with a t); program it, or:
Use a cortex for it. Hook up the limit switches as sensors, program the cortex to act as an input method for a PC. However, this isn’t what the cortex was specifically made to do, though, it’s quite possible to do. How would it be even programmed in the API’s of PROS / RobotC? I can easily see the cortex using the debug stream with the sensors in both, but how would i go about getting the cortex to emulate an IME, or, modifying / creating an interpreter of said debug stream? Just some interesting thoughts mates.
I don’t program a lot, but I do believe that using a non-vex limit switch should still work, as long as it’s the three-wire ones, since all the limit switches/bumpers do is provide a value of 1 or 0 if it is pressed/unpressed.
I also believe it would be easier with an arduino rather than a cortex, but like I said, I don’t program a lot, so I don’t know the capabilities of the cortex.
It’s a keyboard controller, mainly used in custom mechanical keyboards that people make. You may be able to connect it to your arduino or cortex and then use autohotkey to make everything just a bit simpler.
That’s actually what i was referencing when I said something with a T. Granted it’s only 15$, our team(s) will have a spare cortex so that’s why I was thinking about the cortex. I don’t usually see a cortex being used in real life practical situations.