Comment
Author: Admin | 2025-04-28
We are excited to announce our first beta release for 2025. This release contains many changes, improvements and enhancements for 2025.We are excited to read any feedback the community may have.NoteUsers should use "Phoenix Tuner X Preview" (link) (a separate application in the Windows Store) for usage with beta 1DownloadLinks for the vendordeps, a detailed changelog, and more can be found below:https://github.com/CrossTheRoadElec/Phoenix-Releases/releases/tag/v25.0.0-beta-1 You must be logged in to vote Is there still a plan to support running multiple motors with a single tuner x application for 2025? You must be logged in to vote 1 reply This is still an in-development effort. We have already made architectural improvements in the diagnostic server to enable this, but UI and Tuner development is in-progress. You must be logged in to vote 0 replies Various signal logging seems to have broken with the latest update You must be logged in to vote 3 replies Could you elaborate on what you mean? Well it seemed like all signals were broken. I figured it was probably a tuner x out of date issue but the windows store didn't say an update was available. Closing and reopening I can confirm I'm now on 2025.1.0.0, and things are working again. I suspect that was the issue.When I first opened tuner x it knew there was an updated firmware for the talon though. Not sure if that is built into the app or not I see the problem now. We did back break owlet/logging from beta 1 to beta 2. Tuner 2025.1.1.0 is on it's way to the stores and will have a fix (and will also make it work on various logs for various api levels as well). Hey folks. Just a couple of announcements.CANrange is in-stock and shipping now!Phoenix Beta 4 is available now with support for CANrange hardware and full simulation support. You must be logged in to vote 0 replies Does applyConfigs() only apply the configs that have changed, or apply everything again? You must be logged in to vote 1 reply When you apply a full Configuration object, such as TalonFXConfiguration, then we apply everything if the FutureProofConfigs field is true (default). If that field is false or you're applying one of the config groups, such as Slot0Configs, then we only apply configs that have changed since the last call to device.getConfigurator().apply(...). -->
Add Comment