Websites and Social Media - (Team news, build updates, battle & damage reports) Submissions

r/battlebots robot combat wiki Official Team Links I will post about them on this blog.List of Robot Combat events around the world You can expect a new beta build every 1 to 2 weeks, depending on the number of bugs that get found. These are “live documents” and will be updated as the beta program progresses. It also includes some links to get getting started documentation, known issues and a function reference. You can find the original announcement on the ROBOTC forums here. I’ve already got everything compiling, but nothing has been tested yet. I will also be working on porting the Driver Suite to ROBOTC 4.x for both NXT and EV3. The documentation is a work in progress and the APIs are subject to change as they’re being implemented. The beta comes with several example programs to get your started.

Daisy Chaining EV3’s together and using daisy chained motors/sensors.

EV3 specific features (buttons, sounds).

I2C / External Controller (TETRIX, MATRIX) Support.

Multiple Datasets for certain EV3 sensors (like Rate/Heading for Gyro).There are things that haven’t been implemented fully or tested properly: Normal ROBOTC features – Debugger, Multitasking, Variables, Debug Stream, etc.Limited NXT Device Support (basic sensors + motors).Encoder Support (reading encoders + moving to encoder targets).PID Motor Support (regulated movements).General Motor Support (unregulated movements).The basic functionality is mostly all there: This is the first public beta and as with all betas, there will be some missing features and bugs. You can now program your EV3 with ROBOTC.

It took a bit longer than we’d hoped for but the wait is over. It’s here! The first beta of ROBOTC for EV3 has arrived!

Download hexbug beta