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
  • Phoenix Tuner
  • Documentation
  • YAGSL Checklist
  • Communication
  • Example swervedrive.json

Was this helpful?

Edit on GitHub
  1. Devices
  2. Gyroscope

Pigeon

PreviousNavXNextPigeon 2.0

Last updated 1 year ago

Was this helpful?

This refers to the very first iteration of the CTRE Pigeon which is discontinued and only supported via Phoenix 5.

Phoenix Tuner

To communicate and update this device you need to install the Phoenix tuner.

Documentation

The Pigeon is only available in Phoenix 5 so the documentation is located below. You must include Phoenix 5 libraries in YAGSL partly because of this device.

YAGSL Checklist

Communication

After setting the CAN ID you set the id portion of the JSON configuration for the pigeon to the CAN ID. This device is not compatible with CANivore's thus the canbus option does not apply and should be "" or "rio" or null.

Example swervedrive.json

{
  "imu": {
    "type": "",
    "id": ,
    "canbus": 
  },
  "invertedIMU": true,
  "modules": [
    "frontleft.json",
    "frontright.json",
    "backleft.json",
    "backright.json"
  ]
}
Software
Phoenix Tuner is available under "Phoenix Framework for HERO C#"
Bring Up: Pigeon IMU
Guide to programming and configuring the Pigeon
Logo
Logo