TIL There's a builtin function for getting the alliance station from FMS

[AlexNeedsAName]

I found a function in the wpilib that tells you what alliance you're on!

import edu.wpi.first.wpilibj.hal.AllianceStationID;
import edu.wpi.first.wpilibj.hal.HAL;

AllianceStationID AlianceStation = HAL.getAllianceStation();
boolean redAlliance = false;
if(AlianceStation == AllianceStationID.Red1 || AlianceStation == AllianceStationID.Red2 || AlianceStation == AllianceStationID.Red3) redAlliance = true;

I figured this could be useful for some teams in auton since the field isn't symmetrical. I wish they would have made it more accessible, since FIRST doesn't even consider the HAL to be user facing.

[Thad House]

Originally Posted by AlexNeedsAName

I found a function in the wpilib that tells you what alliance you're on!

import edu.wpi.first.wpilibj.hal.AllianceStationID;
import edu.wpi.first.wpilibj.hal.HAL;

AllianceStationID AlianceStation = HAL.getAllianceStation();
boolean redAlliance = false;
if(AlianceStation == AllianceStationID.Red1 || AlianceStation == AllianceStationID.Red2 || AlianceStation == AllianceStationID.Red3) redAlliance = true;

I figured this could be useful for some teams in auton since the field isn't symmetrical. I wish they would have made it more accessible, since FIRST doesn't even consider the HAL to be user facing.

There are functions in the DriverStation class that wrap those functions. There is getAlliance and getStation that get the same information without needing the HAL.

[AlexNeedsAName]

Ok, thanks. I didn't realize that.

[CalTran]

Teams have used it before to control their underglow. But auto programming is a good use for it too.

[euhlmann]

Originally Posted by CalTran

Teams have used it before to control their underglow. But auto programming is a good use for it too.

More than a "good use" considering the field isn't rotationally symmetric this year