Radio Disabling Immediately

Technical
, , ,
1

Our chassis was working fine 1 week ago when we were using 2023 tools to drive it. Then I imported the code and dependencies to 2024, updated the necessary tools and RoboRIO. I then tried to control it via Printer Cable and it was just fine.

However when I tried to connect wirelessly,the robot disabled itself immediately after enabling. I thought it might be an issue with the radio config tool so I loaded firmware and configured again. It didn’t really help. I dont remember the logs exactly but there wasn’t much information as far as I remember

If someone can point out what I might be forgetting or doing wrong, I would really appreciate as we can not do much under those circumstances, such as pathplanning etc. and I need to solve it asap. Thx in advance

2

Assuming you’ve updated the NI game tools, have you tried restarting your driver station laptop?

3

Not sure if this is your issue but I think its possible considering you only started seeing this after you update to the new NI game tools.

There is a known issue where “The Driver Station contains tighter safety mechanisms in 2024 to protect against control issues.” causing some teams to randomly see the robot disable.

See the following

2 Likes
4

our team was experiencing this issue after the upgrade to 2024 NI. we changed our radio to use the 5Ghz band and now everything is working fine.

1 Like
5

I was finding the same problem and when I changed to 5Ghz it was fixed, however, today during the afternoon my driver station started giving the following prompt error:

FPGA not yet configured in wpi::Now(). Time will not be correct

and my code cannot be even deployed to the robot.

1 Like
6

What vendor deps are you using? Is this a Java or C++ program? You should still be able to deploy, that’s a runtime error.

7

image

8

This sounds like a red herring and the actual crash message is above that- scroll up in the log output and see if there is anything else.

9

I got this exact error today after I flashed my Limelight for the latest firmware. Flashing it had reset all the settings for it so I had to enter my team number again, and everything started working again. Maybe some other devices can cause the same effect, so I would look through some of your other hardware.
Hope this helps.

10

Hey I am having the same error that you were having here. Were you able to fix it? And if so how did you do it?

11

This message error does not involve the Radio, in my case, It was happening because, in the same class, I was calling two methods with the same function, this is the reason why the Driver Station was showing that error.

1 Like
12

Ok thanks

13

Turned off all the firewalls, disabled multicast DNS, made sure no other network interference is present and updated the team radio to 5Gh. Don’t think mDNS has actually anything to do with that, as it work right now pretty well even if I enable it. Try these above I would say

14

Just letting you know, we have the same FPGA error on both teams I mentor

15

I had the same problem. It happens once every ~10 reboots and requires a full restart of the Robot to fix. I have several vendordeps since I am using the YAGSL library. Did anyone find a solution? Here is the link to our code: GitHub - Team-4361/RobotCode-2024 at minimal

16

We have the same problem. It only occurs when we use the results method on a photonvision camera. Has anyone resolved this by updating both versions of photon vision on the camera AND the photonLib? Eric G- I see from your code that you are still using v2024.2.8 when v2024.2.9 is most current

17

I had the problem FPGA not yet configured in wpi also. It also turned out to be two duplicate import
commands. Photonvision runs fine with a limelight 2 using Java and SmartDashboard. Thanks for the Post!!