Labview Roborio Deploy or Run Live Issues with CTRE Phoenix and 4.0 image?

Technical NI LabVIEW
1

Anyone else having lots of problems deploying LabVIEW with CTRE or Phoenix?

We are running mixed hardware as we normally do, we have REV SPARKS and CTRE Talons SRX and now trying a couple of Falcon 500 motors.

The issue we have is once deployed, none of the CTRE devices will work when the robot is enabled. Everything else runs find on the robot with a Roborio, we just formatted to version 4.0 as well.

We get alot of failed deployed, errors, etc…the only way to get a good Deploy is to DISABLE the RT Startup, reboot the rio, then deploy, the enable RT startup, then reboot the rio.

Then almost always, NONE of the CTRE devices work when enabled, all the Talons, Falcon 500 blink Yellow when the robot is enabled. To correct this behavior, we have to run Phoenix Installer again on the RIO. Most of the time, it says Target not found, so then we have to DISABLE the RT, reboot, installed the Phoenix Installer, reboot, enable RT startup, reboot…then about 50% of the time, we get drop outs on the CTRE devices…we then re deploy our code again, and then finally everything works as it should.

It’s absolutely laboring to get your code to deploy to an older RoboRio with Image 4.0 installed now…is anyone else having these problems? We are about ready to remove the Talons and switch them to SPARKS just so we don’t have to deal with the CTRE issues we seemed to be having.

1 Like
2

@Gilad can you share with Chris what issues we had with the latest version, and how we handle it?

3

Yes, our team also has had and still have the problem that the motors dont move when we deploy code sometimes.
Our fixes are to chain all the open blocks and add a high timeout to all the motor settings we use 350 on the timeout.

4

Could you post a screen shot of:

How you chain the Open Statements?
Where are you putting a 350 msec timeout?

5

Force all CTRE device Opens (even of different types) to be sequential: https://www.chiefdelphi.com/uploads/default/original/3X/b/b/bb363797b1bf82a81425cb11700805f9ad6c7829.png

6

Did you updated to Phoenix v5.21.1.0? It was supposed to fix the issue that required chaining the Open VIs.

7

Re: Joe
The latest Phoenix software release: https://github.com/CrossTheRoadElec/Phoenix-Releases/releases

Relevant prior discussion of Chris’s problem: https://www.chiefdelphi.com/t/trouble-deploying-simple-talon-srx-and-spark-max-code

8

We did NOT notice Phoenix had a new release of 5.21, we will install that, build code, and try again tonight.

After installing the new update from Phoenix, will it replace all the VIs in our current code or do we need to replace each VI manually?

9

Your current code pulls those vi’s directly from the shared library when you build, so updating the library will pull in the changes the next time you build.

You can see where everything comes from by looking at the Files tab on the project manager window. It shows a tree of where all your project files are coming from.

10

In the library listing for the project:

It shows version “196” for the CTRE Talon SRX OPEN.VI. Is there a listing of VI versions published somewhere to make sure? The history tab is blank for this VI.

11

I don’t know of any third party version tracking on an individual vi basis, nor do they appear to use the revision history section. Neither does WPILib.
My current version for the Talon SRX Open is also “196”

Of course, I don’t use it on my own vi’s either…

1 Like
12

Thanks for all the guidance on this one Mark! Version 196 it is then…

13

Just an FYI… I think this is started when we download the Inspection Sheet for 2022, notice that our RoboRio needed to have version 4.0 installed. We upgraded from 3.0 to 4.0 WITHOUT updating Phoenix to 5.21. I believe that’s when problems started. We switched to another RoboRio with version 3.0 still installed, and was able to get it to work “sometimes” but not all the time after that. Hoping for good results moving forward. Hope this thread helps people.

14

Can you share if the issue is gone? If so, updating the Phoenix version was enough or you also needed to chain the opens (or any other solution)?

15

We updated to Rio Image 4.0 and updated Phoenix, the problem seemed to go away after this. We did leave Mark’s chained Opens in the code as well. No more download problems, or disabled Phoenix motors after that. However, we decided to replace the Falcon 500 with NEOs because we aren’t able to purchase any spare motors online and we only had two for the whole season… so now we don’t have them anymore. The decision was based on a supply issue to not use them anymore after waiting and waiting for stock online at VexRobotics. We are all REV Robotics now on the robot and have spares on hand.

1 Like
16

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.