RobotPy 2011.3

[Peter Johnson]

As there seems to be a lot of interest in trying out Python in the fall, I've released a new (hopefully final) version for 2011: 2011.3

Download the new packages at: http://firstforge.wpi.edu/sf/frs/do/viewSummary/projects.robotpy/frs

Note you want to download all three packages!

The "core" package contains Python (FRC_UserProgram.out) and its standard libraries.

The "WPILib" package contains WPILib - both the libraries for the robot and some sample code.

The "Utilities" package contains some useful utilities (contributed by virtuald).

Both the core and WPILib packages have "robot" directories containing the files that need to be copied to the robot. They also have an install.py Python script that will perform this copy for you (just enter your team number).

This version incorporates WPILib r2262 and some incomplete vision wrappers.

[virtuald]

Haha, I was just going to email you tomorrow about possibly releasing some new packages. :)

[ozzloy]

http://firstforge.wpi.edu/sf/wiki/do/viewPage/projects.robotpy/wiki/Install

says "unzip the release .zip", there's 3 of them here:

http://firstforge.wpi.edu/sf/frs/do/viewSummary/projects.robotpy/frs

my robot is flashed with c++.

i have downloaded all 3 files up there, unzipped them, and ftpd all files in {core,wpilib}/robot/* to 10.te.am.2:/*

i put a robot.py under 10.te.am.2:/py/robot.py next to boot.py

i get red next to Robot Code.

am i skipping a step?

[virtuald]

Yes, that's what you should have done. You should use the NetConsole and see if there are any errors reported when the robot is starting up.

[ozzloy]

now that you've confirmed those steps, i'm running on a new theory.

i think flashing to c++ might not have worked correctly.

we've had it fail to switch before. i'm kicking myself for not thinking of it at the time.

now we're going to retry flashing until a the sample c++ program runs. then we'll load the python interpreter.

i'll let you know how that works this weekend.

i've talked to a couple people on other teams who also have had trouble flashing. is there something better than just retrying until it actually flashes? one guy suggested something about dip switches on the bot?

[404'd]

now that you've confirmed those steps, i'm running on a new theory.

i think flashing to c++ might not have worked correctly.

we've had it fail to switch before. i'm kicking myself for not thinking of it at the time.

now we're going to retry flashing until a the sample c++ program runs. then we'll load the python interpreter.

i'll let you know how that works this weekend.

i've talked to a couple people on other teams who also have had trouble flashing. is there something better than just retrying until it actually flashes? one guy suggested something about dip switches on the bot?

Have you had any luck? Because i've been trying RobotPy, and i still get the no robot code light. Even the sample code wont run. I've formatted crio for C++ (v28 image), ran the install on both core and WPIlib, and copied over the "Simple" sample code, but i still have get no "robot code" light. I've seen some posts about using net console, so i will look into that next time i have access

Josh

[virtuald]

It's pretty much a necessity to have NetConsole enabled when you're using RobotPy. Otherwise you can't tell when things die.