2013-12-15 18:30:16 -05:00
|
|
|
/*----------------------------------------------------------------------------*/
|
2015-06-25 15:07:55 -04:00
|
|
|
/* Copyright (c) FIRST 2008. All Rights Reserved.
|
|
|
|
|
*/
|
2013-12-15 18:30:16 -05:00
|
|
|
/* Open Source Software - may be modified and shared by FRC teams. The code */
|
|
|
|
|
/* must be accompanied by the FIRST BSD license file in $(WIND_BASE)/WPILib. */
|
|
|
|
|
/*----------------------------------------------------------------------------*/
|
|
|
|
|
|
|
|
|
|
#include "IterativeRobot.h"
|
|
|
|
|
|
|
|
|
|
#include "DriverStation.h"
|
2014-05-02 17:54:01 -04:00
|
|
|
#include "HAL/HAL.hpp"
|
2013-12-15 18:30:16 -05:00
|
|
|
#include "SmartDashboard/SmartDashboard.h"
|
|
|
|
|
#include "LiveWindow/LiveWindow.h"
|
|
|
|
|
#include "networktables/NetworkTable.h"
|
|
|
|
|
|
|
|
|
|
constexpr double IterativeRobot::kDefaultPeriod;
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Provide an alternate "main loop" via StartCompetition().
|
2015-06-25 15:07:55 -04:00
|
|
|
*
|
|
|
|
|
* This specific StartCompetition() implements "main loop" behaviour synced with
|
|
|
|
|
* the DS packets
|
2013-12-15 18:30:16 -05:00
|
|
|
*/
|
2015-06-25 15:07:55 -04:00
|
|
|
void IterativeRobot::StartCompetition() {
|
|
|
|
|
HALReport(HALUsageReporting::kResourceType_Framework,
|
|
|
|
|
HALUsageReporting::kFramework_Iterative);
|
|
|
|
|
|
Revert changes preventing old user code from compiling.
I'm not 100% sure whether we want these, but they are a quick
find and replace to do.
Basically, there are two primary things that we have done
this summer that break existing user code:
-Changing GetInstance() calls to return references instead
of pointers. This forces users to change from doing something
like LiveWindow::GetInstance()->AddSensor() to LiveWindow::GetInstance().AddSensor().
-Making PIDGet() and related calls const, forcing users to change
the function signatures wherever they override them.
The GetInstance() calls don't really matter to me either way,
especially since there are no real ownership issues going on there,
unlike the rest of the smart pointer-related changes.
For the const stuff, it is certainly more correct to mandate that
user PIDGet() functions be const and the such, but at the same time,
I'm not sure that there is any strong need for it, and the errors
generated are not the most helpful. While this wouldn't necessarily
be an issue for more experienced teams or completely new teams (who
don't have any old code to be reusing), it may cause issues for more
average teams who aren't familiar with the intricacies of C++ anything.
Change-Id: I6e7007982069292ea70e6d0fc8ca40203340df1b
2015-07-24 19:19:40 -04:00
|
|
|
LiveWindow *lw = LiveWindow::GetInstance();
|
2015-06-25 15:07:55 -04:00
|
|
|
// first and one-time initialization
|
|
|
|
|
SmartDashboard::init();
|
|
|
|
|
NetworkTable::GetTable("LiveWindow")
|
|
|
|
|
->GetSubTable("~STATUS~")
|
|
|
|
|
->PutBoolean("LW Enabled", false);
|
|
|
|
|
RobotInit();
|
|
|
|
|
|
2015-10-20 11:12:02 -07:00
|
|
|
// Tell the DS that the robot is ready to be enabled
|
2015-06-25 15:07:55 -04:00
|
|
|
HALNetworkCommunicationObserveUserProgramStarting();
|
|
|
|
|
|
|
|
|
|
// loop forever, calling the appropriate mode-dependent function
|
Revert changes preventing old user code from compiling.
I'm not 100% sure whether we want these, but they are a quick
find and replace to do.
Basically, there are two primary things that we have done
this summer that break existing user code:
-Changing GetInstance() calls to return references instead
of pointers. This forces users to change from doing something
like LiveWindow::GetInstance()->AddSensor() to LiveWindow::GetInstance().AddSensor().
-Making PIDGet() and related calls const, forcing users to change
the function signatures wherever they override them.
The GetInstance() calls don't really matter to me either way,
especially since there are no real ownership issues going on there,
unlike the rest of the smart pointer-related changes.
For the const stuff, it is certainly more correct to mandate that
user PIDGet() functions be const and the such, but at the same time,
I'm not sure that there is any strong need for it, and the errors
generated are not the most helpful. While this wouldn't necessarily
be an issue for more experienced teams or completely new teams (who
don't have any old code to be reusing), it may cause issues for more
average teams who aren't familiar with the intricacies of C++ anything.
Change-Id: I6e7007982069292ea70e6d0fc8ca40203340df1b
2015-07-24 19:19:40 -04:00
|
|
|
lw->SetEnabled(false);
|
2015-06-25 15:07:55 -04:00
|
|
|
while (true) {
|
|
|
|
|
// Call the appropriate function depending upon the current robot mode
|
|
|
|
|
if (IsDisabled()) {
|
|
|
|
|
// call DisabledInit() if we are now just entering disabled mode from
|
|
|
|
|
// either a different mode or from power-on
|
|
|
|
|
if (!m_disabledInitialized) {
|
Revert changes preventing old user code from compiling.
I'm not 100% sure whether we want these, but they are a quick
find and replace to do.
Basically, there are two primary things that we have done
this summer that break existing user code:
-Changing GetInstance() calls to return references instead
of pointers. This forces users to change from doing something
like LiveWindow::GetInstance()->AddSensor() to LiveWindow::GetInstance().AddSensor().
-Making PIDGet() and related calls const, forcing users to change
the function signatures wherever they override them.
The GetInstance() calls don't really matter to me either way,
especially since there are no real ownership issues going on there,
unlike the rest of the smart pointer-related changes.
For the const stuff, it is certainly more correct to mandate that
user PIDGet() functions be const and the such, but at the same time,
I'm not sure that there is any strong need for it, and the errors
generated are not the most helpful. While this wouldn't necessarily
be an issue for more experienced teams or completely new teams (who
don't have any old code to be reusing), it may cause issues for more
average teams who aren't familiar with the intricacies of C++ anything.
Change-Id: I6e7007982069292ea70e6d0fc8ca40203340df1b
2015-07-24 19:19:40 -04:00
|
|
|
lw->SetEnabled(false);
|
2015-06-25 15:07:55 -04:00
|
|
|
DisabledInit();
|
|
|
|
|
m_disabledInitialized = true;
|
|
|
|
|
// reset the initialization flags for the other modes
|
|
|
|
|
m_autonomousInitialized = false;
|
|
|
|
|
m_teleopInitialized = false;
|
|
|
|
|
m_testInitialized = false;
|
|
|
|
|
}
|
|
|
|
|
HALNetworkCommunicationObserveUserProgramDisabled();
|
|
|
|
|
DisabledPeriodic();
|
|
|
|
|
} else if (IsAutonomous()) {
|
|
|
|
|
// call AutonomousInit() if we are now just entering autonomous mode from
|
|
|
|
|
// either a different mode or from power-on
|
|
|
|
|
if (!m_autonomousInitialized) {
|
Revert changes preventing old user code from compiling.
I'm not 100% sure whether we want these, but they are a quick
find and replace to do.
Basically, there are two primary things that we have done
this summer that break existing user code:
-Changing GetInstance() calls to return references instead
of pointers. This forces users to change from doing something
like LiveWindow::GetInstance()->AddSensor() to LiveWindow::GetInstance().AddSensor().
-Making PIDGet() and related calls const, forcing users to change
the function signatures wherever they override them.
The GetInstance() calls don't really matter to me either way,
especially since there are no real ownership issues going on there,
unlike the rest of the smart pointer-related changes.
For the const stuff, it is certainly more correct to mandate that
user PIDGet() functions be const and the such, but at the same time,
I'm not sure that there is any strong need for it, and the errors
generated are not the most helpful. While this wouldn't necessarily
be an issue for more experienced teams or completely new teams (who
don't have any old code to be reusing), it may cause issues for more
average teams who aren't familiar with the intricacies of C++ anything.
Change-Id: I6e7007982069292ea70e6d0fc8ca40203340df1b
2015-07-24 19:19:40 -04:00
|
|
|
lw->SetEnabled(false);
|
2015-06-25 15:07:55 -04:00
|
|
|
AutonomousInit();
|
|
|
|
|
m_autonomousInitialized = true;
|
|
|
|
|
// reset the initialization flags for the other modes
|
|
|
|
|
m_disabledInitialized = false;
|
|
|
|
|
m_teleopInitialized = false;
|
|
|
|
|
m_testInitialized = false;
|
|
|
|
|
}
|
|
|
|
|
HALNetworkCommunicationObserveUserProgramAutonomous();
|
|
|
|
|
AutonomousPeriodic();
|
|
|
|
|
} else if (IsTest()) {
|
|
|
|
|
// call TestInit() if we are now just entering test mode from
|
|
|
|
|
// either a different mode or from power-on
|
|
|
|
|
if (!m_testInitialized) {
|
Revert changes preventing old user code from compiling.
I'm not 100% sure whether we want these, but they are a quick
find and replace to do.
Basically, there are two primary things that we have done
this summer that break existing user code:
-Changing GetInstance() calls to return references instead
of pointers. This forces users to change from doing something
like LiveWindow::GetInstance()->AddSensor() to LiveWindow::GetInstance().AddSensor().
-Making PIDGet() and related calls const, forcing users to change
the function signatures wherever they override them.
The GetInstance() calls don't really matter to me either way,
especially since there are no real ownership issues going on there,
unlike the rest of the smart pointer-related changes.
For the const stuff, it is certainly more correct to mandate that
user PIDGet() functions be const and the such, but at the same time,
I'm not sure that there is any strong need for it, and the errors
generated are not the most helpful. While this wouldn't necessarily
be an issue for more experienced teams or completely new teams (who
don't have any old code to be reusing), it may cause issues for more
average teams who aren't familiar with the intricacies of C++ anything.
Change-Id: I6e7007982069292ea70e6d0fc8ca40203340df1b
2015-07-24 19:19:40 -04:00
|
|
|
lw->SetEnabled(true);
|
2015-06-25 15:07:55 -04:00
|
|
|
TestInit();
|
|
|
|
|
m_testInitialized = true;
|
|
|
|
|
// reset the initialization flags for the other modes
|
|
|
|
|
m_disabledInitialized = false;
|
|
|
|
|
m_autonomousInitialized = false;
|
|
|
|
|
m_teleopInitialized = false;
|
|
|
|
|
}
|
|
|
|
|
HALNetworkCommunicationObserveUserProgramTest();
|
|
|
|
|
TestPeriodic();
|
|
|
|
|
} else {
|
|
|
|
|
// call TeleopInit() if we are now just entering teleop mode from
|
|
|
|
|
// either a different mode or from power-on
|
|
|
|
|
if (!m_teleopInitialized) {
|
Revert changes preventing old user code from compiling.
I'm not 100% sure whether we want these, but they are a quick
find and replace to do.
Basically, there are two primary things that we have done
this summer that break existing user code:
-Changing GetInstance() calls to return references instead
of pointers. This forces users to change from doing something
like LiveWindow::GetInstance()->AddSensor() to LiveWindow::GetInstance().AddSensor().
-Making PIDGet() and related calls const, forcing users to change
the function signatures wherever they override them.
The GetInstance() calls don't really matter to me either way,
especially since there are no real ownership issues going on there,
unlike the rest of the smart pointer-related changes.
For the const stuff, it is certainly more correct to mandate that
user PIDGet() functions be const and the such, but at the same time,
I'm not sure that there is any strong need for it, and the errors
generated are not the most helpful. While this wouldn't necessarily
be an issue for more experienced teams or completely new teams (who
don't have any old code to be reusing), it may cause issues for more
average teams who aren't familiar with the intricacies of C++ anything.
Change-Id: I6e7007982069292ea70e6d0fc8ca40203340df1b
2015-07-24 19:19:40 -04:00
|
|
|
lw->SetEnabled(false);
|
2015-06-25 15:07:55 -04:00
|
|
|
TeleopInit();
|
|
|
|
|
m_teleopInitialized = true;
|
|
|
|
|
// reset the initialization flags for the other modes
|
|
|
|
|
m_disabledInitialized = false;
|
|
|
|
|
m_autonomousInitialized = false;
|
|
|
|
|
m_testInitialized = false;
|
Revert changes preventing old user code from compiling.
I'm not 100% sure whether we want these, but they are a quick
find and replace to do.
Basically, there are two primary things that we have done
this summer that break existing user code:
-Changing GetInstance() calls to return references instead
of pointers. This forces users to change from doing something
like LiveWindow::GetInstance()->AddSensor() to LiveWindow::GetInstance().AddSensor().
-Making PIDGet() and related calls const, forcing users to change
the function signatures wherever they override them.
The GetInstance() calls don't really matter to me either way,
especially since there are no real ownership issues going on there,
unlike the rest of the smart pointer-related changes.
For the const stuff, it is certainly more correct to mandate that
user PIDGet() functions be const and the such, but at the same time,
I'm not sure that there is any strong need for it, and the errors
generated are not the most helpful. While this wouldn't necessarily
be an issue for more experienced teams or completely new teams (who
don't have any old code to be reusing), it may cause issues for more
average teams who aren't familiar with the intricacies of C++ anything.
Change-Id: I6e7007982069292ea70e6d0fc8ca40203340df1b
2015-07-24 19:19:40 -04:00
|
|
|
Scheduler::GetInstance()->SetEnabled(true);
|
2015-06-25 15:07:55 -04:00
|
|
|
}
|
|
|
|
|
HALNetworkCommunicationObserveUserProgramTeleop();
|
|
|
|
|
TeleopPeriodic();
|
|
|
|
|
}
|
|
|
|
|
// wait for driver station data so the loop doesn't hog the CPU
|
artf4154: Get rid of raw pointers in C++.
This deals with the majority of the user-facing code
in wpilibC++Devices and a substantial portion of it in
wpilibC++. wpilibC++Sim and wpilibC++IntegrationTests
are untouched except where it is necessary to make them
work with the rest of the libraries.
There is still a lot to do in the following areas:
-The HAL (which we may not want to touch at all).
-The I2C, Serial, and SPI interfaces in wpilibC++Devices,
which I haven't gotten around to doing yet.
-Most wpilibC++Devices classes have void* pointers
for interacting with the HAL.
-InterruptableSensorBase passes a void *params for
the interrupt handler.
-I haven't converted all the const char* to std::strings.
-There are plenty of other cases of raw pointers still
existing.
-This doesn't fall directly under raw pointer stuff,
but move syntax and rvalue references could be introduced
in many places.
-I haven't touched vision code.
-The Resource classes conflict (one is in the hal, the other
in wpilibC++). Someone should figure out a more
permanent fix (eg, just renaming them), then doing
what I did (making a new namespace for one of them,
essentially the same as renaming it).
A few other things:
-I created a NullDeleter class which is marked as deprecated.
What this does is it can be passed as the deleter to a
std::shared_ptr so that when you are converting raw pointers
to shared_ptrs the shared_ptr doesn't do any deletion if
someone else owns the raw pointer. This should only be
used in making old raw pointer UIs.
-I had to alter the build.gradle so that it did not
emit errors when deprecated functions called deprecated
functions. Unfortunately, gradle doesn't appear to be
actually printing out gcc warnigns for some reason.
The best way I have found to fix this is to patch
the toolchains (https://bitbucket.org/byteit101/toolchain-builder/pull-request/5/make-gcc-not-throw-warnings-for-nested/diff)
so that a deprecated function calling a deprecated
function is fine but a non-deprecated function calling
a deprecated function will throw a warning (which we
then elevate with -Werror). I believe that clang
deals with this properly, although I have not
tried it myself.
Change-Id: Ib8090c66893576fe73654f4e9d268f9d37be06a2
2015-06-30 15:01:20 -04:00
|
|
|
m_ds.WaitForData();
|
2015-06-25 15:07:55 -04:00
|
|
|
}
|
2013-12-15 18:30:16 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Robot-wide initialization code should go here.
|
2015-06-25 15:07:55 -04:00
|
|
|
*
|
|
|
|
|
* Users should override this method for default Robot-wide initialization which
|
2015-10-20 11:12:02 -07:00
|
|
|
* will be called when the robot is first powered on. It will be called exactly
|
|
|
|
|
* one time.
|
|
|
|
|
*
|
|
|
|
|
* Warning: the Driver Station "Robot Code" light and FMS "Robot Ready"
|
|
|
|
|
* indicators will be off until RobotInit() exits. Code in RobotInit() that
|
|
|
|
|
* waits for enable will cause the robot to never indicate that the code is
|
|
|
|
|
* ready, causing the robot to be bypassed in a match.
|
2013-12-15 18:30:16 -05:00
|
|
|
*/
|
2015-06-25 15:07:55 -04:00
|
|
|
void IterativeRobot::RobotInit() {
|
|
|
|
|
printf("Default %s() method... Overload me!\n", __FUNCTION__);
|
2013-12-15 18:30:16 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Initialization code for disabled mode should go here.
|
2015-06-25 15:07:55 -04:00
|
|
|
*
|
|
|
|
|
* Users should override this method for initialization code which will be
|
|
|
|
|
* called each time
|
2013-12-15 18:30:16 -05:00
|
|
|
* the robot enters disabled mode.
|
|
|
|
|
*/
|
2015-06-25 15:07:55 -04:00
|
|
|
void IterativeRobot::DisabledInit() {
|
|
|
|
|
printf("Default %s() method... Overload me!\n", __FUNCTION__);
|
2013-12-15 18:30:16 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Initialization code for autonomous mode should go here.
|
2015-06-25 15:07:55 -04:00
|
|
|
*
|
|
|
|
|
* Users should override this method for initialization code which will be
|
|
|
|
|
* called each time
|
2013-12-15 18:30:16 -05:00
|
|
|
* the robot enters autonomous mode.
|
|
|
|
|
*/
|
2015-06-25 15:07:55 -04:00
|
|
|
void IterativeRobot::AutonomousInit() {
|
|
|
|
|
printf("Default %s() method... Overload me!\n", __FUNCTION__);
|
2013-12-15 18:30:16 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Initialization code for teleop mode should go here.
|
2015-06-25 15:07:55 -04:00
|
|
|
*
|
|
|
|
|
* Users should override this method for initialization code which will be
|
|
|
|
|
* called each time
|
2013-12-15 18:30:16 -05:00
|
|
|
* the robot enters teleop mode.
|
|
|
|
|
*/
|
2015-06-25 15:07:55 -04:00
|
|
|
void IterativeRobot::TeleopInit() {
|
|
|
|
|
printf("Default %s() method... Overload me!\n", __FUNCTION__);
|
2013-12-15 18:30:16 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Initialization code for test mode should go here.
|
2015-06-25 15:07:55 -04:00
|
|
|
*
|
|
|
|
|
* Users should override this method for initialization code which will be
|
|
|
|
|
* called each time
|
2013-12-15 18:30:16 -05:00
|
|
|
* the robot enters test mode.
|
|
|
|
|
*/
|
2015-06-25 15:07:55 -04:00
|
|
|
void IterativeRobot::TestInit() {
|
|
|
|
|
printf("Default %s() method... Overload me!\n", __FUNCTION__);
|
2013-12-15 18:30:16 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Periodic code for disabled mode should go here.
|
2015-06-25 15:07:55 -04:00
|
|
|
*
|
|
|
|
|
* Users should override this method for code which will be called periodically
|
|
|
|
|
* at a regular
|
2013-12-15 18:30:16 -05:00
|
|
|
* rate while the robot is in disabled mode.
|
|
|
|
|
*/
|
2015-06-25 15:07:55 -04:00
|
|
|
void IterativeRobot::DisabledPeriodic() {
|
|
|
|
|
static bool firstRun = true;
|
|
|
|
|
if (firstRun) {
|
|
|
|
|
printf("Default %s() method... Overload me!\n", __FUNCTION__);
|
|
|
|
|
firstRun = false;
|
|
|
|
|
}
|
|
|
|
|
delayTicks(1);
|
2013-12-15 18:30:16 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Periodic code for autonomous mode should go here.
|
|
|
|
|
*
|
2015-06-25 15:07:55 -04:00
|
|
|
* Users should override this method for code which will be called periodically
|
|
|
|
|
* at a regular
|
2013-12-15 18:30:16 -05:00
|
|
|
* rate while the robot is in autonomous mode.
|
|
|
|
|
*/
|
2015-06-25 15:07:55 -04:00
|
|
|
void IterativeRobot::AutonomousPeriodic() {
|
|
|
|
|
static bool firstRun = true;
|
|
|
|
|
if (firstRun) {
|
|
|
|
|
printf("Default %s() method... Overload me!\n", __FUNCTION__);
|
|
|
|
|
firstRun = false;
|
|
|
|
|
}
|
|
|
|
|
delayTicks(1);
|
2013-12-15 18:30:16 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Periodic code for teleop mode should go here.
|
|
|
|
|
*
|
2015-06-25 15:07:55 -04:00
|
|
|
* Users should override this method for code which will be called periodically
|
|
|
|
|
* at a regular
|
2013-12-15 18:30:16 -05:00
|
|
|
* rate while the robot is in teleop mode.
|
|
|
|
|
*/
|
2015-06-25 15:07:55 -04:00
|
|
|
void IterativeRobot::TeleopPeriodic() {
|
|
|
|
|
static bool firstRun = true;
|
|
|
|
|
if (firstRun) {
|
|
|
|
|
printf("Default %s() method... Overload me!\n", __FUNCTION__);
|
|
|
|
|
firstRun = false;
|
|
|
|
|
}
|
|
|
|
|
delayTicks(1);
|
2013-12-15 18:30:16 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
* Periodic code for test mode should go here.
|
|
|
|
|
*
|
2015-06-25 15:07:55 -04:00
|
|
|
* Users should override this method for code which will be called periodically
|
|
|
|
|
* at a regular
|
2013-12-15 18:30:16 -05:00
|
|
|
* rate while the robot is in test mode.
|
|
|
|
|
*/
|
2015-06-25 15:07:55 -04:00
|
|
|
void IterativeRobot::TestPeriodic() {
|
|
|
|
|
static bool firstRun = true;
|
|
|
|
|
if (firstRun) {
|
|
|
|
|
printf("Default %s() method... Overload me!\n", __FUNCTION__);
|
|
|
|
|
firstRun = false;
|
|
|
|
|
}
|
|
|
|
|
delayTicks(1);
|
2013-12-15 18:30:16 -05:00
|
|
|
}
|