|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: CTRE Toolsuite with Command-Based C++
Your compiler output actually indicates that the build was successful. Important takeaway here: sometimes Eclipse gets it wrong. If it's giving you an error that doesn't make much sense, always check the console to verify that it's real and not just Eclipse being Eclipse.
The error showing up in the driver station log isn't directly related to the other problem you were having. The error says that MotorSafetyHelper is trying to check the FPGA time before the FPGA is initialized, which may be because you're calling CANTalon::SetSafetyEnabled() in the constructor for your subsystem. It may help to move that call to a later point in time, but I don't know how it works under the covers and I haven't seen the rest of your code, so I can't say for sure--maybe one of WPILib's maintainers could chime in on this. I don't think that should be blocking you, though; is your command running now? |
|
#2
|
|||
|
|||
|
Re: CTRE Toolsuite with Command-Based C++
No, that did not work unfortunately, I will see if maybe there is a way to either stop those functions from Timer and MotorSafetyControl to stop running before the initialize. But it doesn't make any sense because I'm not using timers at all.
|
|
#3
|
||||
|
||||
|
Re: CTRE Toolsuite with Command-Based C++
Quote:
I advise them to put those calls in the Init methods. By the time the Init()s are called, the hardware *must* be configured for our use. (Otherwise, what's the point?) If you give that a try, or if you find another solution, would you please let us know how it goes? Your experience will surely be helpful to other teams! |
|
#4
|
||||
|
||||
|
Re: CTRE Toolsuite with Command-Based C++
Quote:
|
|
#5
|
|||
|
|||
|
Re: CTRE Toolsuite with Command-Based C++
I have moved all the functions associated with the Configuration of the Talon not into the constuctor if the subsystem, but of the Initialize() of the Command. However, this has not seemed to change anything in terms of the errors we are receiving.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|