![robotc for ev3 robotc for ev3](https://fiverr-res.cloudinary.com/images/t_main1,q_auto,f_auto,q_auto,f_auto/gigs/146414093/original/634aa11a55032fdb5767ee97d0aaa4f968a0139f/code-for-your-ev3-projct-with-robotc.png)
Robotc for ev3 code#
These messages are really just to help you keep your code clean, as far as the compiler can tell they don’t have the potential to cause any problems.
Robotc for ev3 windows#
The debugging windows and all that fun stuff is also working.
![robotc for ev3 robotc for ev3](https://raw.githubusercontent.com/hershyz/robotC/master/icon.png)
So the status right now is that there’s basic motor and sensor control, so it’s actually possible to make functional robots. However, I did mention in a previous post that I am also working on a massive rewrite of the suite to make it more struct-oriented. Some things like I2C will be different but so badly that it will take a lot of work to get it up and running.
![robotc for ev3 robotc for ev3](https://www.shivarobotics.com/uploads/3/8/9/5/38958221/s214622393936640635_p124_i3_w600.png)
Robotc for ev3 driver#
Pretty soon I can start working on porting the Driver Suite to the EV3. Many bugs and issues were fixed in the base LEGO VM that were causing issues, such as failed auto-id and I2C transactions. There has been an enormous amount of progress in the past few weeks on the ROBOTC for EV3.