Roborio 2 and labview

[ahudson]

We are still struggling with using the Roborio2 with labview. Everytime we download our program to the Roborio 2, it crashes on our laptop. We were part of a discussion in a previous thread about this issue, but I had not seen a resolution to the problem.

[Elkbits]

first the list of dumb questions:

1. have you installed all the updated drivers? this includes the NI fix to install the CRIO drivers?
2. have you installed the newest FRC game tools and flashed the newest firmware to the SIM from March 3rd?
3. if you are using CTRE components, have you used the Phoenix Tuner to load the recent CTRE drivers onto the RoboRIO?

[ahudson]

2. We have not done anything since mid-February with it. (we went back to using the old Roborio). I was not with them last night so I can not guarantee anything they did/did not do. I will have them start there tonight.
3. No CTRE components.

[mshafer1]

When you say “it crashes on our laptop”, you’re saying LabVIEW crashes mid deploy?

[ahudson]

By crashing/destroying/breaking (you ask different people and you get different adjectives) they mean after they deploy the program to the Roborio, the laptop shows the program with a broken arrow and it gives a netcomm error.

[mshafer1]

Didn’t NI release a driver update to fix the broken run arrow showing up?

[Joe_Ross]

Are you saying that you tried all 3 of the solutions posted below and none solved the issue? If so, I’d recommend listing in that thread for better visibility.

Get a NetComm error opening a new default Labview robot code

Here’s an update with findings that I hope lets most of you move forward when you encounter this problem. First, we are fairly certain that the problem is related to how one of the drivers is being installed in the computers that show the behavior. Second, in the affected computers we were able to see that the difference between a “working” and “broken” Robot Main.vi (caused by the System Exec VI) relies on the type of target being used in the project. To be more specific, then the target is s…

[JSIMPSO]

Our team has a similar issue. We haven’t updated any of the drivers. (I think we were hoping that the fix would be part of the recent Game Tools update.) We created a small batch file that “corrects” the LVPROJ file. The two files are attached. Put these in the directory where your LVPROJ file is located. Run this when LabVIEW is closed, then re-open LabVIEW.

Fix_RoboRIO_Target.zip (806 Bytes)