Tekkotsu Homepage | Demos | Overview | Downloads | Dev. Resources | Reference | Credits |
KobukiDriver Class Reference
Inheritance diagram for KobukiDriver:
Detailed DescriptionDefinition at line 157 of file KobukiDriver.h.
Constructor & Destructor Documentation
Definition at line 159 of file KobukiDriver.h.
Definition at line 167 of file KobukiDriver.h. Member Function Documentation
Called when the simulator is stepping while paused or advancing a frozen data source, return true if successful, or false if no more data is available. Implements DataSource.
User hook, called when the data source should release its claim on outputs with feedback (ignoringOuput()). It would be wise to call this from your destructor as well. Reimplemented from DataSource.
user hook for when frozen is set to true; advance() will be called by simulator at user discretion. Reimplemented from DataSource.
user hook for when frozen is set to false; if enteringRealtime() has been called then you should resume sending data. Reimplemented from DataSource.
User hook, called when the controller is going to be running in realtime mode, which is probably the normal mode you'd expect. You might be in realtime mode, but a debugger breakpoint will still pause things, or thread scheduling could hiccup, so try to be robust. Reimplemented from DataSource. Definition at line 192 of file KobukiDriver.h.
Returns the name of the class (aka its type). Suggested implementation is to declare a static string member, set it to the result of calling the registry's registerType, and then return that member here Implements DeviceDriver. Definition at line 169 of file KobukiDriver.h.
Reimplemented from DeviceDriver. Definition at line 171 of file KobukiDriver.h.
Reimplemented from DeviceDriver. Definition at line 173 of file KobukiDriver.h.
Should return true if the MotionHook is successfully connected to physical hardware. If relevant, this will only be called after motionStarting() has been called in order to initialize a connection. This is used mainly to cancel out of the WaitForSensors if all MotionHooks return false. If you are still in the process of connecting or unsure of status, be optimistic and return true. This function will be polled at a coarse rate while blocked on sensors in case of timeouts on the part of the MotionHook render it moot. Implements MotionHook.
User hook, called when leaving realtime mode, which means you have no idea when motionCheck() is going to be called in terms of wall-clock time. Argument set to true if entering full speed mode, which indicates everything should run at full native "frame rate", and may indicate more data will be processed than normal, CPU speed permitting. However, if false, almost certainly indicates updates will be sparse, trigger by user 'step' commands. May be called multiple times if changing between full-speed mode and paused A non-realtime mode might be triggered if the user wants to pause the simulator/controller to step through something... No guarantees though! The debugger might catch a breakpoint and stop things, and this won't be called! Reimplemented from DataSource. Definition at line 193 of file KobukiDriver.h.
Called each time the motion process has polled active motion commands. When in realtime mode, this should be called every FrameTime*NumFrames (defined in the RobotInfo) milliseconds if running at full speed. See enteringRealtime() and leavingRealtime(). This default implementation checks to see which outputs have changed value since the last call and passes the summary on to motionUpdated(). lastOutputs will be updated with the new values after the call to motionUpdated(). If you need to process all the outputs on every frame, you only need to override this function. Your subclass doesn't need to call the MotionHook implementation unless you want to have lastOutputs updated for you. If you only need to process the changed outputs for each frame, override motionUpdated() instead. motionUpdated() is always called for each update, even if there aren't any changes, so you can still use that if there are some outputs which need to be updated every cycle. Reimplemented from MotionHook.
Called when motion process is starting. Reimplemented from MotionHook.
Called when motion process is stopping. Reimplemented from MotionHook.
Returns a descriptive name of the next data segment for user feedback (e.g. a filename for logged data). Just use your class name if you don't have a useful name for individual samples. Implements DataSource. Definition at line 184 of file KobukiDriver.h.
Returns the simulator time of the next data segment. Should be in the future if nothing new since last data segment, otherwise should be the timestamp of the most recent data segment (older segments are skipped), return -1U if there is no more data Implements DataSource.
Implements PrimitiveListener.
User hook, called when the data source should claim which outputs it provides feedback (providingOuput()). Does not indicate the data source should start sending updates yet — wait for enteringRealtime() or advance() to be called Reimplemented from DataSource.
Member Data Documentation
holds the class name, set via registration with the DeviceDriver registry Definition at line 219 of file KobukiDriver.h. Referenced by getClassName().
Definition at line 197 of file KobukiDriver.h. Referenced by KobukiDriver().
Definition at line 214 of file KobukiDriver.h.
Definition at line 216 of file KobukiDriver.h.
Definition at line 223 of file KobukiDriver.h.
used to track partial LED activation (see calcLEDValue()) Definition at line 208 of file KobukiDriver.h.
Definition at line 212 of file KobukiDriver.h.
Definition at line 221 of file KobukiDriver.h.
Definition at line 210 of file KobukiDriver.h.
Definition at line 224 of file KobukiDriver.h.
Definition at line 213 of file KobukiDriver.h. The documentation for this class was generated from the following file: |
Tekkotsu Hardware Abstraction Layer 5.1CVS |
Generated Mon May 9 05:01:41 2016 by Doxygen 1.6.3 |