To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.nxtOpen lugnet.robotics.nxt in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / NXT / 157
156  |  158
Subject: 
Re: Tacho Limit and Braking
Newsgroups: 
lugnet.robotics.nxt
Date: 
Mon, 2 Oct 2006 16:59:34 GMT
Viewed: 
11491 times
  
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.  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.

* It will smoothly slow down and brake precisely at target encoder
  value. NXT-G and NBC will always overshoot and then correct.

This is also incorrect.  Using NBC you can control your motors however you wish,
including smoothly slowing down and braking precisely at the target encoder
value.

The RobotC code to move forward 90 encoder ticks is very simple -- it's
two lines of code.

In NBC it is one line of code:

Rotate(OUT_A, 45, 75); // motor port, angle, power

Hope this helps,

John Hansen



Message has 1 Reply:
  RE: Tacho Limit and Braking
 
(...) You can do just about anything with one line of code if you count user subroutine and user macro calls as "one line". The "Rotate" macro in your example expands to four lines of code that sets up and calls a user program subroutine that is (...) (18 years ago, 2-Oct-06, to lugnet.robotics.nxt)

Message is in Reply To:
  RE: Tacho Limit and Braking
 
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 (...) (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

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR