We have been working on two roboRios. On the first roboRio with a first Laptop we were able to run Rev Hardware Client to setup SparkMax controllers. We can also download Java code using the radio. Initially we were also able to update roboRio Firmware. Since then we can no longer update roboRio Firmware. We also can not run phoenix tuner over usb. Phoenix tuner over the radio will see the roboRio but doesn’t see any devices.
This first laptop on the second 2022 robot can not do anything over the USB connection. (The SparkMax’s were setup on the first system so we haven’t tried RHC again.) Phoenix Tuner with USB can find the roboRio and download the tool but does not see any CAN devices. Didn’t try it over the radio.
This 2022 robot will not allow us to download code using the radio. And the first laptop can not download the code over usb.
Luckily our team has a laptop with Win 10 Pro that can download code over USB, and successfully ran Phoenix tuner to reprogram its talons to the second robot. But we had to port the program to that laptop and run the IDE from there…
The first laptop is a two year old Dell with a quad core 11th gen i7 and 16 GB of ram. Its my personal laptop and I bought it specifically for use on the robotics team.
What can we do to fix it so that we can connect properly over usb to run roboRio Imaging Tool, Phoenix Tuner, and download code? And how do we change the 2022 robot so we can download code over the radio?
I haven’t swapped radios yet. The 2022 Radio is brand new.
Its extremely frustrating to have all issues with these products every January/February/ and March. Then not use them for a full year and expect to be able to use them again.
This problem laptop is running Win 10 Home. All of its drivers were updated in January via the Dell website. There are no errors in its Hardware List. The event log is showing “Can Not Connect”, “Permission Denied”, and “Communication or Connection Timeout” Errors. We have disable the Windows Firewall on the Current Network. Then we disable the Windows Firewall on Public and Private networks too. And we have rebooted numerous times.
I believe so. build.gradle points to 2022.4.1. As to the RIO image our lead programmer updated them Saturday. I’ve been using the first one since then and tried to code for the second one yesterday. Will check that build.gradle is the same on the second laptop which did send code to the second roboRio via usb.
Have not used the roboImage tool on the second laptop. Our lead programmer updated them.
Hi @ksanger. First of all, I’m sorry to hear you’re having issues. Let’s see if we can get to the bottom of this.
Sounds like you have a few things going on, so I’d first like to confirm a few things.
You mention testing over USB. Can you confirm that you’re only using USB-C to connect to REV components using the REV Hardware Client (i.e. for firmware updates), and using USB-A to USB-B (printer cable) to the RoboRio for all other testing (reimaging Rio, deploying code, using Phoenix tuner, etc)?
On the laptop that is unable to connect to the roborio, can you show a screenshot of the network tab on the driver station (assuming it’s installed on this machine). It would also help if you could share any errors you receive from the deployment process in vscode.
When connected to the Rio via USB, can you confirm whether you can successfully ping the roborio mDNS hostname and/or USB IP address? Info on how to do that can be found here.
We’ve had a lot of issues with laptops that can’t be run as administrator or have firewalls. If you haven’t already tried, I’d recommend using a laptop that has no such restrictions on the user.
Also, what team are you working with? I ask because your profile here shows 211, which hasn’t competed in many years, but is from my area, so I’m curious if your current team is from here as well.
Yes I am on the USB-B printer cable to the roboRIO and Phoenix SW.
Haven’t used this laptop to drive again as we moved to the working laptop.
all hostname.local pings fail.
Have not been allowed back onto the 2022 robot (2nd bot).
But the first robot is on
|Firmware Version|6.0.0f1|
|Operating System|NI Linux Real-Time ARMv7-A 4.14.146-rt67|
|Image Version|FRC_roboRIO_2022_v4.0|
On the first laptop build.gradle has id “edu.wpi.first.GradleRIO” version “2022.4.1”
On the first roboRio the web web interface shows 2022.4.0.
But this is a few days later than when I started with this problem and we haven’t updated the roboRio since 2/26/2022.
Can’t get back on the 2022 robot. Its tied up full time.
I have admin privileges on my private laptop. But its Win 10 Home. The other is Win 10 Pro.
Could not ping hostname.local addresses. Found how to disable MS Win 10 mdns on this thread.
I have modified the registry entry to disable Win 10 mdns. Then if I reboot pinging hostnames.local work. Well the pi fails the first time but then works the second time. If I change the wifi to access WWW and then restore the wifi to the local robot the local addresses fail again.
Flushing the dns cache as suggested by this other thread, doesn’t work.
Another thread suggests that Win 10 has a bug that causing dns to fail if it looses wifi, goes to sleep, or any interruption in the internet happens.
Have not had the time to retry usb connection after “fixing” hostname.local name resolution. Next issue to solve is installing wiringpi libraries onto wpilibpi so we can read an i2c device and post to network tables…