[first] RoboRio

RoboRio
fact-sheet
Also see Wpilib blog post

For other posts about the 2014 FIRST conference, see the index page.  (written on my iPad; please excuse typos)

General

  • Control system 2015-2019 (Had crio for 6 years)
  • Java SE 8 (not java me)
  • Runs about 10 times faster than on crio
  • Will support Eclipse.  Chose Eclipse because better c++ support. Then Oracle announced more support in NetBeans.
  • Multi core
  • Linux based. Available by ssh, webdav. Will have admin access. Canco nnecte, but wont require
  • Will probably have an updated driver station image. Will still only run on windows. Getting more portable over time so may happen one day. They also want simpliciity for troubleshooting on the field

pic
Changes to library

  • Port numbers will shift to be zero based
  • Extensions to API will use generics
  • Will try to keep backward compatibility for two years
  • Deprecated apis will probably go away
  • Everything will be zero indexed

Physical device

  • More robust, less points of failure
  • Can integrate custom electronics into mxp expansion port – will post design kit for custom expansions
  • Power distribution board can measure current of every motor on robot
  • Design will be based on CAN. But different than CAN of past
  • Voltage regulation module (vrm) – cheaper, makes power distribution board smaller. Let’s change easily for future years
  • Will be version of talon with CAN on it. Feature comparable to jaguar. Looking into ability to connect to limit switch
  • RoboRIO weighs about a third of cirio. Plus other modules are less/smaller

Cost

  • $200 power distribution
  • $90 pneumatics
  • $49 voltage regulation
  • $435 RoboRio

board
Timeline

  • RoboRIO available in December.
  • Rest available late October in reasonable quantity
  • This system less disruptive than when crio came out so probably wont do early release of hardware
  • Enough will be in kit of parts for veteran teams to get up and running with 4 motors. Not sure if will include voltage regulation module

[first] wpilib in 2015

Wpilib into 2015 (programming with java and c++ on the RoboRio)

Also see RoboRIO post

For other posts about the 2014 FIRST conference, see the index page.  (written on my iPad; please excuse typos)

Synergy in the tools (some of this was introduced for the 2013-2014 year and the rest was introduced earlier)

  • Really pushing commands
  • Associate commands with OI
  • Test commands individually – via buttons on SmartDashboard
  • On test mode, shows status of each subsystem on graphically
  • RobotBuilder produces wiring diagram
  • Spent a long time on RobotBuilder and command based programming (i like the command based programming, but not sold on RobotBuilder)
  • If don’t use Word the right way’ you fight with it. True of wpilib as well
  • command based programing will be improved going forward

New control system
RobotRIO

  • Dual core
  • Ethernet , usb, can, spi,i 2c and serial
  • Pwm, servo, Digital and analog io
  • No breakout boards
  • Just one light plastic piece
  • In the middle is the custom electronics port. Use if want more analog inputs, to do something creative, etc

Power distribution board

  • 12v thru circuit breakers
  • Regulated supplies for RobotRIO, VRM and PCM
  • CAN interface for logging current, temperature and battery

Pneumatics control. Module (PCM)

  • 12v or 24v pneumatics – if need both, use two modules
  • Compressor confrol
  • CAN interface
  • 8 solnoid outputs

voltatge regulator module

  • Multi regulated 12v and 5v
  • Power for d-link radio, custom circuits and ip camera

Usb wireless adapater (asus dongle)

  • Connected to usb port on RoboRIO
  • Can be positioned for improved signal

Linux

  • Standard linux with real time extensions
  • Can do memory checking or anything else that linux can do

Tools

  • Dashboard
  • New inaging tool
  • Robot simulator

Dev tools

  • Everything based on opensource
  • Eclipse
  • Java 8 se – works on Windows, Linux and Mac
  • New c++ – current gcc compilers – works on Windows and Linux
  • Not sure if will support NetBeans in addition to Eclipse
  • Choose small memory profile version ofJava
  • Uses ant to build robot program

Library changes

Mostly compatible plus

  • Improved CAN support – sync or async
  • Units and measures – can specify moving to angle, driving fixed distance, running motor at some speed
  • Continuous inputs
  • Outputs
  • RobotDrive
  • Controller strategies
  • Can move stuff from crio forward but not new code backwards

Open source dev at WPI’s end

  • Usfirst.collab,net
  • They are using mavenand gi t
  • Gerrit based checkins

Reach goals

  • Gazebo simulator in beta test
  • Online curriculum with video lessons in short chunks

Nice quote

  • The whole point of robotics is to automate to make things easier for the driver

My impressions:

People came to hear about 2015. Brad spent more than half the time on things that exist now. He also entertained a lot of questions in that first half. Unsuprisingly he ran out of time before alot of content.  He sounded surprised that he ran out of time.  I look forward to at least reading the full deck when it goes up online after championships end.

[first] robotics and young women

This blog post is a mix of two sessions:

  1. “How robotics programs influence young women’s career choices”
  2. The second half of “FIRST Women in Science and Technology Panel”

For other posts about the 2014 FIRST conference, see the index page.  (written on my iPad; please excuse typos)

Stats about college students

  • Percent grads in CS has gone down over last 20 years
  • Physics and engeineering flatter curve
  • Less than twenty percent of all three after twenty years even with intervention programs

[Interesting because looks at all students not just the cs classroom percent]

Supportive relationships

  •   FRC has several levels of heroes – mentors, teachers, emcees at events and everythingi n between
  • Parents and mentors came up as dominant heroes

(Inputs) Per female undergrads, Frc is

  • Intensive 6 week collaborative jouney
  • Competing – smaller memory than other parts
  • Social cohesion and peer support – dominant memory if frc

Gender memories

  • Girls think differently. Can be positive or negative
  • Some boys treated girls poorly
  • Girls can get pushed aside on mixed gender teams. Often not part of design, build operations or drive team. May not be insiders on some teams.
  • Girls bond more over talking. Boys bond through proximity.
  • The undergrads who pursued STEM degrees tended to be more aware of gender stereotypes. Interesting.

Recommendations

  • Make game experiences more relevant and connected to real world challenges -national academy of enginnering recommends this as well as “changing the conversation”. Talk about solving problems, not math. Talk about what you worked on not how it happened. FLL does this. The game has ties to the real world such as Nature’s Fury.
  • Develop and provide mentor training – student decisions, not mentor decis ions [agree – I don’t make decisions for team).
  • Encourage female students to stretch (might need more pou shing than boys)
  • Caring mentors make good role models
  • Inspire by sharing stories and making career connections.

General

  •  Critical mass helps overcomes stereotype bias –
  • Tough to be only girl. Much easier than when 3 or 4
  • Develop programs tof oster social cohesion and peer support – change mental model for programs with few girls

Some of the Questions

  1. how important are female STEM mentors? A study on race showed helps but not a requirement to inspire
  2. sterotype threats – draw a scientist – get a white male in a lab coat
  3. re respect – female mentors can help atmosphere. But a male can tell the boys to back off too.

General points from afternoon session

  • Nobody know how to ride a bike without practice. Engineering is the same.
  • Can’t know if like something unless try it
  • Some of the best things in live are scary
  • Learn to understand how men think
  • Take in small roles and build up to larger ones
  • Don’t be shy. Approach people. Seek out a mentor. And pay it forward and mentor others. Most people will talk to you about their job for half an hour

Women only groups

  • Society of women engineers (SWE) – men can join too. Criteria is to support women in engineering. Consider it a support group
  • As a women, need groups to meet other women and network/promote each other. But also balance organizations belong to so networking with men too. Balance matters more as an adult
  • Focusing on women because filling a need. Saw problem where women were ready for jobs, didn’t have those skills
  • In 4th grade, girls interested in science and curious. By eight grade, it was gone

All girl teams

  • With same skill level, six year old boy thinks knows everything and six year old girl thinks knows nothing
  • Good to have a mix especially at older age. Boys can be insecure too.
  • More empowering to see a mxied gender teamw ith a female driver or captain
  • Men tend to be comfortable doingso mething when have 60% of knowledge. Girls f eel comfortable at 100%
  • We separate them by gender in summer camp analogy [this stops when they get to be teenagers though]
  • Dont want girls to think couldnt to as well on a mixed gender teams
  • A student spoke about when separted in school classes too, didn’t learn how to work with boys. Try to find common interests
  • People will lean towards a career where they see someone who looks like them. Whether race or gender. Becuase helps imagine self in role. (I identify with this. A lot of my role models are male. Be cause they are doing what I see myself doing)
  • Make sure kids still involved. A big middle ground between a pioneer and pure support. Can be a team player and do work on the team. Still seen as a pioneer though.

Watch how speak

  • We should put that on the robot vs do you think we should put that on the robot.
  • Unfortunate have to watch what say
  • Don’t end sentences with “right?” Sounds like not confident and asking permission

My impressions:

I liked the morning session. It was data driven and not just feel good “we should so something”. Or “girls and boys are the same”.

I have mixed feelings about girl only teams. Bronx sci ence does it well becausei t isnt a second tier team. But women do work with men in the real world. How long do you incubate and keep that separate? And I worry this doesn’t expose boys to working with strong tech females. Which becomes a problem later. I do thinki it is important to have a critical mass of girls so there are female friends on the team.

I struggle with the talking about gender. I want for it to not matter. I’m a developer. But she is right that talking matters. And I remember when one of our students commented about not wanting to be a “female” role model. And I was forced to write that it still matters that the girls can look up to her.  (For my thoughts on that topic, see this blog post.)

Looking around the room at the audience was interesting. It was a mix of pairs of girls and one girl from a team. And of course parents.

For the afternoon session, I wasn’t there long enough to have an impression. It attracted a more diverse crowd though.