i know almost nothing about programming
that being said sounds like this year java teams will be using eclipse rather then netbeans and moving up to java 8. this software is available now right?
also will the old crio be capable of running this new stuff? will the roborio be able to run the “old” stuff? you can transfer programming to roborio using a USB correct?
sorry for my ignorance. we are trying to get some new mentors in to help with programming and i need to be set up ready to go
Everyone is ignorant of something or the other! Someone who claims to be an expert has not met his/her match!
No. The software will not be released until kickoff. Only Beta test teams have access to the software at this point, for testing purposes. FIRST has not made any announcement about releasing the software tools earlier at this point, so we can not assume they will.
No, the JVM on the cRIO is a squawk JVM based on Java ME. The RoboRio is based on SE 8 embedded. While the new 2015 Java API is largely the same, there is enough changes that the NEW stuff will not run on the cRIO. However, all of the 2014 JavaME based tools for netbeans will still work on the cRIO.
When you say run, I assume you mean take the jar file compiled from 2014 and run it on the Roborio. This will not work. The files compiled using the 2014 FRC tools will not run without modifying the Roborio beyond the scope of FRC. It may be possible if you are very familiar with Linux, installing additional JVMs, and the WPILIB HAL, but I doubt this will be FRC competition legal.
However, if you have access to the java source code in 2014, you can use it in 2015. It will require a few source code modifications, before it will compile again, but it should be trivial (rename class names, change port numbers, remove, constructor parameters which are now non-existent like module number). Once you modify the 2014 source code to match the 2015 java libraries and compile using the new 2015 eclipse tools, your Java project based on 2014 code should run on the RoboRio.
Usb, Wifi, or tether Ethernet.
Hope this helps,
very helpful thank you Kevin
If you have other questions, please feel free to contact us (2177 (at) therobettes.com)… We’ve been alpha/beta testing the new system since last fall, in java, and are more than willing to help out another local team get prepared for the season. Also, if you’re coming down for MN SPLASH at the U in a couple of weeks, we’ll be presenting on everything we know there.
For reference, we copied last year’s code over to the new system, and the students were able to get it up and running over the course of a single meeting.
The biggest difference is with constructors - with the cRIO, you could create something using a slot and a port, in case you had two analog, digital, or pneumatic modules. with the roboRIO, there are no modules, so the constructors changed a little bit to reflect this.
If you use CAN, things there changed a bit to make it more user-friendly and less likely to blow up on you.
The AnalogChannel class is now AnalogInput, but otherwise the same. There’s a new Potentiometer class that we really like, as well.
If you use pneumatics, things are a bit different, as there is no compressor code needed. It just works. Otherwise it’s pretty much the same for controlling your solenoids.