Archive for the ‘Cortex’ Category
The VEX IQ Virtual Challenge is part of an ongoing research project by Carnegie Mellon’s Robotics Academy and the University of Pittsburgh’s Learning Research and Development Center designed to assist robotics teams learning to program.
Participating students will learn programming that enables them to solve this year’s VEX IQ Virtual Highrise Challenge. As they learn they will also earn an Introduction to Robotics and Programming Certification.
Robomatter is pleased to be working closely with the Robotics Academy to create high quality STEM learning experiences, and has agreed to provide access to all related materials FOR FREE to celebrate National Robotics Week!
- This year’s Virtual HighRise Challenge Game
- Programming Curriculum to help you learn to program
- A live online course to help guide you through the curriculum
- Free ROBOTC and Robot Virtual Worlds Software for active participants
- Digital Certification for students who complete the course and challenge
The game available for the challenge is VEX IQ Highrise Beltway! In Beltway, you will program your VEX IQ robot to autonomously score as many cubes as possible during the 2 minute period. The standard Highrise game has been augmented with a conveyor belt around the perimeter and several other game play elements. Click here for a more extensive list of the new rules and game play. Beltway is available in the latest update to the VEX IQ Highrise Robot Virtual World download.
Check out our gameplay video to see it in action …
Are you interested in learning how to program in ROBOTC Graphical for VEX IQ or VEX IQ Robot Virtual Worlds? If so, then this YouTube playlist is for you! This set of videos will help you to get started programming with ROBOTC.
These videos are part of the Introduction to Programming VEX IQ Curriculum! To continue further with our free online training, visit our curriculum page here! http://www.education.rec.ri.cmu.edu/previews/robot_c_products/teaching_rc_vex_iq/
We are so excited to share the latest web design update for our VEX CORTEX Video Trainer! This includes all of our previous videos and materials, but in an easy to follow new format.
The VEX CORTEX Video Trainer is a multimedia curriculum that features lessons for the VEX CORTEX Microcontroller, which can also be applied to the older VEX PIC Microcontroller 0.5. It includes in-depth programming lessons for ROBOTC, multi-faceted engineering challenges, step-by-step videos, robotic support material, educational resources, and more! Check it out today and let us know what you think!
Two of China ROBOTC high school VEX teams (3288A and 3288B) earned their 2014-15 VEX World Championship tickets on Singapore South Programming Skill Challenge on Feb 27. With power ROBOTC programming software, team 3288B tied with Singapore Champion team and team 3288A advanced to VEX World Champion with Asia’s best programming score. China ROBOTC’s middle and elementary school teams earned spots to Louisville as well!
Two High School Teams:
3288A: #1 in Asia ; #14 in world ranking
3288B: #2 in Asia ; #24 in world ranking
Mid School Team:
10790: #1 in Asia ; #5 in world ranking
Elementary School Teams:
10579: #1 in Asia ; #4 in world ranking
10689: #2 in Asia ; #12 in world ranking
China ROBOTC, in cooperate with Shaanxi Science and Technology Department, is also jump starting a new robotic competition platform under the name of “iSTEMn”! iSTEMn provides opportunities for members worldwide to collaborate and innovate in the STEM arena. iSTEMnetwork promotes new levels of educational achievement and economic productivity. iSTEMn robotic competition is a K-14 event and students are divided into 4 different age groups: elementary; middle; high schools and colleges. iSTEMn robotic competition features all ROBOTC supported hardware platforms: VEX; LEGO and Makeblock as well as the RVW competition.
After this two days event, students are learning robotic at their schools and preparing for Shaanxi province tournament at the end of 2015. The winning teams will advance to China National Championship in Beijing early 2016. The winning teams with national title are going to California to compete with US teams for the iSTEM Robotic World Championship in late 2016.
We LOVE getting Twitter posts sent to us about ROBOTC. In the last few months, you have shared some great posts and pictures with us. We decided to make a second compilation of some of our favorites to share here…
— EdTech Baton (@EdTechBaton) February 25, 2015
— Chris Calver (@Chris_Calver) February 23, 2015
— Dr. Jim Barger (@drjbarger) February 23, 2015
— Ringo Dingrando (@ringodin) February 23, 2015
— NWMS Robotics (@NWMSRobotics) February 21, 2015
— Prairie Ridge INC (@IndustryCareers) February 19, 2015
— Paul McKnight (@Chewmacca1) February 11, 2015
— Triangle ES Robotics (@Triangle3615) February 6, 2015
Teaching our FLLers to use RobotC. pic.twitter.com/9QoPq3LNa7
— Higgs Bots (@ftc3085) February 5, 2015
Some awesome building today!! pic.twitter.com/bBFHCGEUQZ
— R Hartley (@MrRHartley) February 4, 2015
4th grade robotics class completes the Lego EV3 sonar sensor Maze Challenge using Graphical ROBOTC http://t.co/Eq8XeBAMLY
— Lancer Robotics (@LancerRobotics) January 29, 2015
— Droids Robotics (@droidsrobotics) January 28, 2015
— Regan White (@ReganWhite222) January 23, 2015
— Ringo Dingrando (@ringodin) January 22, 2015
— RSHS Robotics (@RSHSRobotics) January 10, 2015
— Michael Washington (@ADefWebserver) December 31, 2014
— Harli Quyn (@HarliQuyn) December 23, 2014
— Anna Lynn Martino (@annalynnmartino) December 19, 2014
easyC it's been nice working with you…. Hello RobotC !!! #switchinprogramming
— Volt Robotics 5194B (@VoltRobotics) December 18, 2014
— ScratchÖğren (@scratchogren) December 15, 2014
— Spring Valley (@SV_Vikings) December 12, 2014
— Clarke Hosp (@hospdesign) December 12, 2014
Do you have a ROBOTC picture/video/post you would like to share with us on Twitter? If so, include #ROBOTC or @ROBOTC in your message.
Jason McKenna, from the Hopewell Area School District outside of Pittsburgh, PA, writes about his experience in the classroom with the new Robot Virtual World game, VEX IQ Beltway. Check it out below …
The new VEX IQ virtual game Beltway is a great way to challenge your students to apply the basics of ROBOTC programming while also asking them to come up with unique strategies to try to score as many points in the 2 minute game as possible. My students just spent about 3 weeks working on the challenge and trying to score the highest score as possible. The students had an absolute blast and as a teacher, it was great seeing all the different ways the students tried to tackle this completely open-ended challenge.
The objective in Beltway is the same as VEX IQ Highrise: program your VEX IQ robot to autonomously score as many cubes as possible during a 2 minute period. With Beltway, a conveyor belt has been added around the perimeter of the game field in order to assist with game play. Additionally, the virtual environment utilizes “magic stacking” meaning that the cubes automatically jump onto the stack when they are placed onto of the stacking cube regardless of the apparent size of the robot. The conveyor belt reduces the accumulation of error, where, for example, a robot’s slight error in one turn becomes a larger error when the robot repeats that same turn 4 or 5 times. Any time students attempt a long program with many different elements they will at some point become frustrated with the accumulation of error that occurs. Magic stacking and the large margin of error that enables easy pickup of cubes eliminates any frustration that the students may encounter as try to pick up cubes and then stack them. These elements of gameplay in Beltway allow students to focus on their strategy, and it also allows them to try to experiment with many different scoring methods because they are not spending a lot of time programming perfect 90 degree turns and aligning their robots perfectly to pick up a cube. You can click here for a more extensive list of rules and information about gameplay!
Beltway comes with a variety of sample programs that students can use to help them get started or as a reference as they adjust their strategies. For example, if students decided that they wanted to control the conveyer belt manually, they could refer to a sample program to see how that is done. I did that many times while monitoring the students. After a few days, the students aren’t repeatedly raising their hands; instead, they just refer to the sample programs for guidance.
The game also served as a great tool to teach beginning programmers the utility of comments. Oftentimes, beginners don’t make programs quite as long as the ones they will make for Beltway. Students quickly saw the need to point out what was going on in their code with comments so they could go back to those sections and make whatever adjustments they wanted as they progressed with their gameplay.
As I stated earlier, my students had a lot of fun while playing Beltway. It is not easy to keep students’ interest level high in an activity that takes 3 weeks. The students maintained their level of interest and they consistently asked to stay after school to work on their programs some more. We had an in-class competition where the students ran their final programs. The winning team scored the winning points as the timer, literally, went to zero. It was pandemonium in my room. Kids were high-fiving each other, cheering, and remarking at how awesome the competition turned out. Students were also talking about the different strategies that the other teams used and how they could change their programs based upon what they had just seen.
So now, of course, the students want to play some more. This is great because now I can use that as an opportunity to show students how they can take some of the code that they used over and over again (for example, picking up cubes) and show them how they can use full ROBOTC to turn those behaviors into functions. Beltway has proven to be both a great teaching and learning tool in my classroom.
- Jason McKenna
4.29 -> 4.30 Change Log
- (Cortex) Added new sample programs for RVW VEX Cortex using the Natural Language 2.0 commands.
- (Cortex) Fix to enable tankControl to be displayed for Virtual Robots.
- (Cortex) New VEX Cortex Master Firmware (4.25) for VEX Cortex Brain & VEXNet Remote Control
- (Cortex) Update for VEX Competition Template in Natural Language 2.0 to ensure maximum compatibility
- (Cortex) Increased Timeout for VEX wireless communications when using the new VEXNet 2.0 Radios – prevents communications issues
- (IQ) Fixed incorrect samples for VEX IQ in Virtual Worlds (both Text and Graphical)
- (All) Rebuilt firmware to version 10.30. All platforms will require a firmware update.
- (ALL) Prevent Graphical files from asking to save if the “Save On Compile” flag is set to false.
- (ALL) Update all standard models to have correct drive train setting.
- (ALL) Fixed an issue where a “sprintf’ varArg list contains a string constant the compiler was generating incorrect code causing a firmware crash.
- (ALL) Compiler Fix: ‘long’ pointer temporary variables were sometimes being allocated as type ‘signed’ instead of ‘unsigned’.
- (ALL) Checking for “divide by zero” exception forgot to check in the “module” opcodes; it was only checking the “divide” opcodes. Fixed.
- (ALL) Fixed issues where the first time the Debugger “Local Variables” window is painted with values (rather than blank) the address field displays “0xCDCDCDCD” rather than the offset.
- (ALL) Graphical Interface now support “multiple selection” using Shift/Control keyboard modifiers (drag select coming soon!)
- (ALL) Fix for DebugStream which was adding \r to the String as it was written to file.
3.64 -> 3.65 Change Log
- (Cortex) New VEX Cortex Master Firmware (4.25) for VEX Cortex Brain & VEXNet Remote Control
- (Cortex) Increased Timeout for VEX wireless communications when using the new VEXNet 2.0 Radios – Full download/debug support available.
- (All) Fixed issue with licensing system when an unexpected error code (i.e. server is available but service is down) would cause ROBOTC to crash.
- (All) Fixed issue with ‘Check for Update’ functionality where a hotel/school wifi login screen might cause a ROBOTC crash with unexpected XML parameters.
- (All) Fixed issue with licensing system where a license could not be used on the same computer twice.
And to read more about the changes in 4.29, visit our post from earlier this week. Happy Programming!
The Robot Virtual World team is happy to announce our latest updates are available for Ruins of Atlantis, Palm Island, and Operation Reset! We’ve included updated sample program to support all platform types (VEX CORTEX, VEX IQ, EV3, and NXT) within ROBOTC. You can also choose what type of sample program you would like to use from Graphical, Natural Language, or Standard.
Thanks again to everyone who has provided feedback! Please continue to do so at the ROBOTC.net Forums. Happy programming!
What we’re most excited about in this new release is the official version of the brand new “Natural Language 2.0″ libraries for the VEX Cortex, including support for the new ROBOTC Graphical interface with VEX Cortex.
VEX IQ Users:
- Run the “VEX IQ Firmware Update Utility” and update your VEX IQ Brain to firmware version 1.13 (may not be available at time of release, but will be available soon).
- Users will also have to update their VEX IQ Wireless Controller in addition to any other VEX IQ Devices (sensors, motors) that may need to be updated as well.
- After updating to the latest VEX IQ Brain firmware, users will also have to install the latest ROBOTC firmware from inside of ROBOTC.
VEX Cortex Users (with Black VEXnet 1.0 Keys):
- You will need to update your VEX Cortex and VEX Game Controllers with Master Firmware Version 4.23 from inside of ROBOTC.
- After updating the master firmware, users will also have to update the VEX Cortex with the latest ROBOTC firmware as well.
VEX Cortex Users (with White VEXnet 2.0 Keys):
- The new VEXnet 2.0 keys have a specific “radio firmware” that you will need to upgrade to enable “Download and Debugging” support. You can download the VEXnet Key 2.0 Firmware Upgrade Utility here.
- Download the “VEXnet Key 2.0 Firmware Upgrade Utility” and insert your VEXnet 2.0 key to any free USB port on your computer. Follow the instructions on the utility to update each key individually. All VEXnet 2.0 keys must be running the same version in order to function properly.
- After updating your VEXnet 2.0 keys, you will need to update your VEX Cortex and VEX Game Controllers with Master Firmware Version 4.23 from inside of ROBOTC.
- After updating the master firmware, users will also have to update the VEX Cortex with the latest ROBOTC firmware as well.
ROBOTC 4.28 BETA -> 4.29 Change Log:
- (CORTEX) Updated VEX Cortex Graphical Implementation to support competition (single run autonomous per toggle)
- (CORTEX) Modified “BuiltInVariables.txt” to properly show VEX Cortex commands.
- (IQ) Fix RVW Clawbot standard model to match Virtual Worlds configuration.
- (IQ) Add Armbot with Sensors “standard model”
- (IQ) New RVW Specific Motor and Sensor Models + VEX IQ Clawbot – No Sensors model.
- (IQ) Added “moveMotorTarget” to Graphical
- (ALL) “Test Communications Link” dialog was not properly storing/retrieving the registry value for the “Ping Type” variable.
- (ALL) Debug stream fixed so that “Clear Debug Stream” clears the IDE’s Window at the proper location; previously it was possibly erasing the screen at a spot well after the actual “clear” function was called.
- (ALL) Enhance Debug Stream handling to better support (1) Buffer overflow conditions and (2) proper visual appearance on IDE when “Clear Debug Stream” intrinsic is used.
- (ALL) Adjustments so maximum size of messages transferred between IDE and emulator increased to 10K from 1K.
- (ALL) Fix bug when maximum message size now exceeds maximum flash sector size.
- (ALL) Joystick buttons had different enums for real and virtual robots. This affected the joy1Btn() command.
- (ALL) Upissue Firmware Version to 10.29 / Upissue IDE Version to 4.29
- (ALL) Contents of DebugStream window can now be saved through the menu
- (ALL) Automatically select RVW package if one is not selected.
- (ALL) Increase number of RVW Packages available to 40 potential options – allows for future level packs.
- (ALL) DebugStream can now also be saved as a *.csv file
- (ALL) DebugStream Window contents can now be saved to a file.
- (ALL) User models (from Motors and Sensors setup) can now use relative filenames for user models.
- (ALL) Fix crashing issue when CheckForUpdates get a malformed XML file (typically hotel login pages)
- (ALL) Fix crash issue when Version XML file download is corrupted by school/hotel/conference “login” screens.
- (ALL) Fix crash issue when licensing libraries return an unexpected return value – error message string formatting command was invalid causing a crash.
- (ALL) Added pipe symbol to the LCD Printing Libraries fonts.
- (ALL) Fixed backslash character in small font.
- (ALL) Better parsing of “If” and dangling “else” clauses. Prevents a compiler crash when bad syntax in the “if” condition clause.
- (ALL) Support in GUI for use of user-defined “motors and sensor configuration data files”.
- (ALL) New “registry flag” to indicate whether user defined “configuration model” files are allowed.
- (ALL) Previously breakpoints could not be defined in header files. This is now fixed.
- (ALL) Benign. Enhance output in message trace window for “set breakpoint” message.
- (ALL) Command line based activation / deactivation commands. Implemented but not fully tested yet – documentation to follow.
ROBOTC 4.27 -> 4.28 BETA Change Log:
- (ALL) Updated Help System Documentation for new commands and features.
- (ALL) Updated Firmware for 10.28 / 4.28 compatibility.
- (ALL) Added a compiler error when ‘switch’ expression was illegal.
- (ALL) Support for optional “int” keyword as in the declaration “short int” or “int short” in addition to “short”.
- (ALL) Add USB Joystick control to Graphical (in loop blocks)
- (CORTEX) Fixed issue where performing a new motor PID movement when an existing PID movement is in progress didn’t work properly.
- (CORTEX) Allow users to select “Xmtr2″ for VEX Cortex Graphical (Expert and higher menu level)
- (CORTEX) Added competition control and competition template for Cortex Graphical
- (CORTEX) Added Virtual Worlds Natural Language 2.0 Library for VEX Cortex
- (CORTEX) Renamed old-style Natural Language mode to “Natural Language PLTW”
- (CORTEX) Fixed issue where software inspection would fail without a radio link on VEX Cortex
- (CORTEX) Added dialog message to Cortex “Download Firmware” button on large icon toolbar.
- (CORTEX) Multiple incomplete consecutive PID moves. Fix issue when current move is in “ramp down” and new PID movement is initiated.
- (IQ) Added additional standard models for VEX IQ.
- (IQ) Fix issue where mode wasn’t being set for Graphical for VEX IQ Color Sensor.
This is my third year teaching, but my first time working with Project Lead The Way (PLTW) and a robotics course. After accepting this assignment, I was extremely nervous. I did not study robotics in college, and I had never, ever pictured myself in this role. But I am so very happy to have taken on this challenge.
My favorite part about teaching this class is the atmosphere and expectations that I set up with this class and my students. From the first day of school, I was completely honest with the kids. I broke down the walls of the normal teacher-student relationship where the teacher is looked at as the bearer of all knowledge and all knowledge is passed down from the teacher to the students. I created a culture where students and their knowledge are equally valued and as important as the teacher’s. This led to a culture of mutual respect and collaboration. I, as the teacher, was not viewed as the bearer of all knowledge, but as a helpful resource to rely on when problems arose. The most important part of creating this culture is setting up those expectations from the beginning of school.
The major theme from this class was “Problem-Solving”. I would present students with a variety of real-world scenarios and they would have to think of a design to solve that problem. They would work in groups of 2 to 4 students to create, construct, and program these robots to solve the problems I presented to them. This allowed for A LOT of different interpretations and ways to solve these problems, which was awesome!
Several key strategies that I incorporated into the class that proved to be successful were: purposeful grouping, incorporating student choice, and using students in a teacher’s role to help other students who needed more assistance. I incorporated a “Menus” style of teaching and learning. Students would be purposefully grouped into groups of 2-4 and then they would be presented with 3 different levels of activities: Appetizer, Main Meal, and Dessert. Within each level, students would have to choose 1 task out of 3 or 4 different options. As a group, students would choose which task to complete. Once decided, students would work as a group to design, build, and program the robot to complete the task. I would watch the robot perform the task, sign off on their paper, and they would move on to the next part of the menu. The activities got progressively more difficult as students moved from the Appetizer to the Main Meal to the Dessert level, with the Dessert level activities being the most difficult.
As we get ready to begin with the second semester, I cannot help but think about how much I have learned and how better of a teacher that I have become because of teaching this class. Some future ideas I have are the creation of a “Girls in STEM Club”. The purpose of this being opening girls’ eyes to future careers and possibilities associated with this class and the STEM ideals. Also, possibly creating a VEX Competition Robotics club where students would meet after school to construct robots to participate in VEX Robotics competitions. One thing that I realized early on in my teaching career is how much teachers learn from their students. Teaching this class has been one of the best learning experiences of my life.
– Ross Hartley
If you’re a teacher or robotics coach and would like to write a blog about your experiences teaching, send us an email at email@example.com!