We are trying to move from old phoenix 5 API to the latest phoenix 6 API and just found that it seems like our CANCoder (Manufactured in 2019) doesn’t have a capable firmware to use phoenix 6. However, that CANCoder version H (Manufactured in 2022) has a firmware to use phoenix 6. Is it possible to use phoenix 6 on that 2019 version CANCoder or we must replace it with newer versions?
The original CANcoder hardware revision now uses “CANcoder vK” firmware.
I would also recommend using Tuner X instead of Tuner v1, as it simplifies the selection of firmware down to selection v5 or v6, the firmware year, and the version from a list of available versions. You also need Tuner X if you want to use any of the new Phoenix 6 features (including Self Test and Plot) or deploy the temporary diagnostic server.
Thank you for your reply! I will try to flash that firmware.
Sadly for our team, we failed to connect to roborio 2.0 with phoenix X. However, it recognizes our two CANivores while the old phoenix tuner cannot recognize them. Are there any debug advices?
I’m assuming you can connect using Tuner v1?
How are you trying to connect to the roboRIO (USB or Wi-Fi)? Tuner X should default to roboRIO USB, but you can change the IP if you’re connected wirelessly. If Driver Station is connected, we also support a “Driver Station” option (click on the arrow to the right of the textbox to get the list of defaults).
Another thing is there should be text below the Team Number/IP textbox that should say something like “Failed to connect: <address>”. That <address> is what Tuner X thinks is the resolved IP address of the robot, so you can use that to verify that it’s at least trying to connect to the right target.
The “No devices connected” box on the Devices page also lists where Tuner X is failing. There’s three possible conditions where Tuner X doesn’t show devices:
- Cannot ping the target – This means Tuner X can’t find the target IP address. Check the resolved IP and that the target device is actually on and connected.
- Ping succeeded, but cannot connect to the diagnostic server – This means there isn’t a running Phoenix Diagnostic Server. Running the diagnostic server is documented here.
- Ping succeeded, connected to diag server, but no devices – This typically means there’s an issue with the CAN bus or power to the devices.
Make sure the Rio has the latest firmware installed. Before connecting with Tuner X.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.