ROBOTC.net Blog  

ROBOTC News

Archive for the ‘Software’ tag

ROBOTC 4.50 for VEX Robotics Available Today!!

with one comment

ROBOTC 4-50 VEX

The ROBOTC Development Team is very excited to announce our latest update, ROBOTC 4.50. This update is for the VEX Robotics (VEX EDR CORTEX and VEX IQ) robotics systems and includes new features, functionality and a load of bug fixes.

Click here to download 4.50!

Important Setup Information for ROBOTC 4.50:

VEX IQ Users:

  • Run the “VEX IQ Firmware Update Utility” and update your VEX IQ Brain to firmware version 1.15.
  • Also update your VEX IQ Wireless Controller and any other VEX IQ Devices (sensors, motors).
  • After updating to the latest VEX IQ Brain firmware, 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.25 from inside of ROBOTC.
  • After updating the master firmware, you will also have to update the VEX Cortex with the latest ROBOTC firmware.

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.25 from inside of ROBOTC.
  • After updating the master firmware, you will also have to update the VEX Cortex with the latest ROBOTC firmware.

ROBOTC 4.32 —> 4.50 Change Log:

General new features:

  • Graphical blocks can now be copied, cut and pasted

Copy Paste

  • Graphical actions, such as adding, deleting and moving a blocks, changing parameters and their values can be undone and redone.
  • The Graphical repeat and while blocks values can now be adjusted without a keyboard using spin buttons.

Number Scroll
Color Loop
VEX new features:

  • Added support for the new VEX IQ Smart Radio in ROBOTC Firmware (for use with iOS applications)
  • Added Smart Radio based User Messaging system (for use with iOS applications)

General fixes:

  • Large amounts of data in debug stream no longer causes debugger to hang.
  • Fixed issue when mixing PLTW building licenses with other license types.
  • When changing the motor type in the Motor and Sensor Setup utility, the additional parameters, such as PID, drive side, encoder type, are reset to their default values.
  • UAC prompt now appear only once for installing multiple RVW packages.

RVW Package Manager

  • The toolbar buttons are sized to the individual content, instead of the largest one.
  • Recursive pre-compiler statements are correctly identified and no longer crash the IDE.
  • The Graphical block library’s expansion/collapse state is now preserved when switching between files.
  • LineTrackLeft help text has been corrected.
  • Fixed issue of undefined entries in text libraries.
  • Hover over text for NL text commands no longer has artifacts.
  • Building licenses now check and update their local status whenever an active internet connection is available.
  • Fixed issue with the Advanced RBC file saving adding an additional “rbc” to the file name.
  • Opening RBC/RBG files with “download on open” no longer prompts for save and add a “00#” to the end of the file name.
  • Fixed issue where the “Advanced save as macro” feature did not load RVW options correctly.
  • Joystick issue with Graphical and Natural Language fixed;’ waitUntil(), displayButtonValues() and displayControllerValues() now function correctly.

VEX bug fixes:

  • Fixed issue where IQ Graphical playSound() block dropdown displayed internal values.
  • VEX IQ displayButtonValues does not display correct value in RVW.

Happy Programming!

Written by Cara Friez

August 27th, 2015 at 8:16 pm

Download ROBOTC for LEGO MINDSTORMS 4.50 Today!

without comments

ROBOTC 4-50 LEGO

The ROBOTC Development Team is excited to announce our latest update, ROBOTC 4.50! This update is for the LEGO MINDSTORMS (NXT and EV3) robotics systems and includes new features, functionality and a load of bug fixes.

Click here to download 4.50!

 

Important Setup Information for ROBOTC 4.50:

LEGO NXT Users:

  • Simply update to the latest ROBOTC firmware from inside of ROBOTC.

LEGO EV3 Users:

  • All users will need to update the  LEGO EV3′s Kernel by connecting the EV3 and selecting “Robot Menu -> Download EV3 Linux Kernel” from inside of ROBOTC. The version number (1.07X) is the same to keep alignment with the EV3 Programming Software and LEGO’s releases.
  • After updating your EV3′s Linux Kernel, you’ll also need to update the ROBOTC firmware from inside of ROBOTC.

ROBOTC 4.32 —> 4.50 Change Log:

General new features:

  • Graphical blocks can now be copied, cut and pasted

Copy Paste

  • Graphical actions, such as adding, deleting and moving a blocks, changing parameters and their values can be undone and redone.
  • The Graphical repeat and while blocks values can now be adjusted without a keyboard using spin buttons.

Number Scroll Color Loop
General fixes:

  • Large amounts of data in debug stream no longer causes debugger to hang.
  • Fixed issue when mixing PLTW building licenses with other license types.
  • When changing the motor type in the Motor and Sensor Setup utility, the additional parameters, such as PID, drive side, encoder type, are reset to their default values.
  • UAC prompt now appear only once for installing multiple RVW packages.

RVW Package Manager

  • The toolbar buttons are sized to the individual content, instead of the largest one.
  • Recursive pre-compiler statements are correctly identified and no longer crash the IDE.
  • The Graphical block library’s expansion/collapse state is now preserved when switching between files.
  • LineTrackLeft help text has been corrected.
  • Fixed issue of undefined entries in text libraries.
  • Hover over text for NL text commands no longer has artifacts.
  • Building licenses now check and update their local status whenever an active internet connection is available.
  • Fixed issue with the Advanced RBC file saving adding an additional “rbc” to the file name.
  • Opening RBC/RBG files with “download on open” no longer prompts for save and add a “00#” to the end of the file name.
  • Fixed issue where the “Advanced save as macro” feature did not load RVW options correctly.
  • Joystick issue with Graphical and Natural Language fixed;’ waitUntil(), displayButtonValues() and displayControllerValues() now function correctly.

MINDSTORMS fixes:

  • Disconnecting an EV3, with the debugger running, no longer causes the IDE to hang.
  • Missing sensor commands have been added to the EV3 text library.
  • Fixed issue of incorrect NXT sensor variables when dragged into program from the text library
  • Fixed mistakes in examples for the help documentation of the EV3 motor commands.
  • EV3 standard models and sample code have been updated with the default mode for the Gyro set to Rate and Angle and the Color sensor mode set to Color.
  • Corrected issue where nPgmTime was erroneously identified as a signed long in the help.
  • Added numerics to Color name values in help documentation.
  • Wireless Searching for NXT in EV3 context has been removed.
  • Fixed issue where the return value of getColorName() opcode expected a long, but the TLegoColors is a byte, this could cause memory corruption.

Happy Programming!

Written by Cara Friez

August 27th, 2015 at 8:14 pm

Download ROBOTC for VEX Robotics 4.32 Today!

with one comment

ROBOTC 4-32
 

The ROBOTC Development Team is very excited to announce our latest update, ROBOTC 4.32. This update is for the VEX Robotics (VEX EDR CORTEX and VEX IQ) robotics systems and includes new features, functionality and a load of bug fixes.

 

Click here to download 4.32!
Important Setup Information for ROBOTC 4.32:

VEX IQ Users:

  • Run the “VEX IQ Firmware Update Utility” and update your VEX IQ Brain to firmware version 1.15.
  • 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.25 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.25 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.30 —> 4.32 Change Log:

Robot Virtual Worlds Package Manager

Robot Virtual Worlds Package Manager simplifies keeping your RVW worlds up-to-date and allows you to easily download new ones.

RBC Macro Editor

The RBC Macro Editor allows you to quickly create a ROBOTC Text-Based or Graphical macro file that will pre-configure many aspects of the UI, such as platform, the debugger windows that are to be opened, the default save-as file name and many others. If you are targeting Virtual Worlds, you can also select which world should be used.

General Changes

  • Debugstream has been made more robust to prevent buffer overflows and corrupted data.
  • Added quick access, “Add License” menu item.
  • Added command line option to deactivate all active, non-building licenses (-DEACTIVATE).
  • “SensorValue” intrinsic definition changed from ‘word’ to ‘int’. This will allow it be be either ‘short’ or ‘long’ depending on the native “int” format of specific platform.
  • CTRL+ALT+SHIFT+D” is new keyboard accelerator to open preferences.
  • All libraries (DLLs) and executables are now signed.

General Bug Fixes

  • Fix issue where a “save as” with a new document -> then a subsequent “save” would cause a “save as” prompt in the wrong location.
  • Fix enumeration bug in Joystick Driver
  • Context menu for large ICON toolbar changes now take immediate effect.
  • Fix the repeatUntil(0) warning message to say “‘repeat until’ expression is constant ‘0’. Loop will never exit.”
  • Fix issue with command line deactivation with building licenses
  • IDE was not removing error flags from graphical blocks.
  • Long operands on opcodes “&” “|”, “^” and “~” were incorrectly handling negative 16-bit constants.
  • Fix bug in addTo/MinusTo/DivideTo/TimesTo opcode when variable is a global short variable and the operand is a 16-bit or less compile time constant.
  • Fix issue that prevented functions that return pointers to be dereferenced in an expression.
  • Fixed a bug where the missing “Name” field would cause a crash for the command line activation.

Graphical

  • Hitting the Control key no longer deselects all the things.
  • Bug causing Graphical Block artefacts on the screen has been fixed.

VEX

  • Added 2 more RVW Cortex Standard Models.
  • Enhancements to improve the VEX Cortex IME functionality in Virtual Worlds
  • Fixed download firmware button not allowing you to cancel the procedure
  • Small fix for VEX Cortex to disable sensor ports during initialization to prevent solenoid jitter.
  • Fixed issue of “SQUAREBOT” standard model having PID control enabled with quadrature encoders.
  • Fixed issue of “SQUAREBOT” standard model not having the VEX LCD configured.
  • Removed the quadrature encoders from the “SQUAREBOT – IME” standard model.

Happy Programming!

Written by Cara Friez

June 12th, 2015 at 5:29 pm

ROBOTC for LEGO MINDSTORMS 4.32 Available Today!

with 2 comments

ROBOTC 4-32 LEGO
 

The ROBOTC Development Team is excited to announce our latest update, ROBOTC 4.32! This update is for the LEGO MINDSTORMS (NXT and EV3) robotics systems and includes new features, functionality and a load of bug fixes.

Click here to download 4.32!

Important Setup Information for ROBOTC 4.32:

LEGO NXT Users:

  • Simply update to the latest ROBOTC firmware from inside of ROBOTC.

LEGO EV3 Users:

  • All users will need to update the  LEGO EV3′s Kernel by connecting the EV3 and selecting “Robot Menu -> Download EV3 Linux Kernel” from inside of ROBOTC. The version number (1.07X) is the same to keep alignment with the EV3 Programming Software and LEGO’s releases.
  • After updating your EV3′s Linux Kernel, you’ll also need to update the ROBOTC firmware from inside of ROBOTC.

ROBOTC 4.30 —> 4.32 Change Log:

Robot Virtual Worlds Package Manager

Robot Virtual Worlds Package Manager simplifies keeping your RVW worlds up-to-date and allows you to easily download new ones.

RBC Macro Editor

The RBC Macro Editor allows you to quickly create a ROBOTC Text-Based or Graphical macro file that will pre-configure many aspects of the UI, such as platform, the debugger windows that are to be opened, the default save-as file name and many others. If you are targeting Virtual Worlds, you can also select which world should be used.

General Changes

  • Debug Stream has been made more robust to prevent buffer overflows and corrupted data.
  • Added quick access, “Add License” menu item.
  • Added command line option to deactivate all active, non-building licenses (-DEACTIVATE).
  • “SensorValue” intrinsic definition changed from ‘word’ to ‘int’. This will allow it be be either ‘short’ or ‘long’ depending on the native “int” format of specific platform.
  • CTRL+ALT+SHIFT+D” is new keyboard accelerator to open preferences.
  • All libraries (DLLs) and executables (EXEs) are now signed.

General Bug Fixes

  • Fix issue where a “save as” with a new document -> then a subsequent “save” would cause a “save as” prompt in the wrong location.
  • Fix enumeration bug in Joystick Driver
  • Context menu for large ICON toolbar changes now take immediate effect.
  • Fix the repeatUntil(0) warning message to say “‘repeat until’ expression is constant ‘0’. Loop will never exit.”
  • Fix issue with command line deactivation with building licenses
  • IDE was not removing error flags from graphical blocks.
  • Long operands on opcodes “&” “|”, “^” and “~” were incorrectly handling negative 16-bit constants.
  • Fix bug in addTo/MinusTo/DivideTo/TimesTo opcode when variable is a global short variable and the operand is a 16-bit or less compile time constant.
  • Fix issue that prevented functions that return pointers to be dereferenced in an expression.
  • Fixed a bug where the missing “Name” field would cause a crash for the command line activation.

Graphical

  • Hitting the Control key no longer deselects all the things.
  • Bug causing Graphical Block artefacts on the screen has been fixed.

MINDSTORMS

  • New Linux image, updated to 1.07X to ensure compatibility with LEGO EV3 Programming Software. Please be sure to update your brick to the latest Linux firmware.
  • EV3 brick can now be renamed from both the file and the communication utilities in the Robot menu.
  • Refreshed the Driver Suite files for both NXT and EV3
  • getColorRGB() will now also work with a standard LEGO NXT Color sensor.
  • Added intrinsic getSensorConnType() to retrieve sensor connection type.
  • Fixed multi-tasking issue in EV3 VM where multi-tasking was not possible with programs started directly from the EV3 Brick.
  • Fixed a division by zero error in DatalogTest.c sample program
  • Fixed an issue where uploading a file from your EV3 to your PC removed the file extension from the uploaded file.
  • LEGO NXT Sensors that are normally auto-ID’d no longer have their autoID flag disabled for that port.
  • LEGO Energy Meter was improperly configured.
  • Fix Standard Model issue for EV3 (Gyro was improperly configured)

Happy Programming!

Written by Cara Friez

June 12th, 2015 at 5:29 pm

RVW Virtual Brick Giveaway Contest

with one comment

VirtualBrick

Want to earn a free Robot Virtual Worlds – Virtual Brick license? BotBench has an awesome license giveaway going on now. Be one of the first 20 people to write a review about it on your website, blog or Tumblr, and you’ll receive a free license! Read more about it here!

Not sure what the Virtual Brick is? Check out our video …
 

Botbench also did a wonderful “First Look” blog on the Virtual Brick. Check it out here – Virtual Brick: A First Look – Making a Line Follower

Want to try out the Virtual Brick? You can download it here and when you do, you get a 10 day trial period.

Happy Programming!

Written by Cara Friez

February 3rd, 2015 at 9:18 am

Update – ROBOTC for VEX Robotics 4.08

with 4 comments

ROBOTC logo 4 UpdateThe ROBOTC Development Team is excited to announce the availability of ROBOTC for VEX Robotics 4.08 – an update for the VEX Cortex and VEX IQ platforms. This new version supports the latest firmware versions provided by VEX Robotics (4.20 for VEX Cortex / 1.09 for VEX IQ) and all of the new features supported by the new firmware updates. Some of these new improvements include:

– Support for the VEXnet 2.0 (white) Radios for the VEX Cortex
– Bug Fixes for the VEX IQ system to prevent “I2C Errors”
– Speed enhancements for VEX IQ for better performance of motors and sensor
– New VEX IQ commands for Gyro sensors

This new version of ROBOTC also supports the VEX IQ “Graphical Natural Language” feature. This new interface allows users to program robots from inside ROBOTC with easy-to-use graphical blocks that can be drag-and-dropped to form a program. Each block represents an individual command from the “text-based” ROBOTC and Natural Language. The new click and drag interface along with the simplified commands of Natural Language allows any robotics user to get up and running with programming their robots as soon as possible. As of today, the Graphical Natural Language commands work with the VEX IQ system, but we’re actively developing support for ALL ROBOTC supported platforms!

Before you can use ROBOTC for VEX Robotics 4.08, you will need to ensure that your VEX devices are up to date. The instructions to update your hardware will be different depending on what hardware setup you may have…

  • VEX IQ Users
    • Run the “VEX IQ Firmware Update Utility” and update your VEX IQ brain to firmware version 1.09. You 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 version 4.20 from inside of ROBOTC. After updating your master firmware, you will also have to install 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 find this 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 version 4.20 from inside of ROBOTC. After updating your master firmware, you will also have to install the latest ROBOTC firmware as well.
    • Note that this new firmware version will support download and debugging with both VEXnet 1.0 (black) and VEXnet 2.0 (white) keys.

Here’s the list of changes and enhancements between version 4.06 and 4.08.

VEX Cortex:

  • Support for VEX Cortex Master Firmware 4.20 and VEX Game Controller Master Firmware 4.20
  • Support for wirelessly download and debugging using the new VEXnet 2.0 2.4Ghz radios.
  • Fixed an issue with launching ROBOTC in “Virtual Worlds” mode, which may incorrectly choose the wrong compiler target.
  • Fixed issue with Windows XP/Vista/8 where ROBOTC may crash when unplugging/plugging in a device

VEX IQ:

  • Improved motor responsiveness (16ms update cycles as opposed to 50ms today – this was a mitigation for the I2C issues in the current Master FW)
  • Improved sensor responsiveness (varies by sensor – this was a mitigation for the I2C issues in the current Master FW)
  • Gyro sensors can now return either integer values (getGyroDegrees/getGyroRate) or floating point values (getGyroDegreesFloat/getGyroRateFloat)
  • Fixed a bug where the Gyro sensor was not using the “rate” setting to properly return a deg/sec calculation for the getGyroRate command.
  • Exposed the ability to calibrate the gyro sensor from the user program and specify the number of “samples” to take during calibration (more samples = less drift = longer calibration time)
  • Also added a boolean “get” command to read the gyro calibration status bit to know when calibration is done.
  • New PWM adjustment function – allows users to trigger a specific VEX IQ motor to read the current battery voltage from the VEX IQ brain to adjust the PWM scale factor in the motor to ensure consistent performance. This is automatically done each time a program is executed with ROBOTC, but for longer programs end-users might want to readjust the PWM scale factor.
  • New “read immediate current” from motor – returns a value in mA
  • Modified functions for “motor strength” – renamed these to be “motor current limit” and uses values in mA instead of 0-255 byte value. These commands used to be called “getMotorStrength” and “setMotorStrength” – they’re now renamed to “getMotorCurrentLimit” and “setMotorCurrentLimit”
  • Fixed an issue with “Graphical” mode where users may start up in “Cortex” mode and the function library will appear blank
  • Fixed an issue when “Natural Language” mode was enabled that normal sample programs may not run properly (using the leftMotor/rightMotor keywords)
  • Fixed issue with Windows XP/Vista/8 where ROBOTC may crash when unplugging/plugging in a device

If you have any questions or issues, contact us at support@robotc.net. Happy Programming!!

 
 

Robomatter Blog Ad VEX IQ

 

Written by Tim Friez

March 26th, 2014 at 8:40 pm

ROBOTC Graphical Programming Preview Available!

without comments

clickanddragAfter months of work, the ROBOTC Development Team is excited to announce the availability of the first preview release of ROBOTC Graphical Language for the VEX IQ platform. This new interface will allow you to program robots from inside ROBOTC with easy-to-use graphical blocks that can be drag-and-dropped to form a program. Each block represents an individual command from the “text-based” ROBOTC and Natural Language. The new click and drag interface along with the simplified commands of Natural Language will allow any robotics user to get up and running with programming their robots as soon as possible.

The first release of ROBOTC Graphical Language is available for the VEX IQ platform for use with the standard VEX IQ Clawbot and Autopilot Robots. All ROBOTC 4.0 users will receive access to the new Graphical Language interface at no additional cost! Our plans over the next few months are to extend the Graphical Language interface to all of ROBOTC’s support platforms, including the Robot Virtual Worlds technology. You can download the preview version today at http://www.robotc.net/graphical/.

———————————————————————————————————————————————————-

The new ROBOTC Graphical programming environment adds a number of new features we’d like to highlight:

Graphical Language Command List (Drag and Drop)

GraphicalFunctionBar
With the new ROBOTC Graphical Mode, we’ve updated our “Functions Library” to match the style of the Graphical interface. This new mode will allow you to drag and drop blocks of code from the “Graphical Functions” menu into your program to get your program created even faster!

New Language Commands for Easier Programs

NewLanguageCommands
We also added some new language extensions to both ROBOTC and Natural Language; such as the simplistic “Repeat” command. Prior to the Repeat command, users would need to copy and paste large sections of code or use a looping structure (like a ‘for’ or ‘while’ loop) in order to have a set of actions repeat a number of times. With the new “Repeat” command, however, users can simply specify how many times they would like the code to run, with no complex coding required. And users who wish to make an “infinite loop” can use the “repeat forever” command to accomplish this task quickly!

Commenting Blocks of Code!

CommentingOut
Another awesome tool that we’ve implemented in ROBOTC Graphical is the “comment out” feature. You can now comment out an entire line of code just by clicking on the block’s line number. The robot ignores lines of code that are “commented out” when the program runs, which makes this feature very useful when testing or debugging code. This new tool is unique to ROBOTC’s Graphical interface.

Updated and Simplified Toolbar

Toolbar
Sometimes navigating menus as a new user can be a little overwhelming – so many options to choose from and lots of questions about what each option is used for. To help with this, we’ve redesigned ROBOTC’s toolbar to make getting up and running easier. We put the most used commands on a larger toolbar so new users have an area to easily click to download firmware, send their code to their robot, and run their programs without having to use the standard menu interface.

Convert to Text-Based Natural Language

ConvertToText ConvertToText2
Because each Graphical Natural Language block corresponds to a real ROBOTC or Natural Language function, users will be able to graduate from Graphical Programming to full text-based programming with the press of a single button. This allows users to naturally transition from Graphical Natural Language to the text based Natural Language (or ROBOTC), without having to worry about manually converting the code line-by-line!

Teacher’s Guide and Sample Programs

UsersGuide
The new graphical interface includes over 50 new sample programs to help you get up and running with working examples and demo code. In addition, we’ve also developed a 30+page guide to walk new (and existing) users through the new Graphical Programming interface and getting started with the VEX IQ platform. You can find a link to the programming guide here and also on the ROBOTC Graphical page.

———————————————————————————————————————————————————-

This initial release is only the beginning and we’re planning on improving the software with more features and flexibility over the coming months.

Future Support/Features:

  • Copy and Paste
  • Undo/Redo Support
  • Support for custom robots/configurations via an updated “Motors and Sensor Setup” interface.
  • Dynamic Loop and Command Parameters (based on Motors and Sensor Setup / Robot Configuration)
  • Tooltips, Contextual Help, and more!

Click here to download the installer!

Let us know what you think! If you have any feedback or questions, please send them along via the ROBOTC’s VEX IQ forums.

 
 

Robomatter Blog Ad VEX IQ

 

New Robot Virtual Worlds Video!

with one comment

RVWRobot Virtual Worlds just released a new video all about the software!! Check it out here:

 

 

 

 

 

Already using RVW? What do you think? How do you use this software in your classroom? We’d love to hear your feedback!

ROBOTC Curriculum Breakdown

without comments

ROBOTC-BreakdownA curriculum pacing guide is something that teachers have to consider whenever they examine their curriculum. This fact does not escape teachers of <a href=”http://www.robotc.net”>ROBOTC</a>. Whenever I come across teachers who are just starting to use the ROBOTC curriculum, often their first question revolves around how long the curriculum will take. Once again, teachers are used to having some type of pacing guide that delineates how a subject is to be taught. The ROBOTC curriculum is not organized in that fashion. Instead, the curriculum is organized by topic. The topics include basic programming fundamentals, robot movement, robot sensing, etc. The teacher is then free to spend an appropriate amount of time within each topic.

As teachers, this freedom is welcome. It is welcome because the pacing that comes with most textbooks is an impossible guide to follow. In order to create a true pacing guide, student background knowledge would have to be taken into account. Since every classroom is different (sometimes within the same grade, within the same school), it is impossible to gauge how quickly the students are going to master the concepts as they are presented. Screenshot-2013-09-05_15.11.12Additionally, as the teacher becomes more familiar with ROBOTC, they will find that they spend more time on particular concepts then they did the first time they taught the curriculum. For example, when I first taught ROBOTC, I spent 20 minutes discussing Flowcharts and Pseudocode. Experience has now taught me to spend a significant amount of time on these topics. I also spend much more time talking about Errors. Specifically, what should a student do when they get the dreaded compiler errors in their program? Experience has taught me to spend much more time on thinking about the logic of a program before the writing of ROBOTC and on debugging strategies once the code has been written.

Screenshot-2013-08-05_15.01.181Each of the aforementioned sections of the ROBOTC curriculum contains a programming challenge. The programming challenged is designed to showcase the skills that were emphasized in that section. Each section also contains an assortment of “mini challenges”. These challenges can be used at the teacher’s discretion. They all do not have to be completed. However, they can be very useful. For example, after the students have spent a day or two learning a topic, I will begin the following class with one of these mini challenges. They might not know all of the skills needed to complete the section challenge, but the mini challenge is a good assessment of what has been presented so far in that section. This also serves as a good change of pace for the class. Simply, you can’t learn to program without actually programming. In order to really understand the applications of while loops or if/else statements, students need to apply them. The mini challenges found within the ROBOTC curriculum serve as a great opportunity to scaffold skills toward their more challenging applications.

A beginning teacher of ROBOTC could teach the basic ROBOTC curriculum in one semester. By including many of the mini challenges, the curriculum can be stretched easily over a semester. I often tell teachers who are teaching the class for a year to do this, and then to end the year with a larger programming challenge. After the students have made it through the ROBOTC curriculum, I enjoy introducing them to Multi-Robot Communication. The sensor needed (NXTBee) is inexpensive, and there are a lot of great ideas for activities and programming challenges.

 


 

If you have a stronger background in computer science, and maybe you are teaching older students, you may be able to navigate through the curriculum much faster. What then do you do with students if you have them for an entire year? Luckily, there are many great ROBOTC projects on robotc.net. Moreover, the ROBOTC forum is also a wonderful place to look for ideas for projects, in-class competitions, and programming challenges.

Teaching robotics and ROBOTC is a lot of fun. The ability to watch your students apply what they learn in the ROBOTC curriculum in such engaging and open-ended activities is one of the main reasons why.

Setting up ROBOTC and RVW for the Classroom

without comments

Setting-Up-ClassroomOnce the physical hardware (robotics kits) are secured for a classroom, the next step is to install the software (ROBOTC and Robot Virtual Worlds). It would be nearly impossible to cover every single specific setup that could be encountered on a classroom’s computers, but this blog post will cover the basic installation steps and some of the more common installation issues that educators may run into when installing ROBOTC in a classroom.

The first thing you will need to do is install ROBOTC on the computers in your classroom. To do this, always make sure to grab the latest version of ROBOTC that your license supports from the correct ROBOTC download page. If the wrong version is downloaded and installed, or if there is already a different up-to-date version of ROBOTC installed on the computers, you will not need to uninstall and reinstall the program; instead, you will simply need to activate your license in ROBOTC (more on this later). During the download process, ROBOTC will also attempt to install the necessary drivers for communications with physical robots. Depending on the level of security on the computers, you may need to get your IT department involved in order to ensure that the drivers are installed properly.

Activating_ManageOnce ROBOTC and the appropriate drivers have been installed, you will need to activate ROBOTC on each computer manually. The license activation ‘unlocks’ the ability to download code to either a physical robot or a Virtual World, depending on which license is used.  When ROBOTC is installed on a computer, all versions of ROBOTC (including different robotics platforms, such as the VEX and LEGO platforms, and different compiler options, such as Virtual Worlds compiler options) are installed at the same time. Instead of installing additional copies of the software  on the same computer (or opening a new program every time you would like to change the compiler target), the additional platforms and compiler options are ‘unlocked’ by activating their respective keys.

Before we move on to the next blog (Setting up the Robots), here a couple more tips that may come in handy when setting up ROBOTC in a classroom:

  • Depending on the programs, policies, and restrictions in place on the machines, your school’s IT department may need to be present for the installation or activation of ROBOTC, Virtual Worlds, or the installation of any drivers for the physical robots.
  • If your school’s IT department images and deploys the classroom’s computers, make sure they reference the ROBOTC Deployment Guide on the ROBOTC wiki for important help and information.
  • Make sure to check the computers’ hardware to the minimum requirements for ROBOTC or Robot Virtual Worlds before
  • Always test one computer first! If there is a problem with the installation, it is better to find out about it early and fix it before they same issue appears on a classroom full of computers.

– John Watson