In the top menu in RobotC, go to Robot / Platform Type / VEX Robotics flyout menu and make sure it’s set to VEX 2.0 Cortex.Start with robot and joysticks turned off.
So this is why I’m writing this post-hopefully I can save some of you a bit of time on this one. We had a little difficulty getting this item set up and working, and then a little more difficulty getting it to work well after that.
#ROBOTC SOFTWARE DRIVER#
Then the joystick continues to talk to the cortex via the VEXnet keys, as it does during driver control. The other side of the Magic Widget has a different type of cable (looks more like a large, flat telephone wire) which runs from it to the “Program” port on the back of your main joystick (photo below).
The other end of the USB gets connected to a Magic Widget (rectangular orange box, photo at right). So how does this miracle occur? As shown in the image at right, the cable is a 3-part item-the first section is USB, which plugs into your computer, the same way as non-wireless downloading.
Move the robot over to where the person with the computer is, or vice versa.Without wireless capability, every iteration of programming involves the following: 60 seconds of trying to get everything just right with teeny changes and trying again and again. Think about programming autonomous-or even better, autonomous skills. wireless (b) Hardware setup and Cool add-on product (c) Using it and What’s that button for? (d) What if it doesn’t work? and (e) Additional resources.
#ROBOTC SOFTWARE CODE#
#ROBOTC SOFTWARE DOWNLOAD#
you need to download firmware before you can communicate with RobotC (as expected). (a little bit later) That was interesting …. Maybe an option to customise your own shield pin allocations ?Īt the end of the day this first exercise was much easier (simple motor controls in a timed sequence with speed control) than using the standard Arduino approach and looks pretty cool The shields selection option is via the motors/sensors setup menu and only covers a limited variety of shields at this stage but looks promising for the future. Luckily this shield is readily hackable as it uses D12 and D13 for motor direction (conflict with I2C) This was impressive as I was testing a Freetronics Eleven (UNO copy) and the Rugged Circuits heavy duty motor driver shield (up to 30V 2.8A beast of a thing). The good news is that I wrote a simple program driving a couple of motors and after the usual playing around it actually worked !