Changeset 700

Timestamp:

07/17/09 16:05:15 (4 years ago)

Author:

atorf

Message:

• Some more replacements and corrections for ActionAtTachoLimit?

Location:

branches/version-3.00/mfiles/@NXTMotor

Files:

• NXTMotor.m (modified) (2 diffs)
• SendToNXT.m (modified) (1 diff)

branches/version-3.00/mfiles/@NXTMotor/NXTMotor.m

@@ -48 +48 @@
 % Limitations 
 %   When driving with 2 motors (i.e. in sync-mode), a |TachoLimit = 0|
-%   (which means driving forever) and with |ActionAtTachoLimit = true|,
+%   (which means driving forever) and with |ActionAtTachoLimit = 'Brake'|,
 %   stopping the bot (either via the motor object's function |Stop| or via
 %   the command |StopMotor|) will always result in a "hard stop" (as if you had
 %   called |Stop('brake')|), even if the parameter of the stop-command was
-%   "off" (indicating a soft stop into coast mode). There is no workaround
-%   to this (apart from using the command with |ActionAtTachoLimit = false|,
+%   'off' (indicating a soft stop into coast mode). There is no workaround
+%   to this (apart from using the command with |ActionAtTachoLimit = 'Coast'|,
 %   in this case the stop-parameters "brake" or "off" will be interpreted
 %   as expected).
@@ -244 +244 @@
             else
                 error('MATLAB:RWTHMindstormsNXT:InvalidActionAtTachoLimit',...
-                    'ActionAtTachoLimit must be a boolean.');
+                    'ActionAtTachoLimit must be either ''Coast'' or ''Brake''.');
             end
         end

branches/version-3.00/mfiles/@NXTMotor/SendToNXT.m

@@ -18 +18 @@
 %
 % Limitations
-%
-%   This function has a built-in waiting-period. A pause of 75ms will be
-%   made both before and after sending the actual command to the NXT,
-%   resulting in a total execution time of about 150ms for this command.
 %
 %   If you send a command to the NXT without waiting for the previous motor