Subject:
|
RE: Tacho Limit and Braking
|
Newsgroups:
|
lugnet.robotics.nxt
|
Date:
|
Mon, 2 Oct 2006 13:19:17 GMT
|
Reply-To:
|
<dickswan@sbcglobal.!StopSpammers!net>
|
Viewed:
|
11352 times
|
| |
|
|
If you want to try something a little different, use RobotC to do this.
There are several advantages to this:
* It can be done with one "setout" opcode.
* The RobotC PID algorithm for this type of movement is different
than the NXT-G implementation. This includes faster updates, a
different error term definition and different error factors. This
results in superior performance.
* It will smoothly slow down and brake precisely at target encoder
value. NXT-G and NBC will always overshoot and then correct.
* I like programming in C rather than assembler.
The RobotC code to move forward 90 encoder ticks is very simple -- it's
two lines of code.
nMotorEncoderTarget[motorA] = 90; // distance to move
motor[motorA] = 50; // start speed of movement
|
|
Message has 1 Reply:
 | | Re: Tacho Limit and Braking
|
| (...) This is incorrect. There is no "setout" opcode in RobotC. RobotC uses a proprietary commercial alternate firmware with a completely different set of opcodes and virtual machine functionality than the standard NXT firmware. Unfortunately, the (...) (18 years ago, 2-Oct-06, to lugnet.robotics.nxt)
|
Message is in Reply To:
| | Tacho Limit and Braking
|
| I started playing with NBC, and wanted to run the motor until it hits the tachometer limit, and then brake. I have been unable to make this happend with one setout opcode. Is it possible? Is it possible to make the opcode wait until the tacho limit (...) (18 years ago, 1-Oct-06, to lugnet.robotics.nxt)
|
6 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
