Resolving Falcon 500 Control Issues in Phoenix Tuner X

Problem Details

The Falcon 500 (P/N 217-6515) is a brushless motor integrated with a Talon FX motor controller manufactured by Cross the Road Electronics (CTR Electronics). When configuring or troubleshooting these devices with Phoenix Tuner X, engineers frequently encounter a condition where the device appears connected, telemetry plots render correctly, but no motor actuation occurs when issuing %VBus, velocity, or position commands. The symptom typically presents as:

• A dialog prompt: "You must enable the robot in the Driver Station".
• Successful self-test, configuration, and signal plotting from Phoenix Tuner X.
• Zero current draw and no mechanical response when a control request is sent.
• Confirmed working motor actuation when commanded from robot code (Java/C++ via WPILib).

These symptoms point to one of two interacting conditions: the FRC Lock safety interlock or a firmware variant mismatch between Talon FX firmware (v5 vs Pro).

Affected Hardware and Firmware

Root Cause 1 — FRC Lock and the Driver Station Enable Signal

FRC Lock is a safety feature built into the Talon FX firmware stack to prevent unintended actuator motion in a competition environment. When a Talon FX detects that it is connected to an FRC control system (either directly to the roboRIO CAN bus or indirectly through a CANivore), it requires a periodic enable signal from the FRC Driver Station (DS).

The DS enable signal is transmitted over UDP to the roboRIO on port 1110 (DS-to-robot) and 1115 (robot-to-DS). The roboRIO rebroadcasts the enable state onto the CAN bus as a heartbeat frame. The Talon FX monitors this heartbeat and asserts a hardware-level inhibit on the gate drivers if the heartbeat is absent for more than ~250 ms.

Diagnostic Path for FRC Lock

1. Verify the roboRIO is imaged and the team number is configured.
2. Launch the FRC Driver Station and confirm a communications link to the roboRIO (green LED or solid status indicator).
3. Place the DS in Enabled mode (do not remain in Disabled or Teleop-Disabled).
4. In Phoenix Tuner X, re-attempt the motor command.

If a dialog continues to appear after enabling, verify the CAN bus topology. A missing 120 Ω termination resistor or a CANivore firmware mismatch can prevent the heartbeat from reaching the Talon FX. The official CANivore hardware reference describes proper termination and firmware update procedures.

Root Cause 2 — Talon FX Firmware Variant Selection

The Talon FX can run two distinct firmware stacks:

• Phoenix v5 (non-Pro) firmware — free, exposes base motion features (PercentOutput, Velocity, Position, MotionMagic with constrained features), and is the default for unlicensed devices.
• Phoenix Pro firmware — requires a per-device Pro license (purchased from CTR Electronics) and unlocks advanced features such as Motion Magic® Expo, advanced PID slot management, and richer telemetry.

Phoenix Tuner X surfaces a "Phoenix 5" toggle or button in the firmware update dialog. This selector controls which firmware binary is flashed to the Talon FX. Misconfigurations that have been observed in the field:

1. The user has a Pro license but Phoenix 5 firmware is currently flashed. Motion Magic Expo and other Pro-only features will silently fail.
2. The user has no Pro license but the device is flashed with Pro firmware; the Talon FX will refuse all commands from Phoenix Tuner X unless the license is activated.
3. The Phoenix 5 firmware update is available but the user pressed Update without selecting the Phoenix 5 button in the dialog. Phoenix Tuner X then attempts to flash the most recent stack and skips the legacy binary.

Firmware Selection Procedure

1. In Phoenix Tuner X, navigate to the device page for the Talon FX.
2. Click Update Firmware (or Check for Updates).
3. If you do not hold a Pro license, locate the Phoenix 5 button in the firmware update dialog and click it to display the legacy v5 binary list.
4. Select the latest stable Talon FX (v5) firmware and click Update.
5. Allow the device to power-cycle; wait for the status LED to return to solid green/amber per CTR's CAN bus troubleshooting guide.
6. Repeat for every Talon FX on the bus.

Diagnostic Workflow

The following ordered checklist isolates the failure mode before contacting support:

1. Confirm CAN bus health — In Phoenix Tuner X, verify all expected devices appear under the CANivore or roboRIO bus. Missing devices indicate termination, wiring, or device ID conflicts.
2. Read device status — Open the Talon FX self-test page. Confirm Sticky Faults are clear (no FusedBreakerFault, HardwareFault, or FRCLocked sticky bits).
3. Capture a self-test snapshot — Use the Take Snapshot feature while issuing the failed command. Save the .zip archive for support escalation.
4. Validate the DS enable signal — Place the DS in Enabled mode. The Talon FX FRC Locked status flag should clear within one heartbeat cycle (~20 ms).
5. Verify firmware variant — In the device page, confirm the firmware version string begins with either 5. (v5) or Pro. (Pro).
6. Send a low-risk command — Use Set Control: PercentOutput at 5% to verify actuation without risk of mechanical damage.

Solution Summary

Advanced Diagnostics and Telemetry

Phoenix Tuner X provides a self-test snapshot mechanism that bundles device configuration, fault history, signal plots, and CAN frame statistics into a single archive. This artifact is the canonical escalation payload for CTR Electronics support.

1. In Phoenix Tuner X, connect to the Talon FX in question.
2. From the device page, click Run Self-Test while reproducing the issue.
3. Click Save Snapshot to export the .zip.
4. Send the snapshot to [email protected] with a brief description of the robot configuration (CANivore in use, DS mode, roboRIO image version).

The snapshot contains the raw values behind every status register, which allows CTR support to confirm whether the Talon FX observed an enable signal, whether the firmware variant matched the license state, and whether any thermal or hardware fault was latched during the attempted actuation.

Related Configuration Pitfalls

Test Mode Without Robot Code

The Talon FX can be actuated from Phoenix Tuner X while the robot code is not deployed, provided the DS is in Test or Enabled Teleop mode. However, a common error is leaving the DS in Disabled. The enable state is independent of robot code execution; only the heartbeat matters.

Indirect Connection via CANivore

If the Talon FX is connected through a CANivore rather than the roboRIO's native CAN bus, the DS heartbeat still propagates because the roboRIO and CANivore share the same CAN FD bus instance. The CANivore Pro hardware reference documents this bridging behavior and lists supported firmware revisions.

Sticky Faults After Power Cycle

Some faults (e.g., HardwareFault, FusedBreakerFault) are sticky and persist across power cycles. They must be explicitly cleared in Phoenix Tuner X via the Clear Sticky Faults button on the self-test page, or programmatically with ClearStickyFaults() in the Phoenix API.

Verification

After applying the corrective action, run the following verification sequence to confirm full motor control from Phoenix Tuner X:

1. Open Phoenix Tuner X and connect to the Talon FX.
2. Confirm the device appears with the expected firmware version string.
3. Place the Driver Station in Enabled mode.
4. From the Controls tab, issue PercentOutput at +5% for 1 second.
5. Observe positive motor rotation and a corresponding current draw on the live plot.
6. Reverse to -5% and confirm directional response.
7. Issue a velocity command (e.g., 1000 RPM) and confirm closed-loop tracking on the velocity plot.

If all three commands produce the expected mechanical response, the device is fully operational under Phoenix Tuner X.