You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When running a robot project in LabVIEW, it will seemingly deploy correctly then immediately end and say that it lost connection to the RIO.
To Reproduce
Steps to reproduce the behavior:
Create a new robot project in LV
Set team number/target address
Open Robot Main.vi
Run
Once the it is done deploying, Robot Main.vi will show that it is running for half a second and then LV will have a pop up saying it lost connection with the target, stopping the program.
Expected behavior Robot Main.vi should continue running and the target should not disconnect
Screenshots
Popup
Desktop (please complete the following information if applicable):
OS: Windows 11
OS Language: English
Project Information:
LabVIEW
NI beta 2
roboRIO
roboRIO 1
Image version: FRC_roboRIO_2025_v1.1
Additional context
I talked with Greg, and we found that a work around for this right now is to run WPI_DriverStationStart Communication.vi (found in Robot Main.vi) first and that will initialize communication correctly, and you should be able to run Robot Main.vi fine after that. This will need to be repeated when the RIO is power cycled.
This is the VI:
The text was updated successfully, but these errors were encountered:
Describe the bug
When running a robot project in LabVIEW, it will seemingly deploy correctly then immediately end and say that it lost connection to the RIO.
To Reproduce
Steps to reproduce the behavior:
Robot Main.vi
Robot Main.vi
will show that it is running for half a second and then LV will have a pop up saying it lost connection with the target, stopping the program.Expected behavior
Robot Main.vi
should continue running and the target should not disconnectScreenshots
Popup
Desktop (please complete the following information if applicable):
roboRIO
FRC_roboRIO_2025_v1.1
Additional context
I talked with Greg, and we found that a work around for this right now is to run
WPI_DriverStationStart Communication.vi
(found inRobot Main.vi
) first and that will initialize communication correctly, and you should be able to runRobot Main.vi
fine after that. This will need to be repeated when the RIO is power cycled.This is the VI:
The text was updated successfully, but these errors were encountered: