Note it may take up to three business days for the latest Tuner X to become available on Windows Store/Google Play Store.

Current latest versions

• CANcoder (v5) - 22.0.1.2
• CANcoder (v6) - 23.10.1.0
• CANcoder vH (v5) - 22.0.2.1
• CANcoder vH (v6) - 23.10.1.0
• CANdle - 22.3.1.0
• CANivore - 23.2.4.0
• Phoenix Diagnostic Server - 2023.1.0
• Phoenix Installer - 5.30.4.2
• Phoenix-5 - 5.30.4
• Phoenix-6/Libs - 23.1.0
• Pigeon2 (v5) - 22.6.4.1
• Pigeon2 (v6) - 23.10.1.0
• Talon FX (v5) - 22.1.1.0
• Talon FX (v6) - 23.10.1.0
• Tuner X - 2023.3.1.0
• Tuner v1 - 1.9.4.1
• canivore-usb - 1.11

2023/06/02

Fixed 2023/06/02

• (CANivore: 23.2.4.0) Improved USB reconnects for CANivores manufactured after May 1, 2023.

2023/05/25

Fixed 2023/05/25

• (Phoenix 6 Firmware: 23.10.1.0) Fixes issue reported in 23.10.0.1. Fixed configs not being persistent.

2023/05/18

Added 2023/05/18

• (CANcoder (v6): 23.10.0.1) Added support for the free Phoenix 6 API.
• (CANcoder (v6): 23.10.0.1) Improved CAN bus utilization on CAN 2.0.
• (Phoenix-6: 23.1.0) Added an AddYaw method to the Pigeon 2 SimState object.
• (Phoenix-6: 23.1.0) Moved the phoenixpro folders, packages, and namespaces to phoenix6. The phoenixpro namespace is deprecated for removal in 2024.
• (Phoenix-6: 23.1.0) Renamed BaseStatusSignalValue and StatusSignalValue to BaseStatusSignal and StatusSignal. BaseStatusSignalValue and StatusSignalValue are deprecated for removal in 2024.
• (Phoenix-6: 23.1.0) Improved the default control frame update frequency for follower and neutral controls.
• (Pigeon2 (v6): 23.10.0.1) Added support for the free Phoenix 6 API.
• (Pigeon2 (v6): 23.10.0.1) Improved CAN bus utilization on CAN 2.0.
• (Talon FX (v6): 23.10.0.1) Added support for the free Phoenix 6 API.
• (Talon FX (v6): 23.10.0.1) Added faults for using Pro features while unlicensed.
• (Talon FX (v6): 23.10.0.1) Improved CAN bus utilization on CAN 2.0.
• (Talon FX (v6): 23.10.0.1) While disabled, the Talon FX beeps when configuring, blinking, and setting device name and ID.
• (Tuner X: 2023.3.1.0) Added support for Phoenix 6.
• (Tuner X: 2023.3.1.0) Improved the Plot page enable/disable button.
• (Tuner X: 2023.3.1.0) Automatically refresh device configs and self test when entering the device view page.

Fixed 2023/05/18

• (Phoenix-6: 23.1.0) Fixes issue reported in 23.0.12. In Java, improved the performance of the JNI layer.
• (Phoenix-6: 23.1.0) Moved SetUpdateFrequency from StatusSignal to BaseStatusSignal.
• (Tuner X: 2023.3.1.0) Fixed refreshing configs expanding user-collapsed config groups.

Known Issues 2023/05/18

• (Phoenix 6 Firmware: 23.10.0.1) Fixed by 23.10.1.0. Configs are not saved persistently. This is a bug with this specific off-season firmware version. Teams that apply all configs to their devices in robotInit are generally unaffected. We recommend teams update to the latest firmware version. Discovered by Internal Testing

2023/04/27

Fixed 2023/04/27

• (canivore-usb: 1.11) Fixes issue reported in 1.10. Cannot install the canivore-usb kernel module on ARM64 systems running Ubuntu 22.04 or newer.

2023/04/26

Fixed 2023/04/26

• (Phoenix-Libs: 23.0.13) Add support for installation of Phoenix Pro on non-FRC Debian-based systems using APT.
• (canivore-usb: 1.10) Fixes issue reported in 1.9. Cannot install the canivore-usb kernel module on Linux kernel versions 5.17.0+.

Known Issues 2023/04/26

• (canivore-usb: 1.10) Fixed by 1.11. Cannot install the canivore-usb kernel module on ARM64 systems running Ubuntu 22.04 or newer. This is caused by a breaking ABI change on Linux ARM64 systems. Discovered by Customer Email

2023/04/12

Fixed 2023/04/12

• (Phoenix-Libs: 23.0.12) Fixes issue reported in 23.0.11. Fixed issue: Control framing may be incorrect under a very specific circumstance.
• (Talon FX (Pro): 23.6.10.1) Fixes issue reported in 23.6.5.0. Fixed issue: If Motion Magic is started while rotor is in motion and jerk config is nonzero, the motion profile may have a discontinuity near the end.
• (Talon FX (Pro): 23.6.10.1) Fixes issue reported in 2023.2.0.0. Motion Magic now supports modifying jerk and acceleration during motion without introducing profile discontinuities.
• (Talon FX (Pro): 23.6.10.1) Fix Motion Magic start of profile under very specific circumstances: Jerk config is small and non-zero, and previous profile must be truncated due to a late change in final target position.
• (Tuner X: 2023.2.2.0) Fixes issue reported in 2023.2.0.0. Fixed the Sensor Range config enum for Pro CANcoder.
• (Tuner X: 2023.2.2.0) Fixes issue reported in 2023.2.0.0. Fixed deploying temp diagnostic server to a roboRIO 2 that had its team number set by the WPILib roboRIO Team Number Setter.

Known Issues 2023/04/12

• (Phoenix-5: 5.30.4) Cannot construct a device on a CANivore using the CANivore serial number. Users should instead use the configured CANivore name. Discovered by Internal Testing
• (Phoenix-Pro: 23.0.12) Fixed by 23.1.0. In Java, calling refresh() on many StatusSignalValues may cause loop overruns due to the JNI layer. The workaround is to pass all the signals into waitForAll() with a timeout of 0. This performs a bulk refresh of the signals while only paying the cost of JNI once. Discovered by Customer Email
• (Phoenix-Pro: 23.0.12) In simulation, the Talon FX rotor position in the WPILib simulation GUI may be incorrect. The reported rotor position may not take into account user calls to setRotorPosition() on the regular device object. This does not affect the raw rotor position or any of API. Discovered by Internal Testing
• (canivore-usb: 1.9) Fixed by 1.10. Cannot install the canivore-usb kernel module on Linux kernel versions 5.17.0+. This affects Ubuntu 22.04+ and certain Debian Bullseye installations. As a workaround, users can switch to Ubuntu 20.04 or an older version of Debian Bullseye. Discovered by Internal Testing
• (canivore-usb: 1.9) On the roboRIO, CPU spikes are observed every 30 seconds after boot. This is caused by an issue in the roboRIO image and affects all SocketCAN adapters. The workaround is to cycle the CANivore USB connection after the robot program first starts up after boot. This can be done programmatically in robotInit() by running caniv --any --reset using the Linux system() API or similar. Discovered by Customer Email

2023/03/29

Added 2023/03/29

• (CANcoder (Pro): 23.1.3.0) Robustness improvements for CANivore licensing when CAN bus wiring is intermittently lost.
• (Pigeon2 (Pro): 23.1.6.0) Robustness improvements for CANivore licensing when CAN bus wiring is intermittently lost.
• (Talon FX (Pro): 23.6.9.0) Robustness improvements for CANivore licensing when CAN bus wiring is intermittently lost.

2023/03/21

Known Issues 2023/03/21

• (CANcoder vH: 20.1.0.0) Devices may disappear in Tuner under a specific circumstance. This issue may present itself if all the following are true: A device is being field-upgraded, there is a CANcoder vH on the bus, that CANcoder vH has ship firmware 20.1.0.0. If all the requirements are met, then devices may disappear from Tuner once the field-upgrade is finished. The process to resolve this is to do the following: Power cycle CANcoder vHs with ship firmware, Flash CANcoder vH with latest firmware, Repeat until every CANcoder vH is updated. This only affects Tuner, this does not affect API. Discovered by Internal Testing

2023/03/17

Added 2023/03/17

• (CANivore: 23.2.3.1) Improved USB connectivity.
• (CANivore: 23.2.3.1) Added support for multiple CANivores on the same CAN bus - Several teams have asked for multiple CANivore support on the same CAN bus, one CANivore on the roboRIO and one CANivore on an external Linux system. For this to work correctly, one of the CANivores must be named “enable-only”. Otherwise, CAN bus errors may occur due to same-frame-ID transmissions from both CANivores. Note that this merely prevents CAN bus errors. It is not required for the roboRIO FRC enable to reach the CAN bus (which is handled by Phoenix). It also does not prevent the roboRIO FRC enable from reaching the CAN bus (which is handled by Phoenix). There is no influence on the robot enable method. Note that teams should ensure diagnostic server only runs on a single robot controller (either just the roboRIO or just the external Linux system). Consult API documentation for instructions on how to disable diagnostics for such systems (typically routine is called setPhoenixDiagnosticsStartTime or similar).
• (Pigeon2 (Pro): 23.1.4.1) Pigeon 2 will not use compass if it is not compass-calibrated regardless of config state.
• (Pigeon2 (v5): 22.6.4.1) Pigeon 2 will not use compass if it is not compass-calibrated regardless of config state.
• (Talon FX (Pro): 23.6.8.2) Added current threshold and current time threshold to supply configs.

Fixed 2023/03/17

• (Phoenix-Libs: 23.0.11) Fixes issue reported in 23.0.10. Remote CANcoder and Fused CANcoder are now supported in simulation.
• (Phoenix-Libs: 23.0.11) Fixes issue reported in 23.0.0-beta-5. Phoenix Pro simulation now supports supply, stator, and torque current. Simulation uses the rotor velocity and applied output to simulate currents.
• (Pigeon2 (Pro): 23.1.4.1) Roll’s range is now [-180, +180) degrees, up from [-90, +90) degrees. This allows teams to use the roll of the Pigeon 2 for mechanisms such as an arm. Teams that have their Pigeon 2’s mounted upside down may want to mount-calibrate their Pigeon 2 to zero out their roll, as it will now correctly report upside-down (+-180 degrees).

Known Issues 2023/03/17

• (Phoenix-Libs: 23.0.11) Fixed by 23.0.12. Control framing may be incorrect under a very specific circumstance. If the CANivore USB disconnects, there is a change in a control parameter, and the CANivore USB reconnects, the new control parameter may not apply. Discovered by Internal Testing

2023/03/01

Fixed 2023/03/01

• (Phoenix-Libs: 23.0.10) The waitForAll() routine may not set StatusCode to OK if timeout is zero. Users may want to use a zero timeout to refresh many signals at once instead of calling refresh() on each signal to reduce call times.
• (Phoenix-Libs: 23.0.10) The waitForAll() routine does not report an error to the driver station despite returning a nonzero StatusCode.
• (Phoenix-Libs: 23.0.10) The C++ WaitForAll() routine now has an override that takes a vector reference instead of an initializer_list.
• (Phoenix-Libs: 23.0.10) The Java waitForAll() routine does not return the StatusCode.
• (Phoenix-Libs: 23.0.10) Fixes issue reported in 22.2.0. The Java waitForAll() routine sets all StatusCode fields of every signal to a common StatusCode when an erroneous condition is detected, instead of only updating the relevant signals.
• (Phoenix-Libs: 23.0.10) Various updates to API documentation including Motion Magic and FusedCANcoder.
• (Talon FX (Pro): 23.6.7.0) Added performance improvement when Talon FX is at or near stall and supply voltage is near brownout threshold.

Known Issues 2023/03/01

• (Phoenix-Libs: 23.0.10) Fixed by 23.0.11. RemoteCANcoder and FusedCANcoder are not supported in simulation. RemoteCANcoder and FusedCANcoder are not supported in simulation. Workaround is to use RotorSensor when in simulation and simulate using the TalonFXSimState. Discovered by Team 3015

2023/02/27

Fixed 2023/02/27

• (Phoenix-Libs: 23.0.9) Java refresh() calls are no longer slower if device is not present on CAN bus.

2023/02/22

Fixed 2023/02/22

• (Talon FX (Pro): 23.6.6.1) Fixes hard/soft limits when closed looping and open looping under certain circumstances.

2023/02/17

Added 2023/02/17

• (Phoenix Diagnostic Server: 2023.1.0) Add support for plotting on Pro devices.
• (Phoenix Installer: 5.30.4.2) Updated Tuner v1 & Phoenix Libs with newest versions.
• (Talon FX (Pro): 23.6.5.0) Added temperatures to self test.
• (Tuner X: 2023.2.0.0) Fixes issue reported in 2023.1.0.0. Added plotting support for Phoenix Pro devices.
• (Tuner v1: 1.9.4.1) Updated temporary diagnostic server to latest version.

Fixed 2023/02/17

• (Phoenix-Libs: 23.0.8) Simulation derivative output now behaves as expected.
• (Talon FX (Pro): 23.6.5.0) Fixes issue reported in 23.6.4.1. Motion Magic movements with a velocity above 80 rotations per second now report the correct velocity.
• (Talon FX (Pro): 23.6.5.0) Fixes issue reported in 23.6.4.1. Motion Magic movements with a cruise velocity of exactly 100 rotations per second now behave as expected.
• (Talon FX (Pro): 23.6.5.0) Added simultaneous-orange blink pattern that was missing in firmware.

Known Issues 2023/02/17

• (Talon FX (Pro): 23.6.5.0) Fixed by 23.6.10.1. Discontinuity in motion magic under specific circumstance. If motion magic is started while rotor is in motion and jerk config is nonzero, the motion profile may have a discontinuity near the end. Discovered by Internal Testing
• (Tuner X: 2023.2.0.0) Tuner X may increase the roboRIO CPU load. If Tuner X has a live connection to the roboRIO, the roboRIO CPU may experience higher CPU load as reported in the Driver Station. User can workaround this by closing Tuner X when roboRIO is performing CPU intensive operations, or using Tuner v1 instead. Discovered by Internal Testing
• (Tuner X: 2023.2.0.0) Licensing fails with a CTRE_DI_FeatureNotSupported if caniv is too old. If Kickoff version of Tuner v1 was used to interact with CANivore, Tuner v1 places a too-old version of caniv CLI. This prevents CANivore licensing to occur after license-activation. When this issue occurs the bottom of Tuner X will show “Caniv Version: 1.0.5.0”. Workaround is to use latest Tuner v1 (connected to roboRIO) and poll for CANivores (which will auto install correct version of caniv). Or alternatively roboRIO can be reimaged with latest image, which will update the caniv CLI. We recommend CANivore users avoid using the Kickoff version of Tuner v1 (version 1.9.3.0). Discovered by Customer Email
• (Tuner X: 2023.2.0.0) Fixed by 2023.2.2.0. The Pro CANcoder Sensor Range is displayed as a number. The Pro CANcoder Sensor Range is erroneously displayed as a number instead of text. Refer to the API documentation for the possible enumerated values. Discovered by Internal Testing
• (Tuner X: 2023.2.0.0) Fixed by 2023.2.2.0. Tuner cannot deploy temp diagnostic server to a roboRIO 2 that had its team number set by the WPILib roboRIO Team Number Setter. This is caused by a bug in the WPILib roboRIO Team Number Setter. Workaround is to use the latest Tuner X or re-set the team number using the roboRIO Imaging Tool. Discovered by Team 8728
• (Tuner v1: 1.9.4.1) The Pro CANcoder Sensor Range is displayed as a number. The Pro CANcoder Sensor Range is erroneously displayed as a number instead of text. Refer to the API documentation for the possible enumerated values. Discovered by Internal Testing
• (Tuner v1: 1.9.4.1) Tuner cannot deploy temp diagnostic server to a roboRIO 2 that had its team number set by the WPILib roboRIO Team Number Setter. This is caused by a bug in the WPILib roboRIO Team Number Setter. Workaround is to use the latest Tuner X or re-set the team number using the roboRIO Imaging Tool. Discovered by Team 8728

2023/02/10

Added 2023/02/10

• (CANivore: 23.2.1.0) Added support for Pigeon 2 workaround.
• (Phoenix-Libs: 23.0.7) Update Simulation with latest changes to Talon FX Firmware.
• (Tuner X: 2023.1.5.0) Added info banner for workaround with Pigeon 2s.
• (Tuner X: 2023.1.5.0) Added Settings button to execute Pigeon 2 workaround.

Fixed 2023/02/10

• (Phoenix-Libs: 23.0.7) Implemented workaround for Pigeon 2s built in September of 2022. See blog post at https://store.ctr-electronics.com/blog/pigeon2-2023-errata/ for details.
• (Phoenix-Libs: 23.0.7) Fixes issue where applying configs when connected over local canivore diagnostic server would time out even though the apply was successful.
• (Talon FX (Pro): 23.6.4.1) Fixes issue reported in 23.6.3.2. Setting position while invert is true now works as expected.
• (Tuner X: 2023.1.5.0) Self test for v5 devices is monospace.
• (Tuner X: 2023.1.5.0) Fixes bug that prevented control from working after switching from v5 firmware to Pro firmware or visa versa without exiting the device details page.

Known Issues 2023/02/10

• (CANivore: 23.2.1.0) Silicon vendor has announced a recent silicon errata that may prevent the CANivore from powering up. The workaround is to ensure CANivore powers up completely on robot power up by checking LEDs or verifying device connectivity through the Driver Station. Silicon errata suggests this affects a very small number of CANivores. CTRE is working with silicon vendor for a complete solution. Discovered by Supplier
• (Talon FX (Pro): 23.6.4.1) Fused CANcoder out of sync sticky fault occurs on first configure of FusedCANcoder feedback source. The first time a Talon FX is configured to use a FusedCANcoder feedback source, the Fused Sensor Out Of Sync sticky fault trips. To workaround this, clear the sticky faults after initial configure of FusedCANcoder feedback source. Discovered by Internal Testing
• (Talon FX (Pro): 23.6.4.1) Fixed by 23.6.5.0. Motion Magic movements with a velocity above 80 rotations per second will report up to 80 rotations per second. Any motion magic movements where the velocity exceeds 80 rotations per second positive or negative will cap their reported velocity to 80 rotations per second. This may be worked around by setting the sensor to mechanism ratio so that the cruise velocity of the mechanism is under 80 rotations per second. Discovered by Internal Testing
• (Talon FX (Pro): 23.6.4.1) Fixed by 23.6.5.0. Cruise Velocity of exactly 100 rotations per second may cause Motion Magic to jump at end of motion. A cruise velocity of exactly 100 rotations per second may cause the Motion Magic profiler to undershoot its position, causing it to jump once it reaches the target position. The workaround is to specify a cruise velocity slightly over or under 100 rotations per second, such as 101 rotations per second. Discovered by Internal Testing

2023/02/06

Fixed 2023/02/06

• (Talon FX (Pro): 23.6.3.2) Fixes issue reported in 23.6.2.0. Setting rotor position with internal feedback sensor no longer offsets position when later configured for Fused CANcoder.
• (Talon FX (Pro): 23.6.3.2) Fixes bug where kD had no effect. Teams should revisit their kD constant to ensure it is not too high for their application.

Known Issues 2023/02/06

• (Talon FX (Pro): 23.6.3.2) Fixed by 23.6.4.1. Set rotor position is negative when invert is on. When setting the rotor position with invert set to true, the reported position with be negative of what was set. Discovered by Customer Email

2023/02/02

Added 2023/02/02

• (Pigeon2 (v5): 22.6.3.1) Further improved CAN robustness during use in CAN 2.0.

Fixed 2023/02/02

• (Pigeon2 (Pro): 23.1.2.1) Fixes issue reported in 22.99.20.0. LEDs will go simultaneous solid-orange for a second when the Pigeon2 boots.
• (Pigeon2 (Pro): 23.1.2.1) Fixes issue reported in 22.99.20.0. Certain configurations of CAN FD bus with Pigeon 2s manufactured after September 2022 no longer cause red blips.
• (Pigeon2 (v5): 22.6.3.1) Fixes issue reported in 22.6.2.2. Certain configurations of CAN FD bus with Pigeon 2s manufactured after September 2022 no longer cause red blips.

Known Issues 2023/02/02

• (Pigeon2 (Pro): 23.1.2.1) Pigeon 2 may report magnetometer fault. Pigeon 2 may occasionally report a magnetometer fault in the self test. This will not affect performance of the Pigeon 2. Discovered by Internal Testing
• (Pigeon2 (Pro): 23.1.2.1) Pigeon 2 may report accelerometer fault. Pigeon 2 may occasionally report an accelerometer fault in the self test if it moves during startup. This will not affect performance of the Pigeon 2 as long these faults do not occur all the time. Discovered by Internal Testing
• (Pigeon2 (v5): 22.6.3.1) Pigeon 2 may report magnetometer fault. Pigeon 2 may occasionally report a magnetometer fault in the self test. This will not affect performance of the Pigeon 2. Discovered by Internal Testing
• (Pigeon2 (v5): 22.6.3.1) Pigeon 2 may report accelerometer fault. Pigeon 2 may occasionally report an accelerometer fault in the self test if it moves during startup. This will not affect performance of the Pigeon 2 as long these faults do not occur all the time. Discovered by Internal Testing

2023/01/30

Fixed 2023/01/30

• (Talon FX (Pro): 23.6.2.0) Fixes issue reported in 23.6.0.2. Inverted motor no longer breaks closed looping.

Known Issues 2023/01/30

• (Pigeon2 (v5): 22.6.2.2) Fixed by 22.6.3.1. Certain CAN FD configurations with Pigeon2 can cause red blips. Certain configurations of Pigeon2 manufactured after September 2022 on a CAN FD bus may cause red blips. Discovered by Customer Email
• (Talon FX (Pro): 23.6.2.0) Fixed by 23.6.3.2. Setting Rotor Position with Internal Feedback Sensor can offset position when later configured for Fused CANcoder. If the user sets rotor position while the internal sensor is selected as the feedback sensor, and later changes the feedback sensor to be Fused CANcoder, the reported position will be offset. Discovered by Internal Testing

2023/01/26

Added 2023/01/26

• (Talon FX (Pro): 23.6.0.2) Added a new remote sensor type “FusedCANcoder” that will fuse Talon’s rotor and a remote CANcoder to produce an absolute sensor source that updates at 1KHz. Note when using CAN 2.0 - fusion only occurs when mechanism is still (CANFD/CANivore is required for continuous fusion). Note RotorToSensor must be configured for feature to function as expected.

Fixed 2023/01/26

• (CANdle: 22.3.1.0) Removed a debug frame.
• (Phoenix-5: 5.30.4) Fixes issue reported in 5.30.3. Calling CANdle’s SetLED directly after ClearAnimation works as expected.
• (Phoenix-Libs: 23.0.5) Fixes issue reported in 23.0.4. Pigeon 2 self test now uses proper template.
• (Phoenix-Libs: 23.0.5) Fixes issue reported in 23.0.4. Fixed issue where certain devices (including 2015 Talon SRXs) required two firmware upgrades to succeed.
• (Talon FX (Pro): 23.6.0.2) Fixes issue reported in 23.5.0.0. Motion magic now adheres to the continuous wrap config.
• (Tuner X: 2023.1.4.0) PCM and CANifier now have icons for Tuner X.
• (Tuner X: 2023.1.4.0) Tuner X can now deploy required libraries for Phoenix LabVIEW.

Known Issues 2023/01/26

• (Talon FX (Pro): 23.6.0.2) Fixed by 23.6.2.0. PID and Soft Limit does not behave as expected if motor invert is true. PID and Soft Limit does not behave as expected if motor invert is true. Discovered by Customer Email
• (Tuner X: 2023.1.4.0) Control over Tuner X may timeout in certain circumstances. If Tuner X is left on for a while (typically over 1 day) and the user tries to control a device through Tuner X, Tuner X may time out the control. If this is observed, cleanly restart Tuner X. Discovered by Internal Testing

2023/01/23

Fixed 2023/01/23

• (Tuner X: 2023.1.3.0) Fixes issue reported in 2023.0.2.0. Joystick input doesn’t change focus any more.
• (Tuner X: 2023.1.3.0) Fixes issue reported in 2023.1.1.0. Device history page no longer crashes under certain circumstances.

2023/01/16

Fixed 2023/01/16

• (Phoenix-Libs: 23.0.4) Fixes issue reported in 2023.0.1. caniv calls on windows now work as expected.
• (Phoenix-Pro: 23.0.3) Fixes issue reported in 23.0.2. Java setters now work as expected.

Known Issues 2023/01/16

• (Phoenix-5: 5.30.3) Fixed by 5.30.4. Calling SetLED directly after a ClearAnimation call will not set LEDs properly. If the user performs a SetLED directly after a ClearAnimation, the SetLED call will not take place. If instead the SetLED happens some time after the ClearAnimation, it will behave as expected. Discovered by Team 971
• (Phoenix-Libs: 23.0.4) Fixed by 23.0.5. Pigeon 2 Self Test uses Pigeon IMU (Pigeon 1) template. When performing a self-test snapshot on a Pigeon 2, the reported self test follows Pigeon IMU’s format. This causes the reported self-test to indicate that the Pigeon 2 is in BootTareGyroAccel calibration mode when it is not. Users can ignore the Pigeon State, Last CAL mode, Last CAL err, and temperature compensation values. Discovered by Team 4201
• (Phoenix-Libs: 23.0.4) Fixed by 23.0.5. First firmware flash fails on older products. Doing a field-upgrade on older products will cause it to fail the first time, leaving the device in bootloader. A subsequent field-upgrade will successfully flash the device. The current workaround is to flash older devices twice. Discovered by Team 2075
• (Tuner X: 2023.1.1.0) Fixed by 2023.1.3.0. Device History page may crash under certain circumstances. Under a specific circumstance, the Device History page may crash on selection. This has been root-caused and will be addressed in the next release. A potential workaround is to delete either the CachedCANDevices.json or CachedCANivores.json file under the application cache directory. Discovered by Internal Testing

2023/01/12

Added 2023/01/12

• (Phoenix-Pro: 23.0.2) Add basic latency compensation helper method to simplify the use of latency compensation.
• (Talon FX (Pro): 23.5.0.0) Added a continuous wrap closed-loop mode for mechanisms that continuously wrap around themselves. This is useful for mechanisms such as swerve, as it allows the device to find the shortest path to reach the target within 1 rotation.

Fixed 2023/01/12

• (Phoenix Diagnostic Server: 2023.0.1) Fixes issue reported in 2023.0.0. Control tab works with temporary diagnostic server.
• (Phoenix Installer: 5.30.3.0) Phoenix Pro device Simulation Headers are now included for offline install.
• (Phoenix-5: 5.30.3) Fixes issue reported in 5.30.2. CANdle setLED call works as expected.
• (Phoenix-Pro: 23.0.2) Removed Units headers from the WPI header export. Users using units will now only use the WPI-included headers.
• (Talon FX (Pro): 23.5.0.0) Fixes issue reported in 23.4.0.3. Set Position on Limit works.
• (Talon FX (Pro): 23.5.0.0) Fixes issue reported in 23.4.0.3. Fixed motion magic discontinuity near end of trajectory.
• (Tuner X: 2023.1.1.0) Fixes issue reported in 2023.1.0.0. User accounts with spaces in the name will interact with CANivore as expected.
• (Tuner v1: 1.9.3.0) Fixes issue reported in 1.9.2.1. Tuner v1 interacting with CANivores no longer prevent them from being licensed in Tuner X.

Known Issues 2023/01/12

• (Phoenix Diagnostic Server: 2023.0.1) Fixed by 23.0.4. caniv calls on windows don’t work with setname or update firmware. When using caniv on windows, setting the name or updating firmware does not work. Discovered by Internal Testing
• (Phoenix-Pro: 23.0.2) Fixed by 23.0.3. Java setters always set with a 0 value. Using a setter in java, such as setPosition or setYaw, will always apply a value of 0. Discovered by Teams 4414 and 973
• (Talon FX (Pro): 23.5.0.0) Fixed by 23.6.0.2. Motion Magic does not adhere to the Continuous Wrap config. If the Talon FX is using a Motion Magic config, it will not use the Continuous Wrap config. Users that want to use the Continuous Wrap config should instead use Position Closed Loop. Discovered by Internal Testing

2023/01/06

Added 2023/01/06

• (CANcoder (Pro): 23.1.1.3) Cut for 2023 season.
• (Phoenix-Pro: 23.0.1) Add additional configs for new Talon FX features.
• (Talon FX (Pro): 23.4.0.3) Add additional configs.
• (Tuner X: 2023.1.0.0) Added a Copy to Clipboard button to the Self Test page.
• (Tuner X: 2023.1.0.0) Added support for selecting the firmware version in the Batch Upgrade page.
• (Tuner X: 2023.1.0.0) Added a button in the Settings page to manually download the latest firmware files.

Fixed 2023/01/06

• (Phoenix-Pro: 23.0.1) Fixes issue reported in 23.0.0-beta-7. Improved robustness of Talon FX Self Test.
• (Tuner X: 2023.1.0.0) The Configs page correctly handles inputting negative numbers and exponential notation.
• (Tuner X: 2023.1.0.0) Improved the error message when attempting to apply configs before an initial refresh.
• (Tuner X: 2023.1.0.0) Fixed the behavior of the device view page launched from the arrow button on the device list page.
• (Tuner X: 2023.1.0.0) Expanded the height of the control parameter scroll view to the height of the window.
• (Tuner X: 2023.1.0.0) Field upgrading a device in the device view page correctly updates the available controls on the Control page.
• (Tuner X: 2023.1.0.0) Fixed an issue where the CANivore ESP32 Enable and CAN Bus Termination switches would occasionally fail to apply.
• (Tuner X: 2023.1.0.0) Improved the robustness of automatically downloading the latest online firmware files.
• (Tuner X: 2023.1.0.0) Fixed an issue where the CRF dropdown may occasionally contain duplicate firmware versions.

Known Issues 2023/01/06

• (Phoenix Diagnostic Server: 2023.0.0) Fixed by 2023.0.1. Control tab does not work with Temporary Diagnostic server. The control tab in Phoenix Tuner does not function as expected while connected to a temporary diagnostic server. This can be worked around by deploying an application that uses Phoenix. Discovered by Internal Testing
• (Phoenix-5: 5.30.2) Fixed by 5.30.3. CANdle setLED call is not always applied. When using the setLED method in CANdle, the call is not always applied. This does not affect animations, only the setLED call. This will be fixed in a future API update. Discovered by Team 4152
• (Phoenix-Pro: 23.0.1) C++ Static-initialization of a TalonFX object results in lock-up. If a TalonFX object is statically initialized before WPILib’s resources are initialized, the application will lock up. To workaround, initialize the TalonFX object inside the robot header file. Discovered by Internal Testing
• (Talon FX (Pro): 23.4.0.3) Fixed by 23.5.0.0. Set Position on Limit does not work. The Configurations for auto-setting position on limit forward/reverse has no effect when using the kickoff firmware. This does not affect disabling the motor when limit forward/reverse is tripped. Discovered by Internal Testing
• (Talon FX (Pro): 23.4.0.3) Fixed by 23.5.0.0. Motion Magic target position discontinuity near end of trajectory (set position jumps) if jerk value is low. When performing a Motion Magic across a longer period with a low jerk value, the device will jump to the final position instead of smoothly transition to it. This does not occur with larger jerk values or with a jerk value of 0 (disabled). This is due to the target velocity curve reaching zero slightly too early. Discovered by Internal Testing
• (Talon FX (Pro): 23.4.0.3) Current Limiting’s accuracy is not within expectations. There is roughly a 600mA difference between what the Device attempts to limit to and what it does limit to. Discovered by Internal Testing
• (Talon FX (Pro): 23.4.0.3) Talon FX Pro Firmware does not support PWM input. Driving a Talon FX running Phoenix Pro firmware with an PWM input does not work. Users must use CAN to control a Phoenix Pro Talon FX. Users that want to use PWM must use Phoenix 5 firmware. Discovered by Internal Testing
• (Tuner X: 2023.1.0.0) Fixed by 2023.2.0.0. The Plot page is not supported for Phoenix Pro devices. Tuner X currently only supports plotting for Phoenix v5 devices. A future release will provide plotting for Phoenix Pro devices. Discovered by Internal Testing
• (Tuner X: 2023.1.0.0) Fixed by 2023.1.1.0. Windows account names with spaces cannot interact with CANivore when connected via localhost. Phoenix Tuner/Diagnostics is not able to properly interface with the CANivore while a space exists in the windows account name. This will be fixed in a future Phoenix release. Discovered by Team 254
• (Tuner v1: 1.9.2.1) Self test does not work for Phoenix Pro devices on Tuner v1. Performing a self-test snapshot on a Phoenix Pro device results in the message “Self-Test on Phoenix PRO devices require using Tuner X.”. Use Tuner X for self-testing Phoenix Pro devices. Discovered by Internal Testing
• (Tuner v1: 1.9.2.1) Fixed by 1.9.3.0. Tuner v1 interacting with CANivores will prevent them from being licensed in Tuner X. If a user interacts with a CANivore in Tuner v1, they will deploy a caniv binary that is too old and doesn’t support licensing. Discovered by Team 6036

2022/12/20

Added 2022/12/20

• (Tuner X: 2023.0.2.0) Updated the device card colors to be more easily distinguishable. Check out the Phoenix Pro documentation for more information.
• (Tuner X: 2023.0.2.0) Improved the layout of the buttons on the Config page.
• (Tuner X: 2023.0.2.0) Added support for licensing devices while disconnected from a robot.

Fixed 2022/12/20

• (Phoenix-Pro: 23.0.0-beta-7) Fixes issue reported in 23.0.0-beta-5. In Phoenix Pro TalonFX simulation, following now works.
• (Phoenix-Pro: 23.0.0-beta-7) Fixes issue reported in 23.0.0-beta-5. In Phoenix Pro Java, Pigeon 2 simulated supply voltage now shows the correct value in the WPILib simulation GUI.
• (Tuner X: 2023.0.2.0) Fixes issue reported in 2023.0.1.0. The Device list is no longer blank when not connected to internet.
• (Tuner X: 2023.0.2.0) Fixed UI unresponsiveness when canceling a batch upgrade command.
• (Tuner X: 2023.0.2.0) Fixed deploying the temporary diagnostic server to the roboRIO.
• (Tuner X: 2023.0.2.0) Fixed an issue where the Self Test page shows a black screen after a refresh.

Known Issues 2022/12/20

• (Phoenix-Pro: 23.0.0-beta-7) Fixed by 23.0.1. Talon FX Self Test could occasionally fail. Occasionally when performing a self-test on a Talon FX, the self test will report a failure with “InvalidSignal”. Discovered by Internal Testing
• (Tuner X: 2023.0.2.0) Fixed by 2023.1.3.0. XInput Joystick input causes focus to change. Due to a limitation in Windows, XInput devices such as joysticks may cause the GUI’s focus to change when moving the joystick. This can be an issue for self test snapshot and configs page, since the focus will prevent the user from clicking the buttons. Discovered by Internal Testing

2022/12/09

Added 2022/12/09

• (ProFirmware: 23.1.0.6) Improved the latency of CANivore Timesync frames.
• (Talon FX (Pro): 23.3.0.6) Added additional FOC and closed-loop control requests.
• (Talon FX (Pro): 23.3.0.6) Reduced CAN bus utilization on CAN FD networks.

Fixed 2022/12/09

• (Phoenix-Pro: 23.0.0-beta-6) Improved the accuracy of the System timestamp source.

2022/12/03

Added 2022/12/03

• (Phoenix-Pro: 23.0.0-beta-5) Control Requests have default parameters where it makes sense.
• (Phoenix-Pro: 23.0.0-beta-5) Added with* methods to Control requests to modify the data through method-chaining.
• (Phoenix-Pro: 23.0.0-beta-5) Added Phoenix Pro Device Simulation Support.
• (Phoenix-Pro: 23.0.0-beta-5) Added TalonFX Duty Cycle FOC control.
• (ProFirmware: 23.1.0.0) Devices and CANivore support CAN bus licensing.
• (Tuner X: 2023.0.1.0) Added support for licensing CANivores.

Fixed 2022/12/03

• (Phoenix-5: 5.30.1-beta-5) Fixes issue reported in 23.0.0-beta-2. HasResetOccurred works correctly in Phoenix 5.
• (Phoenix-Pro: 23.0.0-beta-5) Fixed CANcoder name casing to be consistent with the product page.
• (Phoenix-Pro: 23.0.0-beta-5) Fixes issue reported in 23.0.0-beta-1. Phoenix Pro Talon FX reports the correct applied duty cycle.
• (Phoenix-Pro: 23.0.0-beta-5) Fixes issue reported in 23.0.0-beta-2. StatusSignalValues will not report errors if constructed very early.
• (Phoenix-Pro: 23.0.0-beta-5) C++ StatusSignalValue is now only templated over unit type.
• (Phoenix-Pro: 23.0.0-beta-5) Device constructors no longer require a CAN bus parameter.
• (Phoenix-Pro: 23.0.0-beta-5) Fixes issue reported in 23.0.0-beta-1. CANcoder Sensor Direction config is correct.
• (Phoenix-Pro: 23.0.0-beta-5) Fixes issue reported in 23.0.0-beta-1. CANivore’s can framing no longer disables on Windows after a long period of time.
• (ProFirmware: 23.1.0.0) Fixes issue reported in 23.0.0. Devices no longer report CouldNotRetrieveFirmware if they are only unlicensed.
• (Tuner X: 2023.0.1.0) Fixes issue reported in 2023.0.0.0. CANivore page no longer requires roboRIO Image v1.4.
• (Tuner X: 2023.0.1.0) Fixes issue reported in 2023.0.0.0. Tuner X can now flash CANivores on remote systems.
• (Tuner X: 2023.0.1.0) Fixes issue reported in 2023.0.0.0. Account login no longer fails when items are left in your cart.
• (Tuner X: 2023.0.1.0) Tuner X now correctly handles user login timeout.

Known Issues 2022/12/03

• (Phoenix-Pro: 23.0.0-beta-5) In Phoenix Pro TalonFX simulation, FOC control does not work. Phoenix Pro TalonFX simulation does not currently support the FOC control modes. Discovered by Internal Testing
• (Phoenix-Pro: 23.0.0-beta-5) Fixed by 23.0.11. In Phoenix Pro TalonFX simulation, Supply, Stator, and Torque current are not supported. Phoenix Pro TalonFX simulation does not currently support simulating the electrical currents. Discovered by Internal Testing
• (Phoenix-Pro: 23.0.0-beta-5) Fixed by 23.0.0-beta-7. In Phoenix Pro TalonFX simulation, following does not work. Phoenix Pro simulated TalonFX devices currently do not follow other TalonFX devices correctly. Discovered by Internal Testing
• (Phoenix-Pro: 23.0.0-beta-5) Fixed by 23.0.0-beta-7. In Phoenix Pro Java, Pigeon 2 simulated supply voltage does not show the correct value in the WPILib simulation GUI. The WPILib simulation GUI shows a different simulated supply voltage for Pigeon 2 than robot code in Java. The regular simulation API is unaffected. Discovered by Internal Testing
• (Tuner X: 2023.0.1.0) Fixed by 2023.0.2.0. The device list is blank when not connected to internet. Due to a bug in the Windows Networking API, the device list is blank when not connected to the internet. Discovered by Team 7028 (Beta Testers)

2022/11/23

Added 2022/11/23

• (Phoenix-5: 5.30.1-beta-4) Added support for hardware simulation vs simulation selection in VScode.
• (Phoenix-Libs: 23.0.0-beta-2) Added support for hardware simulation vs simulation selection in VScode.
• (Phoenix-Libs: 23.0.0-beta-2) Added OSX-Universal build option for M1-based Mac builds.
• (Tuner X: 2023.0.0.0) Added support for online updating to Pro and v5 firmware.
• (Tuner X: 2023.0.0.0) Clicking on the “Pro” column in batch upgrade toggles the Pro/v5 switch for all devices.

Fixed 2022/11/23

• (Tuner X: 2023.0.0.0) Improved the behavior of selecting devices for batch upgrade.

Known Issues 2022/11/23

• (Phoenix-Libs: 23.0.0-beta-2) Fixed by 5.30.1-beta-5. Phoenix 5 devices always report true with hasResetOccurred. When using simulated or real devices with Phoenix 5, the devices will always report that they have reset. Discovered by Team 3630 (Beta Testers)
• (Phoenix-Libs: 23.0.0-beta-2) Fixed by 23.0.0-beta-5. StatusSignalValues constructed immediately on Robot Creation report DriverStation Errors. If a StatusSignalValue is constructed too quickly, such as through static-initialization, it will report CAN Frame not received/too-stale. Discovered by Internal Testing
• (Tuner X: 2023.0.0.0) Fixed by 2023.0.1.0. CANivore page requires RoboRIO Image v1.4. The CANivore page requires roboRIO image v1.4 to see CANivores. The device page and Windows local server is unaffected by this. Discovered by Internal Testing
• (Tuner X: 2023.0.0.0) Fixed by 2023.0.1.0. Cannot flash CANivore on remote system. Tuner X cannot flash CANivores on a remote system. The workaround is to use Tuner v1, or to connect the CANivore to the Windows computer for the firmware flashing. Discovered by Internal Testing
• (Tuner X: 2023.0.0.0) Fixed by 2023.0.1.0. Account Login fails if your user account has items left in cart. If there are items left in the cart for an account that is being logged into for device activation, the login fails. To workaround, log into your account through a web browser and remove the items from your cart. Discovered by Internal Testing

2022/11/17

Added 2022/11/17

• (Phoenix-Libs: 23.0.0-beta-1) Per community input, added standard unit library to C++ API.
• (Phoenix-Libs: 23.0.0-beta-1) Added position and yaw setter methods to the hardware classes.
• (Phoenix-Libs: 23.0.0-beta-1) Replaced the Configurator timeout field with a default timeout field and optional timeout parameters.
• (Phoenix-Libs: 23.0.0-beta-1) Added optional timeout parameters to the Configurator API.

Fixed 2022/11/17

• (Phoenix-5: 5.30.1-beta-3) Fixed devices never enabling in simulation.
• (Phoenix-Libs: 23.0.0-beta-1) Fixed TalonFX GetAppliedControlRequest() reporting an empty control in C++.
• (Phoenix-Libs: 23.0.0-beta-1) Moved the Phoenix Pro C++ API into the ctre::phoenixpro namespace.
• (Phoenix-Libs: 23.0.0-beta-1) Simplified the names of the ControlRequest objects.
• (Phoenix-Libs: 23.0.0-beta-1) Renamed C++ StatusSignalValue::GetTimestamps to GetAllTimestamps.

Known Issues 2022/11/17

• (Phoenix-Libs: 23.0.0-beta-1) The C++ Configs API does not use the standard units library. Currently, the C++ Configuration API does not use the standard units library. Users must manually convert data to the documented unit types. Discovered by Internal Testing
• (Phoenix-Libs: 23.0.0-beta-1) Fixed by 23.0.0-beta-5. CANcoder Sensor Direction config is flipped. When viewing the rotation of the magnet from the LED side of the board, the direction is flipped from the config name. Discovered by Internal Testing
• (Phoenix-Libs: 23.0.0-beta-1) Fixed by 23.0.0-beta-5. CANivore’s CAN framing may disable on Windows after a long period of time. If running hardware-attached simulation on windows for an extended period of time while Tuner X is connected, the CANivore’s frame reporting may disable. This can be worked around by any of the following: Setting the CANivore name, power-cycling the CANivore, or USB re-enumerating the CANivore. Discovered by Internal Testing
• (Phoenix-Libs: 23.0.0-beta-1) Fixed by 23.0.0-beta-5. Self Test snapshot reports nan or 0 for applied duty cycle. When performing a self-test snapshot with a TalonFX that is driving, the reported applied duty cycle is always 0 or -nan. Discovered by Internal Testing

2022/11/04

Added 2022/11/04

• (Phoenix-Libs: 23.0.0-alpha-3) Made ECU config functions thread-safe.
• (ProFirmware: 23.0.0) Beeps during boot up.
• (ProFirmware: 23.0.0) Added full brake control request.
• (Tuner X: 2022.7.0.0) Firmwares come pre-packaged with Tuner X.
• (Tuner X: 2022.7.0.0) Tuner X indicates if you are out-of-date.
• (Tuner X: 2022.7.0.0) Batch field-upgrade and offline field-upgrade is easier to use.
• (Tuner X: 2022.7.0.0) Added a blink button to the grid view.
• (Tuner X: 2022.7.0.0) If the provided SSH credentials are incorrect, Tuner X will now prompt user for credentials.
• (Tuner X: 2022.7.0.0) Improved the Profile page and login experience.
• (Tuner X: 2022.7.0.0) Added a dropdown for common diagnostic server IPs.
• (Tuner X: 2022.7.0.0) Tuner X can get the robot IP from the Driver Station.
• (Tuner X: 2022.7.0.0) Tuner X now requests for additional permissions to use localhost.
• (Tuner X: 2022.7.0.0) Improved UI for several pages on mobile devices.
• (Tuner X: 2022.7.0.0) Added a Busy animation and a few hover effects.

Fixed 2022/11/04

• (Phoenix-Libs: 23.0.0-alpha-3) Added StatusCode reporting to the driverstation/console output.
• (Phoenix-Libs: 23.0.0-alpha-3) Fixes issue reported in 22.0.0. Diagnostic control will override local API control.
• (ProFirmware: 23.0.0) Improvements in startup frame.
• (ProFirmware: 23.0.0) Slot0 and Slot1 setting is honored in closed-loop modes.
• (ProFirmware: 23.0.0) Better FOC/Torque control under no-load conditions.
• (ProFirmware: 23.0.0) Bridge and system state are reported in self-test.
• (ProFirmware: 23.0.0) No longer requires no-motion during bootup, and other various improvements to startup.
• (ProFirmware: 23.0.0) Adjustments to stall whistle.
• (ProFirmware: 23.0.0) MaxDutyCycle parameter in TorqueCurrentFOCRequest limits the maximum output that can be applied.
• (ProFirmware: 23.0.0) CANbus improvements: Test plan passed with increased range: from 75 ft to 100 ft.
• (Talon FX (Pro): 23.0.0) Fixed issue where Talon FX only enables briefly after enabling robot.
• (Talon FX (Pro): 23.0.0) Self Test now reports FRC-Lock.
• (Tuner X: 2022.7.0.0) Fixes issue reported in 2022.4.0.0. Fixed online CANivore firmware upgrade on Windows.
• (Tuner X: 2022.7.0.0) Fixed diagnostic server information not updating when switching between servers.
• (Tuner v1: 1.9.0.0) Fixes issue reported in 1.9.0.0. Tuner v1 allows control of Talon SRXs and Victor SPXs.

Known Issues 2022/11/04

• (ProFirmware: 23.0.0) Fixed by 23.1.0.0. Phoenix Pro devices report both unlicensed and cannot get firmware version if they are unlicensed. Phoenix Pro devices will report that they are both unlicensed and that the API could not retrieve firmware version, even if they are the latest version. Discovered by Internal Testing

2022/10/14

Added 2022/10/14

• (Phoenix-Libs: 22.4.1) General improvements to licensing support.
• (Phoenix-Libs: 22.4.1) Self Test includes Phoenix Version at bottom.
• (Phoenix-Libs: 22.4.1) Diagnostic server reports if device is running Phoenix Pro firmware or Phoenix 5 firmware.
• (ProFirmware: 22.99.22.2) LEDs will indicate if devices are not licensed.
• (ProFirmware: 22.99.22.2) Devices will report they are Phoenix Pro firmware.
• (Tuner X: 22.6.0.0) License icon will not appear if device does not support licensing.
• (Tuner X: 22.6.0.0) Added seat activation support.
• (Tuner X: 22.6.0.0) Added blink button to devices in the devices page.
• (Tuner X: 22.6.0.0) Sorting button has more appropriate contents.
• (Tuner X: 22.6.0.0) Configs have been reworked to be more useful.
• (Tuner X: 22.6.0.0) Performance improvements.
• (Tuner v1: 1.9.0.0) Rebranded Phoenix Tuner to Tuner v1.

Fixed 2022/10/14

• (Phoenix-Libs: 22.4.1) Fixes issue reported in 22.0.0. Moved C++ GetAppliedControlRequest into the public space.
• (Phoenix-Libs: 22.4.1) Fixes issue reported in 22.0.0. Pigeon2 running Phoenix 5 firmware now displays configs from diagnostic server.
• (Phoenix-Libs: 22.4.1) Fixes issue reported in 22.0.0. CANcoder vH configs will show up in Tuner.
• (Phoenix-Libs: 22.4.1) Fixes issue reported in 22.3.0. C++ AsSupplier is correctly capitalized.
• (Phoenix-Libs: 22.4.1) Fixes issue reported in 22.1.0. Invert state is copied in the text when using “Share to Support”.
• (Talon FX (Pro): 22.99.22.4) Fixes issue reported in 22.99.11.0. Slot 0 Peak output used only for position and Slot 1 Peak Output used only for Velocity.
• (Talon FX (Pro): 22.99.22.4) Fixes issue reported in 22.99.11.0. Tuner can use new control interface with TalonFX.
• (Tuner X: 22.6.0.0) Renamed Datasheet to Users Guide.
• (Tuner X: 22.6.0.0) Fixes issue reported in 2022.0.0.0. Setting an ID to an available ID that’s a duplicate of another model’s ID no longer warns about a duplicate IDs.
• (Tuner X: 22.6.0.0) IP Field size increased to fit all IP addresses.
• (Tuner X: 22.6.0.0) Duplicate Tuner no longer crash.
• (Tuner X: 22.6.0.0) Controls tab pre-populates with controls.
• (Tuner X: 22.6.0.0) Fixes issue reported in 2022.0.0.0. Phoenix 5 motor controller control slider is scaled properly to -1.0 to +1.0.
• (Tuner X: 22.6.0.0) Fixes issue reported in 2022.4.0.0. Improvements that should avoid the Licensing/Pro Icon from turning Red erroneously.
• (Tuner X: 22.6.0.0) Fixes issue reported in 2022.4.0.0. CANcoder vHs have a proper image.
• (Tuner X: 22.6.0.0) Fixes issue reported in 2022.4.0.0. Corrupt device cache no longer crashes Tuner.
• (Tuner X: 22.6.0.0) Fixes issue reported in 2022.0.0.0. Self test location is saved, so when another self-test happens user is brought down to where they were.

Known Issues 2022/10/14

• (Tuner v1: 1.9.0.0) Fixed by 1.9.0.0. Talon SRX and Victor SPX cannot be controlled in Tuner v1. When using Tuner v1 to control a Talon SRX or Victor SPX, the control page will report that the firmware is too old. Discovered by Team 1018 (Beta Testers)

2022/09/24

Added 2022/09/24

• (CANcoder (Pro): 22.99.21.5) Added magnet offset config.
• (CANcoder (Pro): 22.99.21.5) Implemented full LED chart, including dimming when CAN is disconnected.
• (CANcoder (Pro): 22.99.21.5) Implemented Kalman-based filter for velocity.
• (Phoenix-Libs: 22.4.0) Supports new CANcoder and Talon FX firmware.
• (Talon FX (Pro): 22.99.21.0) Implemented Kalman-based filter for velocity.

Fixed 2022/09/24

• (CANcoder (Pro): 22.99.21.5) Fixes issue reported in 22.99.20.0. Fixed Voltage Measurement being wrong.

Known Issues 2022/09/24

• (CANcoder (Pro): 22.99.21.5) Velocity filter is not configurable. Velocity filter does not have a config to choose between latency and filtered output. CTRE has found configurable velocity filters to be less relevant, as the Kalman filtering produces reasonably smooth velocities while minimizing latency. Default setting is currently lowest latency. Discovered by Internal Testing
• (Talon FX (Pro): 22.99.21.0) Velocity filter is not configurable. Velocity filter does not have a config to choose between latency and filtered output. CTRE has found configurable velocity filters to be less relevant, as the Kalman filtering produces reasonably smooth velocities while minimizing latency. Default setting is currently lowest latency. Discovered by Internal Testing

2022/09/09

Added 2022/09/09

• (Phoenix-Libs: 22.3.0) Added Position and Yaw Setters.
• (Phoenix-Libs: 22.3.0) Added Status Signal frequency setters.
• (Phoenix-Libs: 22.3.0) Added asSupplier method to StatusSignalValues. This allows easier use of the language-features for type suppliers.
• (Phoenix-Libs: 22.3.0) Added external APIs for Phoenix 5.

Fixed 2022/09/09

• (Phoenix-Libs: 22.3.0) Fixes issue reported in 22.0.0. Added explicit ToString for C++ StatusSignalValues.

Known Issues 2022/09/09

• (Phoenix-Libs: 22.3.0) Fixed by 22.4.1. C++ AsSupplier is incorrectly capitalized. C++ AsSupplier follows Java-convention camelCase instead of C++ convention CapitalCase. Discovered by Internal Testing

2022/08/25

Added 2022/08/25

• (CANcoder (Pro): 22.99.20.0) Added timesync support.
• (Phoenix-Libs: 22.2.0) Added new type of Signal that switches on some other signal.
• (Phoenix-Libs: 22.2.0) Added Pigeon2 Support.
• (Pigeon2 (Pro): 22.99.20.0) Brought Pigeon2 up to date with Phoenix Pro.
• (Pigeon2 (Pro): 22.99.20.0) Added timesync support.
• (Talon FX (Pro): 22.99.20.0) Added time sync for Position/Velocity frames.
• (Tuner X: 2022.4.0.0) Tuner now caches devices and will pull their licenses next time it’s connected to the internet.

Fixed 2022/08/25

• (Talon FX (Pro): 22.99.20.0) Fixes issue reported in 22.99.13.3. Added overvoltage protection.

Known Issues 2022/08/25

• (CANcoder (Pro): 22.99.20.0) Fixed by 22.99.21.5. Voltage measurement is wrong. The voltage measurement for all CANcoders is wrong. Discovered by Internal Testing
• (Phoenix-Libs: 22.2.0) Fixed by 23.0.10. If any frame times out during WaitForAll, all frames return StatusCode RxTimeout. During a WaitForAll command, if any frame times out, all frames have the “RxTimeout” StatusCode. Discovered by Internal Testing
• (Pigeon2 (Pro): 22.99.20.0) Fixed by 23.1.2.1. Certain CAN FD configurations with Pigeon2 can cause red blips. Certain configurations of Pigeon2 manufactured after September 2022 on a CAN FD bus may cause red blips. Discovered by Customer Email
• (Pigeon2 (Pro): 22.99.20.0) Fixed by 23.1.2.1. LEDs do not solid-orange on boot. LEDs should both solid-orange for a second when the Pigeon2 boots, to match the behavior of Phoenix 5. Discovered by Internal Testing
• (Tuner X: 2022.4.0.0) Fixed by 22.6.0.0. Tuner does not support CANCoder vH Icons. This version of Tuner does not have icons for CANCoder vH. This is purely cosmetic, as the functionality of CANCoder vH devices are not affected. Discovered by Internal Testing
• (Tuner X: 2022.4.0.0) Fixed by 22.6.0.0. Pro icon turns red erroneously. Sometimes while Tuner is connected to devices, the PRO icon will turn red indicating a failure in communication. This does not mean the device is no longer licensed. Discovered by Internal Testing
• (Tuner X: 2022.4.0.0) Fixed by 2022.7.0.0. Online CANivore flashing sometimes fails. Sometimes when performing a CANivore firmware flash using an online file, the flash fails with error “Specified CRF file could not be found.” The workaround is to use the offline file dialog and manually select the crf you wish to update to. This is not an issue for Windows 11. Discovered by Team 971 (Alpha Testers)
• (Tuner X: 2022.4.0.0) Fixed by 22.6.0.0. If the device cache file is corrupted, Tuner will crash. If the cache file that’s used to store old devices becomes corrupted, Tuner will crash. This can be worked around by manually deleting the “CachedDevices.json” file in the app’s cache directory. Discovered by Internal Testing

2022/08/12

Added 2022/08/12

• (Phoenix-Libs: 22.1.1) Improvements to licensing.
• (Talon FX (Pro): 22.99.13.7) Improved the robustness of licensing and other diagnostic commands.
• (Talon FX (Pro): 22.99.13.7) Added ability to clear licenses.
• (Tuner X: 2022.3.2.0) Fixes issue reported in 2022.0.0.0. Added ability to provide SSH username and password for non-rio linux targets.
• (Tuner X: 2022.3.2.0) Added more icons to differentiate whether a device is licensed or not.
• (Tuner X: 2022.3.2.0) Added deploy temporary server to RoboRIO functionality.

Known Issues 2022/08/12

• (Tuner X: 2022.3.2.0) Tuner cannot deploy temporary diagnostic server to non-rio Linux targets. This version of Tuner doesn’t have support for deploying the temporary diagnostic server to a non-RIO linux device. Discovered by Internal Testing

2022/08/09

Added 2022/08/09

• (Phoenix-Libs: 22.1.0) Necessary additions for TalonFX Invert and Follower Mode.
• (Talon FX (Pro): 22.99.13.3) Fixes issue reported in 22.99.11.0. Added Follower Mode for other TalonFX’s.
• (Talon FX (Pro): 22.99.13.3) Fixes issue reported in 22.99.11.0. Added Invert modes and follower Invert modes.

Known Issues 2022/08/09

• (Phoenix-Libs: 22.1.0) Fixed by 22.4.1. Self test invert does not appear in text when using “Share to Support”. When performing a self-test snapshot, the invert state does not appear in the text that gets copied to the email when using the “Share to Support” button. Discovered by Internal Testing
• (Talon FX (Pro): 22.99.13.3) Fixed by 22.99.20.0. TalonFX Has no overvoltage protection. This version of TalonFX does not have overvoltage protection. Care must be taken to not allow the Talon to be driven without a battery in circuit. Discovered by Internal Testing

2022/08/02

Added 2022/08/02

• (Phoenix-Libs: 22.0.0) Initial Release of Phoenix Pro.
• (Talon FX (Pro): 22.99.11.0) Initial Release of TalonFX Firmware.
• (Tuner X: 2022.0.0.0) Initial Release of Phoenix Tuner.

Known Issues 2022/08/02

• (Phoenix-Libs: 22.0.0) Fixed by 22.3.0. StatusSignalValue has no ToString() method in C++. The StatusSignalValue class has no method of getting an std::string representation, although it has the ostream « operator overload for a string representation. Discovered by Internal Testing
• (Phoenix-Libs: 22.0.0) Fixed by 22.4.1. C++ GetAppliedControlRequest did not work. C++ GetAppliedControlRequest was protected, and inaccessible. Discovered by Internal Testing
• (Phoenix-Libs: 22.0.0) Fixed by 22.4.1. Pigeon2 running Phoenix 5 firmware did not have diagnostic config support. Tuner could not see or change the configs of a Pigeon2 running Phoenix 5 firmware. Discovered by Internal Testing
• (Phoenix-Libs: 22.0.0) Fixed by 22.4.1. CANcoder vHs did not have configs when communicating over diagnostic server. When selecting a CANcoder vH, diagnostic server did not display the configs in Tuner. Discovered by Internal Testing
• (Phoenix-Libs: 22.0.0) Fixed by 23.0.0-alpha-3. Diagnostic control is same priority as API control. Devices do not prioritize diagnostic control over API control. This causes an issue when both are sent, where the device will oscillate between both controls. Discovered by Team 971 (Alpha Testers)
• (Talon FX (Pro): 22.99.11.0) Fixed by 22.99.13.3. TalonFX has no follower mode. Talon FX has no follower mode in this version of firmware. Discovered by Internal Testing
• (Talon FX (Pro): 22.99.11.0) Fixed by 22.99.13.3. TalonFX has no invert. Talon FX has no invert setting in this version of firmware. Discovered by Internal Testing
• (Talon FX (Pro): 22.99.11.0) Fixed by 22.99.22.4. Velocity closed loop uses slot0 instead of slot1. Position closed loop currently uses slot0 and velocity closed loop currently uses slot1 (future release will support slot selection). However, recent firmware files erroneously use slot0 for peak output when using closed loop velocity. Discovered by OEM Customer
• (Talon FX (Pro): 22.99.11.0) Fixed by 22.99.22.4. Tuner may not use new controls with Pro firmware. There is a firmware issue that may result in Tuner not providing the new control methods to the user when controlling a TalonFX. This only occurs for newer versions of Tuner. This does not affect API. Discovered by Team 3538 (Alpha Testers)
• (Tuner X: 2022.0.0.0) Fixed by 2022.3.2.0. Tuner cannot connect to non-rio linux devices. Tuner does not have the means to connect to any device with a username/password combo other than admin/. This means Tuner can effectively only connect to the RoboRIO. Discovered by Internal Testing
• (Tuner X: 2022.0.0.0) Fixed by 22.6.0.0. Setting an ID to an available ID sometimes erroneously warns about a duplicate ID. When the user sets an ID of a device to the same ID as another device of a different model, Tuner will warn the user about a duplicate ID, even though the ID is valid since the duplicate ID is of a different model. Discovered by Internal Testing
• (Tuner X: 2022.0.0.0) Fixed by 22.6.0.0. Performing a Self-Test Snapshot moves the view back to the top. When a Self-Test Snapshot occurs, the viewpage of the Snapshot moves back to the top of the screen. Discovered by Internal Testing
• (Tuner X: 2022.0.0.0) Fixed by 22.6.0.0. Phoenix 5 motor controllers had incorrectly scaled PercentOutput control sliders. When controlling a Phoenix 5 motor controller in Tuner, the percent output slider was scaled from -1023 to +1023, instead of -1.0 to +1.0. Discovered by Internal Testing