Latest ROBOTC Update is our Official Release!!



We’re very excited for our official release update, ROBOTC 4.26!! This update is for the both the VEX Robotics (CORTEX and IQ) and LEGO MINDSTORMS (NXT and EV3) robotics systems.

Some of these new updates include …

  • Full EV3 Functionality (Sounds, LCD, LEDs, Sensors, Motors)
  • Graphical Language for all platforms (VEX IQ, VEX Cortex – LEGO NXT, LEGO EV3)
  • Updated 3rd Party Driver Library for NXT and EV3
  • Updated Text Based Natural Language for NXT
  • Tons and Tons of Bug Fixes and Enhancements!




ROBOTC 4.25 -> 4.26 Change Log

  • Major Bug Fixes
    • Fixed Encoder Count Issue with VEX IQ Virtual Worlds – Encoders were not properly adjusting to the 360 count scale and may have caused issues when trying to use multiple “setMotorTarget/moveMotorTarget” commands.
    • Fixed Virtual Worlds for VEX Cortex platform – crashes when trying to download to Virtual Worlds with VEX Cortex platform are now resolved.
  • VEX IQ
    • Support for VEX IQ Brain Firmware Version 1.12
    • Increase timeout (4 seconds -> 10 seconds) for downloading over wireless for VEX IQ.
    • New VEX IQ Clawbot image for Standard Models
    • New Dialog Message for successful VEX IQ Firmware Downloading
  • VEX Cortex
    • Implemented fix for dual platform users who may experience compiler errors due to “External Motors/Servo Controllers” flag being enabled.
    • Check that a valid team number has been set for VEX Cortex Controller. The check is made during user program download when the download type has been set to “Competition”. Teams should set their VEX Team Number to assist with debugging at competition while using VEXNet 2.0 (white) radios.
  • LEGO EV3
    • Adjust EV3 Standard Model – Motor ports were reversed (left vs right)
    • Adjusted all EV3 Graphical Sample Program to reflect new “standard model”
    • Support for draw picture (BMP) file on LCD screen. Does not support general BMP files, but rather LEGO specific picture files.
    • Fixed an issue where the EV3 “Reset Gyro” command was not properly resetting the Gyro value.
    • “getBatteryCurrent” command has been fixed.
    • Improved usage of Casper’s “search for devices” so that USB connected EV3 that are disconnected during a ROBOTC session are better handled.
    • Crashes to ROBOTC after closing the IDE Editor after communicating with an EV3 have been resolved.
  • Virtual Worlds
    • Additional Logic to have “TETRIX” based Virtual Worlds appear if the “External Motor/Servo Controller” flag is toggled. Currently they do not appear under any condition.
    • Fixed bug hiding “Joystick Control – Basic” for Virtual Worlds users.
  • Graphical Interface
    • Prevent ‘text’ and ‘graphical’ menus from becoming undocked from the ROBOTC interface – doing so may cause the main ROBOTC interface to become unresponsive.
    • Fixed bug where empty parameter values were using the last provided string as opposed to overwriting with “Blank” values – applies for the “MultipleMotor” Graphical commands.
  • ROBOTC IDE / General
    • Text-Based Function Library will no longer show commands that have been deemed “deprecated”
    • Update “Errors” to “Compiler Errors” based on user’s feedback.
    • Change compiler “error” to “warning” for assignment of a pointer value to an int without use of a cast.
    • Compiler was incorrectly allocating temporary variables during evaluation of “&(NULL)” types of expressions. Fixed.
    • Updated Help documentation files.

Download ROBOTC 4.26 here! And ensure that your devices are up to date by following the instruction in our last post. 

As always, if you have questions or feedback, feel free to contact at or visit our forums! Happy programming!!

Written by Cara Friez

September 2nd, 2014 at 10:07 am

11 Responses to 'Latest ROBOTC Update is our Official Release!!'

Subscribe to comments with RSS or TrackBack to 'Latest ROBOTC Update is our Official Release!!'.

  1. […] out!  ROBOTC 2.26 has been released.  You can read all about it here: [LINK].   It has a lot of changes, so be sure to check the complete Changelog.  Now that it’s […]

  2. The 4.26 release does not contain the EV3 nor NXT platform after I download and installed the new version today. I understand that they would be included in this release.


    2 Sep 14 at 4:02 pm

  3. […] out!  ROBOTC 2.26 has been released.  You can read all about it here: [LINK].   It has a lot of changes, so be sure to check the complete Changelog.  Now that it’s […]

  4. Sounds like your trial might be expired. If you have a license and are still running into this issue, send a ticket into with a screenshot of your license management screen + your licenseID.

    Cara Friez

    2 Sep 14 at 9:29 pm

  5. My problem is fix. I had to manually plug in my License ID and Password. I thought that any release would look at my License and auto it into the new release.

    But all is well.


    4 Sep 14 at 2:36 pm

  6. CONFUSED!!!!!!!!!!!!!! Is the graphical interface optional? what happened to writing the code? Is there a tutorial on this new interface somewhere? Not sure coping Lego was a good idea.


    4 Sep 14 at 9:22 pm

  7. Hi Jacquelyn! The graphical interface is one option available in ROBOTC. Text based coding is still there. You can find out brand new tutorial series (which is still in the works) available here –

    Cara Friez

    5 Sep 14 at 3:20 pm

  8. Does 4.26 have the ability to daisychain? I don’t see any mention of it here.


    5 Sep 14 at 9:17 pm

  9. You cannot daisy chain EV3s yet, but it does support TETRIX daisy chaining with NXT/TETRIX.

    Cara Friez

    6 Sep 14 at 11:03 am

  10. Problem: when i put the NXT into samba mode which i had to do with the 3.0 of robotc to be able to update the firmware the 4.0 does not even see the NXT in this mode making it not able to update the firmware. Is this a bug or has the method of updating the firmware for the NXT change between the versions?


    10 Sep 14 at 7:45 pm

  11. Nothing’s changed with the NXT – but a number of Arduino devices look like an NXT in firmware update mode and put the wrong driver in. Send in a ticket to and we’ll send you some resources to get back up and running.

    Cara Friez

    11 Sep 14 at 10:38 am

Leave a Reply