YAGSL
  • Welcome to Yet Another Swerve Document
    • Resources
  • Overview
    • What we do
    • Our Features
      • Telemetry
      • Simulation
      • Lock Pose
      • Max Speed
      • Chassis Speed Discretization
      • Vision Odometry
      • Heading Correction
      • Auto-centering Modules
      • Offset Offloading
      • Cosine Compensation
      • Module Auto-synchronization
      • Angular Velocity Compensation
    • Changelog
    • Java API
    • Example Code
    • Config Generator
    • 💸Donations
    • 👕Merch
    • Discord
  • Fundamentals
    • Swerve Drive
    • Swerve Modules
  • Bringing up swerve
    • Preface
    • Swerve Information
    • Check your gyroscope
    • Check your motors
    • Creating your first configuration
  • Configuring YAGSL
    • Getting to know your robot
      • Gear Ratio
    • Dependency Installation
    • Configuration
      • Swerve Drive Configuration
      • Physical Properties Configuration
      • PIDF Properties Configuration
        • PIDF
      • Swerve Module Configuration
      • Controller Properties Configuration
      • Device Configuration
    • Code Setup
    • Standard Conversion Factors
    • How to tune PIDF
    • When to invert?
    • Flowcharts
    • The eight steps
    • Swerve Drive Drift
    • SparkMAX Common Problems
    • Verifying your Module Locations
    • Tuning out Drift
  • Devices
    • Gyroscope
      • NavX
      • Pigeon
      • Pigeon 2.0
      • ADXRS450
      • ADIS16448
      • ADIS16470
    • Motor Controllers
      • SparkMAX
      • SparkFlex
      • TalonFX
    • Absolute Encoders
  • Analytics and Debugging
    • FRC Web Components
    • Advantage Scope
  • Product Guides
    • Java API
    • PathPlanner
    • ❌Tuning PID with REV Hardware Client
    • ❌Drive Code
  • Legacy Documentation
Powered by GitBook
On this page
  • Tuner X
  • Documentation
  • YAGSL Checklist
  • Communication
  • Example swervedrive.json

Was this helpful?

Edit on GitHub
  1. Devices
  2. Gyroscope

Pigeon 2.0

PreviousPigeonNextADXRS450

Last updated 6 months ago

Was this helpful?

The Pigeon 2.0 is the next iteration of the Pigeon IMU by CTRE. This device is compatible with the CANivore.

Tuner X

This device can be upgraded via CTRE Tuner X.

Documentation

Pay close attention to the LED status code to help you debug this at any time. Remember that any settings changed in Tuner X for the Pigeon 2.0 are overwritten on startup of YAGSL.

YAGSL Checklist

Communication

Example swervedrive.json

The following is an example of swervedrive.json which sets up the Pigeon 2.0. Keep in mind that the Pigeon 2.0 is compatible with the CANivore so the canbus parameter actually works!

{
  "imu": {
    "type": ,
    "id": ,
    "canbus": 
  },
  "invertedIMU": ,
  "modules": [
    "frontleft.json",
    "frontright.json",
    "backleft.json",
    "backright.json"
  ]
}

This device communicated with the roboRIO over the CAN bus and can be paired with the that way it does not take up bandwidth on the roboRIO's CAN bus. To do this you need to set a name for the and use that as the canbus name in YAGSL.

CANivore
CANivore
Pigeon 2.0CTR Electronics
Phoenix Tuner XPhoenix 6
Pigeon 2.0Phoenix 6
Logo
Logo
Pigeon 2.0 CalibrationPhoenix 6
Logo
CANivore SetupPhoenix 6
Logo
Logo