Motors move only the second time we upload the code

Recently our team had a problem that on the first time we upload code to the robot the motors (falcon 500) doesn’t move although output is being set. when we upload the same code for the second time the robot runs just fine.

Our team works on LabVIEW and we want to know if it happened to someone and if you know how to solve it?

Does this happen EVERY time you come to the shop or just the ones?

If just the once, I’d guess you didn’t have the DLLs on the roboRIO. The CTRE DLLs required to operate the Falcons need to be loaded onto the roboRIO by pushing code. That’ll make the first time you send code fail to connect to the Falcons and then each subsequent push works fine.

If you’re seeing this problem frequently, it’s likely something else we’d want to take a look at.

I don’t know if this is related…

There was also an issue with the CTRE motor controllers that you had to open them sequentially by wiring the error out of one open into the error in of the next. Once we did this things worked better. I don’t know if this has been fixed with the new updated code release or if it is a problem with the falcon. It is easy to do though. There is another post someplace here that shows the example.

This was the post

Actually its very related and very helpful , i will try to use the error wire and update if i come across some other issues regarding this subject

Yes, it happen every time i upload my code after i turn on the robot.
Sometimes i upload the code without the motors begin and then upload it again with the begin and the code runs as i want it to.
I do have the CTRE DLLs.

What are the steps you use when you upload the code?
i.e.,

  • Use the Run button in Robot Main.vi?
    or
  • Build then Run as Startup from the project manager window?

We are using the Run button on Robot Main.vi
We have not tryed to build the code yet

CTRE is in the process of releasing a fix for the Falcon Talon FX (and others) Open problem.
The fix comes in Phoenix Framework v5.21.1 on the CTRE website Software page.
It has a Feb 4 date. (corrected)

https://store.ctr-electronics.com/software/

To clarify, it’s already been released (on Feb. 4th) - it’s just the blog post that went out today.

Thank you Jacon Mark and JSIMPOSO for your help.
I will update the Phoenix Framework and hopfelly it will resolve the problems.

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