Phoenix Pro 2025 - Licensing not licensed?

[burde1jb]

Happy Christmas Eve, CD! Any eyes and help on this would be appreciated.

Had the following error pop up for our steering motors when deploying test code for 2025 -

• Using a Pro only feature on an unlicensed device. The device may not behave as expected if it continues to operate while unlicensed.
• TalonFX ID 4 failed config with error: UsingProFeatureOnUnlicensedDevice

The problem I am having with this is that we did purchase and activate the license on the motor in question -

So we have the license, we activated the license, the team number is in agreement with the program, but we are still getting this error. I believe this error is causing the entire program to fail as well.

The code we are deploying can be found here - GitHub - burde1jb/2025-FRC-4327-Test-Code

Any insights on this one? Thanks!

[sthump]

Did you assign your team number to your RIO?

[burde1jb]

Yes - the roboRIO was imaged with the new 2025 beta image for this testing.

[daltzsmith]

Does your firmware version for each device begin with 25?

[AllenGregoryIV]

We had an issue at an off-season where we had to reflash motor firmware after we licensed the motor for it to pick up the license correctly.

That’s just now our standard procedure to license, than reflash newest firmware afterwards.

[burde1jb]

Yes - All motors have firmware beginning with “25” as shown below.

[burde1jb]

Thank you for the tip, but even after reflashing the firmware on all devices, the error persists.

[sthump]

Your devices in TunerX seem to have the LIC icon. If properly licensed I believe they have the Pro icon. We ran into this last year when the team number was not properly set.

It looks like you did it thru RIO imaging tool. I think there is a way to do it in Visual Studio. Might try that way. I don’t know the exact method but I am sure it’s pretty easy to look up.

[burde1jb]

Nice catch! As seen below, the device says “Not Licensed” even though I activated the 2025 license on the device. @daltzsmith - Any ideas here?

For setting the team number on the roboRIO, since this is done through Tuner X Preview, that shouldn’t be causing this “Not Licensed” issue, right? As in, I should be able to activate a license on a device before ever deploying code, right?

[daltzsmith]

Is an FRC radio connected to the robot and configured to the correct team number?

[cmdada]

@sthump

there is a way to do it in Visual Studio

The wpilib tool roborioteamnumbersetter in the run tools dialogue

[burde1jb]

Good thinking! I did have a brand new VH-109 which was not configured to our team number. So I went through the configuration for our team number, redeployed the code, and now I do not get the error as stated originally in this thread. Not sure how that would be related, but that is the update.

HOWEVER, in Tuner X Preview, the device is still showing as “Not Licensed” when I have activated my 2025 license. So - error is gone when deploying code - but devices are continuing to not acknowledge the licensing.

[sthump]

You have to make sure the RIO has the correct team number set as well.

I think we used this:

roboRIO Team Number Setter

when the RIO Imaging tool wasn’t doing it correctly or wasn’t sticking.

[burde1jb]

Cool! I love learning new tips and tricks from everyone here! To help, I took a screenshot when first opening this tool and then again after setting the team number through this tool. Sadly, no change to the “Pro” licensing status for the devices.

[sthump]

Weird, did you restart everything?

[burde1jb]

Yes - power cycled the robot, restarted the computer, reinstalled Tuner X Preview, everything I can think.

Does the connection have anything to do with this? I am connected via USB to the CANivore which has all of these devices. Not sure of another method.

Whenever connecting to the robot, I am connecting via USB to the roboRIO.

[cmdada]

At this point ctre support is probably the best resource for you

[sthump]

Yea, I am out of ideas too.

We had this same issue last season but assigning team number fixed it for us.

CTRE support is pretty responsive. I bet you get a response today.

[Joe_Ross]

@sthump

CTRE support is pretty responsive. I bet you get a response today.

From Contact Us – CTR Electronics

NOTE: CTR Electronics is closed for the holidays through Wed, January 1st.
Support and Sales requests will be processed when staff returns on January 2nd.

[AllenGregoryIV]

@burde1jb

Does the connection have anything to do with this? I am connected via USB to the CANivore which has all of these devices. Not sure of another method.

I believe this is where the problem is. We normally connect over the robot network either WiFi or Ethernet and then configure TunerX with our team number.

I imagine when you directly connect to the CANivore USB the devices don’t show as PRO licensed since it doesn’t know what team number your robot is configured for as the CANivore is not connected to a RIO at the time.