Subject:
|
Re: Tacho Limit and Braking
|
Newsgroups:
|
lugnet.robotics.nxt
|
Date:
|
Mon, 2 Oct 2006 18:25:14 GMT
|
Viewed:
|
11733 times
|
| |
| |
In lugnet.robotics.nxt, John Hansen wrote:
> The NXT firmware does not support a single operation which has the motor run to
> a specific tachometer limit and then brake.
This made sense, until I read this...
In lugnet.robotics.nxt, John Hansen wrote:
> In NBC it is one line of code:
>
> Rotate(OUT_A, 45, 75); // motor port, angle, power
I had to go back and re-read this to understand one is talking about the NXT
firmware, and the other is talking about NBC.
If I read it correctly, it means:
A) The "standard" NXT Firmware requires two op-codes ("setout opcodes"?) to
execute "move to limit, then break"
B) NBC has one command to send these two op-codes to the firmware
C) Robot C uses two lines to implement this functionality in it's own firmware
In lugnet.robotics.nxt, John Hansen wrote:
> In lugnet.robotics.nxt, <dickswan@sbcglobal.net> wrote:
> >
> > 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.
>
> This is incorrect. There is no "setout" opcode in RobotC.
Dick, I think you need to read up on the RobotC documentation, or something. :)
> 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 RobotC and Robolab 2.9 firmwares both masquerade as the
> standard NXT firmware which has caused a great deal of confusion among NXT users
> when they try to execute an NXT-G program and they get a file error message on
> the NXT.
This sounds like a real headache for LEGO. I never did understand why they made
a proprietary commercial alternate firmware with a completely different set of
opcodes and virtual machine functionality for RoboLab.
But, what do I know about marketing. I just build robots.
Steve
|
|
Message is in Reply To:
| | Re: Tacho Limit and Braking
|
| (...) The NXT firmware does not support a single operation which has the motor run to a specific tachometer limit and then brake. The only way to do what you would like to do involves several operations. But you can wrap it all up into a reusable (...) (18 years ago, 2-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
|
|
|
|