Hello, we are experiencing a strange connection issue. Before everything worked fine, but yesterday when we connected to the radio’s wifi, only the driverstation communication gives a signal, while “code” is disabled. At least everything would be fine if target recognized and allowed the deploy, but only the message appears: “looking for target”. It’s a code that already allowed deployment until yesterday, so the problem cannot be the IP, which is already defined with the number of our team. The firewall is already disabled
Hello.
Has this happened before yesterday? Have you tried reflashing the radio?
Hello, we solved the problem. We just switched pcs and it fixed it. But another problem arose. How do we make it possible to deploy via usb cable? We were able to deploy via radio without any problems. But here in the pit, after configuring the radio, we will not be able to test new codes via wifi from the radio. That’s why we would use a usb cable for this, the problem is that although it recognizes the communications in the driver station, and even lets you control a code that was set as “run as startup”, it is not possible to carry out new deployments in labview. A message appears that the target was not found. I thought that if I left the IP as roboRIO-8276-FRC.local (my team number) it would allow me to deploy both with radio and with usb, but in this case only one is being allowed.
Not exactly. “roboRIO-XXXX-FRC.local” may refer to localhost IP address (“127.0.0.1”) thru USB cable. It also can refer to the IP address given by radio (“10.XX.XX.2”, XXXX as team number)
It makes sense that
since the FMSField Management System ( Field Management System) is loaded into your radio, you can only use that radio by connecting to the FMSField Management System, when you are on the field.
If you’d like to deploy your code thru USB cable, my suggestion is to change the ip address to “172.22.11.2”(edit) . You can adjust the target setting by right-click “target”, then “properties”.
the RoboRio’s default USB ip address is 172.22.11.2
yeah ,my bad
thanks!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.