|Tekkotsu Homepage||Demos||Overview||Downloads||Dev. Resources||Reference||Credits|
RobotInfo Namespace Reference
Contains information about the robot, such as number of joints, PID defaults, timing information, etc. More...
Contains information about the robot, such as number of joints, PID defaults, timing information, etc.
This is just a wrapper for whichever namespace corresponds to the current robot target setting (one of TGT_ERS7, TGT_ERS210, TGT_ERS220, or the cross-booting TGT_ERS2xx)
You probably should look at ERS7Info, ERS210Info, ERS220Info, or ERS2xxInfo for the actual constants used for each model, although some common information shared by all of these namespaces is defined in CommonInfo.h
Enumeration Type Documentation
This function should return the actual RobotInfo::TargetName and not a hard coded string. This way, we can rely on testing equality with a direct pointer comparison instead of strcmp(). (Also eliminates chance of typo or missing refactorization if renamed!).
The result of this function is stored in RobotName, so you don't need to call this function -- the only reason it's declared in the header is so you can call it during static initialization, when you can't rely on RobotName having been initialized yet.
Use this if you have a robot name in string form and want to check or map its capabilities. (For example, if you are communicating with another robot of a different type over the network.) If you know at compile time the type of the robot in question, you could just directly access its 'capabilities' instance via its RobotInfo namespace. (e.g. ERS210Info::capabilities) If you want the capabilities for the current robot, just use the global 'capabilities' instance as RobotInfo.h will automatically import the current robot's namespace into the global space.
The camera correction homography to utilize.
Initialized from file by StartupBehavior::doStart(), using CameraName to indicate file name.
Name of the robot which is actually running.
This is usually set to the TargetName, but if the target model is a "compatability" target, where the actual host hardware may be a different (more restrictive) configuration, then RobotName will be set to the TargetName of that configuration.
Note that you should be able to rely on doing pointer comparisons between RobotName and various TargetNames to test for different robot models, instead of using strcmp() for each.
However, a std::string is used on Aperios to transparently trigger the strcmp because of the way the process model is handled there screws up the pointer comparison (a different process does the static initialization, so we get a pointer relative to its memory space instead of the one we're executing in. Unix-based platforms don't have this problem by using a "real" fork() operation.)
Referenced by ConfigDictionary::ConfigDictionary(), LedEngine::displayNumber(), WorldStateSerializerBehavior::doEvent(), VisualTargetCloseTrans::doEvent(), WorldStateSerializerBehavior::doStart(), EmergencyStopMC::EmergencyStopMC(), EmergencyStopMC::freezeJoints(), PostureEngine::getBinSize(), Controller::init(), PostureEngine::loadLine(), PostureEngine::saveBuffer(), BatteryMonitorBehavior::setFlipper(), LedEngine::setOneOfTwo(), FlashIPAddrBehavior::setupSequence(), EmergencyStopMC::trigger(), and TailWagMC::updateOutputs().
||Generated Sat May 4 06:33:32 2013 by Doxygen 1.6.3|