CRIO-FRCIII

Is there anywhere to ask questions about the new CRIO for the 2015 season? I meant to ask about it at St. Louis last year but didn’t have the time.

Also, when’s the earliest time to get our hands on it? I remember hearing fall of this year.

The FRC NI community page would probably be the way to go: https://decibel.ni.com/content/community/academic/student_competitions/frc?view=discussions\

Some information about the roboRIO is also in the documents section of the same page: https://decibel.ni.com/content/docs/DOC-30419

https://decibel.ni.com/content/docs/DOC-30419

Also, when’s the earliest time to get our hands on it? I remember hearing fall of this year.
http://www.usfirst.org/roboticsprograms/frc/blog-2015-control-system-alpha-testing
Several teams were chosen as alpha testers for the Athena/roboRIO. You can check out their team websites for a summary of results, images, etc.

That’s a shame, I know we would have loved to alpha test (I’m assuming it was either random selection out of teams that won Delphi’s Quality award or submitted applications)

Anyway, thanks for the links!

What is your question about the 2015 Control System. I will try to answer it as best I can.

I am part of the Alpha Test Team.

Regards,
Kevin

FIRST invited 15 teams (former Beta Test teams with good records) to apply to be Alpha Test teams, then accepted 9 of them, 3 per language. If you have any specific questions, I’d be happy to help - my team is one of the Alpha Test teams, and we’ve had ours working in both Java and C++ for several months now.

Well, for either of you I suppose

  1. How is the new Java API? Is it simply the old one or did they re-do it with all Java 8ness
  2. Is it easy to upgrade / switch JRE’s on the niRIO?
  3. (not familiar with C++ on cRIO but our team is considering C++ for 2015) I’ve heard most about the upgrade from Java ME to SE but is it also being updated to C++11? (or does it already have C++11)
  4. How easy is it to write code on standard Java SE / cRIO Java and port it to niRIO?
  5. What are the deploy times?

We are a C++ team, so I’ll take a stab at some of your questions and leave the rest for others.

  1. They are switching IDEs to Eclipse (as is C++), but the libraries are staying much the same. Somebody else will need to elaborate on any differences in the API.
  2. Don’t know
  3. Windriver does not use C++11. It’s stuck somewhere years back in C++ versions. We are using the latest version of Eclipse and C++11
  4. Libraries aren’t expected to change much, but there may be some differences for Java. Somebody chime in here.
  5. Deploy times are pretty quick. It executes script in the command line in Eclipse that ftps the program to the robot restarts the program, no more restarting the OS on every deploy. The whole process takes around 30sec.

I have a few questions.

How long does it take for the whole thing to turn on, including the radio?

Is it still WPIlib for Java?

What’s the radio look like? Are we still using the d-links?

How low does the voltage have to go to brown out the radio/controller?

hm. Faster, not by much

based on his timings, the bootup time is about the same

Is it still WPIlib for Java?

yes

What’s the radio look like? Are we still using the d-links?

i believe so

How good is the support for standard Linux programs, do you think it might be able to run ROS?

I realize the roboRIO has a shorter profile but a larger foot print and now must have external modules for solenoid breakouts and additional analog and digital inputs. Does weight with all the extra components end up similar to the cRIO or is it lighter weight (as we would hope it to be)?

I thought the roboRIO was the radio as well? That’s what I saw at the display model at San Diego or at least what I thought I saw.

Do any of you know what the Solenoid Module will be? I’ve been told it’s a CANipede RCM but it looks a bit old to be used in conjuncture with the new hardware.

Here is an overview of the new 2015 control system:

http://www.fightingpi.org/Resources/Controls/Alpha/Alpha.shtml

Arohowk, please don’t guess at answers. We are currently not using dLinks. We are using USB radios whose drivers reside on the RoboRIO and who don’t require a boot-up like the current radio systems do.

The system will be on display on our 2013 Ultimate Ascent robot this weekend Waterford, and again at the State Championship. In addition, National Instruments reps are planning on coming up to do a LabVIEW seminar and an hour long seminar on the new control system at the State Championships Thursday morning as a part of our ‘1718 Presents’ seminar series. We’ll be releasing more info as States get closer.

Once the competition season ends we’ll restart our Alpha testing and begin updating the web page with more information.

Please keep in mind the software is still VERY much in the development stage. When we met late last year, some of the languages still weren’t completely functional. Take everything with a very large grain of salt: the same folks developing the Alpha hardware are also supporting the current FRC season. Don’t expect much progress for a while.

Whoa. Gunna try to keep up here.

Those times are from my recollection. Please don’t quote me on them just yet.

They are trying to get a USB WiFi dongle working and signs are pretty positive right now. That would mean no more DLink.

The Pneumatics Control Module (PCM) is produced by Cross the Road electronics (makers of the CANipede) communicating via CAN with the roboRio.

Even with the PCM and a breakout for the expansion slot (called the MXP) it should still weigh considerably less than the cRIO. I haven’t weighed everything, but it’s not close to the chunk of metal the cRIO is.

The roboRIO reboots somewhere below 5V (don’t remember exactly) but there may be loss of functionality prior to that. I was just watching for a reboot.

In addition, National Instruments reps are planning on coming up to do a LabVIEW seminar and an hour long seminar on the new control system at the State Championships Thursday morning as a part of our ‘1718 Presents’ seminar series.

Will something similar be offered at Worlds?

Hmm. That would seem to imply that the video camera/server is going to have to be plugged into the new CRIO Ethernet port to get to the network. On the other hand I won’t miss having to find a good place to mount the DLink.

  1. The Java API is, at this point, the same as the old API. Then again, it’s not even all fully functional yet - It’s a better idea to use what they know to get things working perfectly before looking to refactor just for the sake of refactoring.
  2. You’ll be using whatever JRE they decide is FRC legal. The RobotRio is running a RTLinux distro, which makes it very easy to play with.
  3. I’m not sure about the C++ version
  4. Just load up the FRC plugin for Eclipse, and go to town… personally, I like Eclipse a lot better than Netbeans.
  5. Deploy seems a lot quicker - we were going from clicking to driving in under 30 seconds.
  1. We didn’t time it, but it seems quicker than the current cRIO.
  2. Yes, WPI is still heavily involved, and we’re using WPIlib.
  3. Currently, it’s a USB dongle. The final radio hasn’t been decided on yet, and last I heard FIRST was looking at a number of options, including the dongle. Nice point for the dongle: No external power, which means no radio resetting due to power issues!

Overall it weighs less. The modules are all small, simple plastic boxes with nice connectors, very light weight.

It is not the CANipede. It’s a new module developed by CTRE. It connects to the RoboRio through CAN, and provides:

  • Solenoid outputs
  • a jumper to switch between 12 and 24V (with an internal boost, you only need to power it from 12V)
  • A pressure switch input
  • A compressor output

No idea: we just arrange the MI State stuff. We tried to have the NI guys come up last year to the Michigan State Champs but they had some last minute things come up. This year we’re lucky enough to have them planning on attending.